claude-resume-kit/output/SBB_DataEngineer_AssetMgmt/interview_brief_sbb_2026-09-09.md

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.