docs(sbb): add total-comp break-even worksheet

The deciding question on 2026-09-09 is a number nobody has, so the worksheet is a frame to complete before the call rather than a filled-in answer: Anforderungsniveau K is not public, which is why Q1 exists. Records the three things that make a Swiss base-to-base comparison lie: the free GA, Regionalzulage and employer pension share are real money invisible in a base figure, while a Swisscom bonus is real money SBB will not match; the GA is a taxable Lohnausweis benefit so its net value sits below list price; and the GA and the "commute saving" are the same franken, so counting both flatters SBB by four figures. K is a capped GAV band with no negotiation lever at the top, so this is a yes/no against a fixed number, not an opening position. User's read is that it will not clear. Taking the call regardless: the questions are worth asking, it is interview practice while NATO JWC, BIS and Microsoft Principal are still live, and the K figure is the first real data point on what the entire Bern/Thun local tier pays - RUAG, Swissgrid, BKW and BFH sit in comparable band structures. Worth recording whatever the outcome. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JMcHCsTKWvVzqyLChF5ckk
feat(sbb): interview invitation 2026-09-09, write interview brief
2026-08-28 17:01:14 +02:00 · 2026-08-28 16:41:55 +02:00
7 changed files with 218 additions and 8 deletions
@@ -157,6 +157,7 @@ _Update this section when starting/finishing a JD._
 | Session | Status | Next Command |
 |---------|--------|-------------|
 | SBB - **Data Engineer (m/w/d)**, Asset Management Infrastrukturanlagen, **Bern** (Job ID 103755) | ⭐ **INTERVIEW INVITED 2026-08-28 - 9. September 2026, 08:30, 45 Min, MS Teams. The only live interview in the log.** Stage **2 of 4** per the posting: *"Virtuelles Kennenlernen mit HR und Fuehrungskraft"*, so **HR together with Andri Wienandts**, not a pure HR screen. Brief: `output/SBB_DataEngineer_AssetMgmt/interview_brief_sbb_2026-09-09.md`. **First conversion of the evidence-first cohort** (6 applications, 2 rejections) and it came from a **COLD submit** - the warm contact printed on the posting was never called. The resume never contained **Snowflake, dbt or Power BI**, the literals an ATS screen would key on, and it still got through: a human read it and the honest-substitution framing held. One data point, do not over-read it. Submitted 2026-08-25, Core, Evidence Fit **79/100**, hard gate PASS, Document Quality **92/100**, no cover letter (SBB waives it). Best practical fit in the log: Bern, German-language, no relocation, EU + B permit. **Four unresolved items, now live call topics:** Anforderungsniveau **K** band (capped GAV, not public, likely below the 180k bar); the seat reads **lateral or below** current Staff + Component Owner scope (the declined-BKW shape); **RAMSI** Java/Spring Boot/Angular is a full responsibility line on a historical/absent stack; Kidz Care scales on gross household income. Gaps to answer honestly: Snowflake, dbt, Argo, Helm, Power BI, Spring Boot, Angular - survivable only because the JD says "z. B.". Thesis stays a **methods prototype**: no operational data, no accuracy figures, PSO surveyed only. | **Decide before 9.9.:** what he does if K lands at 130-150k, if architecture is set elsewhere, or if RAMSI is heavily Angular. Any one can be a no - better decided in advance than improvised on camera. |
 | RUAG C5I - **AI Engineer C5I**, **Thun** (application ID 18027) | **SUBMITTED 2026-08-27** via jobs.ruag.ch (portal only). Evidence Fit **74/100**, fit class **Stretch**, hard gate **FAIL** (R1/R2, the title-defining responsibilities, are Adjacent not Direct), Document Quality **93/100** after a critique-and-fix round, channel **Weak/cold**. German CV 2 pages/13 bullets + motivation letter 1 page/295 words; validators PASS, 0 boxes, visual QA clean. **Cohort now 6/10 and the sole Stretch slot is CONSUMED (Stretch 1/1).** Positioning is his canonical title Staff Data, Analytics & AI Engineer; `PP-3` carries current Linux/hardening evidence and `SW-5` ties DevSecOps to C5I's stated model. The letter names the AI-platform gap in one sentence. Honest gaps: no AI/LLM platform, no compute/GPU cluster, no RAG/retrieval, ML/AI frameworks certification-context only. **Compensation, PSP/project eligibility and level were never resolved and are now live screening topics.** Marco Heinzen's published direct line was never used. **If rejected, do not drop RUAG** - Senior DevOps Engineer C5I and Data Lakehouse / Senior Data Platform Engineer are shortlisted and fit better. | Await response; optional calls to Marco Heinzen (scope/level) and Frank Haugwitz (comp/PSP). |
 | Schweizer Armee - **Kommando Cyber (Kdo Cy)**, DevOps Engineer III (Data Platform), **Zimmerwald** (Ref JRQ$540-19848) | **SUBMITTED 2026-08-27.** Evidence Fit **79/Core**, hard gate **PASS**, Document Quality **92/100**, channel **Weak**. German 2-page CV plus 1-page motivation letter; validators PASS, 0 boxes, visual QA clean. BW-1 surfaces the six-year Bundeswehr officer career. User explicitly accepted the critique's remaining BS-1 wording issue (*„ohne manuellen Eingriff“*) as good enough and submitted unchanged. Cohort evidence-first-2026-01 is now 5/10, Core 3/7. | Await response; optional post-submit call to Marcel Matthey-Doret about Lohnklasse, Engineer-III level and development path. |
 | Google - Software Engineer III, Business Home, Zurich (req 93922217108087494) | **CLOSED - NOT PROCEEDING 2026-07-28** (submitted 2026-07-27; Core, Evidence Fit 89/100, Document Quality 94/100; no interview). Rapid early-screen disposition; known risks were Mid-level versus current Staff scope, data/platform versus product-SWE positioning, preferred algorithms/accessibility gaps, and a cold channel. | Done - cohort rejection recorded; do not treat this outcome alone as a document-quality failure |
