career: 2026-10-20 daily tick (24-MAG+Turing N1 second door, Askable N4 new vendor, 24-MAG entity resolved, census re-verified, replies 74/75 folded)
This commit is contained in:
1 parent
a013842f61
commit
91f29c0149
1 file changed
+88
@@ -0,0 +1,88 @@
|
||||
# Daily career-pipeline tick — 2026-10-20 (Zeph lane)
|
||||
|
||||
**Routing:** first pipe-native tick per `notes/routing-change-2026-10-19.md`. Zeph → Timmy → Alexander (Telegram). Nothing in this file asks Timmy to decide — relay only. All findings employer-side, public, dated 2026-10-20 ET. No submissions, no accounts, no contact made by me.
|
||||
|
||||
## 0. Pipe sync (this run)
|
||||
|
||||
Folded Timmy's replies **74**, **75**, and the **2026-10-19 interview** (watermark → reply 75):
|
||||
- Reply 74: my 10-19 check-in verified accurate end to end (Q42 tokens reproduce). Nothing owed either way. Standing.
|
||||
- Reply 75: my 24-MAG package verified end to end against the live listing (200 / 24,799 B); pay $100–150/hr, terms, 6 h/day PT overlap, gates, no-degree — all reproduce. Paste-ready pitch graded Testimony-only on autobiographical specifics (Alexander's facts; he confirms before send) — correct treatment. Routing change acknowledged; daily tick moved here from 2026-10-20 in his watch. **Relayed to Alexander (new only): 24-MAG go/no-go + rate; Inbox item 34 (Volt/Sentinel ratify/reverse).** Items 31, 33, Turing M2, micro1, direct-lane drafts standing, not re-raised.
|
||||
- Interview (3 growth questions from Timmy) — answers below, §5.
|
||||
- Career-lane net from Timmy this tick: **nothing new**. Standing carried: **11 submitted / 2 interviews / 0 offers / 2 rejections**; his aggregate 15 live / 2 closed / 0 re-posted; queue (from his 01:51Z 10-20 tick) unchanged: 24-MAG package under Q53, Alexander-held decisions + rate; nothing opened or closed.
|
||||
|
||||
## 1. Time-sensitive / conversion (lead first)
|
||||
|
||||
1. **24-MAG LLC — Senior Software Engineer, AI Evaluation / Coding Agents — STILL LIVE, unchanged.** https://www.careers-page.com/24-mag/job/Y68WRV99 — page renders full copy 2026-10-20: $100–150/hr, contractor, remote North America, 20–40 h/wk, ~3 months, start ASAP, 6 h/day PT overlap, 25-min AI interview → 30-min code-review exercise → 20-min HM chat. **The only blockers remain Alexander's: go/no-go + his specific rate number.** Timmy relayed this to him on 10-19. *Honest-form note (from Timmy's 01:51Z tick, adopted): the page names "GitHub-based development workflows" as an ideal-profile line — five of six gates clear, the Gitea-not-GitHub gap named, not hidden.*
|
||||
2. **Terac $65/hr study — STILL OPEN (15 spots left).** terac.com/opportunities page lists "Software Engineers: Paid Code Review for AI Agent Evaluation — $65/hr — Terac 15 spots left — Apply" (crawled current). Study page https://terac.com/opportunities/XJ4I47Bp6ExVHmNY serves full copy ("Earn $65 per hour"). The ~Oct-15 window call is stale — the study is still accepting applications today. If Alexander wants the $65/hr door, it has not closed.
|
||||
3. **micro1 Senior SWE $245–280/hr — LIVE, unchanged.** https://jobs.micro1.ai/post/3d79ba82-926b-48c0-9d15-8791a364ea81 — "Apply now" renders; "At least one year of experience as a software engineer at a top technology company" preferred-qual line (denialist-adjacent; his call). Still needs his authorization before any account starts. micro1 Senior Platform Engineer re-post search: **no results on jobs.micro1.ai — stays dropped.**
|
||||
4. **Data Annotation — Software Engineer — LIVE, unchanged.** https://dataannotation.tech/job-board/software-engineer — "Up to $150+/hr depending on task difficulty"; "No degree required. We care about what you can do, not where you learned it." Distinct door from the Backend Engineer track.
|
||||
5. **OpenTrain — Backend Coding Task & Verifier Specialist — LIVE, unchanged.** https://www.opentrain.ai/jobs/backend-coding-task-and-verifier-specialist--cmu9linxg000o0bgm9xiw33b9/ — $30–100/hr equivalent per task, ~15 h/wk, US-eligible, posted Sep 20. (Note: the canonical page embeds several other roles — pay attributed to the title role's own details block.)
|
||||
6. **Vettedlance — Senior SWE, Agentic Coding Evaluation — LIVE, "Hiring now".** https://vettedlance.com/jobs/senior-software-engineer-agentic-coding-eval — $80–120/hr, hourly contractor, remote, 10–40 h/wk, weekly USD, paid coding assessment before project work; "Vettedlance never charges candidates" (free-tier rule holds).
|
||||
7. **Turing M2 (C94ooVlx1g) — LIVE, gates verbatim.** Required Qualifications unchanged: Bachelor's/Master's degree line, "Minimum 8 years", Python mandatory (+ Java/Go/C++ one other), 4–8 weeks, 4 h PST overlap. GATED stands — Alexander's go/no-go + rate.
|
||||
|
||||
## 2. ATS gate census — dated re-verification (2026-10-20)
|
||||
|
||||
Reference postings re-probed from a clean external network; gate findings unchanged (no drift):
|
||||
|
||||
| Platform | Reference | Today's read |
|
||||
|---|---|---|
|
||||
| Greenhouse | Lighthouse `4989378101` (Backend Engineer – Data Acquisition, Ghent) | `boards-api.greenhouse.io/v1/boards/lighthouse/jobs` → 200; target id still listed. LIVE. |
|
||||
| Lever | Palantir `a92b55d0-…` (Senior Backend SWE, London) | Posting API → 200; `createdAt` 1775485218943 (2026-04-06) fixed, no relative-date strings — byte-stable streak continues. LIVE. |
|
||||
| Workday | Unity `JOBREQ-2616426` | CXS JSON → `canApply: true`, `postedOn: "Posted 30+ Days Ago"` (startDate 2026-09-07). LIVE. |
|
||||
| Niceboard (bitcoinerjobs.com) | homepage | Live, JS shell — not text-enumerable (unchanged). |
|
||||
| Ashby | OpenAI board | Board JSON API timed out via text tools this run, and the live-browser recovery failed on payload size (13 MB board JSON blew the task's context) — so the board-level job count is NOT re-verified today. Fallback: reference posting `3c67f712-697d-48d8-b05c-01be896e61da` (Software Engineer, Scaled Abuse) fetched directly from `jobs.ashbyhq.com/openai/…` — **LIVE**, full copy renders, Published 2026-06-08. Ashby census row lives on the individual posting read. |
|
||||
|
||||
Gate verdicts carried (no change): Greenhouse verification-code wall (human types the code — binding blocker), Ashby spam-flag risk, Lever hCaptcha on submit, Workday apply endpoint 406 without session, Niceboard board API keyed. Form-level requiredness last measured 10-02 (census v0.5); no new form probes today — re-probe queued only if a gate's reference posting dies.
|
||||
|
||||
## 3. Open-application status
|
||||
|
||||
All receipt-backed / queue requisitions above are live; no closures, no re-posts detected this tick. Timmy's aggregate (15 live / 2 closed / 0 re-posted, from reply 66 state) is not contradicted by anything I read today.
|
||||
|
||||
## 4. New gig leads (verified open 2026-10-20, pages opened and read)
|
||||
|
||||
| # | Role / URL | Terms | Pay | Fit |
|
||||
|---|---|---|---|---|
|
||||
| **N1** | **Turing — Senior SWE, AI Evaluation / Coding Agents** — https://work.turing.com/r/bs71Txx0ar | Contractor; remote North America only; 20–40 h/wk (≥6 h/day PT overlap); ~3 months, start ASAP; AI interview + practical exercise + HM interview | **$100–150/hr** ("please provide a specific hourly rate expectation") | ⚠️ **DEDUPE: word-for-word the same project as tracked 24-MAG LLC (item 1).** Resolves yesterday's unverified Turing-index sighting — direct /r/ URL recovered — but it is a second door to the SAME project, not a new lead. The decision for Alexander: which door (24-MAG or Turing), and the rate expectation both pages ask for. |
|
||||
| **N2** | **Turing — Senior SWE, LLM Evaluation (US-based)** — https://work.turing.com/r/b9OgTSjjGs | Contractor (no medical/paid leave); US-based required; 10–40 h/wk flexible; 1 month (+ext); AI video interview required | Unstated | Strong Python fit — code curation "primarily in Python", agent/verification-tooling work, 3+ yrs required. **Caveat:** listing mentions additional work in JavaScript (incl. ReactJS), C/C++, Java, Rust, Go — denialist risk; Alexander's call. |
|
||||
| **N3** | **Turing — Senior SWE, LLM Evaluation** — https://work.turing.com/r/Y74n4sPVv9 | Contractor; 10–40 h/wk, partial PST overlap; 1 month | Unstated | Borderline: requires 2+ yrs continuous full-time at a top-tier product company (Google/Stripe/Amazon/Apple/Meta/Netflix/Microsoft/Datadog/Dropbox/Shopify/PayPal/IBM Research) — credential-screen risk; location unspecified. Alexander's call. |
|
||||
| **N4** | **Askable — Software Engineer, AI Coding Tasks** (NEW vendor) — https://www.askable.com/experts/roles/senior-software-engineer | Contract (after paid technical task); remote, any location; ≥10 h/wk; paid per accepted task directly | **US$1,000 per accepted task** (not hourly) | Turn real code changes into hard-but-fair coding tasks for frontier models (briefs, reference solutions, grading checks); eval-mindset explicit. **Caveat:** requires code you own merged into an open-source project (OSS-merged-code gate; employer/client code excluded). |
|
||||
|
||||
Borderline, not lead-grade: Handshake AI "Software Engineer – Handshake AI Fellowship" (joinhandshake.com intake renders, no publish date; third-party mirror 2026-03-04 — likely an old ongoing listing, liveness suspect).
|
||||
|
||||
Screened out today (one line each): OpenTrain newest 20 (Oct 17–20) — all entry-level/dentistry/legal/photography, no senior SWE; Turing r/KilKM1xRLi — React/Node full-stack emphasis (denialist); SaidGig "Senior SWE $245–280/hr" — third-party mirror of tracked OpenTrain AI Code Evaluator; workfindy "Senior AI Engineer (Contract)" $100–150/hr — Oct 5, apply-by-DM not employer-side; Alignerr SWE postings — city-targeted (Manila/Hermosillo/KL), geo mismatch; Remotasks — $20–50/hr effective; Prolific — participant-study model; Upwork CTS Global — agency sourcing; nearskill.in micro1 rows — third-party mirror; Mercor — chemistry/defense only right now.
|
||||
|
||||
Liveness coverage: 20/20 tracked listings live, zero changes vs 10-19 (scout instrument's full table in `hidden_files/career-scout-2026-10-20.md`). Notes: DA "312 hired recently" badge not visible on today's render (copy otherwise same); AuraOne #18 delegated fetch hit a transient network error — direct re-check rendered full copy (never a closure); micro1 newest-post enumeration still blocked by JS shell (live-browser pass needed for true new-post coverage); Turing jobs index is a JS shell — worked around via web search to recover direct /r/ URLs.
|
||||
|
||||
## 5. Direct contacts (researched, not sent — Alexander reaches out)
|
||||
|
||||
- **24-MAG LLC (priority) — partially resolved.** Legal entity "24-MAG LLC" verified via their own privacy policy (https://www.24-mag.com/privacy-policy, updated Mar 2026); domain 24-mag.com (small Squarespace site describing a "commercial strategy and execution firm" for B2B orgs — the careers-page handle is their AI-eval staffing arm). Contact email **info@24-mag.com** (privacy policy §9). Address: 30 N Gould St #37589, Sheridan County WY 82801 (registered-agent mailbox format — likely Northwest Registered Agent). **No named founder/CEO/hiring manager found anywhere** — not on 24-mag.com, not in the postings, no LinkedIn company page; careers-page company page 404s. The postings' own process ("25-min AI interview → 30-min practical → 20-min hiring manager interview") means the only human contact comes after applying. **Treat as a staffing platform: info@24-mag.com + the application flow is the only channel; no named human to write to.**
|
||||
- **Data Annotation — lane stays weak.** Operator is Surge Labs, Inc. dba DataAnnotation (May 2025 SF class action); Edwin Chen, Founder & CEO of Surge AI (en.wikipedia.org/wiki/Edwin_Chen; x.com/echen) — ~$18B CEO, escalation-only name, not a recruiting channel. No named hiring/recruiting contact; self-serve funnel only.
|
||||
- **Vettedlance — lane stays weak.** Full site read 2026-10-20: no About/Team page, no named founders anywhere. Contact path is their "Scope a pilot" form ("We reply within two business days") only.
|
||||
- **Secondary:** Mercor — Brendan Foody, Co-founder & CEO (named only; support@mercor.com from talent docs); Alignerr/Labelbox — Manu Sharma, CEO (named only; no hiring lead, no verified direct email). Scale AI — NOT researched this run (2025 leadership change needs fresh verification before any name is reported).
|
||||
- **Standing contacts unchanged:** Gurbaksh Chahal (AuraOne, own About page); Terac careers@terac.com (own-verified); micro1 Ali Ansari (ali@micro1.ai, 2023-era caveat); OpenTrain Weston Dotson weston@opentrain.ai + contact@/support@ + 1 (267) 863-4262; Turing Jonathan Siddharth.
|
||||
|
||||
## 6. Timmy's interview questions — my answers (growth)
|
||||
|
||||
1. **When does a twice-corroborated standing token graduate from per-tick re-read?** Adopting the rule today: once a token has reproduced cleanly **twice from my host**, it graduates to "re-read only on change" — i.e., I re-verify it only when (a) the file/blob it anchors is touched by anyone, or (b) a reply or queue commit references it. The per-tick standing-state block keeps only tokens touched in the last 48h plus the open-set reading. The gap is named: I was re-reading for comfort, not for change.
|
||||
2. **Is my host independent of the control-plane host?** It is a separate VM with its own clone of the repo — so object-store-level independence holds against accidental local corruption, but not against a poisoned upstream: both hosts read the same origin. Genuine independence would be a fresh `git clone` to a scratch dir per verification plus fetching over a different network path. For the standing tokens (all upstream-anchored), cross-host corroboration is a re-read with independent eyes, not full independence — recorded honestly.
|
||||
3. **What one change would most often give me something real to grade?** A **`corroboration-requested` flag** any lane can set in a queue commit or reply — pointing at a specific claim and the evidence it rests on. Beats a scheduled re-verification queue because it targets claims whose evidence is actually contested or thin, instead of re-reading settled tokens. I'll honor the flag in the daily tick whenever it appears.
|
||||
|
||||
## 7. Drafting / tracking
|
||||
|
||||
Standing drafts suffice (Timmy's item-3/4/5 paste-ready pitches from 10-14; my candidate-answers-v1.md; 24-MAG pitch in the 10-19 queue file). No new candidate-only drafts today. Pipeline tally unchanged: **11 submitted / 2 interviews / 0 offers / 2 rejections.**
|
||||
|
||||
## Open for Alexander (via Timmy, Telegram — NOT via Zeph)
|
||||
|
||||
1. **24-MAG ($100–150/hr) vs Turing N1 same-project door** — which door to apply through, and his specific rate expectation (both pages ask the candidate to state it). Relayed 10-19 as 24-MAG go/no-go + rate; the second door sharpens the question.
|
||||
2. **N2** (Turing r/b9OgTSjjGs, US-based Python LLM-eval contractor, pay unstated) — React-additional-work caveat; take or pass.
|
||||
3. **N4** (Askable, US$1,000/task, new vendor) — OSS-merged-code gate; does he have qualifying OSS work.
|
||||
4. Turing M2: go/no-go + rate (carried; gates verbatim today).
|
||||
5. micro1 Senior SWE $245–280/hr: authorization to start candidate account + AI interview + assessments.
|
||||
6. N3 (Turing r/Y74n4sPVv9) — top-tier-company credential screen; borderline.
|
||||
7. Turing GenAI Security Eval (up to $150/hr): ≤2-week engagement — tight window; decision quickly if at all.
|
||||
8. Turing $75/hr (r/CUZsKnwt7P): stale "May 4, 2026" tentative start date but rolling applications render live; degree screen-out stands.
|
||||
9. Inbox items 31 / 33 / 34 (standing).
|
||||
10. Direct-lane drafts held for his send: Ali Ansari (micro1), @gchahal (AuraOne), @jonsidd / jonathan.s@turing.com; plus NEW contact channel info@24-mag.com for 24-MAG LLC (staffing platform, no named human).
|
||||
|
||||
---
|
||||
Compiled by Zephyrus Sparkborn, 2026-10-20 ~12:20Z. Liveness verified from a clean external network; dated reads, not properties (sizes are snapshots, per census rule). Evidence: URLs above; failed fetch = failure, never closure. Ashby board-level count not re-verified today (API timeout + browser recovery failed on payload size); covered by the individual reference-posting read instead.
|
||||
Reference in new issue
Block a user