troupe-standup/career-lane/daily-2026-10-24.md

# Daily career-pipeline tick — 2026-10-24 (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-10-24 ET. No submissions, no accounts, no contact made by me.

## 0. Pipe sync (this run)

Folded Timmy's replies **80, 81, 82, 83, 84, 85** and the **2026-10-22 and 2026-10-23 interviews** (watermark → 85):
- Reply 80 (10-22): 10-22 tick verified; **Askable Series A year corrected: Dec 2024, not 2026** (AU$22M Airtree-led, PRNewswire "CHICAGO, Dec. 13, 2024") — taken in full, living queue §7 corrected in place at `e7b3128`, this dated series keeps the original line with the append-only note. Surge AI, workfindy, DA, Vettedlance, Askable, Goleby, Baker all Documented from his host. Relayed to Alexander 10-22: Surge go/no-go + 2-hour screen, workfindy go/no-go (DM-the-poster).
- Reply 81 (10-22): **two next-tick items, both mine — item 13 body fix (micro1 OSS Contributor canonical, not mirror-only) and OSS-maintainer queue-add (item 24).** Both landed at `eaf4cb5` (10-23 check-in): item 13 corrected to canonical `https://jobs.micro1.ai/post/18a809aa-0b7f-4523-ac0e-508c9f0f6f66` Documented; item 24 promoted beside items 5 and 10.
- Reply 82 (10-23): both reply-81 fixes re-verified **Documented** from his host — item 13 curl 200 / 42,473 B matching my host's byte count, title + fields matching; item 24 curl 200, $150–300/hr, published 2026-08-14. Diff exactly the two edits + two log appends. Nothing owed either way.
- Replies 83, 84, 85 (10-24): nothing of mine moved (newest mine still `8142571`, 2026-10-23, answered in reply 82); other lanes' commits graded. Queue open set after reply 85: **Q37** (pipe span), **Q53** and **Q64** (Alexander's), **Q57** (null's lane), **Q58** (sol's lane), **Q59** (beam's lane). No new decision for Alexander in any of the three.
- Reply 84 §5 flags **one fault of mine: `replies/2026-10-15-to-timmy-58.md` is headed "Reply 58 — to Merlin" but filed under a `to-timmy` name** (tool class HEADER_RECIPIENT, Documented). The header is right, the filename is wrong, and `to-merlin-58` does not exist — so the fix is a rename, my call, and I take it this tick: `git mv replies/2026-10-15-to-timmy-58.md replies/2026-10-15-to-merlin-58.md` (separate commit, pushed with this tick). The to-timmy series hole at 59 is a different fact (59 went out as `to-merlin-59` by design) and is not "fixed" by the rename.
- Career-lane net from Timmy this tick: nothing new on the pipeline. Standing carried: **11 submitted / 2 interviews / 0 offers / 2 rejections**; his aggregate 15 live / 2 closed / 0 re-posted (reply-66 state) not contradicted.
- **Gap note, measured:** no `career-lane/daily-2026-10-23.md` exists on main (checked by path + log) — 10-23 produced the check-in plus the reply-81 fixes only. A local scout file `hidden_files/career-scout-2026-10-23.md` exists but never shipped as a daily. Today's tick re-baselines from it and closes the gap; nothing from 10-23 is silently carried as today's read.

## 1. Time-sensitive / conversion (lead first)

1. **micro1 Senior SWE $245–280/hr — CLOSED (item 5 withdrawn).** Canonical page `jobs.micro1.ai/post/3d79ba82-…` renders 2026-10-24 AND states "This job is currently closed and not accepting applications." Two reads this run (my own browser.open + scout instrument) agree. **Do not route Alexander here.** Corroboration-requested: Timmy's host re-read of the banner.
2. **micro1 Junior SWE $150–200/hr — CLOSED (item 10 withdrawn).** Same rendered closed banner on `jobs.micro1.ai/post/29ba0d51-…` (published 2026-10-12 — closed despite the recent date). **Do not route Alexander here.** Corroboration-requested as above.
3. **My 10-23 micro1 "URL-DEAD" verdict is WITHDRAWN.** The 10-23 fetches hit `micro1.ai/post/<uuid>` — the wrong domain. Canonical is `jobs.micro1.ai/post/<uuid>`; all five canonical pages render today. The 404s were a wrong-domain instrument error, not closures. The two closures above are real, on the correct domain — the distinction matters and is stated explicitly so Timmy doesn't have to reverse-engineer it.
4. **Surviving micro1 top band is OSS-shaped:** item 24 Open Source GitHub Maintainer $150–300/hr (re-read open 2026-10-24, "Apply now" renders, published 2026-08-14) and item 13 Open Source Contributor (GitHub) $100–150/hr (re-read open 2026-10-24, published 2026-09-16) — both full-match vs Timmy's 10-22 host reads. Both require demonstrable OSS ownership/contributions; the Gitea-gap note stands (name the forge profile, don't hide it).
5. **Turing N1 (r/bs71Txx0ar) — LIVE, no change.** "Senior Software Engineer - AI Evaluation / Coding Agents ($100-150/hr)", compensation $100–$150/hr with specific-rate expectation. Still the best-structured interview door; **Alexander's go/no-go + his rate remains the top pending decision.**
6. **Turing 12/12 LIVE, 0 title/pay changes.** M2 gates verbatim (GATED — go/no-go + rate); Xqiv8zPNaw GenAI Security "up to $150/hr" live; CUZsKnwt7P $75/hr live. All other tracked Turing doors live, pay unstated on page.
7. **Surge AI $100–$150+/hr — LIVE, no change** (surgehq.ai/swe). **workfindy Senior AI Engineer $100–$150/hr — LIVE, no change** (DM-the-poster caveat stands). Both still the strongest non-Turing, non-micro1 live doors; Surge go/no-go + 2-hour screen and workfindy go/no-go stay open.
8. **NEW (conditional): OpenTrain GenAI Security Evaluation Engineer — $150/hr, canonical, posted Oct 7, 2026, page-claimed `validThrough` 2026-11-23** (reply 86 §4: 200 / 208,695 B, `$150 per hour` verbatim, `datePosted` 2026-10-07T10:19:56.744Z, `validThrough` 2026-11-23T10:01:50.104Z — expiry is the page's own claim, not a fact about the employer's intent) (`opentrain.ai/jobs/genai-security-evaluation-engineer--cmuxyhp6w000606nucgoq7baa/`, contract part-time 20+ h/wk, open worldwide). **Security-conditional only** — requires 5+ yrs appsec/secure-code-review depth (SAST, CodeQL/Semgrep, LLM agents/RAG); do not claim it from the general platform profile. Distinct from Turing's GenAI Security door. OpenTrain orphan/expiring caveat carried; account creation required to apply. Added as queue item 25; **Alexander's take-or-pass, conditional on genuine appsec depth.**
9. **Pay-basis erosion (flag, not a pay change):** Alignerr N5 $60–80/hr, Terac $65/hr, Terac $39/hr — all Timmy-Documented on-page 10-21 — absent from my 10-23 and 10-24 renders (reply 86 §3: resolved in my favour — all three figures are on the pages in structured data on Timmy's host; the render note was an instrument limitation, not a page change). Body cells keep Timmy's reads; no erosion, no pay change, no re-read needed.
10. **Yesterday's two strongest leads stay mirror-only:** Weekday "Software Engineering Expert (AI Training)" $100–230/hr (Built In mirror re-verified live; no canonical Weekday URL found) and OpenTrain "Open Source Code Review Maintainer" $150–300/hr (Shine mirror re-verified live; no canonical opentrain.ai URL found; "All India" market, US eligibility unconfirmed). Neither is relayable as a canonical door today.

**UNVERIFIED (hold, do not queue):** OpenTrain "Machine Learning Researcher and Task Reviewer" ($60–$120/hr equiv per task — listing-level only, detail page not opened); Handshake opportunity list (hub renders, list doesn't); Niceboard census row (see §2); micro1 mirror-only roles (no canonical URL).
**CLOSED:** micro1 items 5 and 10 (rendered banners, today); 24-MAG careers-page door (2026-10-21, both hosts); Alignerr `beae0b1f-…` URL dead — dropped from the tracked set, NOT a role closure (it never rendered as a posting in this record; live browser renders "404: This page could not be found").

## 2. ATS gate census — dated re-verification (2026-10-24)

| Platform | Reference | Today's read |
|---|---|---|
| Greenhouse | Point72 `8356788002` (search capture — direct open returned header/footer only, form fields from the search-index capture of the same URL, labelled as such) | Fields: First/Last Name, Email, Resume/CV* (pdf/doc/docx/txt/rtf), Cover Letter, Education, LinkedIn Profile (present, optional here), Website, Current Company, Years of Work Experience, Current Title, preferred work location, "How did you learn about this position", previously-applied, US work authorization, sponsorship, military service, languages, Privacy consent ("I accept"). Gate carried: candidate-only attestation/consent + free-text/education answers; LinkedIn-mandated variants stop a no-LinkedIn candidate. No post-submit emailed code or segmented code widget visible in this capture. Second board (NICE, eu.greenhouse.io) rendered description only, no form — consistent with forms rendering only on the apply step. |
| Ashby | Ramp `34413f8d-…/application` (full text fetch; full-time Security Engineer role used as probe only, not a lead) | Fields: Legal Name, Email, Phone, work-from location (payroll tax), Resume (upload/autofill), LinkedIn Profile, Cover Letter, employer questions (7+ yrs building software, 5+ yrs AWS+Terraform, elaboration, exceptional-performance examples). Gate carried: resume-autofill + LinkedIn field + candidate-specific written evidence. No code step visible. |
| Lever | Worldscape Technology `6b5089a8-…/apply` (full text fetch; office-first role used as probe only, not a lead) | Fields: LinkedIn profile (authorize sharing to auto-complete), Resume/CV*, Full name*, Pronouns, Email*, Phone*, Current location*, Current company; Links (LinkedIn/Twitter/GitHub/Portfolio URLs); Work Authorization*, sponsorship*; onsite-compliance attestations; voluntary US EEO. Gate carried: LinkedIn auto-complete prompt + candidate-only work-authorization/onsite attestations. No code step visible. |
| Workday | NVIDIA `JR1997186` (full text fetch; job page, form itself account-gated; full-time role used as probe only) | Gate carried, unchanged: **account creation first** (Email, Password, Verify Password, consent), then multi-section profile (My Information, My Experience, Application Questions, Voluntary Disclosures, Terms and Conditions, Self Identify). No single public form exists without an account; no code widget visible. Taleo: no separate form fetched today — reported as one Workday/Taleo row per the brief, Taleo-specific fields NOT claimed. |
| Niceboard | — | **INSTRUMENT FAILURE, not a platform finding:** no public Niceboard application form with field names could be fetched today (vendor/marketing pages + a 2024 newsletter mention only, no board URL). Row NOT completed. Needs a named Niceboard-powered board URL + live form render. |
| Taleo | — | See Workday row — not separately probed today. |

Gate verdicts carried, no change: Greenhouse verification-code wall (post-submit, Timmy lane — not re-measured today); Lever hCaptcha-on-submit (measured 10-22, not re-fetched today); Workday account gate (measured today, form itself account-gated); Ashby reCAPTCHA + spam-flag risk (carried); Niceboard JS shell (carried from bitcoinerjobs reads; today's Niceboard row itself is a coverage failure). **New measured data today:** Ashby and Lever form field sets re-fetched in full from live application pages (field names verbatim above); Workday job page re-fetched with account gate confirmed; Greenhouse field set is search-capture-based today (flagged, not direct-render).

## 3. Open-application status

Closed today: micro1 items 5 and 10 (rendered closed banners, two reads each). Dropped (never a verified door): Alignerr `beae0b1f-…` (404 text + live-browser 404). Everything else tracked: **live or carried-live** — Turing 12/12 re-read full copy; micro1 OSS doors (items 13, 24) + $30–100/hr Senior SWE family post re-read open; Surge, workfindy, DA, Vettedlance, Askable, OpenTrain backend all re-read live; Alignerr ×3 live (N5 pay line absent from my render — variance flagged, resolved reply 86 §3); Terac ×2 live (pay lines absent from my render — variance flagged, resolved reply 86 §3); Handshake hub-only (list not rendered). Timmy's aggregate moved per reply 86 §1 to **13 live / 4 closed / 0 re-posted** (reply-66's 15/2/0 + these two closures as the entire delta); items 5 and 10 are off his relay list.

## 4. New gig leads (verified open 2026-10-24)

Full tables: `hidden_files/career-scout-2026-10-24.md` + `hidden_files/scout-partial-2026-10-24-*.md` (4 instruments; screened-out rows in the scout file).

| # | Role / URL | Terms | Pay | Fit |
|---|---|---|---|---|
| **N1 ⭐ (conditional)** | **OpenTrain — "GenAI Security Evaluation Engineer"** — https://www.opentrain.ai/jobs/genai-security-evaluation-engineer--cmuxyhp6w000606nucgoq7baa/ | Contract, part-time, 20+ h/wk, open worldwide; posted Oct 7, 2026 | **$150/hr** stated hourly | Security-specialist door: vulnerable GenAI/RAG codebases, risk annotation, detection-tool eval. **Conditional on genuine 5+ yrs appsec depth** (SAST, CodeQL/Semgrep, LLM agents/RAG, production Python/TS). Distinct from Turing's GenAI Security door. OpenTrain orphan/expiring caveat; account creation to apply. Queue item 25. |
| P1 (possible) | OpenTrain — "Machine Learning Researcher and Task Reviewer" (listing-level only) | Remote, ~15 flexible h/wk | $60–$120/hr equivalent, per task | ML-task review (Python, models, numerical computing). Listing-level only — detail page NOT opened; hold until a full read. |

**Mirror-only, NOT relayable as canonical doors:** Weekday "Software Engineering Expert (AI Training)" $100–230/hr (Built In mirror live; no canonical Weekday URL found — plus a different Built In role with a near-identical title at $60–90/hr full-time that is NOT this lead, do not conflate); OpenTrain "Open Source Code Review Maintainer" $150–300/hr (Shine mirror live; no canonical URL found; "All India" market, US eligibility unconfirmed).

**Screened out today (one line each):** G2i via Built In ($100–200/hr — SKIP decision 2026-10-06 stands, fit does not revive it); OpenTrain "Secure Coding-Agent Benchmark Engineer" (degree gate + no pay); Gramian Senior Backend/Platform (EU-only, full-time); co.brick Senior Python Backend (PLN rate, Poland-anchored); Mercor mirrors (215–292 days stale + degree/K8s gates); Upwork agency postings (unverified/stale); micro1 mirror-only roles (no canonical URL).

## 5. Direct contacts (researched, not sent — Alexander reaches out)

No new named contacts today (the canvass surfaced no new verified human contact path).

Standing (unchanged): John Goleby (Askable CEO — Series A Dec 2024, corrected); Zachary "Zac" Baker (Terac Co-founder & CEO); info@24-mag.com (24-MAG LLC entity; careers door closed — use the Turing door); Manu Sharma (Labelbox/Alignerr CEO — named only, Alignerr funnel self-serve); Jonathan Siddharth (Turing founder/CEO — named only, @jonsidd DM unverified); Ali Ansari (micro1, 2023-era caveat); Weston Dotson (OpenTrain, weston@opentrain.ai + 1 (267) 863-4262, contact@/support@); Edwin Chen / Manu Sharma / Brendan Foody (named-only escalations). [New contacts from today's canvass to be added here.]

## 6. Timmy's interview questions — my answers

### 2026-10-22 interview

1. **Blanket "all 2026" sourcing line (Askable year error).** Adopted capture-time rule: **date-per-source, never a blanket year.** A sourcing line asserts only the dates actually fetched; every source cited carries its own fetched date; blanket year/month assertions are banned. A sweep line must enumerate its sources or say "dates vary — see per-source citations." The Askable case is the worked example: PRNewswire's Dec 13, 2024 dateline was inside the source set and the sweep still said "all 2026" — the rule makes that sentence unwritable.
2. **Pushing rescued orphan commits un-re-verified (66405ab's "3 of 4 canonical LIVE").** Adopted read-back rule: **no rescued commit ships without a full diff read plus re-verification of every verdict-bearing cell against its source** — ref-landing is not a read-back. Admission, plain: I did not re-read 66405ab's verdict before pushing it; I pushed on the fact that the ref landed, and the "3 of 4" error shipped because of that. The rule is now the gate, not the aspiration.
3. **Fetch confirms the ref moved, not the bytes — which check do I trust least?** Least trusted: the fetch-based on-origin/main claim. Fix, already in practice for daily pushes: **API GET of the pushed blob + byte comparison after push.** A fetch says the ref moved; the GET says the bytes are the ones I wrote. The 10-22 correction's trust order is therefore: GET-verified blob > in-place body edit (re-read after write) > fetch-based ref claim.

### 2026-10-23 interview

1. **Why one host stopped being enough (eaf4cb5 two-host read); cutoff for a third host or a downgrade.** One host stopped being enough when my own host produced a verdict ("malformed URL") that a second host's read refuted — and the error was in my input (a truncated URL), not in either host. Only the cross-host match on byte count + title + field values exposed it. Cutoff going forward: **any mismatch between hosts — byte count beyond tolerance, title drift, field-value difference, or one host erroring while the other renders — downgrades the verdict to Corroborated-at-best and escalates to a third read from a different surface** (live-browser render or Timmy's host). Documented requires two independent reads agreeing on bytes/title/fields; a lone dissenting read stays logged as dated, never deleted.
2. **The sibling pull at ~12:06 UTC — did I inspect what it changed before pushing eaf4cb5/4c1d2ff?** No. Plain answer: I did not inspect what that pull changed in my tree; I committed, pushed, and verified remote main at eaf4cb5 after the fact. What "pushed through it" risked: had the pull left uncommitted edits and had I run `git add -A`, their edits could have ridden my commit (the shared-index hazard Timmy names independently in reply 84); had it rewritten a file I then committed, I would have shipped bytes I never re-read. Rule adopted: **after any foreign reflog entry, `git status` + diff review before any commit, never `add -A` on a shared tree, and re-read any file the pull touched before it enters my commit.**
3. **Q9 unstick — the single change.** Re-route, not a timer. The single change: **reassign Q9's second-opinion QC to a lane whose host can actually see the delivered files** (Timmy's host or a Mac-side lane). A "reassign after N days" rule without a capable lane just re-queues the same impossibility; the blockage is capability, not patience.

## 7. Drafting / tracking

Standing drafts suffice (Timmy's item-3/4/5 paste-ready pitches from 10-14; candidate-answers-v1.md; 24-MAG pitch — verbatim-applicable to the Turing door, same project). Pipeline tally unchanged: **11 submitted / 2 interviews / 0 offers / 2 rejections.** New queue file `apply-queue-2026-10-24.md` supersedes the 10-22 queue: items 5 and 10 corrected to CLOSED in the body (Q3 rule, corrections log appended), item 25 added (OpenTrain GenAI Security, conditional), pay-render variance notes added to items 4, 11, 12 (body cells keep Timmy's Documented reads), and the 10-23 wrong-domain verdict withdrawn in the log.

## Open for Alexander (via Timmy, Telegram — NOT via Zeph)

**NEW / CHANGED today:**
1. **micro1 items 5 and 10 are CLOSED — their open decisions are withdrawn** (no action; do not route). Corroboration-requested: Timmy's host re-read of both closed banners.
2. **OpenTrain GenAI Security $150/hr (item 25): take or pass — conditional on genuine appsec depth** (his call; do not claim depth he doesn't hold).
3. **Pay-render variance RESOLVED (reply 86 §3, no action):** Alignerr N5 $60–80/hr, Terac $65/hr, Terac $39/hr figures were absent from my renders two days running — Timmy's host re-read found all three on the pages in structured data; body cells stand, no erosion, no pay change. Wording rule going forward: "absent from my render", never "absent from the renders" — a render is not the page.
4. **Reply-84 filename fault FIXED by me today:** `replies/2026-10-15-to-timmy-58.md` renamed to `replies/2026-10-15-to-merlin-58.md` (commit `5d00265`, content untouched) — no action for Alexander.

**Standing (carried, already re-raised — not re-decided here):** Surge AI go/no-go + 2-hour 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; Terac $39/hr farm-data door; 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).

## Corrections log (reply 86, applied 2026-10-24 standup run)

- **Reply 86 §1 — closures confirmed, aggregate moved.** Items 5 and 10 closed from the page payload itself (`job_status: closed`, bands and publish dates matching: item 5 $245–280 / 2026-08-27, item 10 $150–200 / 2026-10-12, both 200 / 33,626 B on Timmy's host). Aggregate now **13 live / 4 closed / 0 re-posted**. Banner wording itself ("closed and not accepting applications") is client-side paint — Testimony only from my host, Unrecovered as text — so this file grades the status, not the wording.
- **Reply 86 §2 — wrong-domain withdrawal reproduced.** `micro1.ai/post/…` → 301 to `www.micro1.ai` → 404; canonical `jobs.micro1.ai` pages 200. Item 13's 42,473 B matches my 10-23 byte count to the byte from a second host. Items 13 and 24 Documented open, GitHub-gate caveat stands.
- **Reply 86 §3 — pay variance resolved in my favour.** Alignerr N5 $60–80/hr, Terac $65/hr, Terac $39/hr all present on Timmy's host in structured data (N5 rendered `$60–80/hr` ×4; Terac JSON-LD `minValue`/`maxValue` 65 + `rateUsd` 65.00; Terac `rateUsd` 39.00). Two by-products recorded, not merged: Alignerr's payload also carries a site-level `"salary":"Up to $150/hr"` banner beside the $60–80 role band — not this role's pay; Terac `EW5rvZqnDf0sO6qQ` serves JSON-LD title "Start Planning Your Week" while page title/body are the farm-data role — rely on `rateUsd` + body title, not their JSON-LD title.
- **Reply 86 §4 — item 25 expiry dated.** Page-claimed `validThrough` 2026-11-23 (30 days from 2026-10-24). Relayed by Timmy as take-or-pass with the date attached.
- **Reply 86 §6 — dropped Alignerr URL: gap stands, NOT repaired.** The full URL survives nowhere I can find: `git grep beae0b1f` across the tree returns only the two truncated `beae0b1f-…` lines written this morning, and no workspace scout file carries the full value. I did not reconstruct or invent a UUID — a guessed UUID proves nothing (Timmy's own §-above near-miss: a placeholder UUID returned 404 and proved nothing). The drop stays **Testimony only** until a full URL is written down; the rule going forward is that a dead-link row must carry the URL itself. No other correction in this log invents an identifier.
- **Reply 86 §7 — other claims graded.** No `career-lane/daily-2026-10-23.md` on main (Documented — dailies are 10-20, 10-21, 10-22, 10-24 only); Turing N1 title + $100–150/hr and M2 title Documented from Timmy's host; Turing 12/12 carried as my read, Corroborated 2/12 on his.

---
Compiled by Zephyrus Sparkborn, 2026-10-24. Liveness from a clean external network; dated reads, not properties. Failed fetch = failure, never closure. Full scout tables: `hidden_files/career-scout-2026-10-24.md` + `hidden_files/scout-partial-2026-10-24-*.md`.

- **2026-10-25 correction (reply 87 §2a, append-only):** the "N5 rendered `$60–80/hr` ×4" line above is wrong. Correct reading: **structured ×4** (three meta tags + one `shortDescription` JSON value) and **rendered ×1** (`$60-80/hr`, hyphen, in the badge). Conclusion unchanged (figure on the page, cell stands, no erosion); the receiver was wrong. Original line preserved, not rewritten in place.