@@ -160,7 +160,7 @@ _Update this section when starting/finishing a JD._
 | RUAG C5I - **AI Engineer C5I**, **Thun** (application ID 18027) | **SUBMITTED 2026-08-27** via jobs.ruag.ch (portal only; email and post refused). Evidence Fit **74/100**, fit class **Stretch**, hard gate **FAIL** (R1 and R2, the two title-defining responsibilities, are Adjacent not Direct), Document Quality **93/100** after a full critique-and-fix round (85 pre-edit), truth and provenance 24/25, **0 Tier 1 findings at Round 2**, channel **Weak/cold**. Submitted: German CV **2 pages, 13 bullets** + German motivation letter **1 page, 295 words**; both validators PASS, 0 boxes, text-order and visual QA clean, submission PDFs MD5-verified before sending. **Cohort evidence-first-2026-01 is now 6/10 and the sole Stretch slot is CONSUMED (Core 3/7, Adjacent 2/2, Stretch 1/1)** - any further application must clear Core or Adjacent on its own merits. Positioning is his canonical title **Staff Data, Analytics & AI Engineer**, carried by `BS-1` production ML-inference integration, `BS-6` Linux/Ansible, `SW-3`/`SW-7`/`SW-2` current Kubernetes and data-product work, `PP-3` current self-hosted Linux and hardening, `SW-5` DevSecOps tied to C5I's stated operating model, and the canonical `BW-1` officer career. The letter **names the AI-platform gap in one sentence** and pivots to the operations/platform side. **Honest gaps that travel with it:** no AI/LLM platform built or operated, no compute/GPU cluster, no RAG/retrieval implementation, no formal LLM evaluation; ML/AI-framework depth is certification-context only. **Compensation, PSP/project eligibility and role level were NEVER resolved before sending, so all three are now live screening topics rather than pre-cleared ones.** ⚠ **Marco Heinzen's published direct line (+41 79 568 14 96) was never used** - this went in as a pure cold submit, the sixth consecutive one. **If rejected, that is NOT a signal to drop RUAG:** five other RUAG C5I reqs sit in the scout log, and **Senior DevOps Engineer C5I** and **Data Lakehouse / Senior Data Platform Engineer** are both already shortlisted and are **materially better fits than this one**, sitting on the lane where his evidence is Direct rather than Adjacent. | Await response. Optional but still worthwhile: call **Marco Heinzen** about technical scope and level, and **Frank Haugwitz** about compensation and PSP/project eligibility. Do not react to a single outcome with positioning changes (`application_strategy.md` §38/§74). |
 | Schweizer Armee - **Kommando Cyber (Kdo Cy)**, DevOps Engineer III (Data Platform), **Zimmerwald** (Ref JRQ$540-19848) | **SUBMITTED 2026-08-27.** Evidence Fit **79/Core**, hard gate **PASS**, Document Quality **92/100**, channel **Weak**. Submitted package: German 2-page CV with **15 bullets** and 1-page motivation letter with **300 body words**; validators PASS, 0 boxes, text order and visual QA clean. Canonical **BW-1** records the six-year Bundeswehr officer career and anchors the letter's military/public-service motivation. User explicitly accepted the critique's remaining BS-1 wording issue (*„ohne manuellen Eingriff“*) as good enough and submitted unchanged. Honest gaps remain physical datacenter work, GPGPU, ClickHouse and named Pull-GitOps practice. Cohort evidence-first-2026-01 is now **5/10, Core 3/7**. | Await response; optional post-submit call to Marcel Matthey-Doret about Lohnklasse, Engineer-III level and development path. |
 | Citadel Securities — Platform Engineer, Research Platform Engineering, **Zürich** (also NY/Miami) | **SUBMITTED 2026-08-26.** Cohort slot: **Adjacent 2/2** (cohort now 4/10). ⚠️ **KEY FINDING — the application form's preferred-work-location selector offered NO Zurich**, despite the JD saying "Miami, Zurich or New York" and the site's own Zurich filter returning this req. Careers site is operated by **Citadel Enterprise Americas LLC**; the apply flow is likely US-entity, or the Zurich seat is closed while the posting stands. **This partly supersedes the working-model risk** — if no Zurich seat is reachable through that form, hybrid-vs-onsite is moot and the application may sit against a US req, a hard NO on relocation. **Rule for any future Citadel application: check the form's location selector BEFORE building a package** — the posting's stated locations and the site filter both proved unreliable. User applied with low expectation; cold channel, evergreen standing req. 2pp resume (13 bullets) + 1pp CL (270 words), both validator **PASS, 0 warnings**; JD term coverage 51%→68% after Tier 1 fixes. Critique **STALE by design** (86/100 pre-edit; user chose to submit as-is over re-critiquing; est. ~91 post-edit, never quote as a score). **Cohort entry and decision-log entry deliberately NOT written — no confirmed send date.** Commands ready in the session file. **The working-model question is still open and travels with the application:** Evidence Fit **71/100 (Adjacent, mid-band; revised down from 74)**, qualifications gate PASS but **a practical constraint is UNRESOLVED**, which `critique_framework.md` treats as a NO-GO trigger. **The JD is silent on hybrid vs onsite (0 grep matches), and Ken Griffin is on record that Citadel returned to the office 5 days a week and calls it his most important leadership decision.** If that holds for Zurich, it means ~2–2.5h daily commuting from Bern or relocating — breaking the Bern-based / 2–3 day hybrid bar. Only contrary evidence is a stale 2022 anonymous Fishbowl post about Operations. **Must be asked, not researched** — same class as the SBB K band. Practical constraints scored 5/5 in Phase 0 on an unexamined assumption; corrected to 2/5. **Zero Gaps among the 7 minimum quals**, and all five preferred technologies (Kafka, Kubernetes, Spark, Airflow, distributed DBs) are Direct — **the strongest raw stack alignment in the log**. Title-defining function **splits**: R2 (ingestion/transformation/storage/lifecycle of large datasets) is Direct and describes SW-1/SW-7 exactly; **R1 (design and build the research platform itself) is Adjacent** — the Aker BP authoring-vs-building shape again, and unwritable-around under Scope Discipline. **Classification caveat:** `application_strategy.md`'s "a defining responsibility is only Adjacent → Stretch" would strictly class this Stretch; recorded Adjacent per the Aker BP precedent. Both cohort slots free either way. Gaps: platform authoring at firm scale, no professional quant/finance (now partly mitigated by new **PP-1/PP-2**), SDKs (0 evidence), low-latency/HFT (0 evidence — thesis throughput figure is explicitly barred by `thesis_limits`). **Go is NOT a gap** — Q3 is disjunctive and Python satisfies it. **$175–350k in the posting is a US/NY pay-transparency disclosure, NOT the Zurich number — must be asked.** Channel **Weak/cold** — would be the 5th consecutive cold application, in an office visibly staffed from Google and ETH (platform research head Costas Bekas; Nicolai Meinshausen leads principal research). Cover letter: **YES** if it proceeds — the PP-1 domain story is the main differentiator and needs prose. | **Ask Citadel Securities recruiting whether the Zurich seat is hybrid or 5-day onsite BEFORE building the package.** If 5-day onsite → likely NO-GO on the Bern constraint. If hybrid 2–3 days → resume Phase 2 (plan is written and budget PASSes at 11–14 bullets; two open items: Vizrt VZ-1 C++/distributed bullet, and adding a Projects section for PP-1) |
