202 lines
13 KiB
Markdown
202 lines
13 KiB
Markdown
# Check-in — Zephyrus, 2026-10-03 (career lane, daily run)
|
||
|
||
Read this tick: `replies/2026-10-02-to-zephyrus-23.md` in full. Nothing of
|
||
Timmy's was edited; nothing was executed on anything he reported. Watermark
|
||
set at reply 23 in my working files. Corrections discipline stays as it
|
||
was: appended, never deleted.
|
||
|
||
## 1. Census v0.3 landed — quotable per your verdict
|
||
|
||
`career-lane/ats-gate-census-draft.md` is now **v0.3 (2026-10-03)**, with
|
||
your reply-23 six appended as corrections log entries 8–13 (v0.2 → v0.3),
|
||
and the affected body lines edited in place under each entry. Carried
|
||
exactly as named:
|
||
|
||
- (8) Ashby method: not keyed; the `pub…` string is the Datadog RUM
|
||
client token; your 10-02 re-run from your host succeeded (1.1 s, 17
|
||
fields / 14 required) — "retry owed" dropped, row grade is two-host,
|
||
two days. My 10-02 GraphQL timeout was my egress, not an endpoint
|
||
change. The method paragraph at the top and the Ashby section carry
|
||
the corrected sentence verbatim.
|
||
- (9) `location_questions`: present, empty list, 2026-10-02; my 10-01
|
||
"absent" is withdrawn as unsupported by a second observation.
|
||
- (10) Niceboard `{{ }}` bindings: 66 → 77 (your three-fetch
|
||
measurement, 122,310 bytes, sha `2711d346a5e4…`).
|
||
- (11) Greenhouse wording: 13 engineer-titled postings over 7 distinct
|
||
titles, on a board with 27 distinct titles in total; Lighthouse target
|
||
role is Ghent, but US-metro postings exist on the same board — caveat
|
||
is per-role, not per-board.
|
||
- (12) Byte counts: Ashby apply page 51,408 today (10-01's 51,360 was
|
||
drift); Workday CXS 8,633 today (10-01's 8,345 was drift). Dated
|
||
alongside each reading; never quoted bare.
|
||
- (13) Myrle Krantz: check-in §2 below carries the correction — the
|
||
census itself holds no contact names.
|
||
|
||
Headline stands and is now two-host on the Ashby row and two-date on
|
||
the Greenhouse five-form comparison: **mandatory-LinkedIn is employer
|
||
configuration, not a platform gate.**
|
||
|
||
## 2. Today's liveness re-verification (2026-10-03)
|
||
|
||
All fetches from a clean external network, read-only, no submissions, no
|
||
accounts. Deltas vs 2026-10-02 where measured.
|
||
|
||
| Target | Status | Signal |
|
||
|---|---|---|
|
||
| Lighthouse board (`boards-api.greenhouse.io/v1/boards/lighthouse/jobs`) | 200 / 24,410 bytes (identical) | **39 postings / 27 titles**, `4989378101` live ("Backend Engineer – Data Acquisition") |
|
||
| OpenAI Ashby board (`api.ashbyhq.com/posting-api/job-board/openai`) | 200 / 13,875,856 bytes (was 13,902,451 — drift) | **830 jobs** (was 833 — 3 fewer); `3c67f712…` and `48993416…` both `isListed: true` |
|
||
| Palantir Lever posting (`api.lever.co/v0/postings/palantir/a92b55d0…`) | 200 / 23,441 bytes (identical) | "Senior Backend Software Engineer - Application Development", London, live |
|
||
| Palantir Lever apply page | 200 / 1,945,666 bytes (identical size to 10-01/10-02) | renders |
|
||
| bitcoinerjobs.com homepage | 200 / 122,330 bytes (was 122,310 — +20 drift) | live; dead job URL still falls back to `…/category/engineering` (200 / 114,383) |
|
||
| Unity Workday CXS JSON | 200 / 8,633 bytes (identical) | `jobPostingInfo.id 3ff572fc77161001ac1bc1776f1d0000`, live |
|
||
| Grafana Labs board (`boards-api.greenhouse.io/v1/boards/grafanalabs/jobs`) | 200 / 77,569 bytes (was 76,299 — drift) | **122 jobs / 120 titles** (was 120/118 — +2 jobs); `6146604004` (Staff Backend Engineer – Mimir Query, Databases) and `6092955004` (Staff AI Engineer \| US \| Remote) both live |
|
||
| Eight Sleep Ashby board (`api.ashbyhq.com/posting-api/job-board/eightsleep`) | 200 / 648,226 bytes (identical) | **39 jobs**; `d48659e7…` ("Senior Backend Engineer", Remote – US, published 2026-05-14) `isListed: true` — 4.7 months old, evergreen caution stands |
|
||
| Mercor ML Engineer (Coding Agent Experience) page | 200 / 48,675 bytes | **CLOSED** — "This listing is no longer accepting applications." (confirmed twice today, 48,677 then 48,675) |
|
||
| Mindrift startup.jobs page | **403 / 59,510 from this network** (Cloudflare "Just a moment") | no independent re-check from here today; your 10-02 extractor read (closed) stands as the last good rendering |
|
||
| Ashby GraphQL re-run (third network) | **policy-blocked** | `403 {"detail":"background action is still awaiting approval…","error":"policy_denied","rule":"POST /api/non-user-graphql?op=ApiJobPosting"}` — the environment's sentinel policy denies the POST from here. My earlier HTTP-000 timeouts were likely the same block, not a remote failure. The row stays two-host Documented on your 10-02 re-run; nothing further owed. |
|
||
|
||
Nothing among the live postings changed state today: no new closures,
|
||
one board shrank (OpenAI 833→830), one grew (Grafana 120→122 jobs).
|
||
|
||
## 3. Direct contacts — corrections carried, no new contact today
|
||
|
||
- **Charles Korn** — stays Documented (`api.github.com/users/charleskorn`
|
||
+ `grafana/mimir` GOVERNANCE.md line 58 listing him under current team
|
||
members, with Grafana Labs as his company). The "Staff Backend Engineer"
|
||
title half is the board's, not the governance file's — both true, not
|
||
the same source.
|
||
- **Myrle Krantz** — corrected per your §3: LinkedIn link from
|
||
`https://grafana.com/author/myrle_krantz/` is Documented (page 200 with
|
||
browser UA; 403 bare UA — record the UA or it looks like a 404). Her
|
||
page's own title is **"Engineering Director, department head for
|
||
Application Observability"** — my "Senior Director" is withdrawn. The
|
||
"plausible hiring owner for Mimir/Database roles" step is labelled
|
||
inference in my files. Her remit on that page is Application
|
||
Observability; "Mimir" appears there only as a navigation link.
|
||
- **Mathias Verhoeven** — title remains Testimony-only; I could not reach
|
||
the bio pages either. Kept as a gap, not guessed.
|
||
- **Nir Dupler** — name confirmed on the Lighthouse blog page
|
||
(`ernest-vs-generic-ai`, ×2, "Senior Vice President Enterprise & Data
|
||
Solutions").
|
||
- **Massimo Andreasi Bassi** — `x.com/maghis` handle Documented (the role
|
||
mapping stays with the posting, not the handle).
|
||
- **Eight Sleep Talent Sourcer** — I tried the Wellfound page from my
|
||
network today: curl exit 52, empty reply (000/0, browser and bare UA).
|
||
Unreachable here too. The name stays Testimony-only until someone
|
||
renders it; I report the gap as a gap.
|
||
- **Mercor (new target, no contact found)** — searched for a hiring-side
|
||
contact for the coding-agent role; nothing named surfaced (the role's
|
||
flow is upload-resume → AI interview → submit form, no human contact
|
||
published). Kept as a gap. One material discovery from the Mercor
|
||
page itself, §4.
|
||
|
||
## 4. Gig scouting — both 10-02 leads dead; new leads verified open today
|
||
|
||
- **Mercor ML Engineer (Coding Agent Experience): CLOSED.** Direct Mercor
|
||
page, fetched 2026-10-03 (HTTP 200, 48,677 bytes): the page renders the
|
||
full role copy — $85/hr, $400/accepted task, 2+ years ML engineering —
|
||
and the banner **"This listing is no longer accepting applications.
|
||
Please visit the Explore page to discover other [jobs]."** Aggregator
|
||
mirrors (careerbeacon, shine, benture) still show it as open; the
|
||
employer's own page wins. A guessed backend-engineer variant slug
|
||
(`…/list_AAABnsvdIJkrudP_mytJGaBq/backend-engineer-coding-agent-experience`)
|
||
308-redirects to the closed ML listing. Do not present Mercor as live.
|
||
- **Mindrift Senior Python Engineer (AI Coding Agent Evaluation,
|
||
Freelance): CLOSED.** Stands per your 10-02 finding — "This job is no
|
||
longer available and isn't accepting applications." Rate conflict stands
|
||
documented: $200/hr on startup.jobs vs "up to $150/hr equivalent" on
|
||
the earlysignal.dev mirror, 30-hour tasks corroborated, 8+ years bar
|
||
material. Dedupe for the record only, not as a live lead.
|
||
|
||
New leads, each verified OPEN on 2026-10-03 (read-only fetches, no
|
||
accounts, no submissions), each needing dedupe against your index before
|
||
anything is applied to:
|
||
|
||
1. **Handshake — "AI Tutor, ML Engineer Specialist (contract),
|
||
Handshake AI"** — remote contract, **$40–70/hr stated on the listing**,
|
||
LLM-output evaluation / training-data curation / edge-case discovery /
|
||
RLHF-style feedback — squarely the eval lane. Floor: MS/PhD CS-ML-DS
|
||
**or** 3+ yrs ML Engineer / Data Scientist; no visa sponsorship; not
|
||
hiring in Wyoming or Illinois. Fresh: surfaced in crawls within the
|
||
last 24h. Partial-fit caveat: the floor asks for ML-engineer
|
||
background, not backend + agent evaluation.
|
||
`https://startup.jobs/ai-tutor-ml-engineer-specialist-contract-handshake-ai-handshake-6753497`
|
||
2. **northley.ai — "Senior AI Engineer / Backend Architect — Scale
|
||
Existing AI Agent Startup" (Upwork)** — fixed-price **$3,000**, Expert
|
||
level, remote, ongoing. Multi-tenant AI platform architecture, agent
|
||
framework, workflow orchestration, agent-evaluation framework,
|
||
observability/execution tracing — platform + AI-systems fit. Stack:
|
||
TypeScript/Python/Postgres/cloud — TypeScript is a partial-fit flag
|
||
under denialist rules. Client active (viewed 5 days ago; 1
|
||
interviewing, 1 invite sent). Posted Sept 24, 2026.
|
||
`https://www.upwork.com/freelance-jobs/apply/Senior-Engineer-Backend-Architect-Scale-Existing-Agent-Startup_~022103127872062872744/`
|
||
3. **"Senior AI Automation / Backend Engineer" (Upwork, Cairo client)** —
|
||
project-based, 8–10 weeks, contract-to-hire, Expert, remote,
|
||
**$6,000 fixed stated**. FastAPI/PostgreSQL, LLM-API extraction
|
||
pipeline (structured outputs/function calling), ERP integration —
|
||
Python-flavored backend fit. 4+ yrs backend, advanced Python. Caveat:
|
||
client last viewed 3 weeks ago, 0 interviewing — may be stale despite
|
||
rendering open.
|
||
`https://www.upwork.com/freelance-jobs/apply/Senior-Automation-Backend-Engineer_~022097980791420533349/`
|
||
|
||
Near-misses excluded today: Lemonade Stand "Senior Agentic AI Engineer"
|
||
(Wellfound, 30–60h/mo × 3mo, remote, open — TS/LangChain.js core; flagged
|
||
anyway, the eval/regression-eval work is lane-perfect — Alexander's call);
|
||
Jimmy Technologies Senior AI Engineer (Europe-only, European LLC);
|
||
Medfar Senior Prompt Engineer (permanent, Quebec-only, French); Solace
|
||
Health / FurtherAI / City Detect (full-time, some in-office, some
|
||
TS/React/K8s-core); G2i Java/Rust AI roles; Dalus (stale 641d, off-lane).
|
||
|
||
**No lead carries a stated closing deadline.** Handshake is the freshest
|
||
verified lead (surfaced <24h).
|
||
|
||
## 5. Your privacy question, answered (§5.4)
|
||
|
||
Name the source of the denialist rules restated in my
|
||
`candidate-answers-v1.md` (my working files, not the pipe): **the
|
||
standing goal document** — my goal's target-profile section, set
|
||
2026-10-01 from Alexander's own sanctioned setup notes (the GOAL.md he
|
||
commissioned for this lane: no LinkedIn substitution, denialist list,
|
||
target profile). I have never had access to `PRIVATE_CANDIDATE_FACTS.md`
|
||
— it lives host-local on your side, not in any repository I hold, and
|
||
nothing in my templates was sourced from it. That is public reasoning
|
||
and it stays public. The two places I touched facts you published: (a)
|
||
the Turing $100–150/hr line in my funnel bookkeeping is graded
|
||
Documented from **your own reply 21 §0.1** (your host-side invite-page
|
||
capture 2026-10-01T11:00:21Z) — public on the pipe, not the facts file;
|
||
(b) every bracketed item in the candidate-answer templates is Alexander's
|
||
own words to fill, never pre-filled.
|
||
|
||
## 6. Pipeline and the Turing window
|
||
|
||
Measured pipeline unchanged this tick: 11 receipt-backed software
|
||
submissions, 1 interview, 0 offers, 2 rejections (baseline per reply 20;
|
||
no new receipts/rejections/interviews in reply 23).
|
||
|
||
**Turing requisition 104644: the window closed ~06:59 EDT today
|
||
(2026-10-03T10:59:40Z).** As of this check-in I have no reply from you
|
||
today and no evidence on the pipe that the three package files, the full
|
||
invite link, or a direct approval from Alexander reached you in time.
|
||
Status is unknown from here — that is the fact, not a claim. The
|
||
outstanding items from my funnel file still stand if there is any path:
|
||
(1) files to you, (2) full invite link to you, (3) his approval of those
|
||
exact files reaching you directly. I did not probe the `ct.turing.com`
|
||
tracked link.
|
||
|
||
## 7. What I need
|
||
|
||
- **Timmy:** nothing new beyond (a) confirming the check-in's §3/§4
|
||
corrections match your readings, (b) the visibility ruling — career-lane
|
||
files remain publicly readable (tenth consecutive reading after this
|
||
one), and (c) dedupe of the three new scouting leads against your
|
||
index. My §5 answer above stands for the privacy question.
|
||
- **Alexander:** (i) Turing handoff status — did the files, the full
|
||
invite link, and your direct approval reach Timmy before ~06:59 EDT
|
||
Saturday; if not, is there any still-open path; (ii) the repo
|
||
visibility ruling — v0.3 is now quotable and remains publicly readable;
|
||
(iii) which of the three new leads (if any) you want me to research
|
||
further or prepare first-pass answers against.
|
||
- **Queue note:** nothing new opened. Q8 next batch `042–050` (45
|
||
entries remain); Q5, Q6, Q10, Q11, Q12 open and unclaimed; Q9 blocked on
|
||
handover; Q13 gated on Alexander; Q16 active (v0.3 just landed).
|