User decision 2026-09-11. The requirement floor is HF/FH or Techniker HF; no
university degree is asked for at all, and he holds an M.Eng.
Level evidence, from Kdo Cy own postings on the same board: every LK 24 role
requires a Hochschul-/Fachhochschul-/Universitaetsabschluss, LK 26 requires a
Studium at FH/UNI/ETH, and LK 18 roles require an Informatik-EFZ. This posting
sits between the EFZ tier and the degree tier - roughly LK 20-22 - while its own
Lohnklasse field said "Keine Angabe". Against ~135k that is very likely a pay
cut: the EPA Lohntabelle 2026 maxima are LK 20 131,870 / LK 21 137,341 /
LK 22 142,832, and those are CEILINGS, not entry salaries.
Recorded emphatically as NOT a capability rejection. Technically this was the
cleanest fit in the log for a DevOps/platform role - Ansible required and BS-6
is intensive including self-written plugins, plus Kubernetes, CI/CD, IaC and
observability - and it carried NO networking line, the gap that killed RUAG
Principal System Engineering, RUAG System Engineer C5I and the NVIDIA hard gate.
The only gaps were vendor substitutions: RHEL vs Debian, OpenShift vs
Kubernetes, AAP vs Ansible. If a similar posting appears a level up, take it
seriously.
Generalised into memory `reference_bund_lohnklassen`: screen jobs.admin.ch roles
on the EDUCATION FLOOR first. The title hides the level - this one carried no
seniority marker at all - but the education requirement tracks the Lohnklasse
closely.
Kdo Cy as an organisation stays open: the 2026-09-10 rejection and this skip are
two requisitions, not a verdict on the employer.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qej5SBvhcbGXHwLqNWiskM
D1/D2 - Bosch title and promotion: CONFIRMED by the user. The promotion and its
timing are correct and came from a re-grading (Neueinstufung). The Zeugnis does
not contradict it - it names DEPARTMENTS ("Ingenieur" in Fertigungstechnologie
1/2/3) rather than job titles. Separately corrected a false provenance note that
claimed official_title was "the formal combined string on the Zeugnis"; it never
came from that document, it comes from the user and LinkedIn.
D3 - part-time from 2021-09: NOT recorded, by the user's decision. Noted for
completeness that tenure wording such as "over ten years" measures elapsed time
and is unaffected; it would only matter if a document claimed FTE years, and
none does.
D4 - French and Italian: the Swisscom Zwischenzeugnis says he uses both
professionally on a regular basis. The user reviewed the sentence and confirmed
it is an ERROR IN THE DOCUMENT. DE/EN only stands. Recorded in
identity.language_note so nobody rediscovers the line and acts on it, with the
practical warning that a reader of that Zeugnis may take it at face value.
D5 - the RUAG MSSQL rule-out: the DECISION stands (user does not want it
revisited), the REASONING is corrected. Two of its four premises were wrong:
MSSQL is not 0 (Fraunhofer SCEDAS ran on Microsoft SQL Server), and "his stack
is AWS cloud-native" was too narrow - the Swisscom Zeugnis documents component
ownership for ETL into the Teradata DWH. Talend and SAP S/4HANA remain genuinely
0, and the required line reads "Aufbau UND Betrieb" while he has documented
Betrieb only - so the skip is still defensible, it was just better than its
written justification. Both RUAG decision rows now carry the correction and a
standing rule for future DWH postings.
D6 - Vizrt end date: 2018-05 stands by the user's decision.
And the follow-through that matters: the data-warehouse, MSSQL and mentoring
evidence is now IN THE BUNDLES, not only in claims.json. BS-6 showed last week
that evidence which reaches no bundle cannot be selected - this is the same
failure mode, caught the same week. The DWH entry carries its scope limit
explicitly: documented Betrieb, not Aufbau.
Validator PASS, 37/37 tests.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qej5SBvhcbGXHwLqNWiskM
Scout
- New `prospective` adapter for ohws.prospective.ch, wired up as `kdocy`
(jobs.admin.ch, filtered to Kommando Cyber). jobs.admin.ch is an S3-hosted
SPA that returns AccessDenied to any direct fetch, headless included, so the
site cannot be scraped -- but the SPA reads a public, unauthenticated API.
All 463 federal roles in ~2.4s, against RUAG's 35s Playwright scrape.
- This board is richer than any other source: Lohnklasse, application deadline,
a named contact per posting, and the full Aufgaben/Anforderungen body, so
scoring runs against the JD text rather than the title.
- Thread `deadline` through normalization, the markdown report and the JSON
dump. A board with hard deadlines needs them on the row.
- Match `verwaltungseinheit_*` by prefix: the sub-unit key is department
specific (VBS 1083398, EFD 1083364) and hardcoding one breaks reuse.
- MANUAL_CHECK entry for the Bundeswehr Reserve portal. The data is reachable
(SAP E-Recruiting OData, SearchCategory 0022) but the portal actively blocks
automation, and getting through needs UA spoofing plus masking
navigator.webdriver. Not wired up by choice -- the operator-sanctioned
Suchauftrag/job alert is the better channel. Reasoning is in the comment.
Applications
- SBB Data Engineer 103755: interviewed 2026-09-09, WITHDRAWN by the candidate
2026-09-11. Net downgrade on four axes (41h vs 40h, 25+Brueckentage vs 28+5,
3 vs 2 office days, and Anforderungsniveau K tops out ~145k against ~135k
inside a band running to ~160k -- he would enter K at its ceiling merely to
break even). The cohort's only interview, and it ended as his no, not theirs.
- Kdo Cy DevOps Engineer III: REJECTED 2026-09-10, 14 days, no interview.
Form letter with no diagnostic content. Identical on every recorded
dimension to SBB (core / 79 / gate pass / DQ 92 / weak channel) and the two
went opposite ways -- recorded as worth watching, not as evidence for the
channel thesis.
- Citadel row cleaned up: it claimed the cohort and decision-log entries were
deliberately unwritten while its own status line read SUBMITTED. Both exist.
The next-step cell still said "ask BEFORE building the package" two weeks
after submission.
Decision log
- 69 RUAG rows -> 3 undecided. 63 title/family rule-outs, each noting that it
is not a JD read, plus three that are: Test Manager C5I, System Engineer C5I,
ICT Solution Architect. Guarded against the shared F/A-18 slug so one write
could not silently swallow the other.
Note: the K->L/Kader rule is SBB-specific and was deliberately narrowed --
Anforderungsniveau is SBB's own system and does not map onto jobs.admin.ch
(Lohnklassen), RUAG or PostFinance. Thun-area employers sit outside the Bern
salary logic entirely.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qej5SBvhcbGXHwLqNWiskM
Scout run 2026-09-04 (36 companies, 778 eligible) plus the NVIDIA package it
surfaced, and the tooling and policy fixes found along the way.
Application
- NVIDIA Senior DevOps Engineer, Zurich (JR2024256): submitted 2026-09-05.
Evidence Fit 64/100 Stretch, hard gate FAIL x2, channel Weak. Sent on an
explicit user override with the working model unresolved, so hybrid-vs-onsite
is a live screening topic. 2pp resume + 1pp cover letter, both validators
PASS, 0 boxes, 0 Tier 1 findings open.
Policy
- Drop the 7 Core / 2 Adjacent / 1 Stretch cohort caps. They had no derivation
and were overridden whenever they bound, and the cohort was confounded: it
tested fit class while holding channel constant at Weak across all six
applications. Keep the recording, drop the rationing.
- Channel replaces the slot budget as the rationed variable: no application
goes out cold when a named contact is published and reachable.
- Propagated through shared_ops, session_file_template, cohort_tracker
(counts, never counts-against-a-target) and application_cohort.json.
Tool fixes
- fetch_workday emitted 404 URLs for every Workday company (NVIDIA, Novartis,
Equinor): externalPath is site-relative and needs the locale + site prefix.
6/6 short-form 404, 3/3 long-form 200. 773 dead links repaired across 42
archived reports.
- find_decision_url silently de-linked decisions on two boards, which is why
ruled-out roles kept resurfacing as undecided. RUAG rotates its UUID on
repost; BIS migrated its vacancy URL scheme, orphaning 5 decisions including
a live application. Fixed as a two-tier match, not a slug key -- slugs
collide (two live RUAG reqs shared one).
Knowledge base
- claims.json: add Bash / shell scripting, the third canonical gap of this
shape after Ansible and Linux administration.
- bundle_data_platform: BS-4 was framed as a delivered observability stack over
what claims.json calls a proof of concept -- the defect the 2026-08-21 sweep
was told to look for.
- CLAUDE.md and AGENTS.md: correct the RUAG Data Lakehouse shortlist claim,
which the JD does not support and which both files still asserted.
- resume_template: comment-guard the missing babel/ngerman language block.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QFb8tTCig5r1KzkQiNXcYt
SBB Data Engineer (Job ID 103755): invited 2026-08-28 for Wednesday
9 September 2026, 08:30, 45 min on Teams.
Per the posting's own process this is stage 2 of 4 - "Virtuelles
Kennenlernen mit HR und Fuehrungskraft" - so HR together with Andri
Wienandts, not a pure HR screen. 45 minutes shared between two people,
which is the practical constraint the brief is built around.
Two facts worth recording:
- This is the FIRST conversion of the evidence-first cohort (6
applications, 2 rejections), and it came from a COLD submit. The
channel plan called for phoning Wienandts before applying; that never
happened, so the published warm contact went unused.
- The resume never contained Snowflake, dbt or Power BI - the three
literals an ATS keyword screen would have keyed on, and a risk the
session had explicitly recorded as "accepted, not solvable". It did
not filter him out, so a human read the dossier and the honest
substitution framing survived first contact. One data point; not
enough to revise strategy on, but it is evidence against assuming
honest omissions are fatal at the screen.
Brief covers the four questions that must not go unasked (Anforderungs-
niveau K band, design/architecture scope vs current Staff + Component
Owner level, RAMSI's Java/Spring Boot/Angular share, Kidz Care rate),
the substitution answers for each named-but-non-canonical tool, the
swissTAMP/RIS/MUD context, and the thesis boundary - methods prototype,
no operational data, no accuracy figures, PSO surveyed only.
It also asks him to decide three things before the call rather than on
camera: what he does if K lands at 130-150k, if architecture is set
elsewhere, or if RAMSI turns out to be heavily Angular. Any one can be
a no, and the level question is the same shape as the declined BKW.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JMcHCsTKWvVzqyLChF5ckk
RUAG C5I - AI Engineer C5I (Thun, app ID 18027): SUBMITTED 2026-08-27.
Evidence Fit 74/100, fit class Stretch, title-capability hard gate FAIL
(R1 build/operate the AI-LLM platform and R2 in-house LLM/retrieval are
Adjacent, not Direct) - all knowingly accepted under the user's explicit
Phase 0 override. Consumes the cohort's sole Stretch slot: cohort is now
6/10, Stretch 1/1.
Critique ran twice. Round 1 scored the documents 85/100 and raised three
Tier 1 items; Round 2, after the fixes, scores 93/100 with truth and
provenance 24/25 and zero Tier 1 findings. Evidence Fit did not move and
was not allowed to: PP-3 is a personal project and cannot convert an
Adjacent title-capability into a Direct one.
Documents (.tex is the deliverable; PDFs are gitignored):
- resume 2pp/13 bullets, letter 1pp/295 words, both validators PASS
- headline is now the canonical title "Staff Data, Analytics & AI
Engineer", which puts the req's own word above the fold
- PP-3 added as a Projekte section - the only current Linux/hardening
evidence, since BS-6 ended Dec 2022
- the letter names the AI-platform gap in one sentence, then connects
SW-5 to C5I's stated DevSecOps model
- "governte" -> "governance-konforme"; JD term coverage 18/22 -> 22/22
claimable, with all six gap terms still correctly absent
Two defects found and fixed that the first critique missed:
- the resume never loaded babel, so a German document was hyphenated
with English patterns (Hal-bleiterfertigung, Tran-skription). Fixed
with babel[ngerman] plus a Transkription exception; this also cleared
an overfull box. Check this on every future German package -
resume_template.tex likely has the same omission.
- IBM AI Engineering had no primary-source record. Certificate read
directly (IBM via Coursera, 4 Jun 2020, verify 3ZBZFVAL6A34), recorded
as entry #8; it also proves PyTorch, now evidence: certification.
Also included: the submitted Kdo Cy DevOps Engineer III package, the
Capgemini omit rule promoted into config.md, BW-1 canonicalized in
experience_bundeswehr.md, and a scout.py comment correcting the
telenorgroup slug from "near-empty" to a claimed board serving stale
phantom listings that DEMO_TITLES would not catch.
Compensation, PSP/project eligibility and role level were never resolved
before sending and are now live screening topics.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JMcHCsTKWvVzqyLChF5ckk
Rejected 2026-08-27, no interview, ~28 days after submission. Recorded
in all four places that track an outcome: cohort state, decision log,
the Active Sessions row and the session file's status block.
The cohort slot is not freed. A rejection consumes an attempt the same
way a submission does, so the Adjacent count stays 2/2 and the cohort
stays 4/10 - unlike the Google FDE III and AWS FDE no-gos, which were
declined before a package existed.
Recorded as rejected_no_interview on the evidence: nothing in the log
shows any contact after submission. Recruiter-vs-hiring-manager
disposition is a tracked cohort variable, so this is one edit away from
being corrected if a screen did happen.
The package was validator PASS with no Tier 1 truth findings and the
follow-up email to Per Olav Marthinsen was never actioned, making this a
pure cold submit. A cold-channel no-interview rejection does not
implicate document quality on its own. That is now 2 of 4 cohort
applications rejected without interview, both cold, which fits the
channel thesis already in the log - and application_strategy.md forbids
reacting to a single rejection, so no positioning or targeting changed.
The Norway lane is explicitly not closed. NATO JWC Stavanger is still
live and strong Norwegian employers remain in scope; both the row and
the decision note say so, because with Aker BP closed the earlier
Equinor note ("lane now reduced to the open Aker BP application") would
otherwise read as an implied closure.
Submission date left inconsistent on purpose: the contemporaneous
records say 2026-07-29, the retrospective ones 2026-07-30. Both now
carry a note pointing at the other rather than one being overwritten.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JMcHCsTKWvVzqyLChF5ckk
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
Application log updates from the 2026-08-24 scout run and the days after.
SBB Data Engineer (Asset Management, Bern, job 103755): SUBMITTED
2026-08-25. Consumes Core slot 2/7 in evidence-first-2026-01. Submitted
with the Anforderungsniveau K comp question still unresolved, against
the channel plan and the critique's closing advice, so the K band, the
design-vs-build-and-run scope question and the Kidz Care rate are now
screening-call topics rather than pre-cleared facts. Next action changed
from "call then submit" to "prep an interview brief". The stale pointer
to an /edit-resume Tier 1 fix is removed - that fix landed 2026-08-21.
Snowflake Sr SWE Enterprise (Observe): CLOSED - NO RESPONSE at 80 days
silent, past the longest real disposition in the log (Equinor, 79).
Recorded as closed_no_response, deliberately NOT as a rejection: none
was ever received, so it must not enter rejection statistics or read as
a document-quality signal. Pre-dates the cohort, so no slot is freed.
An ~86/100 package - the highest in the log - drawing no reply at all is
the strongest evidence yet that the constraint is channel, not documents.
Unblocks the Observe Metrics Platform req, which was paused only to
avoid stacking a second cold application on the same org.
Norway lane: corrected a false "closed" framing that had propagated into
the Equinor row and was used to dismiss Norwegian rows in the scout
readout. The lane is OPEN but selective. The gates are norsk working
language and NO security clearance - NOT compensation: the 180k bar is
CH-only and explicitly does not apply to Norway. Equinor, Telenor and
NATO JWC stay in the scout.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MHtzyTKBcg6BWhD5qFegtK
User declined at the gate: 69 is not a strong enough fit to spend a package on.
Consistent with revealed behaviour — every application actually submitted scored
77.5-89; nothing below 75 has ever been sent.
No cohort slot consumed (Adjacent stays 1/2). No bullets written, no resume, no
cover letter. Phase 0 analysis retained in the session file in case a
better-fitting AWS req appears.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pipeline:
- SDU PhD: closed, not proceeding. Prof. Jørgensen never replied to the
2026-08-02 enquiry; user dismissed it two days before the 2026-08-20 deadline.
- Google FDE III GTM: closed, not proceeding after two Google rejections. The
bar for a third attempt is now a very strong fit; this was Adjacent with an
agent-orchestration gap. Frees the Adjacent cohort slot (back to 1/2).
JD triage — 5 pulled and read, 1 survives:
- SHORTLIST AWS Senior FDE Zurich: all four basic quals pass and AI/agentic is
preferred-only, unlike the Google Senior Staff FDE where vector DB + RAG were
minimum quals. AWS is the evidenced cloud; JD names Kiro, which he uses.
- SKIP AWS ProServe Bern (clinical pharma domain gate), AWS Principal Delivery
Consultant (8+ yrs architecture leadership + VP+ exec comms), GitLab FDE EMEA
(Ruby/Go hard gate), MS 200044133 (title says FDE Data Scientist, quals are
BGP/MPLS/SD-WAN network engineering — mislabelled req).
Roster:
- Dropped Louis Dreyfus: 300 roles, all Brazil/India/Bulgaria ops, zero Swiss.
- Kept MET Group: its "0 eligible" was a filter artifact; exclusion mode reveals
real Baar/Zug commodity-trading roles.
- Kept Equinor/Telenor/NATO. Memory corrected: the Norway lane is selective, not
closed — the user still wants very good Norwegian roles.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Equinor Manager / AI Architect (JR106747): REJECTED 2026-08-14, no interview.
79 days from submission (2026-05-27) to disposition, the longest turnaround
recorded. Pre-dates the evidence-first-2026-01 cohort (started 2026-07-27),
so it does not free an Adjacent cohort slot. Norway lane now reduced to the
open Aker BP application.
Microsoft Senior SWE, ISE Zurich (200040836): REJECTED 2026-08-11, no
interview, ~39 days. The separate Principal FDE req 200043897 is a different
pipeline and remains open.
Also carries forward uncommitted work from the 08-07 / 08-11 sessions:
- Google FDE III, Cloud GTM (78350205438567110) Phase 0 session file and
scraped JD; Adjacent, Evidence Fit 67/100, hard gate PASS.
- Scout skip decisions: BIS jr100411 (platform admin, not data eng), two
Google reqs gated on a C++ minimum qualification, and the FDE III
Generative AI sibling req confirmed taken down.
- settings.local.json: allow the job_scout venv python invocation.
Every closed application to date has been Channel Weak with no interview.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Aker BP ASA — Data Product Architect (FINN 469067315): archive the finalized
resume/CL sources, JD, session and critique. Submitted 2026-07-30 ahead of the
2026-08-02 deadline; logged as applied in the scout decision log and marked
SUBMITTED in Active Sessions.
KB: record Atlassian Compass as Swisscom's metadata/catalogue platform for data
products and lineage (user-confirmed 2026-07-29). Practitioner use only —
claims.json forbids claiming administration, rollout or ownership, and it is
explicitly not a substitute claim for Purview, Collibra or Alation.
Also: close out the Google Business Home session (no interview), extend the job
scout, and allow the job-board domains used during the Aker BP research.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tighten eligibility to CH/DK/Europe-remote (Equinor Norway-only, NATO DK+NO), add Taleo adapter, parallel API fetches, atomic state writes, and empty-board warnings. Log NATO AI Engineer as applied and Architect as skip.
Equinor (Workday) and BFH (Bern, playwright) wired up as new sources; artificial
intelligence/analytics-engineer keywords added so int'l-org listings (BIS) stop scoring
as noise. certifi-backed SSL context works around Workday certs failing verification
against a stale Windows root store.
location_matches() previously treated "remote + any single named EU country" as
CH-eligible, which let single-country residency-locked listings (e.g. Databricks'
"Remote - United Kingdom") pass as if they were open EU-wide. Now requires either a
pan-regional keyword (Europe/EMEA/Global/Worldwide) or 2+ distinct countries named.
Denmark is carved out as its own always-on relocation category (on-site or remote,
any company), replacing the previous Databricks-only opt-in.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Two applications sent and finalized on 2026-06-15:
- Google - Senior Data Engineer (Merchant Data Science, Zurich), 85.5/100.
Tier-1 scope fix + both Tier-2 polish applied: re-scoped the Swisscom
migration claim in resume B2 + CL P2 (Scope-Discipline), added project-
delivery vocab (B4), and JD-exact 'distributed data processing' (B5).
- Kraken (Payward) - SRE, AI Agents (remote, CH-eligible), 87.2/100.
Finalized as-is; crypto-native + production-ML edge, honest infra gaps.
Logs both as 'applied' in job_scout/state/decisions.json and flips their
CLAUDE.md Active Sessions rows to SENT. Open item for both: confirm level
and comp clear the 180k+ all-in bar at the recruiter stage.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Records the 2026-06-06 application (Observe by Snowflake, ~86/100) in the
decision log so it stops resurfacing as a new match.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Track per-job decisions across runs so we don't re-evaluate roles.
- state/decisions.json (keyed by URL: company/title/decision/note/date), now
git-tracked while seen_jobs.json stays local
- --decide "<url>" <status> [note] records a decision; --hide-decided gives an
undecided-only view; report tags each role inline with its decision
- usage docstring updated
- seed 18 decisions (9 shortlist, 7 skip, 1 paused, 1 maybe); flags Google Staff
FDE GenAI as the paused prior session
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
