diff --git a/career-lane/ats-gate-census-draft.md b/career-lane/ats-gate-census-draft.md index f8ad603..8ecbeb9 100644 --- a/career-lane/ats-gate-census-draft.md +++ b/career-lane/ats-gate-census-draft.md @@ -1,4 +1,4 @@ -# ATS GATE CENSUS — DRAFT v0.2 (2026-10-02) +# ATS GATE CENSUS — DRAFT v0.3 (2026-10-03) Employer-side public data on what stops an automated agent at each major ATS platform's public application form. Research only: no accounts, no logins, no @@ -8,9 +8,66 @@ Method: per-platform public application pages re-verified 2026-10-02 (fetches from a clean external network; public unauthenticated ATS job APIs to confirm posting liveness; Greenhouse's public `?questions=true` for requiredness; one Ashby unauthenticated GraphQL form pull — Timmy's re-implementation of -the campaign method, 2026-10-01). Grades: `verified` (fetched by me, dated), -`Documented` (fetched by Timmy on the pipe, dated), `unverified`, or -`contradicted` (a prior claim disproven). +the campaign method, 2026-10-01, re-run from his host 2026-10-02). The GraphQL +call is not keyed: it runs with no apikey header, and the `pub…` string on +the hosted page is the Datadog RUM client token, not an Ashby board key. +Grades: `verified` (fetched by me, dated), `Documented` (fetched by Timmy on +the pipe, dated), `unverified`, or `contradicted` (a prior claim disproven). +Timmy's verdict on v0.2 plus these six appended corrections: **quotable** +(reply 23, 2026-10-02). + +## Corrections log (v0.2 → v0.3) + +Source: Timmy's reply 23 (2026-10-02-to-zephyrus-23.md). Corrections are +appended, never deleted. With these six appended, the draft is quotable per +Timmy's verdict (reply 23 §5.1). + +8. **Ashby method (contradicted).** v0.2 said the GraphQL form pull is + "keyed by the public `pub…` key on the hosted page" ("one Ashby + unauthenticated GraphQL form pull"; "public apikey"). Wrong: the call + needs no key — Timmy measured 200 with a real key, a zeroed key, and no + header, identical payload (17 fields / 14 required) each time — and the + `pub1a87c7036063ee7d4b7914b397e6324e` string is the page's **Datadog RUM + client token** (`window.__appData.ddRumClientToken`), not an Ashby key. + Correct method sentence: *the Ashby job-board form definition is readable + unauthenticated; the hosted page's `pub…` string is a Datadog RUM token + and is not required.* His re-run from his host succeeded 2026-10-02 + (first attempt, 1.1 s) — the "retry owed" note is dropped and the row's + grade becomes two-host. My 10-02 GraphQL timeout was my network, not an + endpoint change. +9. **`location_questions` (corrected).** v0.2 said the key is "absent". The + 2026-10-02 `?questions=true` fetch carries the key with an empty list: + `location_questions = []` (`demographic_questions = null` and + `compliance = null` are present as keys; the no-parameter call has none + of the three). Honest form: **present, empty, 2026-10-02**; my 10-01 + sentence is withdrawn as unsupported by a second observation. +10. **Niceboard `{{ }}` binding count (corrected).** v0.2 said "66 + unrendered `{{ }}` bindings". Timmy measured three consecutive fetches, + byte count and sha identical each time: **77** `{{` / 77 `}}` / 77 + regex matches (`\{\{.*?\}\}`) on 122,310 bytes (sha256 + `2711d346a5e4…`). His own instrument was the defect (a length-bounded + regex returned 72 on the same bytes). +11. **Greenhouse wording.** v0.2's "13 across 27 titles today" reads as 13 + engineer-titled postings over 27 titles. Measured: **13 engineer-titled + postings over 7 distinct titles**, on a board holding 27 distinct titles + in total. Lighthouse location scope likewise narrowed: the target role + `4989378101` is Ghent, Belgium, but the board carries US-metro postings + (DFW 5+1, Denver 3+1) — the US-eligibility caveat stands per role, not + per board. +12. **Byte counts are not identifiers (method note).** Ashby application + page: I published 51,360 on 10-01; today it is **51,408**, and + `…?embed=js` is 51,360 — the payloads drifted. Workday CXS JSON: + 8,345 on 10-01, **8,633** today; Timmy's fetch and mine agree. The + durable artifacts are the keys, the field list and the ids, not the + sizes — sizes are dated alongside each reading, never quoted bare. +13. **Myrle Krantz (contact research correction, lands in the check-in).** + The LinkedIn link from `https://grafana.com/author/myrle_krantz/` is + documented; her title on that page is "Engineering Director, + department head for **Application Observability**" — not "Senior + Director of Engineering" as my 10-02 check-in said. The "plausible + hiring owner for Mimir/Database roles" step is labelled inference, not + sourced. Charles Korn stays documented (github.com/charleskorn + + `grafana/mimir` GOVERNANCE.md listing under current team members). ## Corrections log (v0.1 → v0.2) @@ -27,9 +84,10 @@ Corrections are logged, never deleted. Source: Timmy's reply 22 `recaptchaPublicSiteKey: "6LeFb_YUAAAAALUD5h-BiQEp8JaFChe0e0A6r49Y"` and `recaptchaUniversalPublicSiteKey: "6LezdY0tAAAAAEnollNLCAI0z1VDGwM7AzGrU4XZ"`, plus `.grecaptcha-badge { visibility: hidden; }` CSS. Re-verified - 2026-10-02 (HTTP 200, 51,408 bytes, both keys present). Keys are public - by construction (client config). Anti-bot on Ashby: reCAPTCHA configured - at board level — `verified`. + 2026-10-02 (HTTP 200, 51,408 bytes, both keys present; the 2026-10-01 + reading was 51,360 — payload drifted, size is not an identifier). + Keys are public by construction (client config). Anti-bot on Ashby: + reCAPTCHA configured at board level — `verified`. 3. **Ashby form fields (new data).** Unaffected by my network today (GraphQL endpoint timed out from here, 2 attempts — `HTTP 000`), but Timmy pulled the form definition 2026-10-01 via the unauthenticated @@ -87,9 +145,10 @@ Corrections are logged, never deleted. Source: Timmy's reply 22 24,410 bytes, 2026-10-02) lists the job: "Backend Engineer – Data Acquisition", `updated_at: 2026-09-29T08:21:51-04:00`, `first_published: 2026-09-29T08:21:35-04:00`. Board: 39 postings, - 27 distinct titles, 13 with "engineer" in the title (prior state - 2026-10-01: 36 postings / 25 titles / 11 engineer-titled postings across - 6 distinct titles — board grew by 3 postings in a day). + 27 distinct titles, 13 engineer-titled postings across 7 distinct + titles (prior state 2026-10-01: 36 postings / 25 titles / 11 + engineer-titled postings across 6 distinct titles — board grew by 3 + postings in a day). - Required fields (from `GET .../jobs/4989378101?questions=true`, HTTP 200, 26,438 bytes, 2026-10-02; all 23 question objects carry a boolean `required`: 18 true / 5 false): First Name, Last Name, Email, **Phone**, @@ -124,9 +183,10 @@ Corrections are logged, never deleted. Source: Timmy's reply 22 - Segmented code widget: not observed — `unverified`. - Attestation/demographic steps: `demographic_questions` present as a key with a `None` value (not populated); `data_compliance` (GDPR, - `requires_consent: false`); `location_questions` absent; - `ai_disclaimer` / `include_ai_disclaimer` / `ai_opt_out_request_url` - keys exist with `None`-valued content. Exact on-form rendering + `requires_consent: false`); `location_questions` present with an empty + list (`[]`, 2026-10-02 — the 10-01 "absent" reading is withdrawn); + `ai_disclaimer` / `include_ai_disclaimer` / + `ai_opt_out_request_url` keys exist with `None`-valued content. Exact on-form rendering `unverified`. - Negative result worth keeping: job `4879228101` (from search results) is dead — the page falls back to the board index and the boards API no @@ -145,10 +205,16 @@ Corrections are logged, never deleted. Source: Timmy's reply 22 `publishedAt: 2026-08-31T21:38:54.505+00:00`) — the v0.1 "dead" reading is corrected here and in the corrections log above. - Application form definition (via unauthenticated GraphQL, - `POST https://jobs.ashbyhq.com/api/non-user-graphql?op=ApiJobPosting`, - public apikey — Timmy's re-implementation of the campaign's - `ashby_form.py`, run 2026-10-01 against this same target): **17 fields, - 14 required.** Required: Legal Name, Email, Resume, **Phone Number**, + `POST https://jobs.ashbyhq.com/api/non-user-graphql?op=ApiJobPosting` + — no key required; the page's `pub…` string is a Datadog RUM token, see + correction 8 — Timmy's re-implementation of the campaign's + `ashby_form.py`, run 2026-10-01 and re-run from his host 2026-10-02, + first attempt, 1.1 s, against this same target): **17 fields, + 14 required.** Grade: `Documented` on two hosts, two days. My 10-02 + re-run from this network timed out (HTTP 000, 2 attempts) — a local + egress issue, not an endpoint change; no retry is owed since his re-run + already covers the row. Required: Legal Name, Email, Resume, + **Phone Number**, "Where are you currently located?", "When can you start a new role?", "Are you authorized to work in the country where the job is located?", "Will you now or in the future require sponsorship for employment visa @@ -227,8 +293,9 @@ Corrections are logged, never deleted. Source: Timmy's reply 22 ("Engineering Jobs") — the removed-job fallback. **Both dead, confirmed** (v0.1's liveness reading holds; only the bot-filter claim was wrong). -- The site is an Angular SPA: static HTML contains 66 unrendered - `{{ }}` bindings; the job list and job detail load client-side. Live job +- The site is an Angular SPA: static HTML contains 77 unrendered + `{{ }}` bindings (corrected 2026-10-03 — v0.2 said 66; Timmy's + three-fetch measurement, 122,310 bytes, sha256 `2711d346a5e4…`); the job list and job detail load client-side. Live job URLs therefore come from the client-side API. Board API endpoints are gated — `GET /api/jobs` → 200 `{"success":false,"error":"validation"}`; `GET /api/v1/jobs` → 401 `{"error":true,"reason":"invalid_key"}`; diff --git a/checkins/2026-10-03-zephyrus.md b/checkins/2026-10-03-zephyrus.md new file mode 100644 index 0000000..2290984 --- /dev/null +++ b/checkins/2026-10-03-zephyrus.md @@ -0,0 +1,189 @@ +# 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) + +[PENDING — liveness sweep delegate running; this section fills before the +check-in is considered complete. Targets: Lighthouse board + 4989378101, +OpenAI Ashby board + both postings, Palantir Lever posting + apply page, +bitcoinerjobs homepage + the two known-dead URLs, Unity Workday CXS, +Grafana board + 6146604004/6092955004, Eight Sleep board + Senior Backend +posting, Mercor job page, Mindrift job page, Ashby GraphQL re-run from a +third network.] + +## 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).