Merge remote-tracking branch 'origin/main'
This commit is contained in:
ledger committed
commit
4148849347
3 files changed
+633
No files matched your search
@@ -0,0 +1,411 @@
|
||||
# APPLY QUEUE — 2026-10-31 (for Timmy to queue, Alexander submits)
|
||||
|
||||
**Authority:** Alexander asked Zeph to send Timmy "everything I can apply for
|
||||
today" and have Timmy queue it for Alexander's own submission. Escalation path:
|
||||
Zeph → Timmy (pipe) → Alexander (Telegram); Zeph never relays decisions and
|
||||
raises nothing in chat. **Rules:** Timmy queues only — never submits, never
|
||||
creates accounts, never contacts anyone on Alexander's behalf. He carries the
|
||||
open questions below to Alexander DIRECTLY via Telegram. Materials are
|
||||
public-safe (professional name only; no email, phone, or private facts).
|
||||
Supersedes apply-queue-2026-10-30.md. Compiled by Zephyrus Sparkborn,
|
||||
2026-10-31. Liveness verified from a clean external network unless
|
||||
marked otherwise.
|
||||
|
||||
**Corrections folded into the body this tick (append-only history preserved in
|
||||
daily-2026-10-21.md's corrections section; reply-80 year fix logged 2026-10-22):** N5 Alignerr pay is **$60–80/hr
|
||||
on the page header** (my 10-20/10-21 "unstated" was wrong; third-party
|
||||
$60–120 range dropped); the six corroborated Turing doors now carry their
|
||||
**page-title labels** (reply-78 table), not feed labels — `HI7GzvKjPF` is
|
||||
"Senior Python Engineer – AI Agents Evaluation" (not "GenAI Security");
|
||||
`Xqiv8zPNaw` is the actual GenAI Security door.
|
||||
|
||||
## Pipeline tally
|
||||
**11 submitted / 2 interviews / 0 offers / 2 rejections.** The Alignerr
|
||||
item-29 Seattle variant is LIVE AGAIN (full page on two text fetches
|
||||
2026-10-31, after 404ing on two instruments 2026-10-30) — the role is two
|
||||
city variants again, and the closed count moves 5 → 4. Count CORRECTED:
|
||||
the 10-30 "33 live / Turing 15" line undercounted its own enumeration
|
||||
(Turing is 16, item 33 verified 10-29 but never folded into the count);
|
||||
going forward the count is the enumeration: **38 live doors / 4 closed,
|
||||
Turing 16 of the 38**, one door per canonical URL, Mercor network and
|
||||
Handshake hub named separately as pipeline rows, not doors. Item-35
|
||||
calibration reward CORRECTED to $100 (was $50). Greenhouse probe replaced
|
||||
(Point72 retired; Planet Labs 7555019 now the probe role, form renders
|
||||
fully, LinkedIn optional). Lever probe DEGRADED (Worldscape URL 404s on
|
||||
text fetch + live browser — replacement probe role needed). Ashby
|
||||
code-analysis question presence re-confirmed on live render
|
||||
(presence only). No new submissions.
|
||||
|
||||
## Queue order (by conversion speed)
|
||||
|
||||
### 1. "Senior Software Engineer – AI Evaluation / Coding Agents" — TURING DOOR ONLY ⭐ APPLY-READY, best-structured interview this month
|
||||
- URL: https://work.turing.com/r/bs71Txx0ar (LIVE, full copy re-read 2026-10-22)
|
||||
- The 24-MAG careers-page door is CLOSED (genuine 404, two hosts, 10-21). The
|
||||
project is the same one (word-for-word dedupe verified by Timmy); only the
|
||||
Turing door remains.
|
||||
- Terms: freelance/contract, remote North America only, 20–40 hrs/week with
|
||||
≥6 hrs/day PT overlap (~3–9pm ET — lifestyle call), ~3-month project, start
|
||||
ASAP. **Pay: $100–150/hr — the form asks for a specific rate expectation,
|
||||
so the number is a concrete decision.**
|
||||
- Work: review AI-generated code, design rubrics and acceptance criteria,
|
||||
repo-level analysis, eval-infrastructure pipelines. Two years of Alexander's
|
||||
daily Q-audit work, nearly verbatim.
|
||||
- Interview (three stages, from the live page): ~25-min AI interview →
|
||||
~30-min practical (reviewing AI-generated code, not algorithms) → ~20-min
|
||||
hiring-manager chat.
|
||||
- Gates: 5+ years hands-on SE, Python listed FIRST among languages (no
|
||||
React/Node hard requirement), code review, written communication, modern LLM
|
||||
tooling; "LLM evaluation or coding-agent experience is advantageous." **No
|
||||
degree requirement anywhere.** Named gap (not hidden): the 24-MAG page's
|
||||
"GitHub-based development workflows" line — his public review work lives on
|
||||
Gitea; name it in the application, don't hide it. Five of six gates clear.
|
||||
- Caveats: the page mentions TypeScript/JavaScript, Go, Java among skills —
|
||||
none is a hard requirement, but Alexander knows his denialist lines. First
|
||||
stage is an AI interview, so the standing rule applies: **pause ALL Mac
|
||||
automations before it** (pre-flight procedure: `interview-preflight-24mag.md`).
|
||||
- **Paste-ready pitch (public-safe):**
|
||||
|
||||
> I'm Alexander Payne, a senior backend engineer (Python) contracting
|
||||
> independently. For the last two years my day job has been directing and
|
||||
> evaluating AI coding agents end to end on real repositories: reviewing
|
||||
> generated implementations for correctness, robustness, and maintainability;
|
||||
> designing the acceptance criteria and rubrics the evaluations run on; and
|
||||
> making release decisions on agent output at the diff level. Underneath that,
|
||||
> 5+ years of production Python — Django, Flask, REST APIs, PostgreSQL,
|
||||
> Docker, CI/CD — so I judge generated code the way someone who has shipped
|
||||
> it does: by reading it, running it, and checking the tests. I'm comfortable
|
||||
> cloning an unfamiliar repo, reading its architecture cold, and writing up
|
||||
> exactly where the model went wrong and why. Remote, US-based, available to
|
||||
> start immediately, fine with the PT overlap.
|
||||
|
||||
- **OPEN FOR ALEXANDER (Timmy to ask directly):** go or no-go on the Turing
|
||||
door, and his rate inside $100–150.
|
||||
|
||||
### 2. Data Annotation — "Software Engineer"
|
||||
- URL: https://dataannotation.tech/job-board/software-engineer (LIVE 2026-10-22, 200 after redirect)
|
||||
- Terms: remote, weekly payouts. Pay: **Up to $150+/hr** depending on task
|
||||
difficulty and specialization. **No degree required.**
|
||||
- Work: run agentic coding sessions on real engineering tasks, analyze what
|
||||
the models produce, red-team them until they fail in interesting ways.
|
||||
Distinct door from the Backend Engineer track.
|
||||
|
||||
### 3. OpenTrain — "Backend Coding Task & Verifier Specialist"
|
||||
- URL: https://www.opentrain.ai/jobs/backend-coding-task-and-verifier-specialist--cmu9linxg000o0bgm9xiw33b9/ (LIVE 2026-10-22, 200)
|
||||
- Terms: remote, US-eligible, ~15 flexible hrs/week, mid-senior.
|
||||
- Pay: **$30–100/hr equivalent, paid per task.**
|
||||
- Work: create backend coding tasks and deterministic verifiers for AI
|
||||
systems. Python listed first. Modest pay, clean fit.
|
||||
|
||||
### 4. Terac — "Software Engineers: Paid Code Review for AI Agent Evaluation"
|
||||
- URL: https://terac.com/opportunities/XJ4I47Bp6ExVHmNY (LIVE, full copy re-rendered 2026-10-24; published 2026-10-02)
|
||||
- Terms: remote, hourly. Pay: **$65/hr** (Timmy's on-page read 10-21, Documented). "15 spots left" badge remains client-side-only — carried as my live-browser read, not a verified count.
|
||||
- **Render note 2026-10-26:** live-browser render confirms the side panel reads "Earn $65 per hour" with an "Apply to this opportunity" button and no closure notice — the $65/hr cell is now **live-render confirmed**, not variance-flagged. (The text fetch still shows "Hourly Remote" only: the pay lives in the side panel the extractor drops.)
|
||||
- **NEW named contact:** Zachary "Zac" Baker, Co-Founder & CEO (co-founded 2025 with Jack Blair; source: greenbook.org/company/Terac directory; public business line +1 (703) 405-1525; careers@terac.com held). He reaches out.
|
||||
|
||||
### 5. micro1 — Senior SWE ($245–280/hr) — CLOSED 2026-10-24
|
||||
- URL: https://jobs.micro1.ai/post/3d79ba82-926b-48c0-9d15-8791a364ea81 (page renders 2026-10-24 AND states "This job is currently closed and not accepting applications." — rendered closure, confirmed by two reads this run: my own browser.open + scout instrument)
|
||||
- Terms were: remote contractor, published 2026-08-27, $245–280/hr.
|
||||
- **Do not route Alexander here.** Corroboration-requested: Timmy host re-read of the closed banner (status flip).
|
||||
- Correction: my 10-23 "URL-DEAD" verdict for micro1 was a wrong-domain artifact (fetches hit `micro1.ai/post/` instead of `jobs.micro1.ai/post/`). The canonical pages render; this closure is real, on the correct domain.
|
||||
|
||||
### 6. Vettedlance — "Senior SWE, Agentic Coding Evaluation"
|
||||
- URL: https://vettedlance.com/jobs/senior-software-engineer-agentic-coding-eval (LIVE 2026-10-22, 200)
|
||||
- Terms: hourly contractor, remote flexible PT, 10–40 h/wk, weekly USD.
|
||||
- Pay: **$80–120/hr.** "Hiring now." Paid coding assessment before project
|
||||
work. "Vettedlance never charges candidates" (free-tier rule holds).
|
||||
|
||||
### 7. Askable — "Software Engineer, AI Coding Tasks"
|
||||
- URL: https://www.askable.com/experts/roles/senior-software-engineer (LIVE 2026-10-22, 200)
|
||||
- Terms: contract after paid technical task; remote, any location; ≥10 h/wk.
|
||||
- Pay: **US$1,000 per accepted task** (not hourly).
|
||||
- Gate: code you own merged into a public open-source repository
|
||||
(employer/client code excluded). **OPEN FOR ALEXANDER:** does he have
|
||||
qualifying OSS work?
|
||||
- **NEW named contact:** John Goleby, Co-Founder & CEO of Askable (Brisbane; US/UK/Chicago offices; $22M AirTree-led Series A **Dec 2024** — sources: devopsdigest.com/askable-joins-vendor-forum, thebusinessfrontier.com, cmotech.uk; the year is 2024 per PRNewswire's "CHICAGO, Dec. 13, 2024" dateline, Askable's own blog, Business Insider — my "all 2026" was wrong, fixed 2026-10-22 per reply 80). The funnel is self-serve, but he can go direct on the OSS-gate question. He reaches out.
|
||||
|
||||
### 8. Turing M2 — "Senior SWE – Python (LLM Evaluation & Repository Validation)"
|
||||
- URL: https://work.turing.com/r/C94ooVlx1g (LIVE, full copy re-read 2026-10-22)
|
||||
- Terms: contractor, remote, 4–8 weeks, ≥4 h/day (20 h/wk) with 4 h PST overlap.
|
||||
- Gates verbatim: degree line, "Minimum 8 years … in leading product companies
|
||||
or technology startups", Python mandatory + Java/Go/C++. **OPEN FOR
|
||||
ALEXANDER:** go/no-go + rate.
|
||||
|
||||
### 9. Turing N2 — "Senior SWE – LLM Evaluation (US-based)"
|
||||
- URL: https://work.turing.com/r/b9OgTSjjGs (LIVE, full copy re-read 2026-10-22)
|
||||
- Terms: contractor (no medical/paid leave), US-based required, 10–40 h/wk
|
||||
flexible, 1 month (+ext). AI video interview required.
|
||||
- Fit: code curation "primarily in Python", agent/verification-tooling work,
|
||||
3+ yrs. **Caveat:** additional work in JavaScript (incl. ReactJS), C/C++,
|
||||
Java, Rust, Go (on-page) — denialist risk.
|
||||
- **New on-page data point (10-22):** "Ideal Background" section names
|
||||
frontier-AI employers (OpenAI/NVIDIA/Databricks/Palantir/Snowflake) and
|
||||
"especially welcome" CS programs (UW/UIUC/UT Austin/Michigan/Purdue) —
|
||||
"though exceptional experience and skill always take precedence over
|
||||
pedigree." Flagged as a funnel signal, **not** a hard gate.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 10. micro1 — "Junior SWE" ($150–200/hr) — CLOSED 2026-10-24
|
||||
- URL: https://jobs.micro1.ai/post/29ba0d51-2d9f-412e-ad19-5f28a76ca96e (page renders 2026-10-24 AND states "This job is currently closed and not accepting applications." — rendered closure, confirmed by two reads this run)
|
||||
- Terms were: contractor, remote, $150–200/hr, published 2026-10-12.
|
||||
- **Do not route Alexander here.** Corroboration-requested: Timmy host re-read of the closed banner (status flip despite the recent publish date).
|
||||
|
||||
### 11. Alignerr N5 — "Senior Machine Learning Engineer" ($60–80/hr ON PAGE, Timmy 10-21)
|
||||
- URL: https://www.alignerr.com/jobs/20c08939-56c2-4351-a47a-efcdf022eca5 (LIVE 2026-10-24; pay Documented from the page header by Timmy 10-21: "Senior Machine Learning Engineer $60-80/hr Remote Freelance CODING")
|
||||
- **Render note 2026-10-24:** the $60–80/hr figure does NOT appear in the 10-23 or 10-24 renders (Hourly Contract / Remote / 10–40 h/wk only). The body pay cell keeps Timmy's Documented read; the variance is flagged, not a pay change — a Timmy host re-read settles it.
|
||||
- Terms: hourly contract, remote, 10–40 h/wk, fully async.
|
||||
- Work: LLM training/eval data authoring — reasoning traces, model-failure analysis; adjacent to the AI-eval seat. No LinkedIn/degree required per listing.
|
||||
- Caveats: framed for ML practitioners; pay below the top band.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
- Direct lane stays weak (self-serve funnel; Labelbox CEO Manu Sharma named-only).
|
||||
|
||||
### 12. Terac — "Part-Time Full-Stack Engineers: Farm-Data Platform Development" ($39/hr, Timmy 10-21) — CLOSED 2026-10-25
|
||||
- URL: https://terac.com/opportunities/EW5rvZqnDf0sO6qQ (CLOSED 2026-10-25: live-browser render shows "This listing has closed, but Terac posts new paid opportunities regularly. Sign up to get matched with similar work." with no Apply button or application form for this listing — corroborating Timmy's 2026-10-25 host re-read at `0ba6be9` (closure banner + `isClosed:true`) and sol's sweep. Correction per reply 99 §2: the banner IS in a plain text fetch of the same URL (200/213,617 B, closure sentence twice) — the scout extractor drops the panel, the plain fetch surfaces it. The 10-25 "text fetches neither confirm nor refute" sentence was an instrument generalisation, corrected here.)
|
||||
- Terms were: independent contractor, remote any timezone, ~15 h/wk, 1+ year engagement, weekly pay. Pay was Documented $39/hr on page per Timmy 10-21.
|
||||
- **Do not route Alexander here.** Decision 9 (take or pass) is WITHDRAWN as moot 2026-10-25.
|
||||
|
||||
### 13. micro1 — "Open Source Contributor (GitHub)" ($100–150/hr)
|
||||
- URL: https://jobs.micro1.ai/post/18a809aa-0b7f-4523-ac0e-508c9f0f6f66 (LIVE canonical, re-read 2026-10-24 on two reads this run: title "Open Source Contributor (GitHub)", $100–150/hr, published 2026-09-16; apply/process sections render, no closed banner).
|
||||
- ~~Corroborated LIVE 10-21 via six mirrors (canonical URL malformed; true UUID unresolved)~~ — struck 10-23: the full UUID sat in `micro1-oss-maintainer-2026-10-20.md` line 39 all along; the truncation was mine at write time (reply 81).
|
||||
- Terms: global remote contractor, ~15 h/wk, flexible; ~100 openings.
|
||||
- Gates: public/verifiable GitHub profile with meaningful ownership; Alexander's public review work lives on Gitea — the standing GitHub gate gap. Compensation per-task with minimum weekly submissions — treat band as nominal.
|
||||
- **OPEN FOR ALEXANDER:** queue-add his call (pending the GitHub-gate honest read).
|
||||
|
||||
### 14. Corroborated Turing doors — all LIVE (Timmy's host, reply 78, 10-21) — weighable now
|
||||
- r/Y74n4sPVv9 — **Senior Software Engineer – LLM Evaluation**: 10–40 h/wk, contractor, 1 mo, partial PST overlap. **No $ on page.**
|
||||
- r/HI7GzvKjPF — **Senior Python Engineer – AI Agents Evaluation**: full-time contractual, 40 h/wk, 1 mo, remote. **No $ on page.** (Label corrected — not GenAI Security.)
|
||||
- r/CUZsKnwt7P — **Agentic Coding Evaluation Specialist (Contract)**: **"Compensation: $75/hour"**, ~2–4 weeks (+ ext). **Stale-risk flag 2026-10-25:** body also states "Project start date: May 4, 2026 (Tentative)", rolling "until the batch is full" — still rendering, no closure marker, but weigh as backfill/batch, not a fresh project.
|
||||
- r/JHrOLgPhXZ — **Senior Backend Engineer (Python/FastAPI) – AI Evaluation (US-based)**: 10–40 h/wk, contractor, 1 mo. **No $ on page.**
|
||||
- r/Xqiv8zPNaw — **GenAI Security Evaluation Engineer**: **"Pay up to $150/hr depending on internal evaluation and location"**, freelance/remote/contractor, up to 2 weeks. (The actual GenAI-Security door.)
|
||||
- r/alSSk0vX2k — **Senior Software Engineer – LLM Evaluation (US/Canada/WEU)**: 10–40 h/wk, contractor, 1 mo. **No $ on page.**
|
||||
- Four doors state no figure — weigh on fit, not pay.
|
||||
|
||||
## UNVERIFIED this tick (hold, do not queue)
|
||||
- micro1 Senior Platform Engineer re-post: still absent from the board (JS shell; mirrors only) — stays dropped, watching for a re-post.
|
||||
|
||||
## DROPPED
|
||||
- **24-MAG careers-page door — CLOSED 2026-10-21** (live-browser 404 + Timmy's host 404). The project continues via item 1 (Turing door).
|
||||
|
||||
## Open decisions (for Alexander, via Timmy on Telegram — NOT via Zeph)
|
||||
1. Item 1 (Turing door, $100–150/hr project): go/no-go + his rate number.
|
||||
2. Item 8 (Turing M2): go/no-go + rate (carried from 10-13 — still unanswered).
|
||||
3. Item 9 (N2): take or pass (React caveat + new pedigree-language note).
|
||||
4. Item 5 (micro1 $245–280/hr): ~~authorization to start the candidate account + AI interview + skill assessments~~ — WITHDRAWN 2026-10-24: door CLOSED (rendered banner).
|
||||
5. Item 7 (Askable): does he have qualifying OSS-merged work — and whether to go direct via John Goleby.
|
||||
6. Item 11 (N5 Alignerr MLE, $60–80/hr on page): take or pass.
|
||||
7. Item 4 (Terac $65/hr): window open — and whether to go direct via Zachary Baker.
|
||||
8. Item 10 (micro1 "Junior SWE" $150–200/hr): ~~queue-add his call~~ — WITHDRAWN 2026-10-24: door CLOSED (rendered banner).
|
||||
9. Item 12 (Terac $39/hr farm-data): ~~take or pass~~ — WITHDRAWN as moot 2026-10-25: door CLOSED (live-render corroborated).
|
||||
10. Item 13 (micro1 OSS Contributor $100–150/hr): queue-add his call (GitHub-gate honest read).
|
||||
11. Item 14 (six corroborated doors): weigh on fit now that liveness is Documented.
|
||||
12. Item 25 (OpenTrain GenAI Security $150/hr): take or pass — conditional on genuine appsec depth.
|
||||
13. Item 28 (Alignerr Senior SWE – AI Evaluation): take or pass — pay CORRECTED 2026-10-27 to $60-120/hr on page (Timmy Documented, reply 112 §2); hourly contract, remote, 20–40 h/wk.
|
||||
14. Item 29 (Alignerr Senior SWE – AI Infrastructure): take or pass — pay $20-100/hr on page (CORROBORATED 2026-10-30 on live render, matching Timmy raw-byte, replies 129 §2.1 / 130 §3); hourly contract, remote, 20–40 h/wk. Seattle variant URL REMOVED 2026-10-30 (HTTP 404 + render 404, two instruments), **LIVE AGAIN 2026-10-31 (three instruments)** — role two variants again. Timmy's read: pass (below band).
|
||||
15. Item 30 (Alignerr Senior Systems Engineer – AI Data & Infrastructure): take or pass — pay CORRECTED 2026-10-28 to $50-75/hr on page (Timmy raw-byte, replies 129 §2.2 / 130 §3); hourly contract, remote, 20–40 h/wk. Timmy's read: pass (below band).
|
||||
16. Item 31 (Turing bAJ2YQwFKG, systems-Python door): take or pass — new verified door 2026-10-28, contractor, US-based, 10–40 h/wk, 1 month + extensions; ReactJS-in-overview caveat; pay unstated in text fetch.
|
||||
17. Item 32 (OpenTrain Secure Coding-Agent Benchmark Engineer): take or pass — new verified door 2026-10-28, remote worldwide, 4–8 wks, 20+ h/wk; M2 twin shape; pay not provided in the listing; security-conditional. NO expiry line: OpenTrain validThrough is render-synthesized build+30d, never a deadline (reply 145 §0).
|
||||
18. Item 33 (Turing -8ebgtrDpF, Agent Trace Collection): take or pass — new verified door 2026-10-29, $100/hr, contractor, 3 mo, North America, 20+ h/wk with 4h PST overlap; Copilot CLI agent-trace pipeline in Azure (OTLP/OpenTelemetry, PII/secret scrub, trace viewer). Caveat: posting requires 3+ yrs Azure (or comparable major cloud with clear transfer to Azure PaaS) + 2+ yrs observability/telemetry with direct OpenTelemetry experience — Azure depth is a stated bar, not a claim to make lightly.
|
||||
19. Item 34 (Data Annotation DevOps Engineer, AI Training): take or pass — new verified door 2026-10-29, up to $150+/hr by task difficulty, no degree required, remote. Caveat: posting asks for comfort with a major cloud and tools like Terraform, Kubernetes, or Docker — K8s/Terraform depth is a stated comfort requirement; do not over-claim.
|
||||
20. Item 35 (Terac AI Slide Deck Evaluation): take or pass — new verified door 2026-10-30, $110/hr + one-time $100 calibration-exam reward (CORRECTED 2026-10-31 from $50), independent contractor, fully remote, own schedule, weekly pay, screening interview first. Caveat: evaluation/review work (rank technical slide decks for clarity, structure, effectiveness), not platform building.
|
||||
|
||||
## New lead-grade items 10-22 (scout + corroborated top two by my reads)
|
||||
|
||||
### 15. Surge AI — "Senior Software Engineer: Agentic Coding RL Environments" ($100–150+/hour) ⭐ NEW TOP FIND
|
||||
- URL: https://surgehq.ai/swe (LIVE, full copy re-read by me 2026-10-22; scout instrument corroborates)
|
||||
- Terms: fully remote contractor, 20–40+ hrs/week, choose-your-schedule, async Slack, own equipment.
|
||||
- Pay: **$100–$150+/hour on page** ("Pay scales with your expertise"; "Some projects go well past the top of that range"; header "Make $200–300k+/year").
|
||||
- Work: build coding RL environments and benchmarks for frontier labs; review & red-team model output; write tests, rubrics, success criteria; structured feedback that improves future models.
|
||||
- Gates: professional SWE experience shipping scaled production systems; strong judgment about good code and model failures; expertise in at least one common stack incl. Python; **no AI/ML background required, no degree, no LinkedIn.**
|
||||
- Process: 2-hour coding capability screen → ID verification → paid first task.
|
||||
- Fit: near-perfect lane match — his 2-year agent-directing/eval background maps 1:1 (this is the work he does daily on the archive audits).
|
||||
- **OPEN FOR ALEXANDER:** go or no-go + whether to start the 2-hour coding screen.
|
||||
|
||||
### 16. workfindy.com — "Senior AI Engineer (Contract)" ($100–150/hr)
|
||||
- URL: https://workfindy.com/jobs/8f257919-3692-4422-ba07-60e05805ce8a (LIVE, full copy re-read by me 2026-10-22)
|
||||
- Terms: contractor, remote US/Canada, ≥20 h/wk + 4 h PT overlap, 3-month contract, start soon; no medical/paid leave.
|
||||
- Pay: **$100–$150/hr USD** (on-page).
|
||||
- Work: build data pipelines, review AI outputs, develop quality criteria; "a significant part of the role is being able to explain *why* one response is better than another."
|
||||
- Gates: 5+ yrs Python/TS/JS/Go; hands-on AI preference data or eval rubrics; US/Canada-based; no LinkedIn, no pay-to-evaluate. Published 2026-10-05T16:44:58Z.
|
||||
- **Caveat: employer unnamed — apply by "DM the poster"** (conversion risk).
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 17. Turing — "Senior Python Engineer – LLM Evaluation" (US-based) (L2)
|
||||
- URL: https://work.turing.com/r/HfWfAxm6VX (rendered open today, scout instrument)
|
||||
- Terms: remote contractor, US-based, 10–40 h/wk, 1 mo +ext; pay not stated.
|
||||
- Work: Python-primary eval + verification tooling; 3+ yrs SWE; AI video interview required.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 18. Turing — "Software Engineer – AI Research & Evaluation" (US-based) (L3)
|
||||
- URL: https://work.turing.com/r/7XiC0Ev2xx (rendered open today, scout instrument)
|
||||
- Terms: same engagement shape; pay not stated.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 19. Turing — "Senior Python Engineer – LLM Evaluation" (systems emphasis) (L4)
|
||||
- URL: https://work.turing.com/r/3tkNgppkIt (rendered open today, scout instrument)
|
||||
- Terms: same engagement shape; pay not stated; systems/infra bent — Go/Rust/C++ named but Python first, no hard ownership demanded.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 20. Alignerr — "Senior SWE — Agentic Coding" (L6)
|
||||
- URL: https://www.alignerr.com/jobs/5c4ccb04-ae5e-4274-8a60-6262aa3cb81f (rendered open today, scout instrument)
|
||||
- Terms: hourly contract, remote, 10–40 h/wk; pay not stated. Caveat: intro copy mentions "Berlin" though terms say Remote.
|
||||
- **2026-10-28 note:** second city variant verified open today — New York copy at https://www.alignerr.com/jobs/c002014e-c0a5-4a17-958c-6e2e4169ce71 (hourly contract, remote, 10–40 h/wk, same role body). Per the item-29 city-variant rule this is item 20's second variant, NOT a new numbered item; the scout's "new lead" call on this page is corrected here. Count unchanged.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 21. Alignerr — "Senior SWE — AI Evaluation & Benchmarks" (L7)
|
||||
- URL: https://www.alignerr.com/jobs/f15503d4-74ca-41f3-87e2-e7ccdc39beae (rendered open today, scout instrument)
|
||||
- Terms: hourly, remote, 3-month; pay not stated. Caveat: "proven LLM benchmark design experience" strongly worded.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 22. Alignerr — "Software Engineer - Python (Advanced)" (L8)
|
||||
- URL: https://www.alignerr.com/jobs/c6185f8a-b748-46b5-9e7a-57e0f652356b (rendered open today, scout instrument)
|
||||
- Terms: hourly, remote, 10–40 h/wk; pay not stated. Caveat: "consulting/client-facing experience" must-have; AI-code eval is nice-to-have, not core.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 23. Handshake AI — AI Trainer (filler-hours track) (L9)
|
||||
- URL: https://joinhandshake.com/ai/opportunities (canonical program page rendered open today, scout instrument)
|
||||
- Terms: independent contractor (not FT), fully remote, ~5–20 h/wk when assigned, year-round; pay not stated. 4+ yrs SWE, US-eligible, no LinkedIn/degree mandate.
|
||||
- **OPEN FOR ALEXANDER:** worth a profile, his call.
|
||||
|
||||
### 24. micro1 — "Open Source GitHub Maintainer" ($150–300/hr) — NEW NUMBERED ITEM 2026-10-23 (row verified 10-20; promoted from supplement per reply 81)
|
||||
- URL: https://jobs.micro1.ai/post/51a65c2c-07dd-4307-aba6-f7c4af17311c (LIVE — canonical detail page re-read 2026-10-24; "Apply now" renders; published 2026-08-14)
|
||||
- Terms: contractor, remote global, 15 h/wk, flexible; minimum weekly task submissions; "typically fill roles within 48 hours." Pay **$150–300/hr**, output-based per accepted task (pace-dependent — treat as nominal).
|
||||
- Work: review LLM-generated code patches for the repository the expert maintains; detailed written justifications; peer-review other experts' submissions. In-lane (diff-level review + written justification — Alexander's daily shape).
|
||||
- Gates: "Applicants must have clear open source contributions and profiles to showcase it like GitHub or GitLab" (page-verbatim). Same Gitea-gap as item 13: name the forge profile in the application, don't hide it. Preferred: OSS-maintenance experience; contributor-code review experience.
|
||||
- Process: screening questions → ~10-min AI interview → hiring-manager review. (Mac-automation pause before the AI interview.)
|
||||
- **OPEN FOR ALEXANDER:** queue-add his call. (Top-band micro1 family — weigh alongside items 13 and 24 now that items 5 and 10 are closed, not only in `micro1-oss-maintainer-2026-10-20.md`.)
|
||||
|
||||
### 25. OpenTrain — "GenAI Security Evaluation Engineer" ($150/hr) — NEW 2026-10-24, SECURITY-CONDITIONAL
|
||||
- URL: https://www.opentrain.ai/jobs/genai-security-evaluation-engineer--cmuxyhp6w000606nucgoq7baa/ (LIVE canonical detail page, full fetch 2026-10-24; posted Oct 7, 2026)
|
||||
- Terms: contract, part-time, 20+ h/wk, open worldwide. Pay: **"$150 per hour"** stated as hourly (not per-task equivalent) on page.
|
||||
- Work: build/test vulnerable GenAI agent and RAG codebases, annotate security risks, evaluate detection tools. Requires 5+ years in application/product security or security-focused SWE including secure code review; source-to-sink/taint analysis, SAST, CodeQL or Semgrep; LLM agents/RAG (LangChain/LlamaIndex/OpenAI or Anthropic SDKs or MCP); production Python and/or TypeScript.
|
||||
- **Caveats (read before relaying):** (a) security-specialist door — fits only if the appsec depth above is genuinely present; do NOT claim it from the general platform profile. (b) Distinct from Turing's GenAI Security door (item 14 / Xqiv8zPNaw, "up to $150/hr") — do not merge the two. (c) OpenTrain detail pages carry the 2026-10-13 orphan/expiring caveat (referral scheme retired; pages render but may be expiring) — treat as expiring-class until re-read. (d) Application route requires creating a free OpenTrain account (not a pay-to-eval gate stated on page).
|
||||
- **OPEN FOR ALEXANDER:** take or pass — conditional on genuine appsec depth, his call.
|
||||
- **2026-10-25 note:** today's text fetch confirms title, $150/hr, posted Oct 7, 2026, 20+ h/wk; the page-claimed `validThrough` 2026-11-23 did not re-appear in the text fetch. It stands on Timmy's host read (reply 86 §4) as the page's own claim, not a fact about the employer's intent. 29 days from 2026-10-25.
|
||||
- **2026-10-28 note:** title, $150/hr, posted Oct 7, 2026, 20+ h/wk re-confirmed; `validThrough` again absent from the text fetch — and the standing 2026-11-23 cell is CORRECTED: the page's JSON-LD reads **`validThrough` 2026-11-26 beside `datePosted` 2026-10-07** (Timmy raw-byte, replies 129 §2.4 / 130 §3) — a 50-day computed span, **29 days remaining as of 2026-10-28**, quoted in that form from here on, never as a bare expiry date and never as an employer promise.
|
||||
|
||||
### 26. Mercor — "Software Engineering Expert" talent network ($70–150/hr) — POSSIBLE, new 2026-10-25
|
||||
- URL: https://work.mercor.com/jobs/list_AAABnwpGQEMCh-AXEZdBjbqD/senior-software-engineer-full-stack-typescript-react-aws (canonical page fetched 2026-10-25; the specific Full Stack TS/React/AWS job on it is CLOSED — the open item is the talent network it redirects to)
|
||||
- Terms: standing pool — grading model code/design, writing eval problems; DevOps/platform, systems/performance, security tracks; remote, part-time.
|
||||
- Pay: **$70–$150/hr** "set per project" — precision per reply 99 §4: the band is stated about past listings ("have posted at"), not promised for the next project. Carry as a band, not a rate.
|
||||
- Gates: no degree stated ("Where you trained matters less than whether you have owned code in production"); ~20-min AI interview; no LinkedIn mandate, no pay-to-eval stated.
|
||||
- **Caveat: a network, not a dated project** — match timing "within a week or several months". Weigh as a pipeline row, not a project door.
|
||||
- **OPEN FOR ALEXANDER:** take or pass as a pipeline row.
|
||||
|
||||
### 27. Gramian Consulting — "Python Backend Engineer (AI Agents & SaaS Integrations)" ($300/approved task) — WITHDRAWN 2026-10-26 (reply 99 §1)
|
||||
- URL: https://builtin.com/job/python-backend-engineer-ai-agents-saas-integrations/10501641 (BuiltIn mirror only; no canonical Gramian page found)
|
||||
- Terms were: remote freelance; Python backend apps, REST APIs, microservices, SaaS connectors; build/validate long-horizon AI tasks + rubrics; 2–3 wks, immediate start.
|
||||
- Pay was: **$300 per approved task**, min 1 approved task/day.
|
||||
- **WITHDRAWN: the mirror itself carries the removal notice above the title — "removed at 10:06 a.m. (UTC) on Thursday, Aug 13, 2026".** The 10-25 row dated it from the posting date below the notice; the disposition was wrong, the grading was right. It was never a canonical door, so the aggregate does not move. Today's extracted text again omits the notice (extractor drops it) — that neither re-confirms nor refutes the withdrawal, which stands on the reply-99 corroboration. **Do not route Alexander here; not a decision.**
|
||||
- Obituary note: `300-300 Hourly` is the mirror's own field; the pay is per approved task, as the body cell already says.
|
||||
|
||||
### 28. Alignerr — "Senior Software Engineer – AI Evaluation" (possible) — NEW 2026-10-26, PAY CORRECTED 2026-10-27
|
||||
- URL: https://www.alignerr.com/jobs/cfa052f0-e721-4ec5-8d38-d697e534081b (LIVE canonical detail page, fetched open 2026-10-26 and 2026-10-27; corroborated by my own read)
|
||||
- Terms: hourly contract, remote, 20–40 h/wk.
|
||||
- Pay: **$60-120/hr on page** (CORROBORATED 2026-10-30 on live render, matching Timmy Documented, reply 112 §2). The Timmy-Documented-only provenance is superseded — the badge now renders on an instrument of mine.
|
||||
- Work: design/build scalable evaluation pipelines and frameworks; automated testing harnesses, scoring systems, benchmarking tools for LLMs; APIs, dashboards, internal tools for eval workflows; edge cases, failure modes, reliability issues in AI outputs.
|
||||
- Gates: 4+ years professional SWE shipping production systems; strong Python (pandas, NumPy, FastAPI/Flask/Django); large datasets + data pipelines; comfortable with cloud infrastructure (AWS/GCP/Azure) and containerized deployments — familiarity, not ownership, do not over-claim; Git/CI/CD/testing; written communication, async remote.
|
||||
- Fit: strong in-lane — eval infrastructure is the daily audit shape. No degree stated, no LinkedIn mandate, no pay-to-eval stated.
|
||||
- **OPEN FOR ALEXANDER:** take or pass — at $60-120/hr, top in-band, floor below.
|
||||
|
||||
### 29. Alignerr — "Senior Software Engineer (AI Infrastructure)" (possible) — NEW 2026-10-27
|
||||
- URLs: https://www.alignerr.com/jobs/63d40d5a-d58c-4ce3-9ab3-a997ab255ff2 (Seattle variant — REMOVED 2026-10-30 (HTTP 404 + render 404, two instruments), **LIVE AGAIN 2026-10-31 (three instruments: two text fetches + live render with $20-100/hr tag and Apply present)**) and https://www.alignerr.com/jobs/2d057dd9-3b35-4ba7-a660-468dacfb12e9 (New York variant — LIVE 2026-10-30) — canonical pages fetched open 2026-10-27; identical role copy, city-targeted.
|
||||
- Terms: hourly contract, remote, 20–40 h/wk. Work: production-grade AI training/evaluation/deployment pipelines, APIs/data pipelines/backend services at scale.
|
||||
- Gates: 5+ years, Python/TypeScript/Go/Java or similar; cloud familiarity (AWS/GCP/Azure); Git/CI/CD. No degree stated, no LinkedIn mandate.
|
||||
- Pay: **$20-100/hr on page** (CORROBORATED 2026-10-30 on live render, matching Timmy raw-byte, replies 129 §2.1 / 130 §3). The Timmy-Documented provenance is superseded for the NY variant; the Seattle variant no longer renders at all.
|
||||
- Counted as ONE role, two city variants again (Seattle live again 2026-10-31 after the 10-30 removal; see corrections log).
|
||||
- **OPEN FOR ALEXANDER:** take or pass. Timmy's read: pass (floor far below band).
|
||||
|
||||
### 30. Alignerr — "Senior Systems Engineer — AI Data & Infrastructure" (possible) — NEW 2026-10-27
|
||||
- URL: https://www.alignerr.com/jobs/95a64c38-9a72-4dbc-8143-2b8ac23d4de3 (canonical page fetched open 2026-10-27).
|
||||
- Terms: hourly contract, remote, 20–40 h/wk. Work: high-performance backend systems, data annotation/validation/evaluation tooling, reliable data pipelines.
|
||||
- Gates: 5+ years systems/backend production experience; Go/Rust/Python/C++. No degree stated, no LinkedIn mandate.
|
||||
- Pay: **$50-75/hr on page** (Timmy raw-byte, replies 129 §2.2 / 130 §3: header badge + meta description + JSON-LD shortDescription). CORRECTION of the 10-27 "not stated in text fetch" cell — the cell was wrong. Provenance caveat: my 10-28 extraction again surfaces NO pay line (same header-badge class) — the cell is Timmy-Documented, not mine.
|
||||
- Fit: strong in-lane (systems + eval infra).
|
||||
- **OPEN FOR ALEXANDER:** take or pass. Timmy's read: pass (below band).
|
||||
|
||||
### 31. Turing — "Senior Python Engineer – LLM Evaluation" (US-based) (systems-Python family) — NEW 2026-10-28
|
||||
- URL: https://work.turing.com/r/bAJ2YQwFKG (canonical page fetched open 2026-10-28, my read).
|
||||
- Terms: contractor (no medical/paid leave), remote US-based, 10–40 h/wk, 1 month + potential extensions; AI video interview required; application 15–30 minutes.
|
||||
- Work: Python-primary eval + verification tooling with systems emphasis — systems-level code, performance-critical applications, infrastructure; build agents verifying systems-level/infrastructure code quality.
|
||||
- Gates: several years SWE; strong systems/infrastructure/backend expertise in Python, C/C++, Rust, Go; production-grade software; architecture/design/debugging/code-quality judgment; written communication.
|
||||
- **Caveat: overview mentions JavaScript (including ReactJS)** alongside Python/C++/Rust/Go/Java — React caveat, same class as N2/L4; do not claim React. Required Skills do not name React.
|
||||
- Pay: not stated in text fetch. L4-family alternate door — counted per the Turing /r/ convention (each /r/ is an application door); Turing door count moves 12 → 13 with this door.
|
||||
- **OPEN FOR ALEXANDER:** take or pass.
|
||||
|
||||
### 32. OpenTrain — "Secure Coding-Agent Benchmark Engineer" — NEW 2026-10-28, SECURITY-CONDITIONAL
|
||||
- URL: https://www.opentrain.ai/jobs/secure-software-coding-agent-benchmark-engineer--cmv0u6y87000k06i0ytsnui5a/ (canonical detail page recovered from the OpenTrain cybersecurity category page, fetched open 2026-10-28, my read; posted Oct 9, 2026).
|
||||
- Terms: contract, part-time, remote worldwide, 4–8 wks, 20+ h/wk with 4 h/day and 4 h PT overlap; apply on OpenTrain (free account) then complete on the hiring platform.
|
||||
- Work: design/build realistic benchmark tasks measuring whether AI coding agents complete software work safely and correctly — bug fixes, feature additions, CI repairs, config migrations, integration updates, runtime-state fixes; utility + safety requirements; visible/hidden test suites, safe/unsafe reference solutions, scoring rubrics, calibration notes, runnable evaluators; rollout review (disabling tests, weakening assertions, deleting protected data, leaking secrets, broadening permissions, bypassing validation).
|
||||
- Gates: 8+ years hands-on SWE in leading product companies or tech startups; bachelor's or master's in CS or related discipline; strong Python mandatory + Java, Go, or C++; production systems at scale (deployment pipelines, monitoring, logging, observability, distributed tracing, HA, fault tolerance, disaster recovery); practical vulnerability identification, secure fixes, remediation validation; injection/authorization/memory-safety/race-condition/deserialization/secrets/input-validation familiarity required.
|
||||
- Pay: **not provided in the listing** (page-verbatim).
|
||||
- **Caveats:** (a) M2 twin shape — same 8-yr + degree + Python-mandatory + secure-fix requirements as Turing M2; a distinct door (OpenTrain → hiring platform), not a merge. (b) security-specialist door — fits only if the appsec depth above is genuinely present; do NOT claim it from the general platform profile.
|
||||
- **OPEN FOR ALEXANDER:** take or pass — conditional on genuine appsec depth, his call.
|
||||
|
||||
---
|
||||
|
||||
## Corrections log (append-only)
|
||||
|
||||
- **2026-10-24:** items 5 and 10 CLOSED in the body (per Q3 rule, decisional cells): both canonical pages render AND carry "This job is currently closed and not accepting applications." (two reads this run: my own browser.open + scout instrument). Item 5 ($245–280/hr, published 2026-08-27) and item 10 ($150–200/hr, published 2026-10-12) are withdrawn as application routes; their open decisions are struck above. Corroboration-requested: Timmy host re-read of both banners.
|
||||
- **2026-10-24:** my 10-23 micro1 "URL-DEAD" verdict WITHDRAWN — the 10-23 fetches hit `micro1.ai/post/<uuid>` (wrong domain); canonical is `jobs.micro1.ai/post/<uuid>`, and all five canonical pages render today. The wrong-domain 404s were an instrument error, not closures.
|
||||
- **2026-10-24:** Alignerr `beae0b1f-…` URL DEAD (404 on text fetch + live-browser 404 page) — dropped from the tracked set; it never rendered as a posting in this record, so it is not a role closure.
|
||||
- **2026-10-24:** pay-render variance flagged (not body-corrected): Alignerr N5 $60–80/hr, Terac $65/hr, Terac $39/hr figures — all Timmy-Documented on-page 10-21 — do not appear in the 10-23 or 10-24 renders. Body cells keep Timmy's reads with dated variance notes; a Timmy host re-read settles whether the pages changed or the renders differ.
|
||||
- **2026-10-24:** item 25 added (OpenTrain GenAI Security Evaluation Engineer, $150/hr, canonical detail page fetched 2026-10-24, posted Oct 7, 2026) — security-conditional, distinct from Turing's GenAI Security door, OpenTrain orphan/expiring caveat carried.
|
||||
|
||||
- **2026-10-23, reply 81:** item 13 body corrected in place (per Q3 rule): canonical URL `https://jobs.micro1.ai/post/18a809aa-0b7f-4523-ac0e-508c9f0f6f66` is LIVE — independently read from two hosts (Timmy 10-22 + this host 10-23: 200 / 42,473 B, title "Open Source Contributor (GitHub)", ideal_hourly_rate $100–150, published 2026-09-16). The "canonical URL malformed; true UUID unresolved" line is struck; the full UUID was in `micro1-oss-maintainer-2026-10-20.md` line 39 — the truncation was my write-time error. Verdict now **Documented (canonical)**, GitHub-gate caveat unchanged.
|
||||
- **2026-10-23, reply 81:** OSS-maintainer promoted to numbered item 24 — `https://jobs.micro1.ai/post/51a65c2c-07dd-4307-aba6-f7c4af17311c`, LIVE (canonical read 10-20), $150–300/hr, published 2026-08-14, top-band micro1 family alongside items 5 and 10; **OPEN FOR ALEXANDER:** queue-add his call (via Timmy, not Zeph's relay).
|
||||
- **2026-10-22, reply 80:** Askable's Series A year corrected in the body (2026 → **Dec 2024**). The round is real — AU$22M Airtree-led — but it closed Dec 13, 2024 (PRNewswire: "CHICAGO, Dec. 13, 2024"; Askable's own blog and Business Insider carry the same). My "sources … all 2026" line (from the 10-21 scout read) was the error source; disambiguation kept: Askable is Brisbane-*founded*, Goleby's own public profile is SF Bay Area — both true, no edit owed. Daily-2026-10-22.md carries the same error in its §7 line; it is append-only dated record — correction note appended there at the foot, living index here corrected in place per the Q3 rule.
|
||||
- **2026-10-25, Timmy host re-read:** **item 12 (Terac "Part-Time Full-Stack Engineers: Farm-Data Platform", $39/hr) is CLOSED** — `https://terac.com/opportunities/EW5rvZqnDf0sO6qQ` returns **HTTP 200 / 215,923 B** at 01:14Z with the closure banner twice in the body and `isClosed\":true` in the embedded JSON; sol's independent 3/3 sweep (`8020091`, WorkBench) agrees. The body's "LIVE 2026-10-24" line is superseded, so decision item 9 ("take or pass") is now moot rather than pending — no door left to answer. Re-read in the same minute: item 24 (micro1 Open Source GitHub Maintainer, $150–300/hr) **LIVE**, 200 / 41,581 B, no closure marker; items 5 and 10 were already CLOSED in this file on 10-24, so this sweep adds one closed door, not three.
|
||||
- **2026-10-25:** item 12 CLOSED in the body (per Q3 rule, decisional cells): live-browser render shows the closure notice verbatim with no Apply button or application form for the listing — corroborating Timmy's 2026-10-25 host re-read (`0ba6be9`: banner + `isClosed:true`) and sol's sweep. Decision 9 struck as moot. Text fetches today show no closure language; the notice lives in a rendered side panel text extraction does not surface, so the text fetches neither confirm nor refute it.
|
||||
- **2026-10-25:** item 25 expiry note updated: page-claimed `validThrough` 2026-11-23 did not re-appear in today's text fetch; it stands on Timmy's host read (reply 86 §4) as the page's own claim. 29 days from 2026-10-25.
|
||||
- **2026-10-25:** CUZsKnwt7P stale-risk flag added to §14: "Project start date: May 4, 2026 (Tentative)", rolling — still rendering, no closure marker; weigh as backfill/batch.
|
||||
- **2026-10-25:** items 26 (Mercor talent network $70–150/hr, possible — network, not a dated project) and 27 (Gramian Python Backend $300/approved task, possible — BuiltIn mirror only, Aug 3 dated, freshness unverified) added.
|
||||
- **2026-10-25:** OpenTrain "Machine Learning Researcher and Task Reviewer" resolved and screened OUT: canonical detail page found (posted Oct 23, 2026, $60–$120/hr equiv) but it requires a master's degree or PhD — degree-gated, not queued. No longer carried as listing-level-only.
|
||||
|
||||
- **2026-10-26:** item 27 WITHDRAWN in the body (reply 99 §1): the BuiltIn mirror carries "removed at 10:06 a.m. (UTC) on Thursday, Aug 13, 2026" above the title. The 10-25 "possible, freshness unverified" disposition was wrong; grading (pay, terms, mirror-only status) was right. Never a canonical door; aggregate unchanged. Not a decision for Alexander.
|
||||
- **2026-10-26:** item 12 text-fetch sentence corrected (reply 99 §2): the closure banner IS in a plain text fetch (200/213,617 B, twice); the scout extractor drops the panel, the plain fetch surfaces it. The 10-25 corrections-log sentence ("text fetches neither confirm nor refute") stands as dated record, corrected beside it here.
|
||||
- **2026-10-26:** Terac $65 cell upgraded to live-render confirmed: live render shows side panel "Earn $65 per hour" + Apply button, no closure notice. N5 ($60–80/hr) still owes the same two-instrument test.
|
||||
- **2026-10-26:** Mercor band precision applied (reply 99 §4): $70–150/hr is about past listings ("have posted at"), not a promised rate.
|
||||
- **2026-10-26:** item 28 added — Alignerr "Senior Software Engineer – AI Evaluation" (canonical, fetched open + corroborated by my own read): hourly contract, remote, 20–40 h/wk, pay unstated, 4+ yrs Python eval-infra. Take-or-pass (decision 13).
|
||||
- **2026-10-26:** Lever Worldscape gate line corrected (reply 100 §5a) in daily-2026-10-26.md §2: "LinkedIn auto-complete + candidate attestations + hCaptcha-on-submit" (static text does not surface the submit-path captcha). Palantir pairing correction (reply 100 §5b) logged in the same file: a92b55d0 (Senior, 2026-04-06) ≠ 10dfc8bc (non-Senior, 2024-03-11).
|
||||
- **2026-10-26:** Ashby Ramp code-sample question presence confirmed a second day on my instrument (10-26 fetch); content deliberately not reproduced (safety notice on the embedded task — not decoded, not run, not quoted). "Agent stop" presence-confirmed; content ungraded.
|
||||
|
||||
- **2026-10-27:** item 28 pay CORRECTED in the body (reply 112 §2): $60-120/hr on page (Timmy Documented, 200/43,029 B) — the 10-26 "not stated" cell was wrong. Caveat: my 10-27 extraction + scout text fetch surface no pay line (header block dropped by extraction, same class as Terac $65 / N5) — cell is Timmy-Documented, not mine. Decision 13 reworded.
|
||||
- **2026-10-27:** Terac $65 instrument sentence corrected (reply 112 §0.2/§2): pay is ALSO in the fetched bytes (Timmy raw fetch 200/224,340 B, twice) — "render-only" was an extractor property. Today's text-only sweep again drops the panel — consistent, not contradictory. Door stays live on the 10-26 render.
|
||||
- **2026-10-27:** Ashby Ramp code-sample question presence confirmed a third day on my instrument (10-27 fetch); content withheld as before. Workday NVIDIA probe window closes 2026-10-28 (live browser + text fetch agree) — probe role only.
|
||||
- **2026-10-27:** items 29 (Alignerr Senior SWE – AI Infrastructure, Seattle + New York variants, one role) and 30 (Alignerr Senior Systems Engineer – AI Data & Infrastructure) added as possible — canonical pages fetched open, hourly contract, remote, 20–40 h/wk, pay unstated in text fetch. Decisions 14–15.
|
||||
- **2026-10-27:** item 25 expiry note updated: page-claimed validThrough 2026-11-23 stands on Timmy's host read only; 27 days from 2026-10-27.
|
||||
|
||||
- **2026-10-28:** items 29/30 pay CORRECTED in the body (replies 129 §2.1–2.2 / 130 §3, Timmy raw-byte): item 29 = $20-100/hr (both variants, header badge span); item 30 = $50-75/hr (header badge + meta description + JSON-LD). The 10-27 "not stated in text fetch" cells were wrong. Caveat: my 10-28 extraction again surfaces no pay line on either page (header-badge class) — cells are Timmy-Documented, not mine. Decisions 14–15 reworded; Timmy's read: pass on both; not re-raised.
|
||||
- **2026-10-28:** item 25 expiry CORRECTED in the body (replies 129 §2.4 / 130 §3, Timmy raw-byte): `validThrough` 2026-11-26 beside `datePosted` 2026-10-07 — a 50-day computed span, 29 days remaining as of 2026-10-28. The standing 2026-11-23 cell did not reproduce. Quoted in that form from here on, never as a bare expiry date, never as an employer promise. My text fetches again do not surface validThrough (JSON-LD dropped by extraction).
|
||||
- **2026-10-28:** N5 variance note CLOSED in the body (reply 129 §2.5): $60-80/hr now Documented from Timmy's raw-byte read, not only structured-data. Item 28 cell keeps $60-120/hr, byte count dropped (dated readings).
|
||||
- **2026-10-28:** process rules adopted (replies 129 §5 / 130 §3, standing): (a) raw-byte pay read before writing any new Alignerr/micro1/Terac pay cell; (b) validThrough always quoted beside datePosted.
|
||||
- **2026-10-28:** items 31 (Turing bAJ2YQwFKG, systems-Python door, React caveat, pay unstated) and 32 (OpenTrain Secure Coding-Agent Benchmark Engineer, M2 twin, pay not provided, security-conditional) added as possible — canonical pages fetched open, my read. Decisions 16–17. Item 20 gains a New York variant (c002014e, same role body as L6 Berlin copy) — variant, not a new item; the scout's "new lead" call on it is corrected in the body per the item-29 city-variant rule.
|
||||
- **2026-10-28:** census notes — Ashby Ramp form body returned "Fetching application form" only, so the code-analysis question presence is NOT re-confirmed today (10-25→10-27 streak pauses on an instrument limitation, not a removal); Workday NVIDIA text fetch timed out (upstream failure, no HTTP status), live-browser recovery dispatched and pending at push time — gate stands on 10-25→10-27 measurements, probe row retires after today (page line: "at least until October 28, 2026"); Terac $39 text fetch inconclusive (role copy, no closure language, no Apply element), CLOSED verdict stands on the 10-25 live render + reply-99 corroboration, live-browser re-check pending at push time.
|
||||
|
||||
- **2026-10-29:** item 25 expiry correction WITHDRAWN (reply 145 §0, interview §2.1 — Q116 landing in daily-2026-10-29): OpenTrain `validThrough` is synthesized at render time as build-time + 30 days, NOT a posting deadline. Three dated readings of item 25 (10-24: 2026-11-23; 10-27: 2026-11-26; 10-28: 2026-11-27) each sit exactly 30 days after their own render instant, and item 32 in the same minute 10-28 carries the identical stamp on a different posting. The 10-28 "50-day computed span / 29 days remaining" cell and the 10-28 "expiry CORRECTED" line are superseded; the 10-24 cell was right as a render stamp and wrong only when treated as a deadline. Standing rule REPLACES rule (b): OpenTrain `validThrough` is never quoted as a deadline; if it must appear, label it `render-synthesized, build+30d`. Item 25 keeps its take-or-pass (security-conditional, $150/hr, 20+ h/wk, posted Oct 7) with NO urgency line. Item 32 never receives an expiry line.
|
||||
- **2026-10-29:** count definition corrected (reply 145 §4, interview §2.3): the 10-28 daily's "13 live" was Turing-only mislabeled as a cross-family total. Going forward: one door per canonical URL; Turing 13 inside a 31-door cross-family total, 4 closed — moved to Turing 15 / 33 total today by the verification of wp680rglf0 + JPQ-cmFZSA (previously unverified, now fetched open). Micro1 item 5's closure is NOT re-confirmed today (text fetch returned no extractable content — gap, not a verdict change; a mirror still calls it closed, mirror-only); the closed count of 4 stands on standing verdicts, not on today's fetch.
|
||||
- **2026-10-29:** Terac $39 reason superseded (reply 145 §3): the closure IS in a plain fetch (200/213,580 B, `This listing has closed` x2, `isClosed:true`); the 10-28 daily's "extractor limitation, inconclusive" reason was wrong while the CLOSED verdict stands (10-25 render + reply-99 + 10-28 addendum render). Standing rule: when the extractor is silent, run the second instrument before writing "inconclusive". Today's text fetch of the $39 page again shows no closure language and no Apply element — that silence adds nothing; the verdict rests on the prior instruments, not on today's silence.
|
||||
- **2026-10-29:** census — Ashby Ramp form body renders fully again (Legal Name, Email, Phone, work location, Resume, LinkedIn, Cover Letter, employer experience questions); code-analysis employer question presence RE-CONFIRMED after the 10-28 shell-only pause (presence only, content withheld). Lever Worldscape field set identical. Greenhouse Point72 still header/footer + "Your submission is processing" only. Workday probe row RETIRED after 2026-10-28 (page line "at least until October 28, 2026", re-confirmed on its last day by the 10-28 addendum live render).
|
||||
- **2026-10-29:** items 33–34 added as possible (see decisions 18–19); Turing doors wp680rglf0 + JPQ-cmFZSA verified open (Senior SWE – LLM Eval, US, 1 mo, 10–40 h/wk, pay absent in fetch) — no longer held as unverified. Screened out: Alignerr C# (stack mismatch), Alignerr Tel Aviv variant of item 29 (variant, not a role), Terac SWE Benchmarks $45–75 + LinkedIn/GitHub mandate, Terac South Asian $40, Terac genomics $100 mirror-only, G2i (SKIP stands), OpenTrain related cards (ML/AI Systems $30/task, Life Sciences $280/task out-of-lane, Rust, ML Researcher/Applied Scientist related-card only), Mercor newsletter figures (mirror-only), Surge staff-careers (not a contractor door).
|
||||
- **2026-10-30:** item-29 Seattle variant REMOVED (HTTP 404 text fetch + render 404, two instruments); role now NY-URL-only; item-29 pay upgraded Timmy-Documented → Corroborated (live render badge $20-100/hr). Item 28 pay likewise Corroborated ($60-120/hr render badge); N5 $60-80 and item 30 $50-75 also render-confirmed. New render-only cells: L6 $80-120, L7 $80-100, L8 $50-75, item 20 NY $80-120.
|
||||
- **2026-10-30:** item 35 added as possible (decision 20): Terac AI Slide Deck Evaluation, $110/hr + $50 calibration reward, canonical page fetched open by my own instrument, published 2026-10-24; evaluation/review work, not platform building.
|
||||
- **2026-10-30:** micro1 items 5 + 10 closures both re-confirmed verbatim (item 5 by my text fetch, item 10 on live render); items 13/24 re-confirmed open on live render ($100-150 / $150-300). Terac $65 corroborated on live render; Terac $39 closure re-corroborated on live render (closure banner verbatim) — resolves the delegated text fetch's no-marker render as the known panel-drop class, not a reopening.
|
||||
- **2026-10-30:** census — Greenhouse Point72 probe URL now redirects to the Point72 careers hub (form unreachable at that URL; gate lines carried from prior renders; replacement probe role needed). Ashby Ramp form renders fully on live render; code-analysis question presence RE-CONFIRMED (presence only, content withheld). Lever field set matches prior plus Desired Salary newly noted; hCaptcha-on-submit stands. Turing alSSk0vX2k delegated empty-fetch gap closed by my own full-page fetch (LIVE, unchanged). Screened out: Turing MPKlB1_SPo (duplicate-variant), React/TS-primary doors, C# door, non-US-location door, Alignerr city variants (not senior-titled), OpenTrain related rails (below-band/degree-gated/Rust), micro1 mirror-only write-ups.
|
||||
|
||||
- **2026-10-31:** item 29 Seattle variant LIVE AGAIN (three instruments: my text fetch, delegated sweep, live-browser render with $20-100/hr tag + Apply present) after the 10-30 REMOVED verdict (HTTP 404 + render 404, two instruments). The 10-30 removal was a true reading yesterday, stale today — Alignerr pages flip. Role is two variants again; closed count 5 → 4.
|
||||
- **2026-10-31:** count CORRECTED — 38 live doors / 4 closed, Turing 16 of the 38, one door per canonical URL, enumerated in daily-2026-10-31.md §3. The 10-30 "33 live / Turing 15" line undercounted its own enumeration (Turing 16, item 33 verified 10-29 but never folded into the count; item 34 and the L-series/20NY doors listed live but not counted). Mercor network and Handshake hub are pipeline rows, not doors, named separately so the arithmetic stays checkable.
|
||||
- **2026-10-31:** item 35 calibration reward CORRECTED $50 → $100 (today's text fetch: "one-time $100 reward upon completing and passing the Terac calibration exam"). Door terms otherwise unchanged.
|
||||
- **2026-10-31:** Greenhouse probe REPLACED — Point72 8356788002 retired (redirected to careers hub 10-30); new probe Planet Labs 7555019 (Software Engineer, Platform Operations, US remote), form renders fully on live render: LinkedIn present NOT required, no attestation checkboxes, privacy consent as text above the form. Lever probe DEGRADED — Worldscape URL 404s on text fetch + live browser; replacement probe role needed; gate lines carried from prior renders.
|
||||
|
||||
---
|
||||
## 2026-11-01 tick changes (append-only; supersedes the 10-31 queue where noted)
|
||||
|
||||
- **Count unchanged: 38 live doors / 4 closed; Turing 16 of the 38.** Closed: 24-MAG careers door, micro1 items 5 + 10, Terac $39. No door changed state 2026-11-01.
|
||||
- **Lever probe REPLACED:** Worldscape 6b5089a8 (404 since 10-31) retired; new probe role Extreme Networks Senior SW Systems Engineer (10187), Seattle WA, Hybrid — apply URL https://jobs.lever.co/extremenetworks/3f97b5fc-cf53-4cc7-ac6d-39b8e721e885/apply renders fully on live render. LinkedIn URL PRESENT AND REQUIRED — a hard gate on this Lever form (contrast Greenhouse Planet, LinkedIn optional). Full field set in career-lane/daily-2026-11-01.md §2.
|
||||
- **Greenhouse probe refined:** Planet 7555019 form re-renders fully (same field set; LinkedIn optional; no attestation checkboxes). New detail: invisible-style reCAPTCHA badge icon bottom-right — not an interactive gate, no code widget. Gate line unchanged.
|
||||
- **HI7GzvKjPF crawl caveat SUPERSEDED:** fresh 2026-11-01 fetch serves current copy; the 2026-10-17-crawl caveat no longer applies.
|
||||
- **CUZsKnwt7P stale-risk SHARPENED:** $75/hr + May-4-2026 tentative start unchanged, but that start date is now past while the listing still serves.
|
||||
- **Title renders noted:** Surge page now "Senior Software Engineer: Agentic Coding RL Environments" ($100–150+/hr stands, plus a "$200–300k+/year" page line — not a second door); OpenTrain backend door now renders "Backend Engineer – Remote" (slug unchanged, $30–100/hr equiv stands).
|
||||
- **Alignerr cd5a8955 HELD as duplicate posting, NOT numbered, NOT counted:** "Software Engineer - Python (Advanced)" live on two instruments, but side-by-side comparison with tracked c6185f8a shows same title, terms, must-haves, nice-to-haves, no city-variant copy. Per the Turing-duplicate precedent, same role twice is not a new door. Promotable only on distinct requisition metadata from Timmy's host read.
|
||||
- **Terac $39 + micro1 item 5 closures RE-CONFIRMED on render** (verbatim banners, no Apply); the delegated sweep's text-fetch flags on both are the known panel-drop / shell classes, not reopenings. Item 35 re-confirmed on my direct fetch ($110/hr + $100 calibration reward + Apply).
|
||||
- **Ashby code-question presence RE-CONFIRMED on render** (presence only). LinkedIn REQUIRED on the Ramp probe role.
|
||||
- **Pipeline tally unchanged: 11 submitted / 2 interviews / 0 offers / 2 rejections.**
|
||||
@@ -0,0 +1,92 @@
|
||||
# Daily career-pipeline tick — 2026-11-01 (Zeph lane)
|
||||
|
||||
**Routing:** pipe-native tick. Zeph → Timmy → Alexander (Telegram). Nothing in this file asks Timmy to decide — relay only. All findings employer-side, public, dated 2026-11-01 ET. No submissions, no accounts, no contact made by me.
|
||||
|
||||
## 0. Pipe sync (this run)
|
||||
|
||||
No new Timmy replies since reply 150 (2026-10-28). Watermark 150 stands; nothing new folded, nothing owed either way. Today's tick is a full re-verification + scout on the standing set, with three instruments: my own text fetches, a delegated text-fetch sweep, and live-browser render passes (7 URLs + 1 follow-up, read-only).
|
||||
|
||||
## 1. Time-sensitive / conversion (lead first)
|
||||
|
||||
1. **Lever probe REPLACED — and it mandates LinkedIn.** The Worldscape probe (404 since 10-31) is replaced by Extreme Networks Senior SW Systems Engineer (10187), Seattle WA, Hybrid, full-time — apply URL `jobs.lever.co/extremenetworks/3f97b5fc-cf53-4cc7-ac6d-39b8e721e885/apply` loads live on render. Field set: Resume/CV* (required upload), Full name*, Email*, Phone*, Current location*, **LinkedIn URL* — PRESENT AND REQUIRED**, GitHub/Portfolio/Other website (optional), US work-authorization + sponsorship radios* (required), expected total compensation OTE* (required radio ranges), target salary range (optional), prior-employment / related-to-employee / customer-employment / US-residence questions* (required), voluntary EEO/veteran/disability sections (all optional). No attestation checkboxes; no captcha or code widget visible in the initial form view. Census headline: on this Lever probe, LinkedIn is a hard gate for a no-LinkedIn candidate — unlike the Greenhouse Planet probe, where LinkedIn is optional. (Correction to my own scout note: the search snippet's "Remote" label is wrong — the render header says Seattle, Washington / Hybrid, not remote. The probe role's employment terms don't matter for the census; the form does.)
|
||||
2. **Count UNCHANGED: 38 live doors / 4 closed; Turing 16 of the 38.** No door changed state today. Two sweep flags that looked like changes were both resolved against closure (see §7): Terac $39 stays closed, micro1 item 5 stays closed. One new Alignerr URL is held as a duplicate posting, not counted (see §1.5).
|
||||
3. **Terac $39 CLOSED, re-corroborated on render — sweep flag corrected.** The delegated sweep's text fetch served the full farm-data listing with no closure language and flagged a "discrepancy". That silence is the established panel-drop class for this page (same silence 10-29 and 10-31). Today's live render shows the closure banner verbatim ("This listing has closed, but Terac posts new paid opportunities regularly. Sign up to get matched with similar work.") with no Apply for the listing. CLOSED stands; the sweep's "LIVE-appearing" verdict is superseded by the deciding instrument, not carried.
|
||||
4. **micro1 item 5 CLOSED, re-confirmed on render — sweep gap closed.** The sweep's text fetch returned a title-only shell (2 lines). The live render shows the $245–280/hr badge plus the closure banner verbatim ("This job is currently closed and not accepting applications. Thank you for your interest!"), no Apply panel. CLOSED stands.
|
||||
5. **New Alignerr URL HELD as a duplicate posting, not a new door.** `alignerr.com/jobs/cd5a8955` ("Software Engineer - Python (Advanced)", hourly contract, remote, 10–40 h/wk, 4+ yrs, advanced Python + SQL + consulting/client-facing) is live on two instruments. My own side-by-side comparison against the tracked Python-Advanced door (c6185f8a) shows the same title, terms, must-haves, and nice-to-haves with only intro/closing wording differing, and neither page carries city-variant copy. Per the Turing-duplicate precedent (10-31: a second code for the same role is not a new door), it is NOT numbered and NOT counted. If Timmy's host read shows distinct requisition metadata, it can be promoted; on today's page evidence it is the same role twice.
|
||||
6. **HI7GzvKjPF stale-cache caveat SUPERSEDED.** The sweep's fresh 2026-11-01 fetch serves current copy ("Senior Python Engineer – AI Agents Evaluation", full-time contractual, 40 hrs/wk, 1 mo, remote, pay unstated). The 2026-10-17-crawl caveat no longer applies.
|
||||
7. **CUZsKnwt7P stale-risk flag SHARPENS.** $75/hr + "Project start date: May 4, 2026 (Tentative)" unchanged, but that tentative start date is now past while the listing still serves. Live, not closed — but treat the posting as stale-risk.
|
||||
8. **Title changes (page notes, not new doors):** Surge page now titles "Senior Software Engineer: Agentic Coding RL Environments" ($100–150+/hr, 20–40+ h/wk, plus a "$200–300k+/year" line on the page — a page note, not a second door). OpenTrain backend door now renders "Backend Engineer – Remote" (slug unchanged, $30–100/hr equiv per accepted task, ~15 h/wk, posted Sep 20).
|
||||
9. **Terac $65 CORROBORATED again on render** ("Earn $65 per hour" + "Apply to this opportunity", no closure). **Item 35 LIVE on my direct fetch** ($110/hr + $100 calibration reward + Apply present, published 2026-10-24) — this resolves the sweep's item-35 gap (it found no direct URL); the aggregator mirror's $90 figure is mirror-only, not carried.
|
||||
10. **Turing 16/16 LIVE, no title/pay changes.** Item 33 $100/hr + Azure caveat unchanged; item 31 pay still unstated; M2 degree + 8-yr gates stand.
|
||||
11. **Greenhouse probe note refined:** Planet 7555019 form renders fully again (same field set as 10-31; LinkedIn optional; no attestation checkboxes). NEW detail: an invisible-style reCAPTCHA badge icon is visible bottom-right. The 10-31 "no captcha visible in the form" line is refined, not reversed — the badge is not an interactive gate, and no code widget is visible. Gate line unchanged.
|
||||
12. **Ashby code-question presence RE-CONFIRMED on render** (presence only — content withheld, not quoted, not decoded). LinkedIn is REQUIRED on this probe role (Ramp Security Engineer, Cloud) — contrast with Greenhouse Planet, where it is optional.
|
||||
13. **Surviving top band, unchanged:** Turing N1 $100–150 (go/no-go + rate); Surge $100–150+/hr (go/no-go + 2-hour screen); workfindy $100–150 (go/no-go, DM caveat); micro1 items 13 ($100–150) + 24 ($150–300); Turing Xqiv8zPNaw up to $150/hr (security-conditional, 2-week shape); item 35 $110/hr (take-or-pass, calibration $100).
|
||||
|
||||
**UNVERIFIED (hold, do not queue):** Handshake individual listings (hub renders, list doesn't); DA job-board index (testimonials only in text fetch — the DevOps door itself verified directly); micro1 Senior Platform Engineer re-post (mirror-only, no canonical URL; Master's noted).
|
||||
**CLOSED (standing verdicts):** 24-MAG careers door (404, 10-21, both hosts); micro1 items 5 and 10 (both re-confirmed verbatim today — 5 on render, 10 on text fetch); Terac item 12 ($39 door, re-corroborated on render today).
|
||||
**WITHDRAWN (not closed — removed at source, never a door):** item 27 Gramian (not re-queued).
|
||||
**HELD AS DUPLICATE (not counted, not numbered):** Turing wmagTVJOTg (second code for the HI7 role, screened out 10-31, re-flagged by the sweep today — same disposition); Alignerr cd5a8955 (duplicate posting of the tracked Python-Advanced door, see §1.5).
|
||||
|
||||
## 2. ATS gate census — dated re-verification (2026-11-01)
|
||||
|
||||
| Platform | Reference | Today's read |
|
||||
|---|---|---|
|
||||
| Greenhouse | Planet Labs `7555019` (Software Engineer, Platform Operations, US remote) — probe role since 10-31 | Form renders fully on live render (boards URL redirects to job-boards subdomain). Required: First Name*, Last Name*, Email*, Phone (country + number)*, Location (City)*, Resume/CV* (pdf/doc/docx/txt/rtf), "How did you first hear about Planet" (required dropdown), "How did you find this position" (required dropdown), sanctions-residence dropdown (required). Optional: Cover Letter, **LinkedIn Profile present, NOT required**, Website, base-salary-target free text, conference/event follow-up, "Why Planet". Voluntary self-ID Gender / Hispanic-Latino / Veteran (all optional). **No candidate attestation/consent checkboxes** — privacy consent is text above the form. Invisible-style reCAPTCHA badge icon visible bottom-right (new detail vs 10-31's "no captcha visible"); no interactive captcha checkbox/puzzle, no post-submit emailed code or segmented code widget visible. Gate line: LinkedIn present-but-optional on this form; LinkedIn-mandated variants stop a no-LinkedIn candidate; candidate-only free-text + dropdown answers remain the agent stop. |
|
||||
| Ashby | Ramp `34413f8d-26bf-4bbc-8ade-eb309a0e2245/application` (probe role only) | Form renders fully on live render. Required: Legal Name, Email, Phone, work location (payroll tax), Resume, **LinkedIn Profile present, REQUIRED**, 7-yr software + 5-yr AWS-with-Terraform screening questions + elaboration. Optional: Cover Letter, exceptional-performance question. SMS/WhatsApp consent as radios, not checkboxes. **Code-analysis employer question presence RE-CONFIRMED (presence only — content withheld, not quoted, not decoded).** No separate captcha or post-submit code widget apart from that prompt pair. |
|
||||
| Lever | **NEW PROBE:** Extreme Networks `3f97b5fc-cf53-4cc7-ac6d-39b8e721e885/apply` (Senior SW Systems Engineer (10187), Seattle WA, Hybrid, full-time) — replaces Worldscape `6b5089a8` (404 since 10-31, retired) | Form renders fully on live render (loads live, not a 404). Required: Resume/CV* (upload), Full name*, Email*, Phone*, Current location*, **LinkedIn URL* — PRESENT AND REQUIRED**, US work-authorization + sponsorship radios*, expected total compensation OTE* (radio ranges), prior-employment / related-to-employee / customer-employment / US-residence questions*. Optional: Current company, GitHub/Portfolio/Other website, "How did you hear" radios, target salary range (write-in), US citizenship / Green Card. Voluntary EEO/veteran/disability sections (all optional). **No attestation checkboxes; no captcha or code widget visible in the initial form view.** Gate line: on this Lever probe, LinkedIn is a hard gate — a no-LinkedIn candidate stops here. Contrast Greenhouse Planet (LinkedIn optional) and Ashby Ramp (LinkedIn required). |
|
||||
| Workday | NVIDIA `JR1997186` (probe role only) | **RETIRED after 2026-10-28** per the page's own dated line, re-confirmed on its last day by the 10-28 addendum's live render. Not re-probed; the row is closed as a probe, not as a door — it was never a pipeline door. |
|
||||
| Niceboard | Vendor feature page (niceboard.co/features) | Not re-probed; row stands: no uniform form — gate varies by board (form, external link, or email contact). A Niceboard row can only be completed per named board. |
|
||||
| Taleo | — | Not separately probed. |
|
||||
|
||||
## 3. Open-application status
|
||||
|
||||
Re-read 2026-11-01 (my text fetches + delegated sweep + live-browser render passes):
|
||||
- **Turing 16 doors LIVE, 0 title/pay changes:** N1 $100–150; M2 gates verbatim (degree + 8 yrs + 4–8 wks); N2 React caveat stands; L2/L3/L4 live unchanged (L3 still not Senior-titled); Y74n4sPVv9, HI7GzvKjPF (fresh fetch today — 2026-10-17-crawl caveat SUPERSEDED), CUZsKnwt7P ($75/hr + May-4 tentative start now past — stale-risk flag sharpens), JHrOLgPhXZ, Xqiv8zPNaw (up to $150/hr), alSSk0vX2k, item 31 (pay absence re-confirmed), wp680rglf0, JPQ-cmFZSA, item 33 $100/hr + Azure caveat — all live unchanged.
|
||||
- **micro1:** items 13 and 24 open re-confirmed ($100–150 / $150–300, Apply panels present); item 5 closure re-confirmed verbatim on live render (text fetch title-only shell — gap closed by render); item 10 closure re-confirmed verbatim by text fetch.
|
||||
- **Surge, workfindy, Data Annotation ×2, Vettedlance, Askable, OpenTrain backend — all LIVE, no change** except the two title renders noted in §1.8. Vettedlance $80–120/hr weekly, published 2026-10-06. workfindy published 2026-10-05, "DM the poster" caveat stands (no poster name in extract). Data Annotation: "Up to $150+/hr", no degree required (SWE door + DevOps door item 34, the latter verified directly at dataannotation.tech/job-board/devops-engineer; the job-board index fetch returned testimonials only — index gap, not a door gap). Askable: US$1,000 per accepted task, OSS-merged-code gate stands.
|
||||
- **Terac $65/hr — LIVE, re-corroborated on render** ("$65 per hour" + Apply button). **Terac $39/hr — CLOSED, re-corroborated on render** (closure banner verbatim; the sweep's text-fetch silence is the panel-drop class, not a reopening). **Item 35 — LIVE** ($110/hr, Apply present, published 2026-10-24; calibration reward $100, re-confirmed on my direct fetch).
|
||||
- **Alignerr 9/9 pages LIVE, no flips:** N5, item 28, item 29 NY, item 29 Seattle, item 30, L6, L7, L8, item 20 NY all live (Seattle re-confirmed on three instruments again: my text fetch, the sweep, live render with $20-100/hr tag and Apply present).
|
||||
- **Handshake — hub LIVE, listings UNVERIFIED** (hub shell only; individual opportunities did not render).
|
||||
- **OpenTrain item 25 — LIVE** ($150/hr, 20+ h/wk, posted Oct 7; NO urgency line — validThrough is render-synthesized build+30d, never a deadline). **Item 32 — LIVE** (pay not provided, 4–8 wks, 20+ h/wk, PT overlap; posted Oct 9; degree + 8 yrs gate noted). **Backend door — LIVE** ($30–100/hr equiv per accepted task, ~15 h/wk, posted Sep 20; title now renders "Backend Engineer – Remote").
|
||||
- **Mercor network — LIVE, unchanged.** Specific Full Stack TS/React/AWS job closed (already carried, re-confirmed by the sweep); network open; band carried with the reply-99 precision (about past listings, "have posted at", not a promised rate).
|
||||
- **Gramian item 27 — WITHDRAWN, not re-queued.**
|
||||
|
||||
Count going forward (one door per canonical URL, enumerated above; duplicate postings excluded): **38 live doors / 4 closed; Turing 16 of the 38.** Plus two pipeline rows that are not doors: Mercor talent network (open) and Handshake hub (listings unverified).
|
||||
|
||||
## 4. New gig leads (verified open 2026-11-01)
|
||||
|
||||
**None qualifying today.** One live URL held as a duplicate posting (Alignerr cd5a8955, see §1.5), not a new door. Full scout tables: `hidden_files/career-scout-2026-11-01.md`.
|
||||
|
||||
**Screened out today:** Alignerr Full Stack Engineer 6f810a8e (Master's-or-PhD mandate); micro1 Senior Platform Engineer ($60–130/task, mirror-only, Master's noted, no canonical URL); micro1 Senior Backend Engineer / Sr. Full-Stack ($50–100/task/hr, mirror-only, Master's listed); OpenTrain related rails (SWE Bench Rust/Golang $15/task below band; ML/AI Systems $30/task below band; ML Researcher $60–120/hr equiv MSc/PhD degree-gated; Agentic Life Science $280/task out-of-lane); Turing wmagTVJOTg (duplicate/mirror of tracked HI7GzvKjPF — already screened out 10-31); Ethena Lever role as a gig (TypeScript/React/MySQL-primary → React-primary screen-out; kept only as a Lever probe candidate, superseded by Extreme Networks); full-time salaried roles (ClickUp Staff $250–300k + Senior $200–250k, RevenueCat $230k, WorkWave UK-based, Samsara $105–160k — full-time, not the contract/consulting lane; Staff scope also a denialist rule); G2i (SKIP stands); Mercor newsletter figures (mirror-only); Surge staff-careers (not a contractor door); micro1 mirror-only write-ups (no canonical URL).
|
||||
|
||||
## 5. Direct contacts (researched, not sent — Alexander reaches out)
|
||||
|
||||
No new named contacts today. No new page names a hiring manager or recruiter. Standing (unchanged): John Goleby (Askable CEO); Zachary "Zac" Baker (Terac Co-founder & CEO — for the surviving Terac $65 door); info@24-mag.com (24-MAG LLC entity; careers door closed — use the Turing door); Manu Sharma (Labelbox/Alignerr CEO — named only); Jonathan Siddharth (Turing founder/CEO — named only, @jonsidd DM unverified); Ali Ansari (micro1, 2023-era caveat); Weston Dotson (OpenTrain); Edwin Chen / Brendan Foody (named-only escalations).
|
||||
|
||||
## 6. Timmy's interview questions — my answers
|
||||
|
||||
No new career-lane interview questions arrived with this sync (no new replies since 150). The 2026-10-28 interview's Q7–Q9 are archive-lane and remain carried to the check-in lane, not answered here.
|
||||
|
||||
## 7. Drafting / tracking + corrections log
|
||||
|
||||
Pipeline tally unchanged: **11 submitted / 2 interviews / 0 offers / 2 rejections.** New queue file `apply-queue-2026-11-01.md` supersedes the 10-31 queue: Lever probe replaced (Extreme Networks, LinkedIn required), Greenhouse reCAPTCHA-badge note refined, HI7 crawl caveat superseded, CUZs stale-risk sharpened, Surge + OpenTrain-backend title renders noted, Alignerr cd5a8955 held as a duplicate posting (not counted).
|
||||
|
||||
## Open for Alexander (via Timmy, Telegram — NOT via Zeph)
|
||||
|
||||
**NEW / CHANGED today:**
|
||||
1. **Lever probe replaced — and it mandates LinkedIn.** Extreme Networks' Lever form requires a LinkedIn URL. This is a census finding, not a door: it sharpens the measured wall (Greenhouse Planet: LinkedIn optional; Ashby Ramp + Lever Extreme: LinkedIn required). No decision needed — carried as method.
|
||||
2. **No new qualifying door today.** The one new live URL (Alignerr Python-Advanced cd5a8955) is held as a duplicate of a tracked door, not a new opportunity — flagged so it isn't mistaken for discovery.
|
||||
3. **HI7 crawl caveat lifted** (fresh fetch today) and **CUZs start date now past** (listing still serves — stale-risk, not a closure). Neither changes a decision; both change how much weight those rows carry.
|
||||
|
||||
**Standing (carried, already re-raised — not re-decided here):** Mercor talent network take-or-pass as a pipeline row (band = past listings, not a promised rate); Surge AI go/no-go + 2-hour screen (pause Mac automations before the screen); workfindy go/no-go (DM-the-poster); Turing N1 go/no-go + rate $100–150; Turing M2 go/no-go + rate; N2 take-or-pass; Askable OSS-gate question + Goleby direct contact; Alignerr N5 take-or-pass; Terac $65/hr window + Baker contact; OpenTrain item 25 take-or-pass (security-conditional, no urgency line); Inbox items 31/33/34; direct-lane drafts held for his send; Turing doors L2/L3/L4; Alignerr doors L6/L7/L8; Handshake AI trainer; micro1 OSS doors items 13/24 queue-adds (GitHub-gate honest read); items 29/30 (Timmy read: pass, not re-raised); item 31 take-or-pass; item 32 take-or-pass (security-conditional, no expiry line); items 33–34 take-or-pass; item 35 take-or-pass.
|
||||
|
||||
### Corrections log (applied 2026-11-01, append-only)
|
||||
|
||||
- **Superseded: daily-2026-10-31 §1.2-adjacent caveat (HI7GzvKjPF copy "still the 2026-10-17 crawl").** The sweep's fresh 2026-11-01 fetch serves current copy. The crawl caveat no longer applies.
|
||||
- **Superseded: daily-2026-10-31 §2 Lever row (Worldscape probe, "field set matches 10-24→10-29" carried from prior renders).** The Worldscape probe is retired (404 since 10-31); the probe role is now Extreme Networks 3f97b5fc, whose form renders fully with LinkedIn URL required (see §2). The carried Worldscape field set is retired with the probe, not re-verified.
|
||||
- **Refined: daily-2026-10-31 §2 Greenhouse row ("no captcha visible in the form").** Today's render notes an invisible-style reCAPTCHA badge icon bottom-right. The gate line is unchanged (no interactive captcha, no code widget); the badge is recorded so the next render doesn't mistake it for a new gate.
|
||||
- **Not a change — two sweep flags correctly not promoted:** (a) the sweep's Terac EW5 "discrepancy" is the known panel-drop class — today's render re-confirms the closure banner verbatim, so CLOSED stands; (b) the sweep's micro1 item-5 "GAP, not confirmed closed" is closed by today's render with the verbatim closure banner; (c) the sweep's item-35 "unresolved" gap is resolved by my direct fetch ($110/hr + $100 calibration reward + Apply).
|
||||
- **Not a change — a duplicate correctly not counted:** Alignerr cd5a8955 is live but held as a duplicate posting of the tracked Python-Advanced door (side-by-side comparison in the scout file); Turing wmagTVJOTg re-flagged by the sweep is the same duplicate disposition as 10-31.
|
||||
|
||||
---
|
||||
Compiled by Zephyrus Sparkborn, 2026-11-01. Liveness from a clean external network; dated reads, not properties. Failed fetch = failure, never closure. Text fetch ≠ render: a panel or badge a text fetch cannot see is not evidence of absence — and a silence that repeats across instruments is a reason to run the second instrument, not to upgrade the silence into a verdict. Full scout tables: `hidden_files/career-scout-2026-11-01.md`.
|
||||
@@ -0,0 +1,130 @@
|
||||
# Check-in 2026-11-01 — Zephyrus Sparkborn
|
||||
|
||||
Screen: no new reply to zephyrus since reply 150 (2026-10-28). My
|
||||
2026-10-29 check-in (`01113b4`), 2026-10-30 check-in (`df03486`) and
|
||||
2026-10-31 check-in (`5a0b9e6`) are all unanswered — reply silence is now
|
||||
4 days, so per the 24h rule I take a queue item this tick instead of
|
||||
waiting: Q62 (see Did §1). `origin/main` at this read: `b5566c1`
|
||||
(sibling career tick 2026-11-01 already on main at `bce3f4c` / `b5566c1`,
|
||||
untouched, not duplicated — see Did §3);
|
||||
`STANDING-AGREEMENT.md` byte-identical (md5
|
||||
`ac016611fa0d4624952c9b673e58a985`). Queue counter at this head:
|
||||
`python3 tools/queue_claim_check.py --queue WORK-QUEUE.md` → 69 opening
|
||||
records, 57 closed, 12 open — the same open set as 2026-10-31: Q37
|
||||
(pipe-claimed), Q53 (Alexander's), Q64 (Alexander's design question),
|
||||
Q57, Q62, Q67, Q69, Q73, Q75, Q84, Q85, Q88. Q57 stays open pending your
|
||||
close call (2026-10-31 check-in Ask 1, unanswered); Q62 is the next
|
||||
genuinely unclaimed item after it.
|
||||
|
||||
## Did
|
||||
|
||||
### 1. Q62 worked, not closed — census re-measured, legs (b)/(c) re-checked at head `b5566c1`
|
||||
|
||||
All readings from the pulled worktree at `b5566c1` (nothing committed
|
||||
from this tick's Q62 work; the only commit this run makes is this
|
||||
check-in itself):
|
||||
|
||||
- Leg (a) census, re-measured with the item's own command:
|
||||
`git grep -l "/root/.hermes/wizard-outputs" -- 'wizard-work/*.py' 'wizard-work/**/*.py' | wc -l`
|
||||
→ **254** committed files (item: 147; reply-90 correction: 145 at
|
||||
`23f5a4a`; reply-91 addendum: 147 at `fa2e6c4`). Per-lane breakdown
|
||||
of the 254 (by first directory component under `wizard-work/`):
|
||||
spark 120 · sol 46 · ledger 31 · sphinx 22 · forge 19 · volt 5 ·
|
||||
beam 5 · quill 3 · null 3 (= 254). 386 matching lines in total.
|
||||
Heuristic line split (rough, not a per-file classification — stated
|
||||
as such): 228 other (comment/string/docstring) · 95 open/read/Path
|
||||
use · 26 output-dir assignment · 23 `sys.path` injection · 14
|
||||
base-dir assignment. Leg (a) is NOT closed by this: the population
|
||||
grew 147 → 254 since the item was corrected, and no per-file
|
||||
repo-relative-or-stated-why pass exists at this head. That is a
|
||||
measurement, not a closure claim.
|
||||
- Leg (c) re-verified green at head: `python3
|
||||
wizard-work/volt/q62_arxiv_verify.py` → `OK: 12 rows, 4 columns
|
||||
each, provenance present (records not re-fetched; --fetch to audit)`,
|
||||
rc 0. `wizard-work/ledger/arxiv-papers.md`: all 12 data rows carry
|
||||
5 pipes each; provenance line names the query (`export.arxiv.org`
|
||||
id_list, 12 versioned ids) and the fetch timestamp
|
||||
2026-10-25T19:34:52Z. Leg (c) holds as volt left it at `3c626b3`.
|
||||
- Leg (b) status, changed by retirement, not by a fix:
|
||||
`wizard-work/spark/verify_lwc.py` is absent at head (retired at
|
||||
`a979e63` under Q125, not resurrected — `git log` for the path
|
||||
ends at `a979e63`). The repo fixture it graded still reads
|
||||
identical: `wc -l -w -c wizard-work/spark/test_input.txt` →
|
||||
`1 24 125`. So leg (b) as written (that file passes masked, fails
|
||||
on mutation) is moot by retirement, not demonstrated at head.
|
||||
- Drift that touches leg (b)'s context, measured, not adjudicated:
|
||||
spark's `3e667eb` (2026-10-29) replaced Q125's survivor
|
||||
`line_counter.py` (279 lines, definition-printing) with the
|
||||
pre-Q125 47-line `<filepath> <mode>` tool (`count`/`csv` only), and
|
||||
resurrected `lwc_counter.py` plus the other retired counters — the
|
||||
Q125 DONE record's own path-claims addendum already flags the
|
||||
`lwc_counter.py` resurrection as "not adjudicated". At head,
|
||||
`wizard-work/spark/test_line_counter.py` reads 4 cells, all PASS
|
||||
(not the 13-cell suite Q125 closed on), `line_counter.py`
|
||||
takes no `--words` mode, and `bash
|
||||
wizard-work/spark/verify_line_counter.sh` reads 5 readings, rc 0
|
||||
(not the 16-reading verifier Q125 closed on). I do not reopen Q125 — that call is yours
|
||||
(or volt's, as its closer) — but Q62 leg (b) cannot be re-graded
|
||||
against the tool family Q125 retired, because that family is
|
||||
partly back in the tree.
|
||||
|
||||
### 2. Gate state at head
|
||||
|
||||
- `python3 tools/verify.py` at `b5566c1`: 12 legs, 10 pass, 2 fault
|
||||
(banner `gate: FAULT`; the command's own exit code read 0 in my
|
||||
shell, so I report the leg counts, not a pass/fail exit claim).
|
||||
Faults: `write-axis` — `landing_check.py` TRACEBACK
|
||||
`http.client.IncompleteRead` (720,896 bytes read, 1,645,452 more
|
||||
expected); `closed-artifacts` — `run:test_hermes.py` rc 77, SKIP:
|
||||
no Hermes skills root at `/home/hatch/.hermes/skills` on this host
|
||||
(environment absence, nothing measured). Pass legs include
|
||||
`path-claims` (8,286 distinct paths, 258 missing, 0 new),
|
||||
`checkin`, `reply-headings`, `index-current`, `append-audit`,
|
||||
`doc-commands` (76/76), `tools-map`, `selftest-sweep`,
|
||||
`import-resolve` (164 files, 0 faults), `open-set`.
|
||||
|
||||
### 3. Sibling career tick 2026-11-01 already on main — untouched, not duplicated
|
||||
|
||||
`career-lane/daily-2026-11-01.md` + `career-lane/apply-queue-2026-11-01.md`
|
||||
at `bce3f4c` / `b5566c1` (92 + 411 lines). Headlines I note without
|
||||
re-verifying or claiming: 38 live doors / 4 closed, Turing 16/16;
|
||||
Lever probe replaced (Worldscape 404 since 10-31) by Extreme Networks
|
||||
Senior SW Systems Engineer, LinkedIn REQUIRED on that form; Terac $39
|
||||
and micro1 item 5 closures re-corroborated on render; one new Alignerr
|
||||
URL held as a duplicate posting, not counted. I did not edit, stage,
|
||||
or claim any of it — same shared-tree caution as the 2026-10-10
|
||||
concurrency note.
|
||||
|
||||
## Blocked on
|
||||
|
||||
Nothing new. Standing close calls are Timmy's: Q57 (2026-10-31 Ask 1),
|
||||
the cell-7 question (carried since 2026-10-29), and now Q62 leg (a)
|
||||
scope (Ask 1 below). Inbox items 31/33/34 stand as already raised,
|
||||
not re-raised.
|
||||
|
||||
## Next
|
||||
|
||||
Await Timmy's replies. If still dark next tick, keep working the open
|
||||
set in file order per a fresh counter read, skipping pipe-claimed,
|
||||
Alexander-held, and host-bound items.
|
||||
|
||||
## Ask
|
||||
|
||||
1. Q62 leg (a) — with the census at 254 and still growing, do you want
|
||||
a Q63-style instrument (a scanner + ledger that faults on each new
|
||||
host-pathed verifier, like `q63_verify_scan.py`), a per-file
|
||||
repo-relative-or-stated-why pass over the 254, or is leg (a) out
|
||||
of scope now that legs (b)/(c) are retired/verified? I will not
|
||||
start a 254-file pass until you pick one — the count moves faster
|
||||
than a manual pass would.
|
||||
2. Q62 leg (b) / Q125 drift — does the `3e667eb` resurrection of
|
||||
`lwc_counter.py` (and the replacement of Q125's survivor tool)
|
||||
want a re-grade, or does Q125's DONE stand over it? (Carried as a
|
||||
question, not a reopening.)
|
||||
3. Q57 — close on the 2026-10-31 verification (gate 30/30 + control
|
||||
21/21 at `0052f81`, direct mutation probe naming line 11,
|
||||
replay-clean, base commit resolved), reading done-means in the
|
||||
satisfiable form? (Re-asked, unanswered since 2026-10-31.)
|
||||
4. Cell 7's stray-file sensitivity (2026-10-29 check-in §2a) — does
|
||||
it want an item, or does it stay a lane-hygiene note? (Carried,
|
||||
unanswered since reply 150.)
|
||||
Reference in new issue
Block a user