Submitted 2026-08-26. Cohort entry added (Adjacent 2/2, cohort now 4/10, channel weak x3) and decision logged. The finding that matters is not the submission. The application form's preferred-work-location selector offered no Zurich, despite the JD body reading "in Miami, Zurich or New York", the posting header listing Zurich, and the site's own Zurich location filter returning this exact req when checked on 2026-08-25. The careers site footer reads Citadel Enterprise Americas LLC, so the likeliest explanation is a US-entity apply flow with European seats routed elsewhere, or a Zurich seat that is closed while the multi-location posting stands. This partly supersedes the working-model risk that blocked Phase 2. If no Zurich seat is reachable through that form, whether Zurich runs hybrid or five-day onsite is moot, and the application may be sitting against a US requisition - a hard no under the standing no-relocation constraint. Carry-forward rule recorded in both CLAUDE.md and the session file: check the application form's location selector before investing in a package. Two independent signals - the posting's stated locations and the employer's own location filter - both proved unreliable as evidence that a seat is actually reachable. Phase 0 treated the filter result as confirmation that the req was live in Zurich; that inference was weaker than it looked. Package itself is finished and reusable: both documents cleared the validator with zero warnings and the Tier 1 fixes lifted JD term coverage from 51% to 68%. Nothing about the documents is the weak point. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MHtzyTKBcg6BWhD5qFegtK
62 lines
1.9 KiB
JSON
62 lines
1.9 KiB
JSON
{
|
|
"cohort_id": "evidence-first-2026-01",
|
|
"status": "active",
|
|
"started": "2026-07-27",
|
|
"target_mix": {
|
|
"core": 7,
|
|
"adjacent": 2,
|
|
"stretch": 1
|
|
},
|
|
"definitions": {
|
|
"core": "Evidence Fit 75+ and no hard-gate failure",
|
|
"adjacent": "Evidence Fit 60-74, no required Gap, normally at most one serious preferred gap",
|
|
"stretch": "Evidence Fit below 60 or a defining responsibility is only Adjacent"
|
|
},
|
|
"applications": [
|
|
{
|
|
"company": "Google",
|
|
"role": "Software Engineer III, Business Home",
|
|
"application_date": "2026-07-27",
|
|
"fit_class": "core",
|
|
"evidence_fit": 89.0,
|
|
"hard_gate": "pass",
|
|
"channel": "weak",
|
|
"outcome": "rejected_no_interview"
|
|
},
|
|
{
|
|
"company": "Aker BP ASA",
|
|
"role": "Data Product Architect - AI-ready Data Products",
|
|
"application_date": "2026-07-29",
|
|
"fit_class": "adjacent",
|
|
"evidence_fit": 79.0,
|
|
"hard_gate": "pass",
|
|
"channel": "weak",
|
|
"outcome": "applied",
|
|
"submitted": "2026-07-29"
|
|
},
|
|
{
|
|
"company": "SBB",
|
|
"role": "Data Engineer (m/w/d), Asset Management Infrastrukturanlagen, Bern",
|
|
"job_id": "103755",
|
|
"application_date": "2026-08-25",
|
|
"fit_class": "core",
|
|
"evidence_fit": 79.0,
|
|
"hard_gate": "pass",
|
|
"channel": "warm_contact_published",
|
|
"outcome": "applied",
|
|
"submitted": "2026-08-25",
|
|
"open_risk": "Anforderungsniveau K is a capped GAV band, figures not public; seat may read lateral or below current Staff + Component Owner scope."
|
|
},
|
|
{
|
|
"company": "Citadel Securities",
|
|
"role": "Platform Engineer, Research Platform Engineering (Zurich/NY/Miami)",
|
|
"application_date": "2026-08-26",
|
|
"fit_class": "adjacent",
|
|
"evidence_fit": 71.0,
|
|
"hard_gate": "pass",
|
|
"channel": "weak",
|
|
"outcome": "applied"
|
|
}
|
|
]
|
|
}
|