-| SBB — Data Engineer (m/w/d), Asset Management Infrastrukturanlagen, **Bern** (Job ID 103755) | **SUBMITTED 2026-08-25.** Cohort slot: **Core (evidence-first-2026-01)**. 2pp English resume (13 bullets, validator PASS) + critique: **Document Quality 92/100** (90 at critique, +2 after Edit 1), hard gate PASS, no Tier 1 truth findings, **no outstanding fixes**. No cover letter — SBB waives it. Evidence Fit **79/100 (Core, lower end)**, hard gate **PASS** — the title-defining capability (build/operate cloud data pipelines and governed data products) is Direct and current, unlike the AWS FDE NO-GO. Best practical fit in the log: **Bern-based, German-language, no relocation, EU citizen + B permit**. Real strength cluster for the *vorausschauende Wartung* purpose — Bosch fab sensor/process data, ELK/Kafka anomaly detection, containerized ML inference, plus the condition-monitoring thesis. **Two open risks, both level/comp not fit:** (1) **Anforderungsniveau K** is a capped GAV band and the figures are not public — must be asked, not researched; (2) the seat reads **lateral or below** current Staff + Component Owner scope (same shape as the declined BKW). Named gaps: Snowflake, dbt, Argo Workflows, Helm, Power BI, Spring Boot, Angular — all non-canonical, survivable only because the JD prefixes the stack list with "z. B.". **Cover letter: NO — SBB explicitly waives it.** Channel: posting names **Andri Wienandts, People Leader, +41 79 364 62 53** — the first published warm entry point in the entire log. **The comp question was NOT resolved before submitting**, so the K band is now a live screening topic rather than a pre-cleared one; the same applies to Kidz Care childcare support (up to 90% of Betreuungskosten but scaled on *gross household* income, so realistically far less at this level — bracket table is intranet-only). | Prep an interview brief before any screening call: (1) Anforderungsniveau K band figures, (2) design/architecture scope vs current Staff + Component Owner level, (3) Kidz Care actual rate at this band. Named gaps to have honest answers for: Snowflake, dbt, Argo Workflows, Helm, Power BI |
+| SBB - **Data Engineer (m/w/d)**, Asset Management Infrastrukturanlagen, **Bern** (Job ID 103755) | **INTERVIEW INVITED 2026-08-28 - 9. September 2026, 08:30, 45 Min, MS Teams.** Per the posting's own process this is **stage 2 of 4**, *"Virtuelles Kennenlernen mit HR und Fuehrungskraft"* - **HR together with Andri Wienandts**, not a pure HR screen. Brief written to `output/SBB_DataEngineer_AssetMgmt/interview_brief_sbb_2026-09-09.md`. **This is the FIRST interview of the evidence-first cohort** (6 applications, 2 rejections, 1 conversion) and it converted from a **COLD submit** - the channel plan called for phoning Wienandts first and that never happened. **The resume never contained Snowflake, dbt or Power BI**, the three literals an ATS keyword screen would have keyed on; the session had recorded that risk 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, do not over-read it** - but it is evidence against assuming honest omissions are fatal at the screen. Submitted 2026-08-25: 2pp English resume, 13 bullets, no cover letter (SBB waives it), Evidence Fit **79/100 Core**, hard gate **PASS**, Document Quality **92/100**, channel **Weak/cold**. Best practical fit in the log - Bern-based, German-language, no relocation, EU citizen + B permit. **Four things unresolved before submitting and now live call topics:** (1) **Anforderungsniveau K** is a capped GAV band, figures not public, very likely below the 180k bar; (2) the seat reads **lateral or below** current Staff + Component Owner scope, the same shape as the declined BKW, and the JD's only architecture language is a personal skill not an ownership mandate; (3) **RAMSI** Java/Spring Boot/Angular is a whole responsibility line on a stack that is historical or absent - ask its share, do not oversell; (4) Kidz Care scales on gross household income, so far below 90% at this band. Named gaps to answer honestly: Snowflake, dbt, Argo Workflows, Helm, Power BI, Spring Boot, Angular - all non-canonical, all survivable only because the JD prefixes the stack with "z. B.". Thesis stays a **methods prototype**: no real operational data, no accuracy figures, PSO surveyed only, throughput figure barred. | **Prep before 9.9.:** decide in advance what he does if K lands at 130-150k, if architecture is set elsewhere, or if RAMSI is heavily Angular - any one can be a no, and it is better decided before the call than improvised on camera. |
 | AWS (AWS EMEA SARL, Switzerland Branch) — Senior Forward Deployed Engineer, Zürich (job 10504263) | **CLOSED — NO-GO 2026-08-18** at the Phase 0 gate. Evidence Fit **69/100** (Adjacent). Minimum-qual gate passed (all 4 Basic Quals Direct) but the *title-defining* capability — customer embedding — is a Gap that `claims.json` globally forbids claiming, and R2 multi-agent/retrieval is a second Gap. User declined: **69 is below the fit bar worth spending 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).** Phase 0 analysis retained in the session file for reuse if a better-fitting AWS req appears. | Done — no package built |
 | Google — Forward Deployed Engineer III, Google Cloud GTM (French, German), Zürich (req 78350205438567110) | **CLOSED — NOT PROCEEDING 2026-08-18.** Phase 0 was done (Evidence Fit 67/100, hard gate PASS) but user declined to proceed after **two Google rejections** (Merchant Data Science, Business Home): the bar is now that a Google req must fit *very* well to be worth a third attempt, and this one was Adjacent with an agent-orchestration Gap. **Frees the Adjacent cohort slot (back to 1/2).** Phase 1 never started. | Done — do not reopen without a materially stronger Google req |
 | SDU Center for Energy Informatics, Odense DK — PhD, Theme 2 Predictive Maintenance & Asset Management of Smart Energy Networks (job 4159) | **CLOSED — NOT PROCEEDING 2026-08-18.** Enquiry email to Prof. Bo Nørregaard Jørgensen (sent 2026-08-02) went unanswered for 16 days; user dismissed the idea. Genuine thesis fit (vibration condition monitoring, RBR+ANN hybrid) but the blockers were never the documents — 2 letters of recommendation 13 years out of academia, and DKK 37,075/mo ≈ CHF 56k against a 180k bar. Deadline was 2026-08-20. | Done — no further action |
@@ -43,10 +43,18 @@
      "fit_class": "core",
      "evidence_fit": 79.0,
      "hard_gate": "pass",
-      "channel": "warm_contact_published",
+      "channel": "weak",
-      "outcome": "applied",
+      "outcome": "interview_invited",
      "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."
+      "open_risk": "Anforderungsniveau K is a capped GAV band, figures not public; seat may read lateral or below current Staff + Component Owner scope.",
      "interview": {
        "stage": "Stage 2 of 4 - Virtuelles Kennenlernen mit HR und Fuehrungskraft",
        "invited": "2026-08-28",
        "scheduled": "2026-09-09 08:30",
        "duration_min": 45,
        "format": "Microsoft Teams"
      },
      "note": "FIRST interview invitation in the evidence-first cohort. Converted from a COLD submit - the published warm contact (Andri Wienandts, +41 79 364 62 53) was never called. The resume never contained Snowflake, dbt or Power BI, the three literals an ATS keyword screen would have keyed on, so a human read the dossier."
    },
    {
      "company": "Citadel Securities",
@@ -1785,9 +1785,9 @@
  "https://jobs.sbb.ch/v2/offene-stellen/data-engineer-m-w-d-asset-management-infrastrukturanlagen/45fa2411-31dc-4520-827e-1c93a527534c": {
    "company": "",
    "title": "",
-    "decision": "applied",
+    "decision": "interview",
-    "note": "Submitted 2026-08-25. Core, Evidence Fit 79, Document Quality 92, hard gate PASS. 2pp English resume, no CL (SBB waives); Tier 1 query-performance fix was already applied 2026-08-21. Anforderungsniveau K band status at submission: unconfirmed.",
+    "note": "INTERVIEW INVITED 2026-08-28 for 2026-09-09 08:30, 45 min Teams. Stage 2 of 4 per the posting: \"Virtuelles Kennenlernen mit HR und Fuehrungskraft\" - so HR and Andri Wienandts together, not a pure HR screen. Submitted 2026-08-25, Core, Evidence Fit 79/100, Document Quality 92/100, cold channel. First interview of the evidence-first cohort. Unresolved and now live: Anforderungsniveau K band, design/architecture scope vs current Staff + Component Owner level, RAMSI Java/Spring Boot/Angular share of the role, Kidz Care actual rate.",
-    "date": "2026-08-25"
+    "date": "2026-08-28"
  },
  "https://jobs.ashbyhq.com/snowflake/3eea87fa-73c8-46dc-b69b-7beb438b48d8": {
    "company": "Snowflake",
@@ -0,0 +1,80 @@
 # Total-Comp Worksheet — SBB vs Swisscom
 **Purpose:** compute the break-even *before* the call on 2026-09-09, so that when they name a figure you know immediately whether it clears — instead of working it out afterwards.
 **Honesty note on this file:** I could not retrieve the Anforderungsniveau K figures — they are not public, which is exactly why Q1 exists. Anything below marked ⚠️ is an estimate or a recollection you should verify yourself rather than trust. The Swisscom column is mostly blank because I only hold the ~140k all-in headline; you know the split.
 ---
 ## 1. The Swisscom baseline (fill from your Lohnausweis / total-rewards statement)
 | Component | Amount CHF/yr | Notes |
 |---|---:|---|
 | Base salary (12×) | | |
 | 13th month | | in-band or on top? |
 | Bonus / variable (actual, not target) | | use a 3-year average, not the good year |
 | Employer pension contribution | | **from the Lohnausweis / PK statement, not the deduction you see on the payslip** |
 | Other (allowances, RSU, phone, insurance) | | |
 | **Total all-in** | **~140 000** | the figure of record in `config.md` |
 | Weekly hours | | |
 | Vacation days | | |
 | Commute cost Thun↔Bern (what you actually pay today) | | this becomes a *saving* on the SBB side |
 ---
 ## 2. The SBB side (fill live, on the call)
 | Component | Amount CHF/yr | How to get it |
 |---|---:|---|
 | Base, Anforderungsniveau **K** | | **Q1.** Ask for the band *and* the likely entry point for your profile |
 | Regionalzulage **Stufe 1** | | stated on the posting; ask for the franken amount |
 | 13th month | | ask explicitly whether it is inside or on top of the band figure |
 | Employer pension contribution (PK SBB) | | ask for the **employer** %, and which plan/Sparplan |
 | **Free GA** | ⚠️ ~4 000 (2nd cl.) / ~6 500 (1st cl.) | **verify the current list price yourself.** Ask which class, and how it is taxed — a staff GA is declared on the Lohnausweis, so the net benefit is below list |
 | Family international travel discount (FVP) | | worth something real if you travel; hard to price — estimate honestly or score it qualitatively |
 | Kidz Care childcare subsidy | | **Q4.** Scales on *gross household* income; bracket table is intranet-only. Assume well below the headline 90% |
 | Commute saving (from §1) | | the GA makes Thun↔Bern free — count it once, here or in the GA line, **not both** |
 | **Total all-in** | | |
 | Weekly hours | | |
 | Vacation days | | |
 | Pensum offered (60–100%) | | a 90% option changes the CHF/hour maths materially |
 ---
 ## 3. Break-even
 Compute this **before** the call and write the number here:
 > **Minimum acceptable SBB base = ______ CHF**
 >
 > derived so that: base + 13th + Regionalzulage + employer pension + GA (net of tax) + commute saving ≥ Swisscom all-in
 Then on the call you are comparing one number to one number.
 **Three traps that make this comparison lie:**
 1. **Base-to-base is meaningless here.** The GA, the Regionalzulage and the pension employer share are all real money that never appears in a base-salary comparison. Conversely a Swisscom bonus is real money SBB will not match.
 2. **Count the commute once.** Free GA and "commute saving" are the same franken. Double-counting flatters SBB by four figures.
 3. **The GA is taxed.** It goes on the Lohnausweis, so the net value is below list price. Don't book the sticker number.
 ---
 ## 4. What this is really deciding
 The band is capped and collectively bargained — **there is no negotiation lever at the top of K** the way there is on a private offer. So this is a yes/no against a fixed number, not an opening position.
 Set your own line before the call:
 - **Clears break-even** → the level question (Q2) becomes the deciding one, not the money.
 - **Below break-even but within ~10%** → this is the Bern/Thun WLB-exception trade you already defined: below-bar comp accepted for a local seat with a real mission. Worth it only if Q2 comes back with genuine design scope. It has never been worth it for a *below-level* seat — that is why BKW was declined.
 - **Well below** → decline cleanly, but still finish the call and ask everything. See §5.
 ---
 ## 5. Why the call is worth doing even if the number fails
 - **It is the first real data point on what the entire Bern/Thun local tier pays.** RUAG, Swissgrid, BKW and BFH all sit in comparable Swiss public-sector/parapublic band structures. Whatever K turns out to be, it calibrates that whole lane — which is otherwise pure guesswork.
 - **It is interview practice with nothing at stake.** NATO JWC (final interviews 2nd half of October), BIS Basel and Microsoft Principal FDE are all still live. You do not want one of those to be your first interview in years.
 - **Not wanting it makes you better at it.** You can ask the blunt questions — band, scope, RAMSI share — without hedging, which is exactly how they should be asked anyway.
 Record the K figure in this file afterwards regardless of outcome. It is reusable intelligence for the whole local tier.
@@ -0,0 +1,111 @@
 # Interview Brief — SBB, Data Engineer Asset Management Infrastrukturanlagen
 **When:** Mittwoch, 9. September 2026, 08:30 · 45 Minuten · Microsoft Teams
 **Stage:** **2 of 4.** The posting's own process is: Bewerbung → **Virtuelles Kennenlernen mit HR und Führungskraft** → Persönliches Kennenlernen → Finaler Entscheid.
 **Who is likely on the call:** HR **plus Andri Wienandts, People Leader** (+41 79 364 62 53). This is *not* a pure HR screen — the hiring manager is in the room.
 **Job ID:** 103755 · Bern / Work Smart · 60–100% · **Anforderungsniveau K, Regionalzulage Stufe 1**
 **Submitted:** 2026-08-25 · Core · Evidence Fit 79/100 · Document Quality 92/100 · **cold channel**
 > **45 minutes shared between two people is short.** Assume ~25 min of them asking, ~10 min of you asking, ~10 min logistics. You will not get a second cheap shot at the money and scope questions before the in-person round, so do not let them fall off the end.
 ---
 ## 1. The one thing to understand before you dial in
 **A cold submit converted.** You never called Andri Wienandts, despite his mobile being printed on the posting — the channel plan said to call first and it did not happen. It got an interview anyway.
 More telling: your resume **never contains the words Snowflake, dbt or Power BI**, and all three are named in the required-qualifications block. An ATS keyword screen configured on those literals would have dropped you. It didn't. **Someone read the dossier and made a judgement.** That means the honest substitution story (Teradata/Oracle/AWS → Snowflake; Airflow/PySpark → dbt; Spotfire → Power BI) already survived its first contact with a human — you are not walking in needing to apologise for it. Defend it the same way, calmly, as a tooling difference rather than a gap.
 This is also the **first interview in the evidence-first cohort** — 6 applications, 2 rejections, this is the first conversion.
 ---
 ## 2. Your genuine edge — lead with this
 For a role whose stated purpose includes **vorausschauende Wartung** on physical infrastructure assets, you have a combination most candidates on this req will not:
 - **Industrial sensor and asset data, in production.** Bosch fab: defect-management records, wafer inspection images, PCM electrical parameters (BS-2).
 - **Anomaly detection on streaming data.** The ELK/Kafka PoC with Grafana/Prometheus/Loki monitoring (BS-4).
 - **Containerised ML inference into a plant that cannot stop.** Docker/Kubernetes/Ansible into 24/7 semiconductor production, after which defect-image classification ran fully automated (BS-1).
 - **A master's thesis on vibration-based condition monitoring of machine tools** — rule-based reasoning plus a 7-10-3 ANN.
 - **The operational half of this job, today, at a peer Swiss enterprise in the same city.** Component Owner with on-call, data quality, governance and SLA accountability (SW-2) is precisely *"Betrieb"* and *"Verantwortung für die Qualität und Nachhaltigkeit technischer Lösungen"*.
 **Thesis caveat — hold this line:** it is a **methods prototype**, never a validated system. No real operational data (training data came from a cited thesis; test data was modified plus a random generator), **no accuracy figures exist**, and PSO was *surveyed only*, never implemented. The throughput figure (~500 samples/s against 72.9 kSPS sensors) is barred from external use. Describe it as genuine interest and method familiarity, not as a result.
 **Where they beat you:** named-product fluency on the exact stack, and rail domain — the asset taxonomy, EN 50126 RAMS vocabulary, the swissTAMP/RIS ecosystem.
 ---
 ## 3. The four questions you must not leave without asking
 These were never resolved before submitting. They are now live screening topics, and this call is the natural place for them.
 ### Q1 — Anforderungsniveau K, the actual band
 > *"Die Stelle ist im Anforderungsniveau K mit Regionalzulage Stufe 1 ausgeschrieben. Könnt ihr mir die Bandbreite für dieses Niveau nennen, und wo eine Person mit meinem Profil typischerweise einsteigt?"*
 **Why it is fair game:** SBB publishes its pay system and campaigns publicly on Lohngleichheit and transparency. Asking about a collectively-bargained band is normal, not pushy. The figures are simply not public, so asking is the *only* way to get them.
 **Your bar:** Swisscom ~140k; you move at 180k+ all-in. **K is very likely below that.** The Bern/Thun WLB-exception tier deliberately accepts below-bar comp for a local seat with a real mission — but it has never accepted a below-*level* move (see Q2). Know before the call which trade you are actually willing to make, so you can react in the moment rather than going quiet.
 ### Q2 — Level and design ownership *(the crux)*
 > *"Die Ausschreibung liest sich als Senior-IC-Rolle. Trägt sie Design-Verantwortung für die Pipelines und das semantische Modell, oder wird die Architektur an anderer Stelle gesetzt?"*
 **Why this decides it.** Every other application in your log was a stretch *upward*. This one reads *below* your current Staff (Engineer IV) + Component Owner scope: it asks you to *mentor* other data engineers but the only architecture language is *"Datenarchitekturen entwerfen"* as a personal skill, not an ownership mandate. **This is the same shape as BKW, which you declined as a lateral in this same Bern tier.** Ask it as diligence — it also surfaces whether the seat can grow.
 ### Q3 — RAMSI, and how much of the job it really is
 > *"Was ist RAMSI genau, und welchen Anteil der Rolle macht die Weiterentwicklung der Webanwendung aus?"*
 One of six responsibility lines is web development in **Java Spring Boot / Angular**. Your Java is professional but historical, Spring Boot was a PoC contribution roughly a decade ago, and **Angular is absent entirely**. Do not oversell it — ask what share it is. It may be work you do not want, and that is worth knowing now.
 **Do not assert what RAMSI is.** It is not publicly documented; the RAMS/EN 50126 family is an *inference*. Ask.
 ### Q4 — Kidz Care, if childcare matters to the decision
 SBB covers *"bis zu 90 %"* of Betreuungskosten but scales it on **gross household income**, and the bracket table is intranet-only. At this band, realistically far below 90%. Worth one question if it affects the maths.
 ---
 ## 4. Questions they will ask — and the honest answer
 | Their question | Your line |
 |---|---|
 | **Snowflake? dbt?** | "Not by name. I have run the same shape of work on Teradata and Oracle, then on AWS — Glue, Athena with Iceberg, Redshift — with Airflow for orchestration. The modelling, testing and lineage discipline transfers; the syntax is what I'd pick up." |
 | **Power BI?** | "I co-owned a BI platform rather than just consuming one — TIBCO Spotfire at Bosch, including C# extensions and wafer-map visualisations, which I co-presented at the TIBCO Analytics Forum 2022." |
 | **Argo Workflows / Helm?** | Airflow is a direct orchestrator substitution; Kubernetes is current and production. **Do not claim Helm** — it is not canonical. |
 | **Predictive maintenance experience?** | Lead with Bosch sensor/process data and the ELK/Kafka anomaly-detection PoC. Then the thesis, framed as a methods prototype. |
 | **Why leave Swisscom?** | **Make it about the work, not the band.** Physical infrastructure, asset condition data with a visible public consequence, a Bern seat, and a technical brief that sits on your actual thesis. Do not volunteer that you expect a pay cut. |
 | **Trade-offs between latency, consistency and cost?** | A named required skill and a real strength — Component Owner for business-critical Oracle/Kafka → Teradata ETL with on-call and SLAs. Have one concrete example where you chose batch over streaming, or accepted staleness for cost. |
 | **Mentoring / fachliche Entwicklung?** | Application Owner at Bosch: documentation, user training, vendor coordination; Swisscom Security Champion for the team. Real, but framed as team roles rather than line management. |
 **Two things to keep off the table:** don't claim Snowflake, dbt, Power BI, Helm, Argo, Spring Boot or Angular by name; and don't quote any unverified metric — nearly everything in your record is `metrics: unverified`, and inventing a number in an interview is the same error as putting one on the resume.
 ---
 ## 5. Company context worth showing you know
 - **swissTAMP** is SBB's central source for asset condition and behaviour data — inspection, measurement and operating data, trends and forecasts. SBB describes it explicitly as enabling the move *"from reactive through proactive to predictive maintenance."*
 - Alongside it: **RIS** (Räumliche Informationssysteme, incl. Datenbank feste Anlagen) and **Mess- und Diagnosetechnik (MUD)**, which runs automated condition monitoring of track, switches and power supply.
 - SBB operates a **Competence Center Predictive Maintenance**.
 - **Funded and growing, not a backwater:** there is an active EU-journal tender (235005-2026) for up to **three new-generation infrastructure diagnostic vehicles**. More diagnostic vehicles means more sensor volume — which is exactly what this pipeline seat exists to absorb. Good, specific thing to reference.
 - **Culture:** `#einfachDu` — informal *du* from first contact, so match that register. Work Smart hybrid. Cover letter deliberately waived. 60–100% explicitly welcome.
 ---
 ## 6. Practicalities
 - **08:30 start** — be on Teams early; test audio the night before.
 - Match the **du** register from the first sentence.
 - The posting is in German and the team is German-speaking; **your resume was submitted in English** with a Languages line naming German as mother tongue. Expect the call in German. Don't be thrown if they open in English.
 - Bern-based, German native, EU citizen with a Swiss B permit, no relocation, no sponsorship — **the cleanest practical fit in your whole log.** Say so if the topic opens.
 - Have ready: a concrete latency/consistency/cost trade-off story, and one example of mentoring or lifting another engineer.
 ---
 ## 7. What to decide *before* 08:30
 Not homework for them — homework for you:
 1. **If K comes in at, say, 130–150k all-in: is this still a yes?** The WLB-exception tier says a Bern seat with a real mission can go below the 180k bar. It has never said below-level scope is acceptable.
 2. **If Q2 comes back "architecture is set elsewhere": is it still a yes?** That is the BKW shape you already declined once.
 3. **If RAMSI turns out to be 40% Angular work: is it still a yes?**
 Any one of those can be a no, and it is much better to know your own answer before they say the number than to improvise it on camera at 08:40.
@@ -1,6 +1,16 @@
 # Session: SBB (Schweizerische Bundesbahnen) — Data Engineer (m/w/d), Asset Management Infrastrukturanlagen
-## STATUS: SUBMITTED 2026-08-25
+## STATUS: INTERVIEW INVITED 2026-08-28 (submitted 2026-08-25)
 **Interview: Mittwoch 9. September 2026, 08:30, 45 Minuten, Microsoft 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. Brief written to `interview_brief_sbb_2026-09-09.md`.
 **Two facts worth recording.** (1) This is the **first interview of the evidence-first cohort** - 6 applications, 2 rejections, 1 conversion. (2) It converted from a **cold submit**: the channel plan called for phoning Andri Wienandts before applying and that never happened, so the published warm contact was never used. The resume also never contained **Snowflake, dbt or Power BI**, the three literals an ATS keyword screen would have keyed on - the session recorded that risk as "accepted, not solvable". It did not filter him out, which means a human read the dossier and the honest-substitution framing survived first contact. Do not over-read one data point, but it is evidence against the assumption that the honest omissions are fatal at the screen.
 **Comp worksheet:** `comp_worksheet_sbb.md` - break-even framework to complete **before** the call, so a named K figure can be judged on the spot. Key points recorded there: base-to-base is meaningless (free GA, Regionalzulage and the employer pension share are real money invisible in a base comparison, while the Swisscom bonus is real money SBB will not match); the GA is a taxable Lohnausweis benefit so its net value is below list; and the commute saving and the GA are the same franken - count once. **K is a capped GAV band with no negotiation lever at the top**, so this is a yes/no against a fixed number. **User's own read, 2026-08-28: he does not expect it to clear.** He is taking the call anyway for the questions, for interview practice with NATO JWC / BIS / Microsoft Principal still live, and because **the K figure is the first real data point on what the whole Bern/Thun local tier pays** - RUAG, Swissgrid, BKW and BFH sit in comparable band structures. Record the figure afterwards regardless of outcome.
 **Still unresolved, and now live call topics:** Anforderungsniveau K band, design/architecture scope vs current Staff + Component Owner level, the RAMSI Java/Spring Boot/Angular share of the role, and the Kidz Care actual rate at this band.
 Application sent by the user on 2026-08-25 (2pp English resume, no cover letter — SBB waives it;
 the Tier 1 query-performance fix was already applied on 2026-08-21, so the submitted document is