feat(app): NVIDIA Senior Production Engineer, DGX Cloud submitted; on-duty, GPU and networking KB gaps closed; triage 2026-10-22

Application (submitted 2026-10-22, Workday): - NVIDIA JR2027105, Switzerland Remote. Evidence Fit 65, Stretch (SLIs and error budgets not evidenced), hard gate PASS, channel Weak, no cover letter. - Package in output/NVIDIA_ProdEng_DGX_Cloud/: session, resume .tex, critique (Document Quality 85 before Edit 1; Tier 1 + all Tier 2 applied), verbatim JD. - Prior NVIDIA req JR2024256 was pulled (last listed 2026-09-18; page gone 2026-10-22): noted on that application, so there was no stacking conflict. KB (claims.json, user-confirmed 2026-10-22): - SW-11: current rotating engineer-on-duty role, Opsgenie alerting, alerts and bugs auto-create Jira tickets; he writes alert thresholds (e.g. data quality). - BS-1: the Bosch inference ran on NVIDIA GPUs; CUDA registered forbidden as a skill (system context only, little configuration done). - BS-4: the PoC included Grafana, Prometheus and Loki; ELK Stack, Grafana, Prometheus and Loki registered as PoC-context skills. - networking: certification context only (AWS SA Associate); work uses automated landing zones. - Extraction and CLAUDE.md log row added. Scout state: - decisions: RUAG Senior DevOps (Kubernetes) C5I parked (home-office terms); SLB Data Scientist skipped (user); NVIDIA JR2008695 skipped (C++/Rust 8y); JR2027105 applied; Norway/Apple/Swiss JD-read triage decisions. - employer_reputation: SLB (Glassdoor 3.9), MazeMap and SpareBank 1 Nord-Norge (unchecked). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(scout): Apple blind to CH for 2 months, BIS behind Cloudflare, NAV rate limit, EMEA leak; reputation for every board
2026-10-22 22:29:27 +02:00 · 2026-10-22 10:44:45 +02:00 · 2026-10-22 09:42:47 +02:00 · 2026-10-22 09:19:05 +02:00 · 2026-10-22 09:18:50 +02:00
22 changed files with 3657 additions and 151 deletions
@@ -30,6 +30,7 @@ job_scout/state/*
 !job_scout/state/decisions.json
 !job_scout/state/application_cohort.json
 !job_scout/state/applications.json
 !job_scout/state/employer_reputation.json
 !job_scout/state/history/
 job_scout/state/history/*
 !job_scout/state/history/application_status_before_2026-09-11.json
@@ -183,6 +183,10 @@ _See `config.md` for user-specific corrections. Add verified errors here as you
 | Date | Correction | Files fixed |
 |------|-----------|-------------|
 | 2026-10-22 | **Current on-call was unrecorded, which made the KB look as if his production-operations evidence ended at ART B2B. This is the eighth gap of the recurring ops shape, surfaced by the NVIDIA *Senior Production Engineer, DGX Cloud* (JR2027105) fit check.** User-confirmed in his current team: **Opsgenie** alerting, a **rotating engineer-on-duty role** he takes part in, and bugs and alerts that automatically create Jira tickets the team assigns and fixes. Recorded as **SW-11**. A follow-up confirmed that **he writes the alert thresholds for his own pipelines**, data-quality thresholds being the named example. The Opsgenie/Jira integration is not his and "24/7" is not established. The follow-up also confirmed that the Bosch BS-4 PoC included **Grafana, Prometheus and Loki** (previously only in his earlier CV); registered as PoC-context skills with ELK Stack. **Same message:** (a) the Bosch ML inference (BS-1) **ran on NVIDIA GPUs with CUDA**, but he "never did much configuration there". The writable form is "GPU-backed inference on NVIDIA GPUs". **CUDA is registered `forbidden`** as a skill (it is system context only), and GPU tuning is forbidden on BS-1. (b) **Networking: no professional configuration.** Day-to-day work runs on automated AWS landing zones, and AWS networking is covered only by the Solutions Architect – Associate certificate. Recorded as `networking`, certification context only. **Lesson, the same as before: on an SRE/production JD, ask about the CURRENT on-call and alerting setup before scoring. The past SW-2 Rufbereitschaft had hidden the current one.** | `claims.json` (SW-11, BS-1, skills Opsgenie/CUDA/networking); `knowledge_base/extractions/2026-10-22_oncall_networking_gpu_clarification.md` |
 | 2026-10-21 | **Software design and architecture was under-recorded: the seventh canonical gap of the recurring shape, surfaced by the Google *Staff SWE, Shopping Graph* minimum *"3 years of experience with software design and architecture."*** Before this, the only design evidence was SW-7 (current, undated, 2026-10-03) and a *contribution* at Generali (GN-3), so the line read as unproven. User-confirmed: **software design and architecture were part of his work at Bosch (ingestion and inference scripts, 2020-2022) and at Swisscom (data products)**, and both count toward the year requirement; together they exceed three years. Recorded on BS-1, BS-2 and SW-7, with `designed` added to the BS-1/BS-2 allowed verbs. **Scope kept tight:** at Bosch, "designed" covers the ingestion scripts and the inference integration only, not the data services in general (the first patch over-extended it and was trimmed the same session). Design never means an architect title, design authority or shared-platform architecture. The Swisscom start date stays undated. **Lesson, the same as 10-08 and 10-14: when a JD has a years-of-X minimum that the canonical file states without a duration, ask for the duration before scoring.** | `claims.json` (BS-1, BS-2, SW-7); `config.md` (data-product design row); `knowledge_base/extractions/2026-10-21_software_design_architecture_clarification.md` |
 | 2026-10-22 | **Scout findings fixed in one pass; the biggest one is that Apple had been blind to Switzerland for about two months.** (a) **Apple:** the `location=switzerland-CHE` slug stopped resolving and Apple silently applied a US location ("Chesterfield, Missouri"). Every run from at least 2026-08-31 to 2026-10-22 returned the same 21 US/intern cards and **0 Swiss roles**, which read as "Apple has nothing" rather than as a failure. The code is now `CHEC` (from `/api/v1/refData/postlocation`); the card is the result list item, so the location is readable; and there is pagination, a settle delay and per-element timeouts (one run took 876s, the next 25s). Result: **24 Swiss roles**, Zurich AIML/infra included. (b) **BIS:** bis.org went behind a Cloudflare challenge (403, even for a headless browser), so the board moved to its Workday tenant `bis.wd3.myworkdayjobs.com/External`, which also gives the real office. A host alias plus a lower-cased jr-id keep all 9 `bis.org#jr…` decisions linked (applied jr100498 included). (c) **NAV:** the search API 429s after ~9 requests and then for hours. Discovery now stays at 8 searches, and posting text comes from NAV's official third-party feed (`pam-stilling-feed`, public rotating token), which tolerated bursts. The feed lacks ~2/3 of ads, so a small, slow website-page fallback covers those, and verdicts are cached. (d) **EMEA leak fixed:** a country allowlist without CH/DK plus a trailing "EMEA" tag is no longer Europe-remote (27 rows removed). Swiss/Danish segments in multi-location strings are checked per segment, so "PL-Poland-Remote \| CH-Zurich-MSO" stays Swiss. A regression over all *eligible* 2026-10-22 rows showed only the fenced rows changing (rows newly admitted by the per-segment check were not regression-tested). (e) **Reputation:** every board now has a dated verdict. Glassdoor and **kununu** are both primary sources, and whichever has more reviews decides (user tip: kununu is far better for Swiss employers). AVOID: **BIS** (Glassdoor 2.9/56, where an application is pending), **BFH** (kununu 3.3/132), **Kdo Cy** (federal-administration kununu 3.4/997, not unit-specific). **Lesson: a board that returns the same non-zero count with zero eligible rows for weeks is a silent failure, not an empty market. Check what filter the site actually applied.** | `scout.py` (Apple, BIS, NAV, location filter, reputation); `state/employer_reputation.json` |
 | 2026-10-21 | **FIXED 2026-10-22 (Microsoft links; the EMEA leak below was fixed the same day, see the 2026-10-22 row).** Fix: `fetch_pcsx` now emits `apply.careers.microsoft.com<positionUrl>?jobId=<displayJobId>`, a `?jobId=` pattern precedes the `/job/` one in `_JOB_ID_PATTERNS`, and `_HOST_ALIASES` maps the new host to the old so `_decision_key` is unchanged. Verified: all 7 logged Microsoft decisions still resolve (applied 200043897 included), and a new-form link opened the real posting with the job number on the page. Reports before 2026-10-22 still carry the dead form. Original finding: **every Microsoft link the scout emits is dead, in every report**, found in the 2026-10-20 triage. `fetch_pcsx` builds `jobs.careers.microsoft.com/global/en/job/<displayJobId>`, which now redirects to a generic `apply.careers.microsoft.com/careers?...&pid=1970393557041551` search page. Verified on 200060867 and on the **pending application 200043897** (Principal FDE). The application itself is unaffected; only the link is. The working form is `https://apply.careers.microsoft.com/careers/job/<pcsx id>`, the API's `positionUrl`. **Deliberately NOT patched yet:** 6 logged Microsoft decisions (including 200043897) are keyed on `displayJobId` through the `careers\.microsoft\.com /job/(\d+)` pattern. Swapping the URL would re-key them on the pcsx id and orphan them, the same failure as the 09-04 RUAG/BIS de-linking. **Safe fixes:** (a) keep `url` and add a working `apply_url` field to the row, or (b) emit the new URL with the display id carried in it, plus a host-normalised key pattern. Either way, verify all 6 rows still resolve through `find_decision_url` afterwards. Same triage, also OPEN: an **"EMEA" region suffix lets country-fenced roles through the location filter** (GitLab FR/DE/NL/ES/UK, Grafana ×5, Fivetran Serbia: 7 of 109 new rows), which breaks the docstring rule against multi-country allowlists that omit CH. | not yet fixed: `scout.py` (`fetch_pcsx`, location filter); evidence in `reports/2026-10-20.triage.md` |
 | 2026-10-15 | **Two scout adapters were reporting wrong data without failing; both were found by the 2026-10-14 triage.** (a) **BIS:** the RSS adapter stamped `default_location: Basel, Switzerland` on every vacancy, so **jr100491 (Hong Kong, BIS Asia office)** passed the CH filter and reached a JD read. The feed carries no location, but each vacancy page has a static *Geographical location* field. `fetch_rss` now reads it per item (`location_page_regex`), falls back to a *"based in ..."* sentence in the feed description, and only then uses `default_location`, printing a warning when it does. Verified: Basel reqs still pass, and jr100491 now reads *8 Finance Street, Central, Hong Kong* and is excluded. (b) **Confluent:** IBM closed the acquisition on 2026-03-17, and the Ashby board went from 17 jobs (10-08) to `{"jobs":[]}` (10-14). careers.confluent.io sits behind a Vercel bot checkpoint. The roles are now IBM requisitions, served by the open IBM careers search API (`www-api.ibm.com/search/api/v2`, POST, `size` capped at 100, pages with `from`). New `ibm` adapter; Confluent keeps its id, so seen-state and decisions still link. First run: 84 roles, 0 in CH/Europe-remote scope. **HashiCorp was dropped on 2026-06-06 for having "no clean public ATS API" after IBM absorbed it. That API exists, so HashiCorp can come back through the same adapter if wanted.** **Rule: when an adapter must assume a field, the assumption has to be visible. A silent default looks exactly like real data.** | `scout.py` (`fetch_rss`, `_rss_item_location`, `fetch_ibm`, BIS and Confluent config) |
 | 2026-10-14 | **Spotfire was the sixth evidenced-but-unregistered skill, and junior mentoring was unrecorded - both surfaced by the BIS Basel jr100498 *Senior/Lead Data & Analytics Engineer* (MED IT) triage.** (a) **TIBCO Spotfire** sat in the BS-5 and BS-8 scopes (co-owned environment, technical Application Owner, C# extensions, TAF 2022, spatial wafer-data map charts) but not in the `skills` array, so the JD line *"using database reporting and business intelligence tools"* had no citable skill; registered `production-historical`, `allowed` on user instruction. It does not license Power BI, Tableau or Qlik. (b) The JD requires *"Experience providing general supervision and task-specific guidance to junior colleagues"*, and the only canonical evidence was BS-7 (students, one thesis as Zweitpruefer). User-confirmed: he **onboarded and mentored junior developers at Bosch and at Swisscom** - recorded as **BS-9** and **SW-10**, one per employer. The Swisscom phase (ART B2B or ART DPT) is not recorded, so write it in past tense. Neither is people management. (c) **SDMX: user-confirmed never used**; registered `forbidden` so the scanner catches it. It is an accountability line in the JD, not a qualification. (d) The same audit found **Teradata, Oracle Database and Hadoop/Impala** evidenced only in the SW-2/BS-2/BS-8 scopes and absent from the `skills` array, although every past skills line listed them; registered `production-historical` from those scopes (Oracle explicitly does not establish DBA work). **Lesson, same as 10-08: when a JD has a supervision or mentoring line, ask about junior colleagues before falling back on BS-7. Student supervision is weaker evidence and the stronger evidence was simply unrecorded.** | `claims.json` (BS-9, SW-10; skills TIBCO Spotfire, SDMX, Teradata, Oracle Database, Hadoop / Impala); `knowledge_base/extractions/2026-10-14_mentoring_spotfire_sdmx_clarification.md` |
 | 2026-10-08 | **Three more canonical gaps of the recurring shape, surfaced by the Kongsberg Seatex *Lead Engineer, DevOps and Test Infrastructure* (Trondheim) package.** (a) **Jenkins and GitLab CI/CD** were evidenced in claim scopes (GN-1, FC-1, BS-6, SW-3) but absent from the `skills` array, so no skills line could cite them; registered as `production-historical`, with GitLab keeping SW-3's "used, not built" limit. (b) **Embedded coursework** was unrecorded: user-confirmed an Embedded Systems course (C/C++ and VHDL with an ARM platform) and Robotics during his studies, and **no embedded work since** - recorded as **ED-1**, coursework-only, degree attribution not yet given. (c) **Current unit testing** was unrecorded: he writes unit tests today and knows pytest - recorded as **SW-9**; whether pytest is the Swisscom framework is not confirmed. The JD's required line *"Experience working with embedded SW and Linux"* stays a **half Gap** (hard-gate FAIL); the user overrode it knowingly. **Lesson, again: for any DevOps/test JD ask about current testing practice and about academic hardware work before scoring - neither lives in `claims.json` by default.** | `claims.json` (ED-1, SW-9, 7 skills); `knowledge_base/extractions/2026-10-08_embedded_coursework_testing_clarification.md`; Kongsberg package |
@@ -63,7 +63,7 @@ Verified errors to never re-introduce. Add entries as you catch mistakes.
 | LangChain | **NEVER USED — do not list.** Crept into Apple and Infineon resume outputs as a fabrication when "custom GPTs" was reframed to fit JD vocabulary. Verified GenAI toolchain: **Kiro** (AI IDE / spec-driven dev), **VS Code + Copilot**, **LiteLLM** (LLM API gateway — created/used APIs), **custom GPTs** with fed domain knowledge. Never substitute LangChain/LangGraph/LlamaIndex for these. |
 | Python backend frameworks | **Django, Flask and FastAPI used in private/hobby projects only, never professionally** (user-confirmed 2026-09-18; PP-4). Allowed with explicit personal-project context. Do not infer project names, dates, scale or production deployment. |
 | Enterprise SaaS/SSO administration | **Not performed**, user-confirmed 2026-09-18. Personal server administration and the Bosch secrets plugin do not establish enterprise SaaS/identity administration. This is not a blanket statement that OAuth/SCIM/Okta have never been encountered in any context. |
-| Data-product design / frontend | **User-confirmed 2026-10-03:** current Swisscom work includes data modelling, design and implementation of data products (SW-7). Exact duration is unconfirmed. **No frontend experience**; do not claim frontend/UI development or Full Stack expertise from backend JavaScript, Selenium tests, thesis wording or a personal dashboard. |
+| Data-product design / frontend | **User-confirmed 2026-10-03:** current Swisscom work includes data modelling, design and implementation of data products (SW-7). **Updated 2026-10-21:** software design and architecture were part of his work at Bosch (ingestion/inference scripts, 2020-2022) and at Swisscom (data products); combined they exceed three years. The Swisscom start date stays undated, and design is scoped to his own components, never shared-platform architecture or an architect title. **No frontend experience**; do not claim frontend/UI development or Full Stack expertise from backend JavaScript, Selenium tests, thesis wording or a personal dashboard. |
 ---
@@ -26,7 +26,7 @@
      "outcome": "applied",
      "id": "app-9068f462d9b9",
      "label": "NVIDIA - Senior DevOps Engineer, Zürich (req JR2024256)",
-      "next_action": "Await response. At first contact, clarify homeoffice/onsite requirements and total package. Baseline is 3 homeoffice days/week; fewer days require a clear overall improvement. Note: `claims.json` has no shell-scripting entry, so **Bash is omitted** from Skills although the JD names it and ten years of Debian admin plus Ansible work plainly involve it - same shape as the Ansible/Linux gaps found 2026-08-27. Confirm with the user and record it. Groovy stays out regardless.",
+      "next_action": "No action expected; req pulled ~2026-09-20. Treat as dormant. Does not block NVIDIA JR2027105 (Senior Production Engineer, DGX Cloud).",
      "current_summary": "SUBMITTED 2026-09-05.",
      "events": [
        {
@@ -39,6 +39,11 @@
        {
          "type": "applied",
          "date": "2026-09-05"
        },
        {
          "type": "note",
          "date": "2026-10-22",
          "note": "Posting pulled: JR2024256 was last listed in the 2026-09-18 scout scrape, absent from every scrape since 2026-09-23, and the posting page reads 'The page you are looking for doesn't exist' on 2026-10-22. No response from NVIDIA recorded. Outcome left as applied (no rejection received). The req is closed, so it no longer blocks a second NVIDIA application (BIS jr100429 precedent)."
        }
      ],
      "cohort_id": "evidence-first-2026-01"
@@ -363,7 +368,7 @@
      "url": "https://www.google.com/about/careers/applications/jobs/results/140594136896938694-senior-software-engineer-full-stack-commerce?location=Switzerland",
      "fit_override_reason": null,
      "rubric_version": "critique-framework-2026-09-11",
-      "next_action": "Choose Shopping Ads SWE III (Mid; compensation unpublished), search further Google Senior roles, or explicitly override the stated Commerce frontend gap. No application submitted.",
+      "next_action": "No action - superseded by the Staff Shopping Graph package (output/Google_Staff_SWE_Shopping_Graph/). Reopen only if the user explicitly overrides the frontend gap.",
      "current_summary": "Preparation held: frontend experience denied; Full Stack title-defining gap. Not submitted.",
      "events": [
        {
@@ -375,6 +380,11 @@
          "type": "note",
          "date": "2026-10-03",
          "note": "User confirmed current data-product modelling/design/implementation and denied frontend experience. Full Stack is title-defining: project fit-policy no-go; no separate explicit frontend minimum claimed. Design duration still unconfirmed. Preparation held; not submitted and not user-withdrawn."
        },
        {
          "type": "note",
          "date": "2026-10-21",
          "note": "Superseded 2026-10-21: the user chose Google Staff SWE, Shopping Graph (Feeds Infra) as the single Google application after comparing all live Zurich reqs (job_scout/reports/2026-10-20.triage.md addendum). Commerce stays unsubmitted; frontend gap unchanged."
        }
      ],
      "session": "output/Google_Senior_SWE_Commerce/session_google_senior_swe_commerce.md",
@@ -445,6 +455,56 @@
          "outcome": "applied"
        }
      ]
    },
    {
      "id": "app-google-staff-shopping-graph-102064172115600070",
      "company": "Google",
      "role": "Staff Software Engineer, Shopping Graph (Feeds Infra), Zürich",
      "label": "Google — Staff Software Engineer, Shopping Graph (Feeds Infra), Zürich",
      "application_date": "2026-10-21",
      "fit_class": "stretch",
      "evidence_fit": 70.0,
      "hard_gate": "pass",
      "channel": "weak",
      "outcome": "applied",
      "cohort_id": "evidence-first-2026-01",
      "job_id": "102064172115600070",
      "url": "https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland",
      "fit_override_reason": "Stretch by definition (Staff-level technical leadership only Adjacent); all five minimums met; user chose it as the single Google application 2026-10-21.",
      "rubric_version": "critique-framework-2026-09-11",
      "next_action": "Await Google response. Google limit: next Google application window counts this submit (3 per rolling 30 days). At first contact clarify level (L6 vs L5), Zurich hybrid days vs current 3 homeoffice days, and total package. Interview prep: SW-4 prototype story as the technical-direction example, plus one concrete Staff-level example the user names; Java currency; end-to-end system design with scale and trade-offs. Package: output/Google_Staff_SWE_Shopping_Graph/.",
      "current_summary": "applied",
      "events": [
        {
          "type": "applied",
          "date": "2026-10-21"
        }
      ]
    },
    {
      "id": "app-b13ee50001fc",
      "company": "NVIDIA",
      "role": "Senior Production Engineer, DGX Cloud, Switzerland Remote (JR2027105)",
      "label": "NVIDIA — Senior Production Engineer, DGX Cloud, Switzerland Remote (JR2027105)",
      "application_date": "2026-10-22",
      "fit_class": "stretch",
      "evidence_fit": 65.0,
      "hard_gate": "pass",
      "channel": "weak",
      "outcome": "applied",
      "cohort_id": "evidence-first-2026-01",
      "job_id": "JR2027105",
      "url": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Remote/Senior-Production-Engineer----DGX-Cloud_JR2027105",
      "fit_override_reason": "Stretch: required SRE line (SLIs, SLOs, error budgets) only Adjacent; hard gate PASS. User chose it 2026-10-22 over the alternatives (remote CH, NVIDIA rating 4.4); prior NVIDIA req JR2024256 pulled, so no stacking.",
      "rubric_version": "critique-framework-2026-09-11",
      "next_action": "Await response. Send the LinkedIn note to an NVIDIA recruiter or DGX Cloud engineer (draft in session). Interview prep: incident debugged end to end (SW-2/SW-11); safe model rollout in the fab (BS-1, rollout mechanics not in KB); Kubernetes recency; distributed systems at scale; vLLM/SGLang/Dynamo not used. Package: output/NVIDIA_ProdEng_DGX_Cloud/.",
      "current_summary": "applied",
      "events": [
        {
          "type": "applied",
          "date": "2026-10-22"
        }
      ]
    }
  ]
 }
@@ -28,7 +28,7 @@
      "outcome": "applied",
      "id": "app-9068f462d9b9",
      "label": "NVIDIA - Senior DevOps Engineer, Zürich (req JR2024256)",
-      "next_action": "Await response. At first contact, clarify homeoffice/onsite requirements and total package. Baseline is 3 homeoffice days/week; fewer days require a clear overall improvement. Note: `claims.json` has no shell-scripting entry, so **Bash is omitted** from Skills although the JD names it and ten years of Debian admin plus Ansible work plainly involve it - same shape as the Ansible/Linux gaps found 2026-08-27. Confirm with the user and record it. Groovy stays out regardless.",
+      "next_action": "No action expected; req pulled ~2026-09-20. Treat as dormant. Does not block NVIDIA JR2027105 (Senior Production Engineer, DGX Cloud).",
      "current_summary": "SUBMITTED 2026-09-05.",
      "events": [
        {
@@ -41,6 +41,11 @@
        {
          "type": "applied",
          "date": "2026-09-05"
        },
        {
          "type": "note",
          "date": "2026-10-22",
          "note": "Posting pulled: JR2024256 was last listed in the 2026-09-18 scout scrape, absent from every scrape since 2026-09-23, and the posting page reads 'The page you are looking for doesn't exist' on 2026-10-22. No response from NVIDIA recorded. Outcome left as applied (no rejection received). The req is closed, so it no longer blocks a second NVIDIA application (BIS jr100429 precedent)."
        }
      ],
      "cohort_id": "evidence-first-2026-01"
@@ -751,7 +756,7 @@
      "url": "https://www.google.com/about/careers/applications/jobs/results/140594136896938694-senior-software-engineer-full-stack-commerce?location=Switzerland",
      "fit_override_reason": null,
      "rubric_version": "critique-framework-2026-09-11",
-      "next_action": "Choose Shopping Ads SWE III (Mid; compensation unpublished), search further Google Senior roles, or explicitly override the stated Commerce frontend gap. No application submitted.",
+      "next_action": "No action - superseded by the Staff Shopping Graph package (output/Google_Staff_SWE_Shopping_Graph/). Reopen only if the user explicitly overrides the frontend gap.",
      "current_summary": "Preparation held: frontend experience denied; Full Stack title-defining gap. Not submitted.",
      "events": [
        {
@@ -763,6 +768,11 @@
          "type": "note",
          "date": "2026-10-03",
          "note": "User confirmed current data-product modelling/design/implementation and denied frontend experience. Full Stack is title-defining: project fit-policy no-go; no separate explicit frontend minimum claimed. Design duration still unconfirmed. Preparation held; not submitted and not user-withdrawn."
        },
        {
          "type": "note",
          "date": "2026-10-21",
          "note": "Superseded 2026-10-21: the user chose Google Staff SWE, Shopping Graph (Feeds Infra) as the single Google application after comparing all live Zurich reqs (job_scout/reports/2026-10-20.triage.md addendum). Commerce stays unsubmitted; frontend gap unchanged."
        }
      ],
      "session": "output/Google_Senior_SWE_Commerce/session_google_senior_swe_commerce.md",
@@ -833,6 +843,56 @@
          "outcome": "applied"
        }
      ]
    },
    {
      "id": "app-google-staff-shopping-graph-102064172115600070",
      "company": "Google",
      "role": "Staff Software Engineer, Shopping Graph (Feeds Infra), Zürich",
      "label": "Google — Staff Software Engineer, Shopping Graph (Feeds Infra), Zürich",
      "application_date": "2026-10-21",
      "fit_class": "stretch",
      "evidence_fit": 70.0,
      "hard_gate": "pass",
      "channel": "weak",
      "outcome": "applied",
      "cohort_id": "evidence-first-2026-01",
      "job_id": "102064172115600070",
      "url": "https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland",
      "fit_override_reason": "Stretch by definition (Staff-level technical leadership only Adjacent); all five minimums met; user chose it as the single Google application 2026-10-21.",
      "rubric_version": "critique-framework-2026-09-11",
      "next_action": "Await Google response. Google limit: next Google application window counts this submit (3 per rolling 30 days). At first contact clarify level (L6 vs L5), Zurich hybrid days vs current 3 homeoffice days, and total package. Interview prep: SW-4 prototype story as the technical-direction example, plus one concrete Staff-level example the user names; Java currency; end-to-end system design with scale and trade-offs. Package: output/Google_Staff_SWE_Shopping_Graph/.",
      "current_summary": "applied",
      "events": [
        {
          "type": "applied",
          "date": "2026-10-21"
        }
      ]
    },
    {
      "id": "app-b13ee50001fc",
      "company": "NVIDIA",
      "role": "Senior Production Engineer, DGX Cloud, Switzerland Remote (JR2027105)",
      "label": "NVIDIA — Senior Production Engineer, DGX Cloud, Switzerland Remote (JR2027105)",
      "application_date": "2026-10-22",
      "fit_class": "stretch",
      "evidence_fit": 65.0,
      "hard_gate": "pass",
      "channel": "weak",
      "outcome": "applied",
      "cohort_id": "evidence-first-2026-01",
      "job_id": "JR2027105",
      "url": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Remote/Senior-Production-Engineer----DGX-Cloud_JR2027105",
      "fit_override_reason": "Stretch: required SRE line (SLIs, SLOs, error budgets) only Adjacent; hard gate PASS. User chose it 2026-10-22 over the alternatives (remote CH, NVIDIA rating 4.4); prior NVIDIA req JR2024256 pulled, so no stacking.",
      "rubric_version": "critique-framework-2026-09-11",
      "next_action": "Await response. Send the LinkedIn note to an NVIDIA recruiter or DGX Cloud engineer (draft in session). Interview prep: incident debugged end to end (SW-2/SW-11); safe model rollout in the fab (BS-1, rollout mechanics not in KB); Kubernetes recency; distributed systems at scale; vLLM/SGLang/Dynamo not used. Package: output/NVIDIA_ProdEng_DGX_Cloud/.",
      "current_summary": "applied",
      "events": [
        {
          "type": "applied",
          "date": "2026-10-22"
        }
      ]
    }
  ],
  "targeting_notes": [
@@ -146,13 +146,6 @@
    "note": "TOP CANDIDATE 2026-07-03 run. ISE = MSFT forward-deployed org (ex-CSE): co-engineering with strategic customers. IC4, published base CHF 146.2-245.9k clears bar; German explicitly beneficial; travel up to 25%; AI/LLM reqs are integration-side (RAG, prompt eng, model monitoring) not model-building. Zürich hybrid from Bern. | SENT 2026-07-03 (resume+CL finalized, 85.8/100). REJECTED 2026-08-11, no interview (~39 days after submission). Separate Microsoft req 200043897 (Principal FDE, German-speaking, Zürich) remains open and is unaffected.",
    "date": "2026-07-03"
  },
  "https://jobs.ruag.ch/offene-stellen/senior-devops-engineer-c5i/3b3093ab-badc-4e95-8166-0f6ee32c18d0": {
    "company": "RUAG (Thun/Bern)",
    "title": "Senior DevOps Engineer C5I",
    "decision": "shortlist",
    "note": "Bern-local WLB-exception tier. English-first (German a plus); Linux/Docker+K8s/Python/GitLab CI/Prometheus-Grafana-ELK = core DevOps lane; analytics-platform ops for Army Cyber Command (C5I, 260p unit, DevSecOps). No citizenship gate in JD (only criminal-record/debt excerpts) but verify clearance as German citizen. Comp likely lateral (market + 13th month) — local tier has relaxed bar. Contact: recruiting-c5i@ruag.ch.",
    "date": "2026-07-03"
  },
  "https://job-boards.greenhouse.io/gitlab/jobs/8522408002": {
    "company": "GitLab",
    "title": "Forward Deployed Engineer - Germany (Staff)",
@@ -1133,13 +1126,6 @@
    "note": "Claude judgment 2026-07-06: GPU networking research specialization",
    "date": "2026-07-06"
  },
  "https://nvidia.wd5.myworkdayjobs.com/job/Switzerland-Zurich/Senior-Software-Developer_JR2008695": {
    "company": "NVIDIA",
    "title": "Senior Software Developer",
    "decision": "maybe",
    "note": "Claude judgment 2026-07-06: generic title, no domain signal from the title alone - worth a quick JD read",
    "date": "2026-07-06"
  },
  "https://nvidia.wd5.myworkdayjobs.com/job/Switzerland-Zurich/Senior-Software-Developer--AI-Networking_JR2016186": {
    "company": "NVIDIA",
    "title": "Senior Software Developer, AI Networking",
@@ -1511,13 +1497,6 @@
    "note": "Claude judgment 2026-07-06: Senior SWE with practical AI/ML experience (not research-depth), local tier",
    "date": "2026-07-06"
  },
  "https://jobs.ruag.ch/offene-stellen/software-engineer-c5i/ec08db9a-3b4f-4aad-8eb5-6134c5e87458": {
    "company": "RUAG (Thun/Bern)",
    "title": "Software Engineer C5I m/f/d",
    "decision": "maybe",
    "note": "Claude judgment 2026-07-06: same C5I domain as the DevOps req but a non-senior/generic SWE variant",
    "date": "2026-07-06"
  },
  "https://careers.roche.com/global/en/job/202603-108151/Sr-Scientist-Computational-Biology-Neuroscience-Rare-Diseases": {
    "company": "Roche",
    "title": "Sr. Scientist - Computational Biology - Neuroscience & Rare Diseases",
@@ -1560,13 +1539,6 @@
    "note": "Claude judgment 2026-07-06: internship",
    "date": "2026-07-06"
  },
  "https://career2.successfactors.eu/sfcareer/jobreqcareer?jobId=1476&locale=en_US&company=Swissgrid": {
    "company": "Swissgrid (Aarau)",
    "title": "(Senior) Cloud Security Engineer (80-100%)",
    "decision": "maybe",
    "note": "Claude judgment 2026-07-06: cloud is a core skill, security specialization a partial gap, local tier",
    "date": "2026-07-06"
  },
  "https://career2.successfactors.eu/sfcareer/jobreqcareer?jobId=912&locale=de_DE&company=Swissgrid": {
    "company": "Swissgrid (Aarau)",
    "title": "Bachelor's- & Master's thesis",
@@ -1824,13 +1796,6 @@
    "note": "REJECTED 2026-09-10, 14 days after the 2026-08-27 submission, no interview. Form letter from Besarta Mehmeti with no diagnostic content. Was Core, Evidence Fit 79, hard gate PASS, Document Quality 92, channel weak. Marcel Matthey-Doret's published line was never called. Kdo Cy had 11 roles open on the portal at submission time, so the ORGANISATION is not closed - only this req. Submitted 2026-08-27. Ref JRQ$540-19848, Zimmerwald. Core, Evidence Fit 79, Document Quality 92, hard gate PASS, channel weak. German 2-page CV plus 1-page motivation letter; the six-year Bundeswehr officer career is included as military-context and motivation evidence. User explicitly accepted the critique's remaining BS-1 wording issue ('ohne manuellen Eingriff') as good enough and submitted without the proposed correction. Honest gaps at submission: physical datacenter work, Pull-GitOps as a named practice, GPGPU, ClickHouse and second Swiss official language. Lohnklasse and Engineer-III level were not recorded as clarified.",
    "date": "2026-09-10"
  },
  "https://jobs.ruag.ch/offene-stellen/senior-devops-kubernetes-engineer-c5i/2eef27f6-9546-499d-8492-c1cec22f548a": {
    "company": "",
    "title": "",
    "decision": "shortlist",
    "note": "Rank 1 and the only Core-classifiable target in the log. Re-verified live on the board 2026-09-04. Every required line has canonical evidence: Kubernetes SW-3/SW-7, Linux BS-6/PP-3, GitLab CI-CD SW-5/VZ-1, Ansible BS-6. Only von-Vorteil items missing (VMware/Nutanix/Proxmox, 0 canonical). JD states militärische Karriere als höherer Unteroffizier oder Offizier von Vorteil, so BW-1 scores. Gated on the Frank Haugwitz call (comp, PSP eligibility, whether a second C5I application is welcome while 18027 is pending).",
    "date": "2026-09-04"
  },
  "https://jobs.ruag.ch/offene-stellen/senior-data-engineer-mssql-mit-data-lakehouse-perspektive/96da2356-d9f4-45da-a0ed-caa1acbe8ef9": {
    "company": "",
    "title": "",
@@ -2503,13 +2468,6 @@
    "note": "Same requisition JRQ$540-19848 he applied to and was rejected without interview (see applications.json); this URL is a repost UUID. NOTE 2026-10-08: posting requires 'Aktive Kenntnisse einer zweiten Amtssprache' - plausible, unproven factor in the rejection.",
    "date": "2026-10-08"
  },
  "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Remote/Senior-Production-Engineer----DGX-Cloud_JR2027105": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-08 (JD read), NOT a user decision. TOP FIND. JR2027105, posted ~2026-10-06, Switzerland REMOTE or Zurich. Build/operate automation for DGX Cloud inference/agentic endpoints and control plane. Direct: Python, Ansible config mgmt + CloudFormation (JD says IaC, config mgmt OR GitOps), Linux, containers, AWS, SLOs (BS-3), on-call/incident (SW-2), production ML inference in 24/7 fab (BS-1). Adjacent: 8+ yrs production services and large-scale distributed systems; Kubernetes historical; metrics/logs/traces only via BS-4 PoC; networking fundamentals. Stand-out items (vLLM/SGLang/CUDA/Terraform/ArgoCD) are Gap but optional. Rough Evidence Fit ~68 provisional. CAVEAT: NVIDIA Senior DevOps JR2024256 pending since 2026-09-05 - stacking a second cold NVIDIA application is the user's call.",
    "date": "2026-10-08"
  },
  "https://www.google.com/about/careers/applications/jobs/results/110222556983632582-software-engineer-iii-site-reliability-engineering-prod-ai?location=Switzerland": {
    "company": "",
    "title": "",
@@ -2524,13 +2482,6 @@
    "note": "TRIAGE 2026-10-08 (JD read), NOT a user decision. Google Senior SWE SRE (Technical Infrastructure), Zurich. Min quals: 5 yrs software dev Direct; 3 yrs designing/troubleshooting large-scale distributed systems Adjacent; 2 yrs leading projects/technical leadership Adjacent (Component Owner SW-2, Application Owner BS-3, BDD introduction GN-1). Level-matched alternative to the SRE III Prod AI req.",
    "date": "2026-10-08"
  },
  "https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-08 (JD read), NOT a user decision. Google Staff SWE, Shopping Graph - Feeds Infra (ingestion infrastructure: files, APIs, crawling; data quality). Min quals: 8 yrs programming in Python/Java/Kotlin - Direct (2015 onward); 5 yrs testing and launching software - Direct-ish; 3 yrs software design/architecture - Adjacent (SW-7 data-product design, duration unconfirmed); GenAI tools/LLM interfaces in workflows - Adjacent (SW-8). On-thesis data-ingestion work; Staff-level tech leadership is the reach. Backend infra, NOT the frontend-gated Commerce Full Stack req.",
    "date": "2026-10-08"
  },
  "https://jobs.admin.ch/offene-stellen/devsecops-ict-ingenieur-in-professional/9db3251b-9f5c-4836-914e-388112908b93\r": {
    "company": "",
    "title": "",
@@ -2705,5 +2656,369 @@
    "decision": "applied",
    "note": "Submitted 2026-10-15 by the user via the BIS portal (tracker app-bis-jr100498; package output/BIS_Lead_Data_Analytics_MED/). Core 78, hard gate PASS, Document Quality 88, channel Weak. MED IT, a different unit from the rejected jr100429. Deadline was 2026-11-02.",
    "date": "2026-10-15"
  },
  "https://www.google.com/about/careers/applications/jobs/results/111782570709918406-senior-software-engineer-site-reliability-engineering-youtube-ml?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-20 (JD read, reports/2026-10-20-fit-sources/google_sre_youtube_ml.txt), NOT a user decision. Google Senior SWE, SRE, YouTube ML (MSCA org), Zurich. Min quals identical to the 10-08 Senior SRE (Technical Infrastructure) req: 5 yrs software dev - Direct; 3 yrs designing/analyzing/troubleshooting large-scale distributed systems - Adjacent; 2 yrs leading projects/technical leadership - Adjacent (Component Owner SW-2, Application Owner BS-3). ML-serving SRE sits closer to his AI-platform positioning than the TI req; BS-1 (containerized ML inference in a 24/7 fab) is the bridge. Apply to ONE of the two Senior SRE reqs, not both. Google 3-per-30-days: no Google submit since 2026-07-27.",
    "date": "2026-10-20"
  },
  "https://roche.wd3.myworkdayjobs.com/roche-ext/job/Basel/Senior-Engineer---Machine-Learning---AI-Enablement_202610-125361-1/apply": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/roche_ml_ai_enablement.txt). Core duty: 'Lead technical design, architecture, and hands-on implementation of agentic AI solutions' - SW-8 forbids claiming agent orchestration. Required breadth line: 'from GPU optimization and model performance to backend systems and cloud-native architecture (e.g., Kubernetes, AWS) with solid knowledge of statistics and ML theory' - backend/AWS/K8s Direct, GPU/model performance Gap, ML theory certification-level only. Stretch at best; user may override. Not the regulated-manufacturing Roche role the 10-14 note hoped for.",
    "date": "2026-10-20"
  },
  "https://roche.wd3.myworkdayjobs.com/roche-ext/job/Basel/Senior--AI-Engineer----Imaging-_202610-126099-2/apply": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/roche_ai_engineer_imaging.txt). Required: 'Deep expertise in computer vision algorithms (e.g., CNNs, Vision Transformers, UNet, SAM/Segment Anything, Cellpose)' and 'Expert knowledge of machine learning theory, image processing fundamentals' on microscopy/pathology imaging. CV model-building; BS-1 establishes inference integration, not model development.",
    "date": "2026-10-20"
  },
  "https://roche.wd3.myworkdayjobs.com/roche-ext/job/Basel/Sr-Scientist---Computational---Applied-AI_202610-125552-1/apply": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/roche_sr_scientist_applied_ai.txt). Drug-discovery scientist: '3+ years ... of post-doctoral or biopharmaceutical industry experience delivering applied AI and data science solutions in a drug-discovery setting'; causal inference, GNNs, biological foundation models. Not his lane.",
    "date": "2026-10-20"
  },
  "https://roche.wd3.myworkdayjobs.com/roche-ext/job/Kaiseraugst/Data---AI-Excellence-Lead---RDT-Data-Management---Governance_202610-126529/apply": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/roche_data_ai_excellence_lead.txt). '10+ years of direct experience leading data and/or AI culture, change management, governance, or digital transformation' - an organizational-change and policy-adoption role, not engineering. Data-mesh/data-product vocabulary matches SW-7, the job does not. Kaiseraugst, no relocation.",
    "date": "2026-10-20"
  },
  "https://jobs.sbb.ch/v2/offene-stellen/data-engineer-m-w-d/5eb1bd60-9853-4ae5-b801-c178de4823c2": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/sbb_data_engineer.txt). Applies the USER's SBB rule. Job ID 104409, Team Ampere, Digital Solution Energie (generation, Energiehandel, rail grid supply) on the Snowflake-based EAP - the energy-trading domain is the draw. But: 'Diese Stelle befindet sich im Anforderungsniveau J' - below Niveau K, which the user ruled too low on 2026-09-11 (withdrawal from Job 103755: aim at L and/or Kader). Required 'Python, Java und TypeScript sowie den dazugehoerigen Frameworks (dbt, Spring Boot, Angular)' - TypeScript forbidden; Snowflake and ArcGIS/FME (nice-to-have) forbidden. Named contact: Nisanthan Ratnasingam (personelle Fuehrung).",
    "date": "2026-10-20"
  },
  "https://jobs.admin.ch/offene-stellen/ict-system-engineer-senior-application-mcx-platform/b146f208-dfad-4a85-b76f-bee88b33aacb": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/kdocy_sys_eng_app_mcx_platform.txt). Gate: 'Gute aktive Kenntnisse einer zweiten Amtssprache' - DE+EN only. Also 'Fundierte Erfahrung mit Kommunikations- und Kollaborationsplattformen sowie mit Real-Time-Communication- und Telco-Architekturen' - Gap (Swisscom work is data, not telco architecture). LK 23, Bern, Pikett, deadline 2026-11-19.",
    "date": "2026-10-20"
  },
  "https://jobs.admin.ch/offene-stellen/product-owner-senior/c2dd357c-7f11-4139-b80e-5d8319b787f5": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/kdocy_product_owner_senior.txt). Gate: 'Gute Kenntnisse mindestens einer zweiten Amtssprache'. Also 'Mehrjaehrige Erfahrung als Product Owner sowie in der Leitung komplexer ICT- und Telekommunikationsvorhaben' and Mobilfunk/Festnetz/Netzwerktechnik - Gap. LK 23.",
    "date": "2026-10-20"
  },
  "https://jobs.admin.ch/offene-stellen/ict-system-engineer-senior-network-transport/f40ed236-f5b8-41e4-8b29-ef1c2fa1e000": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/kdocy_sys_eng_network.txt). Gate: 'Gute aktive Kenntnisse einer zweiten Amtssprache'. Also 'Sehr gute Kenntnisse von IP- und Layer-3-Architekturen, Routing, Segment Routing, VPN, QoS' - network engineering, Gap. LK 23.",
    "date": "2026-10-20"
  },
  "https://jobs.admin.ch/offene-stellen/ict-system-engineer-senior-device-user-environment/edcf3381-ed33-4463-a9b0-560e1239d0e6": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/kdocy_sys_eng_device_user_env.txt). Gate: 'Gute aktive Kenntnisse einer zweiten Amtssprache'. Also 'Fundierte Kenntnisse im Mobile Device Management und Unified Endpoint Management sowie in Android Enterprise, iOS/iPadOS' - Gap. LK 23.",
    "date": "2026-10-20"
  },
  "https://www.bis.org/vacancy/jr100471": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/bis_infra_architect.txt). Required: 'Demonstrated expertise in designing and architecting hybrid infrastructure environments across on-premises data centers, private and public cloud, including compute, virtualization, containers, networks, storage and platforms' - Gap (PP-3 is explicitly not datacenter evidence); OpenShift Gap. Architecture-governance role (policies, design authority), same shape as the Swissgrid ICT Architect skip. jr100498 is pending at BIS: no second cold application to the same org. Deadline 2026-11-05.",
    "date": "2026-10-20"
  },
  "https://jobs.careers.microsoft.com/global/en/job/200060867": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read via https://apply.careers.microsoft.com/careers/job/1970393557027202 (reports/2026-10-20-fit-sources/ms_senior_csa.txt) - the report URL redirects to a generic search page. Partner-facing Data & AI pre-sales (Cloud & AI Partner Architects DACH), measured on Azure consumption. Required: 'Proven experience in technical consulting, solution architecture, or technical pre-sales' - Gap; preferred Fabric/Foundry/Azure - Azure forbidden; '10+ years of experience in customer-facing or partner-facing technical roles' - Gap. IC5, CH base CHF 154.0-300.2k. Principal FDE 200043897 is still pending: no stacking.",
    "date": "2026-10-20"
  },
  "https://job-boards.greenhouse.io/gitlab/jobs/8860196002": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/gitlab_staff_sa_ai.txt). Location gate: 'Remote, France; Remote, Germany; Remote, Netherlands; Remote, Spain; Remote, United Kingdom' - CH not listed (scout passed it on 'EMEA'). Also a pre-sales SME measured on 'technical win rate and bookings'; 'Substantial experience in technical pre-sales' - Gap.",
    "date": "2026-10-20"
  },
  "https://www.amazon.jobs/en/jobs/10578467/senior-delivery-consultant-ai-ml-specialist-telecommunications-aws-professional-services": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/aws_proserve_aiml_telco.txt). Basic quals: '3+ years of customer-facing work, engaging with customer executives, technologists or partners' - Gap (internal enterprise roles only); '5+ years of machine learning, statistical modeling, data mining, and analytics techniques experience' - ML Gap, analytics Adjacent. ProServe executive-advisory role.",
    "date": "2026-10-20"
  },
  "https://jobs.smartrecruiters.com/CERN/744000155986767": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/cern_fullstack_java.txt). Graduate programme: 'a maximum of two years of professional experience since graduation' - ineligible. Fully onsite, Geneva.",
    "date": "2026-10-20"
  },
  "https://www.google.com/about/careers/applications/jobs/results/108203660361507526-software-engineer-iii-youtube-trust-and-safety-automation?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/google_swe3_yt_tns.txt). 'Build classifiers for YouTube videos and livestreams using various modalities' - multimodal ML model-building, outside positioning; '1 year of experience with end-to-end Machine Learning' only partly via BS-1. Mid level; a Google slot is better spent on the SRE / Shopping Graph set.",
    "date": "2026-10-20"
  },
  "https://www.google.com/about/careers/applications/jobs/results/97084041571771078-infotasks-productivity-agents-deepmind?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/google_deepmind_infotasks.txt). DeepMind agent research engineering: 'Build and optimize multi-agent hierarchical pipelines', automated evaluation raters, training environments; preferred 'training GenAI models'. SW-8 forbids agent orchestration and formal LLM evaluation; top-lab model work is outside positioning.",
    "date": "2026-10-20"
  },
  "https://careers.axpo.com/jobs/8566126-ai-adoption-specialist-f-m-d": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/axpo_ai_adoption.txt). L&D / change-management role: '2-4 years of experience in technology enablement, digital adoption, technical training, learning & development or change management' - not engineering, level-down. Baden commute rule (user 2026-08-27).",
    "date": "2026-10-20"
  },
  "https://jobs.ruag.ch/offene-stellen/ict-application-manager/8c4dd1c6-75a9-4ae5-96d0-32ac614faa50": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/ruag_ict_app_manager.txt). Key-user application management (accounts, licences, incidents); 'Abgeschlossene Berufslehre, vorzugsweise in der Informatik' - level-down. Emmen/Thun.",
    "date": "2026-10-20"
  },
  "https://jobs.bfh.ch/offene-stellen/leiter-in-innovationsfeld-und-wissenschaftliche-r-mitarbeiter-in-co-leitung-moeglich/a31835a2-d42b-428d-9aa2-aff2f1130948": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/bfh_innovationsfeld.txt). Nursing research lead: 'Masterstudium in Pflege- oder Gesundheitswissenschaften mit Doktorat' - out of field.",
    "date": "2026-10-20"
  },
  "https://telenornorway.teamtailor.com/jobs/8550341-tech-lead-fullstack-utvikler": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/telenor_techlead_fullstack.txt). Norwegian-language posting (working language Norwegian; he is A2), Oslo/Fornebu. 'Erfaring med Java/Kotlin og Spring Boot, samt TypeScript/JavaScript og moderne frontend-rammeverk. Hos oss bruker vi Vue.' - TypeScript forbidden, frontend Gap. This req only; the Norway lane stays open.",
    "date": "2026-10-20"
  },
  "https://jobs.ruag.ch/offene-stellen/head-of-engineering/ab919c1d-8283-4896-a5f8-f5d36366bb1a": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-20, JD read (reports/2026-10-20-fit-sources/ruag_head_eng_a.txt + ruag_head_eng_b.txt). ONE row for TWO live postings of the same req: EN 559b77da and DE ab919c1d share the slug, so the slug fallback in find_decision_url resolves both here. Wangen, Sensors & Electronic Warfare. Division head: 'Proven experience in managing a division', 'cost centre responsibility', 'sensor technology and reconnaissance systems; knowledge of radar systems' - Gap.",
    "date": "2026-10-20"
  },
  "https://www.google.com/about/careers/applications/jobs/results/136295776576774854-software-engineer-iii-youtube-viewcount-and-aggregations?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-21, JD read (reports/2026-10-20-fit-sources/g_swe3_yt_viewcount_aggregations.txt). Min qual '2 years of experience with software development in C++' - C++ is production-historical-limited (do not oversell C++). CONTENT is the closest Google match on the board (batch and streaming pipelines over billions of daily events, monitoring/alerting/data validation for metric quality), so revisit only if the C++ line is ever relaxed. Mid level.",
    "date": "2026-10-21"
  },
  "https://www.google.com/about/careers/applications/jobs/results/79119194099983046-software-engineer-iii-merchant-shopping-intelligence-and-agents?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-21, JD read (reports/2026-10-20-fit-sources/g_swe3_merchant_shopping_agents.txt). Builds Gemini/ADK merchant agents: 'Implement automated evaluations, guardrails, and prompt engineering strategies' - SW-8 forbids agent orchestration and formal LLM evaluation. Mid level.",
    "date": "2026-10-21"
  },
  "https://www.google.com/about/careers/applications/jobs/results/104587629684499142-software-engineer-iii-data-protection-acceleration?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-21, JD read (reports/2026-10-20-fit-sources/g_swe3_data_protection_accel.txt). Core team privacy/policy-enforcement infrastructure; generic mid-level minimums, off-thesis next to the Shopping Graph and SRE options.",
    "date": "2026-10-21"
  },
  "https://www.google.com/about/careers/applications/jobs/results/118334068726080198-staff-software-engineer-site-reliability-engineering-connections?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-21, JD read (reports/2026-10-20-fit-sources/g_staff_sre_connections.txt). Staff SRE (Cloud TI): 8 yrs software dev Direct, but '3 years of experience leading projects' and '3 years ... designing, analyzing, and troubleshooting distributed systems' are both Adjacent - a double reach (level and SRE depth). The Senior SRE reqs cover the SRE lane at the right level.",
    "date": "2026-10-21"
  },
  "https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland": {
    "company": "",
    "title": "",
    "decision": "applied",
    "note": "USER DECISION: SUBMITTED 2026-10-21 via Google Careers, cold (no referral). Evidence Fit 70, fit class Stretch, hard gate PASS, Document Quality ~86 (post-edit estimate; critique scored 84 before the last edit). Package: output/Google_Staff_SWE_Shopping_Graph/. Registry id app-google-staff-shopping-graph-102064172115600070.",
    "date": "2026-10-21"
  },
  "https://jobs.ruag.ch/offene-stellen/senior-devops-engineer-c5i/cd0c7781-211e-46db-bfba-3fa3c2dd50e4": {
    "company": "RUAG (Thun/Bern)",
    "title": "Senior DevOps Engineer C5I",
    "decision": "skip",
    "note": "Claude triage 2026-10-22, JD read (reports/2026-10-22-fit-sources/ruag_senior_devops_c5i.txt). DIFFERENT ROLE from the 2026-07-03 shortlisted req of the same title (3b3093ab, analytics-platform ops, since closed): this one runs self-hosted email/groupware/collaboration services on an on-prem private cloud (LDAP/OIDC, Terraform+Ansible, Kubernetes), Bern. Hard gate: 'Swiss citizenship required' - he is a German citizen. Also 'Experience with self-hosted email, groupware or collaboration platforms' is personal-only (PP-3 mail/Nextcloud server) and Terraform is forbidden. Superseded row note (July): shortlist, Bern-local WLB tier, Linux/Docker/K8s/Python/GitLab/Prometheus-Grafana-ELK DevOps lane, no citizenship gate in THAT JD.",
    "date": "2026-10-22"
  },
  "https://careers.nordicsemi.com/jobs/8483837-embedded-software-test-automation-engineer": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nordic_embedded_sw_test_automation.txt), NOT a user decision. Nordic Semiconductor, Oslo or Trondheim; English working language ('communication and presentation skills in English'); employer rated GOOD (Glassdoor 4.0/103). CI/CD for a multi-platform Bluetooth stack: Python strong - Direct; Jenkins + Docker + CI/CD pipelines - Direct (FC-1, BS-6, VZ-2, SW-3 historical); Grafana/monitoring + database - Adjacent (BS-4 PoC); Bash tooling Direct; Groovy named in duties - forbidden. HARD GATE: required 'Experience in embedded software development, especially within Bluetooth stack or other wireless protocol projects' and 'embedded development kits' - ED-1 coursework only. Same gate the user overrode for Kongsberg Seatex (2026-10-08). User's call.",
    "date": "2026-10-22"
  },
  "https://careers.nordicsemi.com/jobs/8411130-ate-test-engineer": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "Claude triage 2026-10-22, JD read (reports/2026-10-22-fit-sources/nordic_ate_test_engineer.txt). Chip production test: 'Proven track record in high frequency, mixed-signal, digital and analog test development and execution' and 'Automated Test Equipment (ATE) Test Development in high volume manufacturing' - Gap. Bosch fab data analysis is adjacent domain, not ATE test development.",
    "date": "2026-10-22"
  },
  "https://jobs.apple.com/en-us/details/200634821-4170/aiml-senior-ml-rl-training-infrastructure-engineer-afm?team=MLAI": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/apple_afm_training_infra.txt). Apple Core Foundation Models, Zurich: RL training infra on TPU/JAX. Minimums 'Hands-on experience designing, building, or maintaining large-scale ML training infrastructure' and 'Strong proficiency with PyTorch or JAX and experience running training workloads on GPUs/TPUs' are Gap: BS-1 is inference integration, PyTorch is certification-context-only, JAX/TPU absent. Model-training infra at a top lab, outside the AI-platform overlap (user_positioning).",
    "date": "2026-10-22"
  },
  "https://jobs.apple.com/en-us/details/200680814-4170/staff-machine-learning-engineer-siri-runtime-systems-and-interaction?team=MLAI": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, apple_siri_runtime_staff.txt). Despite the 'Runtime Systems' title the role leads audio/video GENERATION: minimum 'Deep hands-on experience with generative audio and/or video architectures (e.g., diffusion models, autoregressive models, GANs, VAEs...)' - Gap. Model-building.",
    "date": "2026-10-22"
  },
  "https://jobs.apple.com/en-us/details/200687930-4170/hid-algorithms-software-engineer?team=HRDWR": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, apple_hid_algorithms.txt). HID sensor-algorithm frameworks with firmware teams. Minimum 'Strong C/C++ programming' - C++ is not a strength (feedback_cpp_emphasis); embedded preferred (ED-1 coursework only). SW architecture minimum would be Adjacent (BS-1/BS-2/SW-7), but the language gate decides.",
    "date": "2026-10-22"
  },
  "https://jobs.apple.com/en-us/details/200634000-4170/applied-machine-learning-engineer-security?team=SFTWR": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, apple_applied_ml_security.txt). SEAR offensive security research. Minimums 'Expertise in ML, especially large language models and generative modeling' and offensive-security experience - both Gap (SW-8 is configured assistants; SW-5 Security Champion is a team role).",
    "date": "2026-10-22"
  },
  "https://jobs.sbb.ch/v2/offene-stellen/projektleiter-in-datenmanagement/9eb0bb3e-89c7-4d3e-a892-8c6f587e0624": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, sbb_projektleiter_datenmanagement.txt). Job ID 104238, Olten. 'Diese Stelle befindet sich im Anforderungsniveau H' - below Niveau K, which the user ruled too low (2026-09-11). Project coordination of RIS/BIM inventory data capture and external suppliers, not engineering.",
    "date": "2026-10-22"
  },
  "https://career2.successfactors.eu/sfcareer/jobreqcareer?jobId=1476&locale=de_DE&company=Swissgrid": {
    "company": "Swissgrid (Aarau)",
    "title": "(Senior) Cloud Security Engineer (80-100%)",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/swissgrid_cloud_security.txt); resolves the 07-06 title-only maybe. Azure cloud-security role in Platform Services, Aarau. Required 'Mehrjaehrige Erfahrung in Cyber Security Rollen mit Fokus auf Cloud Security', 'Erfahrung in Offensive Security (Security Auditing, Pentesting, CTF...)', Azure services and Terraform/GitHub Actions - Gap (Azure and Terraform forbidden; SW-5 Security Champion is a team role).",
    "date": "2026-10-22"
  },
  "https://jobs.ruag.ch/offene-stellen/software-engineer-c5i/d4cff80d-97d5-4ef7-8460-fc72c54eb3be": {
    "company": "RUAG (Thun/Bern)",
    "title": "Software Engineer C5I m/f/d",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, ruag_software_engineer_c5i.txt); resolves the 07-06 title-only maybe. Thun, Fuehrungsinformationssysteme, non-senior. Required 'Sehr gute Kenntnisse von .NET Framework (C#), Visual Studio (ganzer Technologie Stack) sowie in SCRUM' - C#/.NET is limited/secondary (Fraunhofer only). Technical contact Cedric Wyss, Principal Software Engineering C5I.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/b17ef550-ab1f-44bf-b2c3-1adc9de1a54a": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_kredittbanken_data.txt). Kredittbanken Data Engineer, Trondheim. Requirement sentence 'God skriftlig og muntlig fremstillingsevne paa norsk og engelsk' = Norwegian required (A2); the scout read ENGLISH OK from the NAV 'Arbeidsspraak Engelsk eller norsk' field, a classifier defect. Stack is Azure Synapse/Power BI/DAX (Azure forbidden).",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/a1ce9d86-a95a-495e-9653-e1db8d67c100": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_kongsberg_norcontrol_devops.txt). Kongsberg Norcontrol DevOps & Test Engineer, Horten. Function fits (CI/CD, test automation, Docker/K8s), but requirement 'Kommunisere tydelig paa norsk og engelsk' = Norwegian required; scout read ENGLISH OK from the Arbeidsspraak field (classifier defect). Clearance required (not a gate). Kongsberg Seatex application pending.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/f9753f42-1af7-4282-9161-d3e52a8d1c62": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_kd_fullstack_positioning.txt). Kongsberg Discovery HiPOS full-stack, Horten; English only. Required 'application development using technologies such as C++, C#' and 'Real-time programming, real time operating systems' - Gap. Same company as the pending Seatex application; deadline 2026-10-23.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/9c0de8f3-3c34-47f7-aac3-b9cc359aea33": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_norwegian_fullstack.txt). Norwegian Air Shuttle Fullstack, Bodoe. 'Good communication skills, in Norwegian and English' = Norwegian required (scout read ENGLISH OK from the Arbeidsspraak field). Java/Kotlin/C# web and app development.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/cab34bc3-7ba6-48f6-b71c-5446a659a916": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_reitan_dataplattform.txt). Reitan Eiendom data engineer, Trondheim; function fits (DWH, ETL/ELT, Python, Databricks/Snowflake-type), but 'god muntlig og skriftlig fremstillingsevne paa norsk' = Norwegian required.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/3a90f1b5-2b87-4907-a82d-64411d58964a": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_norautron_dataplattform.txt). Norautron AI & Data Engineer, Horten: Microsoft Fabric/Azure/Power BI/Boomi platform - Azure forbidden, Fabric/Boomi absent. Language unstated (Norwegian ad).",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/7b71105c-1e7a-468b-aece-b03012651374": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_slb_software.txt). SLB Rig Equipment Software Development Engineer, Kristiansand; English only. Core stack 'C#, .NET, WPF, WinUI' desktop/equipment software - C#/.NET is secondary (Fraunhofer only). The sibling Data Scientist req is the better SLB fit.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/0edf3ca5-e911-4bbc-84e6-3f7ccb0c1131": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_kongsberg_maritime_senior_dev.txt). Kongsberg Maritime Drives R&D, Bergen: 'Strong understanding of drive control systems, power electronics, electric motors' - electrical/control engineering, not software.",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/ba3282b1-f394-4c95-85ac-38611d2f277e": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_mazemap_senior.txt), NOT a user decision. MazeMap Senior Product Development Engineer, Trondheim; 'Fluent English Communication' only (Arbeidsspraak Engelsk). 8+ yrs IC building scalable backend - Direct/Adjacent (11 yrs; scale unquantified). 'Python Mastery: Deep, hands-on Python expertise (AsyncIO, performance tuning, microservices)' - Python Direct, AsyncIO specifics not in KB, ask. Java working knowledge (allowed-with-context), C++ exposure. AI dev tools - SW-8 (Copilot/Kiro). 'spatial data, graph algorithms, mathematical modeling' - BS-8 SDO_GEOMETRY + CRS transforms is a genuine bridge. ~21-person SaaS; reputation UNCHECKED (Glassdoor 1 review).",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/6c3365ed-adb8-4c64-8508-804d98df1037": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_kda_platform.txt), NOT a user decision. KDA Defence Systems (NASAMS) platform developer, Kongsberg (travel Asker/Moss). Required: CI/CD and build/test/deploy automation (GN-1, FC-1, BS-6 Jenkins/GitLab), IaC and environment standardisation (BS-6 Ansible), Linux (BS-6, PP-3) - Direct. Preferred GitLab, containers (SW-3/BS-1), observability (BS-4 PoC only), CMake (unknown), embedded/Ada (ED-1 coursework). Clearance-eligible required (not a gate). LANGUAGE UNCLEAR: Norwegian ad, no requirement sentence, NAV tag norsk - ask the recruiter. Same group as the pending Kongsberg Seatex application (different business area) - stacking is the user's call. Kongsberg verdict OK (no Glassdoor; Indeed 3.8/101).",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/80658525-2197-4705-8d34-8f1b7535a5a8": {
    "company": "",
    "title": "",
    "decision": "maybe",
    "note": "TRIAGE 2026-10-22 (JD read, reports/2026-10-22-fit-sources/nav_sparebank1_ai.txt), NOT a user decision. SpareBank 1 Nord-Norge KI-ingenioer, Tromsoe. Required lines are generic dev (systems development, APIs/integrations, version control/testing, production lifecycle, security/privacy) - Direct. GenAI/agents/Azure/Copilot Studio are advantages only ('Erfaring med KI-utvikling er en fordel, men ikke et krav'); SW-8 forbids agent-orchestration claims. LANGUAGE UNCLEAR (Norwegian ad, no sentence, NAV tag norsk; a regional bank likely works in Norwegian). Tromsoe is far north. Reputation UNCHECKED.",
    "date": "2026-10-22"
  },
  "https://jobs.ruag.ch/offene-stellen/senior-devops-kubernetes-engineer-c5i/4767c36f-2816-463f-846d-4f0283dc7c15": {
    "company": "",
    "title": "",
    "decision": "parked",
    "note": "USER DECISION 2026-10-22: not applying for now - 'there homeoffice rules are not good' (same C5I unit rejected 18027 after interview over home office). Keep it visible in the scout: 'maybe i need it later'. Fit unchanged (Sept estimate 86; JD re-fetched 2026-10-22, still live, no citizenship line).",
    "date": "2026-10-22"
  },
  "https://arbeidsplassen.nav.no/stillinger/stilling/d2560ea2-eef6-45e7-babe-f94f9f236b6b": {
    "company": "",
    "title": "",
    "decision": "skip",
    "note": "USER DECISION 2026-10-22: 'SLB doesn't attract me at the moment'. Fit was real (data-engineering body, English only, Glassdoor 3.9); deadline 2026-10-29. Not a Norway-lane closure.",
    "date": "2026-10-22"
  },
  "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Zurich/Senior-Software-Developer_JR2008695": {
    "company": "NVIDIA",
    "title": "Senior Software Developer",
    "decision": "skip",
    "note": "Claude triage 2026-10-22, JD read (reports/2026-10-22-fit-sources/nvidia_senior_software_developer.txt): AI networking acceleration library; requires '8 years experience in modern C++ / C / Rust development' and 'Deep knowledge of the TCP/IP network stack' - both Gap (C++ is secondary per feedback_cpp_emphasis; networking 0 canonical).",
    "date": "2026-10-22"
  },
  "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Remote/Senior-Production-Engineer----DGX-Cloud_JR2027105": {
    "company": "",
    "title": "",
    "decision": "applied",
    "note": "SUBMITTED 2026-10-22 via Workday. Evidence Fit 65 Stretch, hard gate PASS, Document Quality 85 (pre-edit; Edit 1 applied, not re-measured), channel Weak/cold, no cover letter. Package: output/NVIDIA_ProdEng_DGX_Cloud/.",
    "date": "2026-10-22"
  }
 }
@@ -0,0 +1,811 @@
 {
  "description": "Employer reputation lookups for job_scout (user requirement 2026-10-22: only recommend roles at employers with a good reputation as a place to work). Glassdoor blocks direct access (HTTP 403), so every figure here is a dated lookup from search results, not live data. Verdicts are computed by scout.reputation_verdict() from the thresholds below unless verdict_override is set. Entries older than 365 days show as STALE and must be re-checked. An employer missing from this file is UNCHECKED: look it up before recommending a role there.",
  "thresholds": {
    "good_min_rating": 3.8,
    "good_min_reviews": 50,
    "ok_min_rating": 3.5,
    "rule": "good: Glassdoor >= 3.8 with >= 50 reviews. ok: 3.5-3.79, or >= 3.8 on fewer than 50 reviews backed by a second source, or no Glassdoor page but a solid second source. avoid: below 3.5 unless the user overrides. excluded: user decision. A second source with a score (secondary_rating) must itself be >= 3.5 to back a thin or missing Glassdoor rating; below that the verdict is avoid. Glassdoor and kununu are both primary sources; whichever has more reviews decides (kununu is often far better populated for Swiss employers).",
    "approved": "user, 2026-10-22"
  },
  "employers": {
    "Vizrt": {
      "aliases": [],
      "verdict_override": "excluded",
      "note": "User decision 2026-10-22: worked there (Bergen, 2017-18) and does not want to work there again. Roles are hidden from reports.",
      "checked": "2026-10-22"
    },
    "Arm": {
      "aliases": [
        "Arm Norway",
        "ARM Norway"
      ],
      "glassdoor": {
        "rating": 4.5,
        "reviews": 2633,
        "scope": "company-wide"
      },
      "note": "Trondheim-specific reviews are mixed: recent ones positive, a 2023 one criticised local middle management for engineers relocating from abroad.",
      "sources": [
        "https://static.glassdoor.at/Reviews/Arm-Reviews-E7834_P800.htm",
        "https://static-pc.glassdoor.fr/Reviews/Employee-Review-Arm-E7834-RVW80607582.htm"
      ],
      "checked": "2026-10-22"
    },
    "Nordic Semiconductor": {
      "aliases": [
        "Nordic Semi"
      ],
      "glassdoor": {
        "rating": 4.0,
        "reviews": 103,
        "recommend_pct": 83,
        "scope": "company-wide"
      },
      "secondary": "TrueUp 82% recommend (100+ reviews)",
      "sources": [
        "https://www.glassdoor.com/Overview/X-EI_IE681660.htm",
        "https://www.trueup.io/co/nordic-semi"
      ],
      "checked": "2026-10-22"
    },
    "Equinor": {
      "aliases": [],
      "glassdoor": {
        "rating": 4.3,
        "reviews": 769,
        "recommend_pct": 87,
        "scope": "company-wide"
      },
      "secondary": "Indeed 4.0 (299); Universum: top student employer in engineering/business/technology 2024",
      "sources": [
        "https://www.glassdoor.co.uk/Reviews/Equinor-Reviews-E10408.htm",
        "https://uk.indeed.com/cmp/Equinor/reviews"
      ],
      "checked": "2026-10-22"
    },
    "Kongsberg": {
      "aliases": [
        "Kongsberg Gruppen",
        "Kongsberg Maritime",
        "Kongsberg Digital",
        "Kongsberg Defence",
        "Kongsberg Discovery",
        "Kongsberg Satellite Services",
        "KSAT",
        "Kongsberg Norcontrol",
        "Kongsberg Seatex"
      ],
      "not_aliases": [
        "Kongsberg Automotive"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "secondary": "No Glassdoor page found; Indeed 3.8 (101 reviews, group); Universum 2025 professionals: 3rd in IT, 2nd in Engineering",
      "note": "Ratings vary by division; Kongsberg Maritime JobStreet sample is small (7). Kongsberg Automotive is an unrelated company and is NOT covered by this entry.",
      "sources": [
        "https://uk.indeed.com/cmp/Kongsberg-1",
        "https://www.kongsberg.com/news/stories/2025/11/Professionals-place-KONGSBERG-among-Norways-top-employers-in-Universum/"
      ],
      "checked": "2026-10-22",
      "secondary_rating": 3.8
    },
    "DNV": {
      "aliases": [
        "DNV AS"
      ],
      "glassdoor": {
        "rating": 4.2,
        "reviews": 94,
        "recommend_pct": 82,
        "scope": "company-wide (CA/NZ snapshot; UK page 3.9 on 47)"
      },
      "secondary": "Indeed 3.8 (444 reviews, Feb 2026)",
      "note": "Praised for flexibility and people; common complaints are pay and slow progression.",
      "sources": [
        "https://www.glassdoor.ca/Reviews/DNV-Reviews-E6648554.htm",
        "https://uk.indeed.com/cmp/Dnv/reviews"
      ],
      "checked": "2026-10-22"
    },
    "SINTEF": {
      "aliases": [],
      "glassdoor": {
        "rating": 4.0,
        "reviews": 62,
        "recommend_pct": 81,
        "scope": "company-wide"
      },
      "note": "Autonomy and good people; salary on the lower end, some bureaucracy for project leads.",
      "sources": [
        "https://www.glassdoor.co.in/Reviews/SINTEF-Reviews-E458950.htm"
      ],
      "checked": "2026-10-22"
    },
    "Telenor": {
      "aliases": [
        "Telenor Norge",
        "Telenor ASA"
      ],
      "glassdoor": {
        "rating": 3.8,
        "reviews": 1305,
        "recommend_pct": 65,
        "scope": "company-wide, not Norway-specific"
      },
      "secondary": "Indeed 4.1 (311)",
      "note": "Exactly at the threshold. Good work-life balance; complaints about limited growth and frequently changing strategy.",
      "sources": [
        "https://www.glassdoor.com/Reviews/Telenor-Reviews-E11282.htm"
      ],
      "checked": "2026-10-22"
    },
    "Microsoft": {
      "aliases": [
        "Microsoft Norge",
        "Microsoft Development Center Norway"
      ],
      "glassdoor": {
        "rating": 4.0,
        "reviews": 54474,
        "recommend_pct": 76,
        "scope": "company-wide"
      },
      "sources": [
        "https://static-pc.glassdoor.fr/Reviews/Microsoft-Reviews-E1651.htm"
      ],
      "checked": "2026-10-22"
    },
    "NATO": {
      "aliases": [
        "NATO JWC",
        "Joint Warfare Centre"
      ],
      "glassdoor": {
        "rating": 4.0,
        "reviews": 240,
        "recommend_pct": 93,
        "scope": "all NATO bodies"
      },
      "note": "Pay, benefits, international setting; heavy workload, bureaucracy, rigid military structure. Reviews do not separate civilian staff.",
      "sources": [
        "https://www.glassdoor.com/Reviews/NATO-Reviews-E22846.htm"
      ],
      "checked": "2026-10-22"
    },
    "Nammo": {
      "aliases": [],
      "glassdoor": {
        "rating": 3.9,
        "reviews": 21,
        "recommend_pct": 56,
        "scope": "company-wide"
      },
      "secondary": "Indeed 3.2 (87 reviews)",
      "note": "Thin and mixed: Glassdoor 3.9 on only 21 reviews with 56% recommending; the larger Indeed sample is 3.2, below the 3.5 line. A 2026 review alleges production pressure compromising safety. User may override.",
      "sources": [
        "https://www.glassdoor.co.nz/Reviews/Nammo-Reviews-E4444878.htm",
        "https://www.indeed.com/cmp/Nammo"
      ],
      "checked": "2026-10-22",
      "secondary_rating": 3.2
    },
    "Kitron": {
      "aliases": [],
      "glassdoor": {
        "rating": 3.1,
        "reviews": 15,
        "recommend_pct": 34,
        "scope": "company-wide"
      },
      "note": "Below threshold on a thin sample: limited growth, pay, unclear strategy.",
      "sources": [
        "https://www.glassdoor.co.uk/Reviews/Kitron-Reviews-E311133.htm"
      ],
      "checked": "2026-10-22"
    },
    "Google": {
      "glassdoor": {
        "rating": 4.4,
        "reviews": 48616,
        "scope": "company-wide",
        "recommend_pct": 87
      },
      "sources": [
        "https://static.glassdoor.ca/Reviews/Google-Reviews-E9079.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "NVIDIA": {
      "glassdoor": {
        "rating": 4.4,
        "reviews": 5486,
        "scope": "company-wide",
        "recommend_pct": 91
      },
      "sources": [
        "https://static.glassdoor.at/Reviews/NVIDIA-Reviews-E7633_P92.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Roche": {
      "glassdoor": {
        "rating": 4.1,
        "reviews": 6459,
        "scope": "company-wide",
        "recommend_pct": 82
      },
      "note": "Recurring: job-security worries during transformation, slow progression; experience varies by team.",
      "sources": [
        "https://static.glassdoor.fr/Reviews/Roche-Reviews-E3480_P90.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Novartis": {
      "glassdoor": {
        "rating": 4.0,
        "reviews": 9050,
        "scope": "company-wide",
        "recommend_pct": 80
      },
      "note": "Recurring: slow advancement, restructuring.",
      "sources": [
        "https://static.glassdoor.ch/Reviews/Novartis-Reviews-E6667_P33.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Apple": {
      "glassdoor": {
        "rating": 4.1,
        "reviews": 43100,
        "scope": "company-wide",
        "recommend_pct": 79
      },
      "sources": [
        "https://static.glassdoor.de/Reviews/Apple-Reviews-E1138_P159.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "OpenAI": {
      "glassdoor": {
        "rating": 4.1,
        "reviews": 100,
        "scope": "company-wide",
        "recommend_pct": 74
      },
      "note": "High pace and workload; culture said to have become more top-down.",
      "sources": [
        "https://www.glassdoor.com.au/Reviews/OpenAI-Reviews-E2210885.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Anthropic": {
      "glassdoor": {
        "rating": 4.2,
        "reviews": 30,
        "scope": "company-wide",
        "recommend_pct": 86
      },
      "secondary": "JobsByCulture aggregate 4.4 (222 Glassdoor reviews, Mar 2026)",
      "note": "Glassdoor's own page is thin (27-34 reviews); main complaint is workload.",
      "sources": [
        "https://www.glassdoor.co.in/Reviews/Anthropic-Reviews-E8109027.htm",
        "https://makerstations.io/anthropic-employee-statistics"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Kraken": {
      "aliases": [
        "Payward"
      ],
      "glassdoor": {
        "rating": 4.4,
        "reviews": 216,
        "scope": "company-wide",
        "recommend_pct": 91
      },
      "note": "No HR function by design; pay not top of market.",
      "sources": [
        "https://static.glassdoor.es/Reviews/Kraken-Reviews-E8860582.htm"
      ],
      "checked": "2026-10-22"
    },
    "Databricks": {
      "glassdoor": {
        "rating": 4.0,
        "reviews": 1620,
        "scope": "company-wide",
        "recommend_pct": 76
      },
      "sources": [
        "https://static.glassdoor.ch/Reviews/Databricks-Reviews-E954734_P7.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Snowflake": {
      "glassdoor": {
        "rating": 3.7,
        "reviews": 1087,
        "scope": "company-wide",
        "recommend_pct": 66
      },
      "note": "Below the good line: KPI pressure, more corporate/political.",
      "sources": [
        "https://static.glassdoor.de/Reviews/Snowflake-Reviews-E928471.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Palantir": {
      "glassdoor": {
        "rating": 3.7,
        "reviews": 886,
        "scope": "company-wide",
        "recommend_pct": 65
      },
      "note": "Work-life balance weak (aggregator 2.8); long hours.",
      "sources": [
        "https://static.glassdoor.co.uk/Reviews/Palantir-Technologies-Reviews-E236375.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Amazon": {
      "aliases": [
        "AWS",
        "Amazon Web Services",
        "Amazon / AWS"
      ],
      "glassdoor": {
        "rating": 3.6,
        "reviews": 13935,
        "scope": "AWS",
        "recommend_pct": 62
      },
      "note": "Work-life balance 3.0.",
      "sources": [
        "https://static.glassdoor.at/Reviews/Amazon-Web-Services-Reviews-E7470741_P74.htm"
      ],
      "checked": "2026-10-22"
    },
    "Meta": {
      "glassdoor": {
        "rating": 3.6,
        "reviews": 17952,
        "scope": "company-wide",
        "recommend_pct": 55
      },
      "sources": [
        "https://www.glassdoor.co.uk/metacareers"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "GitLab": {
      "glassdoor": {
        "rating": 3.6,
        "reviews": 735,
        "scope": "company-wide",
        "recommend_pct": 58
      },
      "note": "Mixed (3.3-3.6 across snapshots): leadership and culture shifts.",
      "sources": [
        "https://www.glassdoor.com/Reviews/GitLab-Reviews-E1296544.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Grafana Labs": {
      "aliases": [
        "Grafana"
      ],
      "glassdoor": {
        "rating": 4.1,
        "reviews": 215,
        "scope": "company-wide",
        "recommend_pct": 79
      },
      "note": "Frequent leadership changes. Geo-fenced pay (see scout memory).",
      "sources": [
        "https://www.glassdoor.com/Reviews/Grafana-Labs-Reviews-E2300269.htm"
      ],
      "checked": "2026-10-22"
    },
    "Datadog": {
      "glassdoor": {
        "rating": 4.0,
        "reviews": 1630,
        "scope": "company-wide",
        "recommend_pct": 75
      },
      "note": "3 office days/week, no remote.",
      "sources": [
        "https://static.glassdoor.it/Reviews/Datadog-Reviews-E762009.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Elastic": {
      "glassdoor": {
        "rating": 3.7,
        "reviews": 880,
        "scope": "company-wide",
        "recommend_pct": 68
      },
      "note": "Snapshots range 3.6-3.9; layoffs and reorgs.",
      "sources": [
        "https://www.glassdoor.co.uk/Reviews/Elastic-Reviews-E751551.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Fivetran": {
      "glassdoor": {
        "rating": 3.6,
        "reviews": 440,
        "scope": "company-wide",
        "recommend_pct": 66
      },
      "secondary": "Blind 3.5 (103)",
      "note": "Leadership and layoffs criticised.",
      "sources": [
        "https://www.glassdoor.com.au/Reviews/Fivetran-Reviews-E1415980.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "Cisco": {
      "aliases": [
        "Isovalent",
        "Splunk"
      ],
      "glassdoor": {
        "rating": 4.1,
        "reviews": 33605,
        "scope": "company-wide",
        "recommend_pct": 82
      },
      "note": "Recurring layoffs.",
      "sources": [
        "https://static.glassdoor.com.mx/Reviews/Cisco-Reviews-E1425_P51.htm"
      ],
      "checked": "2026-10-22"
    },
    "IBM": {
      "aliases": [
        "Confluent",
        "Confluent (IBM)",
        "HashiCorp"
      ],
      "glassdoor": {
        "rating": 3.9,
        "reviews": 107347,
        "scope": "company-wide",
        "recommend_pct": 78
      },
      "note": "IBM rating; Confluent has been IBM since 2026-03-17.",
      "sources": [
        "https://static.glassdoor.it/Reviews/IBM-Reviews-E354_P4.htm"
      ],
      "checked": "2026-10-22"
    },
    "Axpo": {
      "glassdoor": {
        "rating": 3.9,
        "reviews": 91,
        "scope": "company-wide",
        "recommend_pct": 82
      },
      "sources": [
        "https://www.glassdoor.com/Reviews/Axpo-Reviews-E755157.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "CERN": {
      "glassdoor": {
        "rating": 4.3,
        "reviews": 854,
        "scope": "company-wide",
        "recommend_pct": 91
      },
      "note": "Pay low for Switzerland; short-term contracts.",
      "sources": [
        "https://www.glassdoor.com/Reviews/CERN-Reviews-E150483.htm"
      ],
      "aliases": [],
      "checked": "2026-10-22"
    },
    "MET Group": {
      "aliases": [
        "METGroup"
      ],
      "glassdoor": {
        "rating": 3.7,
        "reviews": 34,
        "scope": "company-wide, 2024 snapshot",
        "recommend_pct": 70
      },
      "note": "Thin and dated (24-34 reviews, 2024).",
      "sources": [
        "https://www.glassdoor.ie/Reviews/Met-Group-Reviews-E734317.htm"
      ],
      "checked": "2026-10-22"
    },
    "BIS": {
      "aliases": [
        "Bank for International Settlements",
        "BIS (Basel)"
      ],
      "glassdoor": {
        "rating": 2.9,
        "reviews": 56,
        "scope": "company-wide",
        "recommend_pct": 42
      },
      "note": "BELOW threshold: 42% recommend, 33% CEO approval (page may list an outdated CEO). Thin but 56 reviews. NB: an application (jr100498) is pending there.",
      "sources": [
        "https://www.glassdoor.com/Overview/X-EI_IE10670.htm"
      ],
      "checked": "2026-10-22"
    },
    "RUAG": {
      "aliases": [
        "RUAG (Thun/Bern)"
      ],
      "not_aliases": [
        "RUAG International"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "secondary": "Indeed CH 3.1 (sample size not shown)",
      "note": "kununu group 3.5 on 523 reviews (73% recommend, last 2 years) replaces the thin Indeed 3.1. Subsidiaries vary: RUAG Aviation 3.1 (26), RUAG Ammotec 3.0 (17); RUAG International (2.8) is a different entity. Industry average 3.4.",
      "sources": [
        "https://ch.indeed.com/cmp/Ruag/reviews",
        "https://www.kununu.com/ch/ruag"
      ],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.5,
        "reviews": 523,
        "recommend_pct": 73,
        "scope": "RUAG Schweiz group profile"
      }
    },
    "SBB": {
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "secondary": "Indeed CH 4.2 (46); kununu 3.46 (289) in 2015, dated",
      "sources": [
        "https://ch.indeed.com/cmp/Sbb-Ag/reviews",
        "https://www.netzwoche.ch/news/2015-02-05/top-10-der-schweizer-arbeitgeber-ausgezeichnet",
        "https://www.kununu.com/ch/sbbcffffs/kommentare"
      ],
      "aliases": [],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.8,
        "reviews": 1808,
        "scope": "SBB CFF FFS"
      },
      "note": "Praised: atmosphere, pay and benefits, home office; criticised: leadership and communication. An older SBB Informatik review is notably critical."
    },
    "Swissgrid": {
      "aliases": [
        "Swissgrid (Aarau)"
      ],
      "glassdoor": {
        "rating": 4.2,
        "reviews": 6,
        "scope": "6 visible of 45",
        "recommend_pct": 91
      },
      "secondary": "jobs.ch 15 reviews, mostly positive",
      "note": "Snapshots range 3.5-3.9 (135-209 reviews). Pension fund, pay, varied work; leadership (3.5) and workload criticised; many external contractors.",
      "sources": [
        "https://www.glassdoor.ca/Reviews/Swissgrid-Reviews-E673595.htm",
        "https://www.jobs.ch/en/companies/7621-swissgrid-ag/reviews/",
        "https://www.kununu.com/ch/swissgrid"
      ],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.6,
        "reviews": 146
      }
    },
    "PostFinance": {
      "aliases": [
        "PostFinance (Bern)"
      ],
      "glassdoor": {
        "rating": 4.1,
        "reviews": 16,
        "scope": "company-wide",
        "recommend_pct": 79
      },
      "secondary": "Indeed CH 3.6 (25)",
      "note": "Colleagues 4.1, communication 3.3; promotion criticised; an Oct 2026 comment reports a recent decline in atmosphere and work-life balance.",
      "sources": [
        "https://www.glassdoor.com/Reviews/PostFinance-Reviews-E602813.htm",
        "https://ch.indeed.com/cmp/Postfinance-Ag/reviews",
        "https://www.kununu.com/ch/postfinance6/kommentare"
      ],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.8,
        "reviews": 497,
        "recommend_pct": 76
      }
    },
    "BFH": {
      "aliases": [
        "Berner Fachhochschule",
        "BFH (Bern)"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "secondary": "Indeed CH 3.5; Glassdoor career-opportunities sub-score 3.9 (64); Swiss Arbeitgeber Award 2022 top-3 large employer",
      "sources": [
        "https://ch.indeed.com/cmp/Berner-Fachhochschule",
        "https://www.plattformj.ch/artikel/204982/",
        "https://www.kununu.com/ch/berner-fachhochschule"
      ],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.3,
        "reviews": 132,
        "recommend_pct": 52
      },
      "note": "Below the education-sector average (3.6): communication 2.6, leadership 2.8; interesting work 3.8."
    },
    "BKW": {
      "aliases": [
        "BKW (Bern)",
        "BKW Energie"
      ],
      "not_aliases": [
        "BKW Management"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "note": "Interesting work and conditions; communication (3.2) and leadership criticised.",
      "sources": [
        "https://www.glassdoor.com/Reviews/BKW-Reviews-E40434.htm",
        "https://www.kununu.com/ch/bkwag"
      ],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.7,
        "reviews": 345,
        "recommend_pct": 70,
        "scope": "BKW AG"
      }
    },
    "Schweizer Armee": {
      "aliases": [
        "Kdo Cy",
        "Kommando Cyber",
        "Schweizer Armee - Kdo Cy",
        "Bundesverwaltung"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "note": "Federal administration profile (no Kdo-Cy-specific profile): varied work, pay and benefits praised; career progression, communication and leadership criticised; slow hiring processes. Below the public-administration average (3.5).",
      "sources": [
        "https://www.jobs.ch/en/companies/70645-bundesverwaltung/reviews/",
        "https://www.kununu.com/ch/vbs-schweizer-armee"
      ],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.4,
        "reviews": 997,
        "recommend_pct": 63,
        "scope": "Bundesverwaltung / VBS profile"
      }
    },
    "QuantCo": {
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "note": "Thin (18 reviews, German entity); pay and benefits 5.0. Not to be confused with Quant Qualitaetssicherung.",
      "aliases": [],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 4.3,
        "reviews": 18,
        "recommend_pct": 94,
        "scope": "QuantCo Germany (Rodgau)"
      },
      "sources": [
        "https://www.kununu.com/de/quantco6"
      ]
    },
    "Bitcoin Suisse": {
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "note": "Thin (14-18 reviews); leadership said to have worsened after a management change.",
      "sources": [
        "https://trueup.io/co/bitcoin-suisse",
        "https://www.kununu.com/ch/bitcoin-suisse1"
      ],
      "aliases": [],
      "checked": "2026-10-22",
      "kununu": {
        "rating": 3.8,
        "reviews": 18,
        "recommend_pct": 77
      }
    },
    "SLB": {
      "aliases": [
        "Schlumberger",
        "SLB OneSubsea",
        "OneSubsea"
      ],
      "glassdoor": {
        "rating": 3.9,
        "reviews": 15113,
        "recommend_pct": 73,
        "scope": "company-wide"
      },
      "note": "Work-life balance 3.4 (lowest sub-rating), culture 3.9, career 3.8; praise for training and international mobility, criticism of long hours and management. Industry average 3.7.",
      "sources": [
        "https://static.glassdoor.com.br/Reviews/SLB-Reviews-E588_P3871.htm"
      ],
      "checked": "2026-10-22"
    },
    "MazeMap": {
      "aliases": [
        "Mazemap As",
        "MazeMap AS"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "verdict_override": "unchecked",
      "note": "Glassdoor page exists with a single review (3.0, March 2024: good colleagues and office; no full remote, sales over engineering). One review is no signal, so the verdict stays unchecked. ~21 employees (OpenCorporates). Do not confuse with 'Maze' (E4132839).",
      "sources": [
        "https://www.glassdoor.com/Reviews/MazeMap-Reviews-E4814325.htm",
        "https://opencorporates.com/companies/no/912197905"
      ],
      "checked": "2026-10-22"
    },
    "SpareBank 1 Nord-Norge": {
      "aliases": [
        "SpareBank 1 Nord Norge",
        "Sparebanken Nord-Norge"
      ],
      "glassdoor": {
        "rating": null,
        "reviews": null
      },
      "verdict_override": "unchecked",
      "note": "No Glassdoor, Great Place to Work or Universum entry found 2026-10-22. Bytt.no's 2.5 is a CUSTOMER rating, not an employee one, and must not be used.",
      "sources": [],
      "checked": "2026-10-22"
    }
  }
 }
@@ -0,0 +1,41 @@
 # Software design and architecture at Bosch and Swisscom — user clarification
 Source: direct user message, 2026-10-21, during the Google *Staff Software Engineer, Shopping Graph*
 fit check. The posting's minimum qualification under test was *"3 years of experience with software
 design and architecture."*
 Question asked: since when he has done software design or architecture work, e.g. how long he designed
 services and integrations at Bosch and since when he has designed data products at Swisscom.
 Verbatim:
 > Yeah, I mean... Software Design and Architecture (for Data Products, for ingestion/inference scripts at Bosch) were part and my work at Swisscom and Bosch can consider this.
 Established facts:
 - **Bosch (2020-02 to 2022-12):** software design and architecture were part of his work, for the
  **ingestion and inference scripts** he built. "Scripts" is his word; the statement does not extend
  `designed` to the Bosch data services in general. This pairs with BS-1 (the Zeugnis's
  *"Erarbeitung und Durchfuehrung von Integrationsstrategien"* for ML models in the 24/7 fab) and BS-2
  (data services in Python/Java/C# over Oracle and Hadoop/Impala).
 - **Swisscom (2023-10 to present):** software design and architecture were part of his work, for
  **data products** (SW-7; the 2026-10-03 clarification already established design of data products as
  current work).
 - The user states that his work at both employers can be counted toward a "years of software design and
  architecture" requirement. Bosch alone spans 2 years 11 months (elapsed time). Together with the
  Swisscom data-product design, the total exceeds three years.
 Not established:
 - The date design work began at Swisscom. The ART B2B / ART DPT switch date stays deliberately unrecorded,
  so never date it.
 - Any architecture role or title, any company-wide or cross-organisation architecture authority, and any
  architecture-governance or design-authority function. Design is scoped to **his own** ingestion and
  inference scripts, the inference integration (BS-1) and his data products.
 - The architecture of shared platforms (the Data Mesh, ODP-Flow, the Bosch fab IT architecture). Scope
  Discipline still applies: he designed his components inside them, never the platforms themselves.
 - Full-time-equivalent years. The year count is elapsed time, consistent with the D3 ruling on Bosch
  part-time.
 Canonical destination: BS-1, BS-2 and SW-7 scope notes, plus `designed` as an allowed verb on BS-1 and
 BS-2 for his own scripts only, in `resume_builder/canonical/claims.json`.
@@ -0,0 +1,66 @@
 # On-duty alerting, networking and Bosch GPUs — user clarification
 Source: direct user message, 2026-10-22, during the NVIDIA *Senior Production Engineer, DGX Cloud*
 (JR2027105) fit check. Three questions were asked because the KB has repeatedly under-recorded
 ordinary operations work (Ansible, Linux, Bash, Kotlin, Jenkins/GitLab).
 ## Questions and verbatim answers
 1. *Monitoring in your current Swisscom unit: do you monitor or get alerted on your Glue/Airflow
   pipelines (CloudWatch alarms, failure alerts, dashboards)? Is there on-call in your current team?*
   > Yes, we get alerted ... we are using opsgenie and we have a engineer on duty role which rotates.
   > Bugs and Alerts also automatically create Jira issue tickets which we dann asign an fix.
 2. *Networking at work: any AWS VPC, security group or private-endpoint work at Swisscom, or firewall,
   DNS, proxy or load-balancer work at Bosch?*
   > No, not really - probably only my AWS solution architect cert covers AWS network topics... but day
   > to day work is using automated landing zones.
 3. *GPUs at Bosch: did the ML inference containers run on GPUs?*
   > The ML inference did ran on NVIDIA GPUs (using CUDA for performance boost - but i never did much
   > configuration there)
 ## Follow-up questions and verbatim answers (same day)
 4. *Bosch monitoring PoC: your earlier CV says it also included Grafana, Prometheus and Loki; the Bosch
   reference letter only mentions ELK. Correct?* and 5. *Do you also write or adjust the alerts for your
   own pipelines, or only respond to them?*
   > 1. both are correct 2. yes, i wrote e.g. thresholds for data quality etc....
 ## Established facts
 - **BS-4 stack:** the Bosch PoC covered ELK and Kafka plus monitoring and alerting with Grafana,
  Prometheus and Loki. It is still a proof of concept.
 - **SW-11 alert definitions:** he defines alert thresholds for his own pipelines; data-quality
  thresholds are the named example. Other alert types are not established.
 - **Current on-duty (new claim SW-11):** his current Swisscom team uses Opsgenie for alerting and has a
  rotating engineer-on-duty role that he takes part in. Bugs and alerts automatically create Jira
  tickets, which the team assigns and fixes. This is the current counterpart of the past SW-2 on-call
  at ART B2B.
 - **Networking (skill `networking`, certification context only):** no professional network
  configuration. AWS networking is covered by the AWS Certified Solutions Architect – Associate
  (26 Sep 2024, active). At work he uses automated AWS landing zones that the platform provides.
 - **Bosch GPUs (BS-1 scope):** the containerized ML inference he integrated ran on NVIDIA GPUs, with
  CUDA used for acceleration. He did little CUDA or GPU configuration himself.
 ## Not established
 - Who built or configured the alerting, the Opsgenie routing or the Jira automation.
 - Which metrics or logs feed the alerts; SLIs, SLOs or error budgets at Swisscom.
 - Incident counts, response times, MTTR or availability figures.
 - Whether the on-duty role covers nights and weekends (do not write 24/7).
 - Any professional VPC, security-group, firewall, DNS, proxy or load-balancer work.
 - Building or designing landing zones or network topology.
 - CUDA programming or configuration, GPU tuning or GPU performance analysis. GPU model, count and
  serving framework at Bosch.
 ## Canonical destination
 `claims.json`: new claim **SW-11**; **BS-1** scope and forbidden list; skills **Opsgenie**
 (allowed-with-context), **CUDA** (forbidden; system context only) and **networking**
 (certification-context-only).
@@ -0,0 +1,144 @@
 # Critique: Google — Staff Software Engineer, Shopping Graph (Feeds Infra), Zürich
 > **STALE (2026-10-21):** the resume was edited after this critique (leadership framing, SW-8, BS-1, trims). See the
 > session Edit History. Evidence Fit (70, Stretch, gate PASS) is unaffected; Document Quality needs a re-score.
 Date: 2026-10-21. Document: `e2e_google_staff_swe_shopping_graph_resume.tex` / `.pdf` (2 pages).
 JD: `jd_google_staff_swe_shopping_graph_2026-10-21.txt`, a verbatim Playwright render of the live posting,
 retrieved 2026-10-21. Cover letter: intentionally omitted (session decision NO).
 ## 1. Fit verdict and hard-gate audit
 **Verdict: STRETCH, hard gate PASS.** Every minimum qualification is met, so nothing disqualifies the
 application. It is a Stretch because the role's defining responsibility, Staff-level technical leadership,
 is only Adjacent (`application_strategy.md`: "a defining responsibility is only Adjacent").
 | Minimum qualification | Class | Evidence on the page | Risk |
 |---|---|---|---|
 | Bachelor's or equivalent | Direct | B.Eng., M.Eng. | none |
 | 8 yrs programming in C++/Java/Python/Kotlin/Go | Direct, tight | Generali Java 2015-17, Vizrt Python/C++ 2017-18, Bosch Python/Java 2020-22, Swisscom Python/PySpark 2023- (about 8.8 yrs; 8.0 without Vizrt). Fraunhofer was C#/JS and does not count | A recruiter who discounts Vizrt (a *contribution*) lands exactly on 8 |
 | 5 yrs testing and launching software | Direct | GN-1, VZ-2, FC-1, BS-1, SW-1, SW-9 | none |
 | 3 yrs software design and architecture | Direct, scoped | SW-7 (present), BS-2 scripts, BS-1 integration, GN-3 contribution; iSAQB CPSA-F | Design is component-scale. A Staff reader expects system design of large services |
 | GenAI / LLM interfaces integrated into workflows | Direct, modest | SW-8 bullet; LiteLLM, Copilot, Kiro | Configuration/integration level only. Expect "what did you build with it?" |
 No level-based NO-GO trigger applies: the role is an IC tech lead, not people management, external-account
 ownership or company-wide architecture authority.
 ## 2. Evidence Fit — 70 / 100 (Stretch by definition)
 Scored independently of the provisional 73 in the session. It comes out stricter on responsibilities and
 level, as seen from the hiring manager's chair.
 | Dimension | Weight | Score | Reason |
 |---|--:|--:|---|
 | Required qualifications | 35 | 31 | All five Direct; two are tight or modest (8 yrs, GenAI) |
 | Core responsibilities | 25 | 15 | Design/build/test/deploy and ingestion with data quality are Direct. Four of the five responsibility lines are leadership or coordination, and those are Adjacent |
 | Level and ownership | 15 | 7 | Component Owner, Application Owner and mentoring; no recorded project-team lead or technical direction set for others |
 | Recency and depth | 10 | 8 | Current Python/PySpark/AWS ingestion and data-product design |
 | Domain/tool transfer | 10 | 6 | Ingestion and data quality transfer well. Web crawling and the commerce domain are gaps. Java is historical (Google Feeds Infra is likely Java/C++-heavy). Google's internal stack is new to every external candidate |
 | Practical constraints | 5 | 3 | Zürich hybrid against a 3-homeoffice-day baseline, plus the Thun–Zürich commute. Acceptable only for a clear overall improvement; clarify at first contact |
 | **Total** | 100 | **70** | Numerically Adjacent. **Classified Stretch** because a defining responsibility is only Adjacent |
 ## 3. Document Quality — 84 / 100
 | Dimension | Weight | Score | Reason |
 |---|--:|--:|---|
 | Truth and provenance | 25 | 24 | Every claim traces to `claims.json` (audit below). One framing nit: the SW-8 bullet puts the domain-grounded assistants inside "development workflows", but their recorded use is Q&A and domain tasks |
 | Information hierarchy | 20 | 16 | Employer/title/dates are clean. Page 1 carries only Swisscom, and the Bosch design and ingestion evidence that backs the 3-yr design minimum sits on page 2. About a quarter of page 1 is white space (acceptable, not padding) |
 | Bullet evidence and impact | 20 | 14 | Specific and scoped, but almost no outcomes: only "reduced manual image classification". No verified scale or impact numbers exist, and none was invented. For a Staff screen the leadership evidence is thin on the page |
 | Relevance and terminology | 15 | 12 | Ingestion, data quality, design, architecture, testing, GenAI and matrixed work are all covered. The JD's "launching" has no visible counterpart; "technical direction" is absent (correctly, since it is unrecorded) |
 | Skills evidence | 10 | 9 | Every skill is canonical and interview-ready; 8 rendered lines, at the top of the range |
 | Mechanics/readability | 10 | 8 | 2 pages, no overfull/underfull boxes, validator 0 warnings, cadence within range. Three bullets run to about 35-37 words (SW-2, BS-2, Generali). Minor hyphenation: *Spot-fire*, *exam-iner*, *mod-els* |
 | **Total** | 100 | **84** | |
 Truth/provenance is 24/25, above the automatic-failure line.
 ## 4. Channel Strength — Weak
 Cold submit through Google Careers. The user has no referral, and Google postings name no contact. The last
 three cold Google applications drew no interview; no cause is inferred from that. Optional warm action: a short
 LinkedIn note to a Google Zürich Commerce/Shopping technical recruiter after submitting. It does not upgrade
 the channel unless it produces a conversation.
 ## 5. Competitive read and reader sequence
 - **Obvious-fit competitor:** a senior/staff backend engineer from a large-scale ingestion or catalog team,
  current in Java/C++, who has tech-led several engineers.
 - **Dennis's real advantage:** a decade of ingestion and data-quality work across very different sources (fab
  sensor/process data, telco fulfillment data), current data-product design on AWS, and production
  integration under a hard failure constraint (24/7 fab).
 - **Competitor's real advantage:** Google-scale distributed systems, current Java/C++, and a recorded
  tech-lead role. Do not value the bridge as highly as their direct evidence.
 | Reader | Verdict | Reason |
 |---|---|---|
 | Parser/ATS | Pass | Single column; text extracts in employer, dates, title, location order; core JD terms present |
 | Recruiter glance | **Borderline** | Minimums visibly met, but no Staff-level tech-lead signal. The recruiter may consider a lower level or pass |
 | Hiring manager | Maybe | Ingestion and data quality are directly relevant; scale and team leadership are not shown |
 | Technical reviewer | Credible | First challenges: "a system you designed end to end, its scale and trade-offs"; "how you set direction for other engineers"; Java currency |
 ## 6. Claim audit
 | Claim | Canonical | D/A | Safe? | Fix |
 |---|---|---|---|---|
 | Summary: over ten years of software engineering | GENERALI 2015-05 → present (Capgemini omitted) | Direct | yes | — |
 | Summary/BS: designed ingestion scripts and the ML-inference integration | BS-2, BS-1 (2026-10-21) | Direct | yes | — |
 | Design and build governed data products ... Atlassian Compass | SW-7 | Direct | yes, scoped to "within company-wide Data Mesh" | — |
 | Migrated legacy ETL for owned domains ... Glue/PySpark/Iceberg/Airflow, pytest, part of company-wide programme | SW-1, SW-6, SW-9 | Direct | yes, scope hedged | — |
 | Owned ETL component, Oracle → Teradata, quality/security/compliance, on-call | SW-2 (past) | Direct | yes, past tense | — |
 | Integrated LLM tooling into development workflows; configured assistants; LiteLLM, Copilot, Kiro | SW-8 | Direct (modest) | yes; framing nit | Tier 2 #3 |
 | Onboarded and mentored junior developers; prototype-and-iterate with stakeholders | SW-10, SW-4 | Direct | yes, past tense | — |
 | Data services in Python and Java over Oracle and Hadoop/Impala; defect/image/PCM data | BS-2 | Direct | yes | — |
 | Normalized spatial wafer data (SDO_GEOMETRY) across CRS; tuned performance | BS-8 | Direct | yes; transformation location not asserted | — |
 | ML inference integration; defect could have halted production; reduced manual classification | BS-1 | Direct | yes; approved wording, qualitative result | — |
 | Technical Application Owner, KLA DMS and Spotfire; TAF 2022 co-presentation | BS-3, BS-5 | Direct | yes | — |
 | Guided juniors; one Bachelor thesis as second examiner | BS-9, BS-7 | Direct | yes, not pluralised | — |
 | Fraunhofer: C#/SQL Server, Jenkins build jobs; Express.js/Docker microservices | FC-1, FC-3 | Direct | yes ("set up", no quality-gate claim) | — |
 | Vizrt: test suites as CI/CD quality gates; contributed Python/C++ | VZ-2, VZ-1 | Direct / contribution | yes | — |
 | Generali: Java/J2EE services, contributed to design; introduced BDD, trained team | GN-3, GN-1 | Direct | yes | — |
 | Skills: all listed; Kafka and Kubernetes historical but `allowed` | skills array | — | yes | — |
 | Certifications: AWS SAA 2024-2027; iSAQB CPSA-F 2016; IBM AI Engineering 2020 | thiessen_certifications.md | — | yes; IBM not shown as academic | — |
 Forbidden-term scan (validator): clean. No Capgemini, no LangChain, no Terraform/GCP/Flume, and no unverified
 metric.
 ## 7. Fixes
 **Tier 1 (truth/fit, blocks approval): none.** Validator PASS, and every claim is canonical. The Stretch
 classification is a fit finding the user already knows about, not a document defect.
 **Tier 2 (presentation, optional, ranked by expected effect):**
 1. **Leadership evidence: ask, don't write.** This is the decisive gap for a Staff screen. If true, the most
   valuable addition would be one recorded instance of setting technical direction for other engineers. For
   example: a data-product design pattern or modelling convention others adopted, design reviews he ran, or
   coordinating his domains' migration with other teams. It can only be added after the user confirms it and
   it is recorded in `claims.json`.
 2. **Scale.** Any verifiable count (data products designed, source systems onboarded, pipelines migrated, data
   volumes) would answer the "large-scale" question. Same rule: only from the user, recorded first.
 3. **SW-8 framing.** "Integrated LLM tooling into development workflows, configuring domain-grounded
   assistants..." links the assistants to development work, which is not recorded. Safer: "Configured
   domain-grounded LLM assistants by selecting models and supplying curated knowledge; use LiteLLM APIs,
   Copilot and Kiro in development."
 4. **A launch signal.** BS-1 allows `deployed`: "Designed the integration of containerized ML inference ...
   and deployed it into a continuously operating semiconductor fab, where ..." puts the JD's
   testing-and-launching sense into words without a new claim.
 5. **Trim the three ~35-37-word bullets** (SW-2, BS-2, Generali) by a clause each. Optional; they parse fine.
 ## 8. Cover letter
 Decision NO stands: not requested, the screen is driven by minimum qualifications, and a letter would add no
 transition, relocation or personal-connection context. Not penalised.
 ## 9. Mechanical verification
 - `validate_resume_system.py --document`: PASS, 0 warnings.
 - Fresh scratch compile: 2 pages, no overfull/underfull boxes. Its text matches the delivered PDF except the
  single-pass page footer.
 - `pdftotext`: employer, dates, title, location in order for all five roles; 648 words.
 - PDF metadata: empty Title and Author; Producer MiKTeX pdfTeX.
 - Contact line: Bern, B permit, email, phone, LinkedIn. No personal data. No Capgemini.
 - `page_metrics.py` could not run (Git's `pdftotext` lacks `-bbox`). Visually, experience starts at about 45%
  of page 1.
 **Status:** not submit-ready until the user approves this critique and decides on the Tier 2 items. Fit class
 Stretch; hard gate PASS.
@@ -0,0 +1,89 @@
 % Google - Staff Software Engineer, Shopping Graph (Feeds Infra), Zurich.
 % International Tech profile. Generated 2026-10-21 from resume_builder/canonical/claims.json
 % and the experience files; no historical output used as a source.
 % Session: session_google_staff_swe_shopping_graph.md
 \documentclass{resume}
 \usepackage[utf8]{inputenc}
 \usepackage[T1]{fontenc}
 \usepackage{lmodern}
 \usepackage[a4paper,left=0.65in,right=0.65in,top=0.55in,bottom=0.55in]{geometry}
 \usepackage{xcolor}
 \usepackage{hyperref}
 \hypersetup{hidelinks}
 \usepackage[version=4]{mhchem}
 \usepackage{fancyhdr}
 \pagestyle{fancy}
 \fancyhf{}
 \renewcommand{\headrulewidth}{0pt}
 \fancyfoot[R]{\small \thepage/\pageref{LastPage}}
 \name{Dennis Thiessen, M.Eng.}
 \headline{Staff Data Engineer $\vert$ Data Ingestion, Data Products, Data Quality $\vert$ Python, PySpark, AWS}
 \contactline{Bern, Switzerland (Swiss B permit) $\vert$ \href{mailto:dennis@thiessen.io}{dennis@thiessen.io} $\vert$ +41 795 955 585 $\vert$ \href{https://linkedin.com/in/dennis-thiessen}{LinkedIn}}
 \begin{document}
 \begin{rSection}{Summary}
 Staff data engineer with over ten years of software engineering. At Swisscom, sets the technical direction for the data products of his domains and designs and builds them on AWS; at Bosch, designed the ingestion scripts and the ML-inference integration for a continuously operating semiconductor fab.
 \end{rSection}
 \begin{rSection}{Technical Skills}
 \skillline{Languages}{Python, SQL, Bash; Java and Kotlin (earlier roles)}
 \skillline{Data processing}{PySpark, AWS Glue, Apache Airflow, Apache Iceberg, Athena, Redshift, Kafka, Oracle, Teradata, Hadoop/Impala; relational data modelling}
 \skillline{Platform}{AWS, CloudFormation, Docker, Kubernetes, GitLab CI/CD, Jenkins, Ansible, Linux}
 \skillline{Testing}{Unit testing with pytest; automated test suites as CI/CD quality gates; BDD test automation}
 \skillline{AI tooling}{LiteLLM, domain-grounded LLM assistants, Copilot, Kiro}
 \skillline{Certifications}{AWS Solutions Architect -- Associate (2024--2027); iSAQB \mbox{CPSA-F} software architecture (2016); IBM AI Engineering (2020)}
 \end{rSection}
 \begin{rSection}{Professional Experience}
 \begin{rSubsection}{Swisscom (Schweiz) AG}{Oct 2023 -- Present}{Staff Data, Analytics \& AI Engineer (promoted from Senior, Apr 2025)}{Bern, Switzerland}
 \item Design and build governed data products on AWS within Swisscom's company-wide Data Mesh: logical and physical relational models, source onboarding, and metadata and lineage documented in Atlassian Compass.
 \item Set the technical direction for a B2B data product whose requirements could not be fixed up front: built a prototype, proposed it to business stakeholders, architects and engineers, and iterated on it with them. Onboarded and mentored junior developers.
 \item As primary engineer for the owned data domains, migrated their legacy ETL pipelines to AWS as Python and PySpark Glue jobs on Apache Iceberg tables, orchestrated with Airflow and unit-tested with pytest, within the company-wide migration programme.
 \item Component Owner for the ETL that loaded business-critical Fulfillment data from Oracle into the Teradata data warehouse; responsible for its data quality and governance compliance through to on-call support.
 \item Integrated GenAI tools and LLM interfaces into workflows: configured domain-grounded assistants with curated knowledge and called models through LiteLLM APIs; develop with Copilot and Kiro.
 \end{rSubsection}
 \end{rSection}
 % Keep the current role on page 1 and start Bosch, the second major evidence block, on page 2.
 \newpage
 \begin{rSection}{Professional Experience (continued)}
 \begin{rSubsection}{Robert Bosch Semiconductor Manufacturing Dresden GmbH}{Feb 2020 -- Dec 2022}{Senior Data Engineer, Data Analysis (promoted from Data Engineer, Jan 2021)}{Dresden, Germany}
 \item Designed and built ingestion scripts and developed Python and Java data services over Oracle and Hadoop/Impala, serving fab analysis teams with defect records, wafer inspection images and PCM electrical parameters.
 \item Normalized spatial wafer data (Oracle SDO\_GEOMETRY) across the different coordinate reference systems of fab tools and systems and transformed it between them; tuned its performance.
 \item Designed the integration of containerized ML inference (Docker, Kubernetes, Ansible) and deployed it into a continuously operating semiconductor fab, where a software defect could have halted production; it reduced manual image classification.
 \item Served as technical Application Owner for the KLA Defect Management System and TIBCO Spotfire, defining their SLOs and handling vendor communication; co-presented wafer-map analytics at TIBCO Analytics Forum 2022.
 \item Guided junior developers and supervised student work, including one Bachelor thesis as second examiner.
 \end{rSubsection}
 \begin{rSubsection}{Fraunhofer Center for Maritime Logistics and Services CML}{Sep 2018 -- Oct 2019}{Research Software Engineer}{Hamburg, Germany}
 \item Developed C\# crew-scheduling software on Microsoft SQL Server and set up Jenkins build jobs for its automated deployment; built microservices for a research data-exchange platform with Express.js and Docker.
 \end{rSubsection}
 \begin{rSubsection}{Vizrt}{Jul 2017 -- May 2018}{Test Automation / DevOps Engineer}{Bergen, Norway}
 \item Developed automated test suites and connected them to the CI/CD pipeline as quality gates; contributed Python and C++ engineering to a distributed video-transcoding backend.
 \end{rSubsection}
 \begin{rSubsection}{Generali Deutschland Informatik Services GmbH}{May 2015 -- Jun 2017}{IT Consultant}{Hamburg, Germany}
 \item Developed Java/J2EE workflow services and contributed to their design and architecture; introduced Behaviour-Driven Development and trained the project team in it, with technical responsibility for its test automation.
 \end{rSubsection}
 \end{rSection}
 \begin{rSection}{Education}
 \compactentry{M.Eng. Computer Aided Engineering}{Apr 2012 -- Oct 2013}
 Universität der Bundeswehr München; Software Design \& Engineering.
 \compactentry{B.Eng. Information and Telecommunication Technologies}{Oct 2009 -- Oct 2012}
 Universität der Bundeswehr München.
 \end{rSection}
 \begin{rSection}{Languages}
 German (native), English (fluent)
 \end{rSection}
 \end{document}
@@ -0,0 +1,208 @@
 URL: https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland
 FINAL: https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland
 google.com/about/careers/applications uses cookies to deliver and enhance the quality of its services and to analyze traffic. If you agree, cookies are also used to serve advertising and to personalize the content and advertisements that you see. Learn more
 Agree
 No thanks
 Careers
 Skip navigation links
 home
 Home
 Home
 work_outline
 Jobs
 Jobs
 noogler_hat
 Students
 Students
 google
 How we work
 How we work
 handyman
 How we hire
 How we hire
 person_outline
 Your career
 Your career
 help_outline
 Help link
 feedback
 Send feedback
 Sign in
 Job Details
 arrow_back
 Back to jobs search
 Jobs Search Results
 AI Strategic Pursuit Lead, Automotive Agent, Google Cloud EMEA
 London, UK; Zürich, Switzerland; +1 more
 Staff Forward Deployed Engineer, GenAI, Google Cloud
 Zürich, Switzerland
 Software Engineer III, Shopping Ads
 Zürich, Switzerland
 Solution Architect, Capital Markets and Exchanges, Google Cloud
 Frankfurt am Main, Germany; Zürich, Switzerland; +2 more
 Staff Software Engineer, Generative AI, Commerce
 Zürich, Switzerland
 Senior Forward Deployed Engineer, GenAI, Google Cloud
 Zürich, Switzerland
 AI Outcome Customer Engineer, Google Cloud
 Zürich, Switzerland
 Research Scientist, User Signals from Agentic Logs, DeepMind
 Zürich, Switzerland
 Software Engineer III, Search Ads, Quality and AI
 Zürich, Switzerland
 Student Researcher, 2027
 Zürich, Switzerland; Berlin, Germany; +7 more
 Staff Research Engineer, Generative AI, Cloud AI Research, Co-Scientist
 Zürich, Switzerland
 Data Cloud Partner Specialist, Google Cloud
 London, UK; Zürich, Switzerland; +3 more
 Software Engineering PhD Intern, 2027
 Zürich, Switzerland
 Data Scientist Product MS Intern, 2027
 Zürich, Switzerland
 Software Engineer III, YouTube Viewcount and Aggregations
 Zürich, Switzerland
 Software Engineer III, Site Reliability Engineering, Prod AI
 Zürich, Switzerland
 Staff Research Data Scientist, Ads Metrics
 Zürich, Switzerland
 Staff Software Engineer, Site Reliability Engineering, Google Cloud
 Munich, Germany; Zürich, Switzerland
 Senior Staff Software Engineer, Site Reliability Engineering, Privacy, Security and Safety
 Zürich, Switzerland
 Software Engineer III, AI/ML YouTube Shopping Creator
 Zürich, Switzerland
 Showing 1 to 20 of 59 rows
 1‑20 of 59
 navigate_next
 Go to next page
 Staff Software Engineer, Shopping Graph
 share
 Share Staff Software Engineer, Shopping Graph
 corporate_fare
 Google
 place
 Zürich, Switzerland
 bar_chart
 Advanced
 Apply
 info_outline
 X
 In most instances, this position requires in-person interviews as part of the hiring process.
 Minimum qualifications:
 Bachelor's degree or equivalent practical experience.
 8 years of experience programming in C++, Java, Python, Kotlin or Go.
 5 years of experience testing, and launching software products.
 3 years of experience with software design and architecture.
 Experience integrating generative AI tools or LLM interfaces into workflows.
 Preferred qualifications:
 Master’s degree or PhD in Engineering, Computer Science, or a related technical field.
 8 years of experience with data structures/algorithms.
 3 years of experience in a technical leadership role leading project teams and setting technical direction.
 3 years of experience working in a complex, matrixed organization involving cross-functional, or cross-business projects.
 About the job
 Google's software engineers develop the next-generation technologies that change how billions of users connect, explore, and interact with information and one another. Our products need to handle information at massive scale, and extend well beyond web search. We're looking for engineers who bring fresh ideas from all areas, including information retrieval, distributed computing, large-scale system design, networking and data storage, security, artificial intelligence, natural language processing, UI design and mobile; the list goes on and is growing every day. As a software engineer, you will work on a specific project critical to Google’s needs with opportunities to switch teams and projects as you and our fast-paced business grow and evolve. We need our engineers to be versatile, display leadership qualities and be enthusiastic to take on new problems across the full-stack as we continue to push technology forward.
 The Shopping Graph is Google's comprehensive dataset of commercial information. It powers shopping experiences across all of Google, including Search, YouTube, Ads, and next-generation AI experiences like Gemini and AI Overviews. The Data Acquisition team is responsible for acquiring this high-quality commerce data. Our vision is to make it effortless for merchants to submit and enhance their product information, ensuring the Shopping Graph maintains extensive coverage and data quality.
 As a core pillar within Data Acquisition, the Feeds Infra team builds and owns the foundational infrastructure that ingests data into the Shopping Graph via files, APIs, and web crawling. Beyond ingestion, we empower merchants and downstream teams to continuously improve product data quality, meeting the rigorous demands and rising bar of Agentic Commerce.
 People shop on Google more than a billion times a day - and the Commerce team is responsible for building the experiences that serve these users. The mission for Google Commerce is to be an essential part of the shopping journey for consumers - from inspiration to to a simple and secure checkout experience - and the best place for retailers/merchants to connect with consumers. We support and partner with the commerce ecosystem, from large retailers to small local merchants, to give them the tools, technology and scale to thrive in today’s digital world.
 Responsibilities
 Provide technical leadership on high-impact projects.
 Influence and coach a distributed team of engineers.
 Facilitate alignment and clarity across teams on goals, outcomes, and timelines.
 Manage project priorities, deadlines, and deliverables.
 Design, develop, test, deploy, maintain, and enhance large-scale software solutions.
 Information collected and processed as part of your Google Careers profile, and any job applications you choose to submit is subject to Google's Applicant and Candidate Privacy Policy.
 Google is proud to be an equal opportunity and affirmative action employer. We are committed to building a workforce that is representative of the users we serve, creating a culture of belonging, and providing an equal employment opportunity regardless of race, creed, color, religion, gender, sexual orientation, gender identity/expression, national origin, disability, age, genetic information, veteran status, marital status, pregnancy or related condition (including breastfeeding), expecting or parents-to-be, criminal histories consistent with legal requirements, or any other basis protected by law. See also Google's EEO Policy, Know your rights: workplace discrimination is illegal, Belonging at Google, and How we hire.
 If you have a need that requires accommodation, please let us know by completing our Accommodations for Applicants form.
 Google is a global company and, in order to facilitate efficient collaboration and communication globally, English proficiency is a requirement for all roles unless stated otherwise in the job posting.
 To all recruitment agencies: Google does not accept agency resumes. Please do not forward resumes to our jobs alias, Google employees, or any other organization location. Google is not responsible for any fees related to unsolicited resumes.
 Equity is granted exclusively and discretionarily by Alphabet Inc. on the basis of an agreement concluded between you and Alphabet Inc. Alphabet Inc. is your sole contractual partner with respect to equity grants. GSU grants are not guaranteed, are discretionary, are subject to approval by the Alphabet Inc. board of directors or its delegate, the terms of the relevant Alphabet Inc. stock plan, and your grant agreement. They have no impact on statutory payments. Current or past grants do not confer an acquired right.
 Follow Life at Google on
 More about us
 About usopen_in_new
 Contact usopen_in_new
 Pressopen_in_new
 Related Information
 Investor relationsopen_in_new
 Blogopen_in_new
 Equal Opportunity
 Google is proud to be an equal opportunity and affirmative action employer. We are committed to building a workforce that is representative of the users we serve, creating a culture of belonging, and providing an equal employment opportunity regardless of race, creed, color, religion, gender, sexual orientation, gender identity/expression, national origin, disability, age, genetic information, veteran status, marital status, pregnancy or related condition (including breastfeeding), expecting or parents-to-be, criminal histories consistent with legal requirements, or any other basis protected by law. See also Google's EEO Policy, Know your rights: workplace discrimination is illegal, Belonging at Google, and How we hire.
 Privacyopen_in_new
 Applicant & Candidate Privacyopen_in_new
 Termsopen_in_new
 Manage cookies
 helpHelpopen_in_new
 language
 English
 Info In most instances, this position requires in-person interviews as part of the hiring process.
@@ -0,0 +1,59 @@
 \ProvidesClass{resume}[2026/07/27 Evidence-first professional resume]
 \LoadClass[11pt,a4paper]{article}
 \RequirePackage{enumitem}
 \RequirePackage{ifthen}
 \RequirePackage{lastpage}
 \RequirePackage{parskip}
 \RequirePackage{needspace}
 \pagestyle{empty}
 \setlength{\parindent}{0pt}
 \def\@resumename{}
 \def\@resumeheadline{}
 \def\@resumecontact{}
 \newcommand{\name}[1]{\def\@resumename{#1}}
 \newcommand{\headline}[1]{\def\@resumeheadline{#1}}
 \newcommand{\contactline}[1]{\def\@resumecontact{#1}}
 \newcommand{\printresumeheader}{%
  {\LARGE\bfseries \@resumename}\par
  \vspace{0.15em}
  \ifthenelse{\equal{\@resumeheadline}{}}{}{\@resumeheadline\par}
  \vspace{0.1em}
  {\small \@resumecontact}\par
  \vspace{0.45em}
 }
 \AtBeginDocument{\printresumeheader}
 \newenvironment{rSection}[1]{%
  \vspace{0.35em}
  {\bfseries #1}\par
  \vspace{0.1em}\hrule\vspace{0.35em}
 }{%
  \vspace{0.2em}
 }
 % Arguments: employer, dates, formal title, location.
 \newenvironment{rSubsection}[4]{%
  \Needspace{6\baselineskip}%
  {\bfseries #1}\hfill{\small #2}\par
  {\itshape #3}\hfill{\itshape #4}\par
  \vspace{0.1em}
  \begin{itemize}[leftmargin=1.25em,label=\textbullet,itemsep=0.18em,topsep=0.15em,parsep=0pt,partopsep=0pt]
 }{%
  \end{itemize}
  \vspace{0.25em}
 }
 \newcommand{\skillline}[2]{%
  \textbf{#1:} #2\par
  \vspace{0.08em}
 }
 \newcommand{\compactentry}[2]{%
  \textbf{#1}\hfill #2\par
 }
@@ -0,0 +1,182 @@
 # Session: Google — Staff Software Engineer, Shopping Graph (Feeds Infra)
 ## JD Integrity
 - File/source: `jd_google_staff_swe_shopping_graph_2026-10-21.txt` (this folder). Employer posting:
  https://www.google.com/about/careers/applications/jobs/results/102064172115600070-staff-software-engineer-shopping-graph?location=Switzerland
 - Retrieval method and date: Playwright render of the employer page (job_scout `.venv`), 2026-10-21. Also present in
  the 2026-10-08, 10-14 and 10-20 scout runs.
 - Verbatim posting: YES (full rendered page text; page chrome kept, unedited).
 - Posting status: LIVE on 2026-10-21. Location Zürich only. Google level label "Advanced". No salary range shown.
  *"In most instances, this position requires in-person interviews."*
 ## Application Decision
 - Audience profile: International Tech
 - Evidence Fit: 73 (provisional, pre-critique)
 - Fit class: **Stretch.** The score alone would read Adjacent, but `application_strategy.md` defines Stretch as
  "a defining responsibility is only Adjacent", and on a Staff req technical leadership is defining (rows 8, 10,
  11 are Adjacent). The comparison alternative, Senior SWE SRE YouTube ML, would also be Stretch (pure SRE is a
  listed Stretch target; its distributed-systems and leadership minimums are Adjacent), so the pick stands.
  Fit class is a preparation signal, not a spend limit: expect the leadership questions.
 - Hard gate: PASS. All five minimum qualifications are Direct; the design/architecture line became Direct with the
  user's 2026-10-21 clarification.
 - Channel Strength: Weak
 - Channel plan: cold submit via Google Careers. The user has no referral (2026-10-21). Optional warm action after
  submitting: a short LinkedIn note to a Google Zürich Commerce/Shopping technical recruiter.
 - Named contact published? NO (Google postings name no contact).
 - Decision: PROCEED (user chose this req 2026-10-21 as the single Google application)
 - Google limits: 3 applications per rolling 30 days; last Google submit 2026-07-27 (SWE III Business Home). Not a role
  he applied to before, so the 90-day same-role wait does not apply.
 - Prior Google record (context, no causal inference): SWE III Business Home, Senior Data Engineer (Merchant DS) and
  Sr SWE Infrastructure (Data Pipeline) went cold and drew no interview.
 ## Requirements
 | # | Requirement | Required/preferred | Direct/Adjacent/Gap/Constraint | Canonical evidence | Gate? |
 |---|---|---|---|---|---|
 | 1 | Bachelor's degree or equivalent | Required | Direct | EDU-BENG, EDU-MENG | yes |
 | 2 | 8 yrs programming in C++, Java, Python, Kotlin or Go | Required | Direct but TIGHT: ~8.0 yrs elapsed without Vizrt (Generali Java 2015-17, Bosch Python/Java/Kotlin 2020-22, Swisscom Python 2023-), ~8.8 with Vizrt Python (VZ-1 rests on a user statement the reference letter does not corroborate); Fraunhofer C#/JS not counted. Name the language in each role's bullet so a recruiter can count | GN-3, VZ-1, BS-2, SW-1, SW-6 | yes |
 | 3 | 5 yrs testing and launching software products | Required | Direct | GN-1, VZ-2, FC-1, BS-1, BS-2, SW-1, SW-9 | yes |
 | 4 | 3 yrs software design and architecture | Required | Direct, scoped to own components (Bosch 2020-22 + Swisscom data products; user-confirmed 2026-10-21) | BS-1, BS-2, SW-7, GN-3 (contribution) | yes |
 | 5 | Integrating GenAI tools or LLM interfaces into workflows | Required | Direct, modest depth (configuration/integration level only) | SW-8; LiteLLM, Copilot, Kiro | yes |
 | 6 | Master's/PhD in Engineering or CS | Preferred | Direct | EDU-MENG (Software Design & Engineering focus) | no |
 | 7 | 8 yrs data structures/algorithms | Preferred | Adjacent (practised, not separately recorded; interview-tested) | general | no |
 | 8 | 3 yrs technical leadership leading project teams, setting technical direction | Preferred | Adjacent: component/application ownership, BDD introduction, mentoring; no project-team lead recorded | SW-2, BS-3, GN-1, BS-9, SW-10 | no |
 | 9 | 3 yrs complex matrixed org, cross-functional projects | Preferred | Direct | SWISSCOM (SAFe ART, company-wide Data Mesh), BOSCH (fab teams, vendors) | no |
 | 10 | Technical leadership on high-impact projects; influence and coach a distributed team | Responsibility | Adjacent | SW-2, BS-3, BS-9, SW-10 | no |
 | 11 | Facilitate cross-team alignment; manage priorities, deadlines, deliverables | Responsibility | Adjacent | SW-4 (prototype-and-iterate with stakeholders/architects), SW-3 (backlog with PO) | no |
 | 12 | Design, develop, test, deploy, maintain large-scale software | Responsibility | Direct for the function; Google scale is Adjacent | SW-1, SW-7, BS-1, BS-2 | no |
 | 13 | Feeds infrastructure: ingestion via files, APIs, web crawling; product data quality | Domain | Direct for ingestion and data quality; web crawling Gap; commerce/merchant domain Gap | SW-2, SW-1, SW-7, BS-2, BS-8 | no |
 | 14 | Zürich onsite/hybrid, in-person interviews | Constraint | Constraint: Thun–Zürich commute and fewer than his 3 homeoffice days; acceptable only for a clear overall improvement (config Job-change Preferences). Clarify at first contact | config.md | no |
 Evidence Fit (critique_framework.md): required 32/35 · responsibilities 17/25 · level/ownership 8/15 ·
 recency/depth 7/10 · domain/tool transfer 6/10 · practical 3/5 = **73**. Class **Stretch** by definition (defining
 responsibility only Adjacent), not by score. Serious gap: Staff-level technical leadership (rows 8, 10, 11).
 ## Competitive Read
 - Obvious-fit candidate: a senior/staff backend engineer from a large-scale ingestion or catalog team (Google
  internal, Amazon catalog, a marketplace), current in Java/C++, who has tech-led a team of engineers.
 - Dennis's advantage: over a decade of end-to-end ingestion and data-quality work across very different sources (fab
  sensor/process data, telco fulfillment data), current design of governed data products on AWS, production
  integration under a hard failure constraint (24/7 fab), and long work inside matrixed enterprises.
 - Their advantage: Google-scale distributed systems, current Java/C++, a recorded tech-lead role, and fluency in
  the data-structures/algorithms interview.
 - Level/scope comparison: Staff (L6) asks for project-team leadership he has only as component/application owner
  and mentor. Present that honestly; do not inflate it.
 ## Framing Strategy
 - Professional identity: Staff data engineer who designs and builds data ingestion and data products.
 - Strongest proof points: SW-7 (design of governed data products, current), SW-2 (owned ingestion component with
  data quality and on-call), BS-2/BS-1 (designed ingestion services and the ML-inference integration at Bosch).
 - Honest adjacent bridges: Glue/PySpark/Airflow ingestion as a bridge to Feeds Infra; Bosch normalization across
  coordinate systems (BS-8) as a data-quality story; SW-8 as the GenAI-in-workflows minimum.
 - Explicit gaps: web crawling, commerce domain, Google internal stack (Flume/Spanner/Bigtable are forbidden as
  claims), technical leadership of a team, current Java.
 - User directives: none beyond the role choice.
 ## Resume Plan
 - Summary: 2 lines.
 - Skills: about 5 rendered lines plus certifications (see the plan presented 2026-10-21).
 - Swisscom: SW-7, SW-1+SW-6+SW-9, SW-8, SW-2, SW-10+SW-4 (5 bullets; mentoring leads the last one).
 - Bosch: BS-2 ("designed" covers the ingestion scripts only), BS-1, BS-8, BS-3+BS-5+BS-9 (4 bullets); BS-6 held in
  reserve.
 - Earlier experience: Fraunhofer FC-1+FC-3, Vizrt VZ-2+VZ-1, Generali GN-1+GN-3 (1 each; GN-1 shows introducing BDD,
  presenting it and training the project).
 - Leadership evidence, allowed verbs only (owned, served, onboarded, mentored, guided, introduced, trained): SW-2,
  BS-3, SW-10, BS-9, GN-1. Never "led" or "managed".
 - Total bullets: 12.
 - Impact evidence still needed: none claimed. All metrics are unverified and omitted.
 - Open wording check: SW-8 "migration and data-mapping" detail rests on `experience_swisscom.md` (user-confirmed
  2026-07-10), not on canonical SW-8 scope. Ask before using it.
 ## Cover Letter Decision
 - YES/NO: NO
 - Reason: not requested; Google's screen is minimum-qualification driven, and there is no transition, relocation or
  personal connection a letter would add. If the portal offers an optional field, leave it empty.
 - Information it adds beyond resume: none material.
 - Verified hook sources: n/a
 ## As Built (2026-10-21)
 - Plan confirmed by the user 2026-10-21 ("i confirm, go on"). The SW-8 "migration and data-mapping" detail was
  NOT answered, so it is omitted (accuracy default).
 - 13 bullets: Swisscom 5 (SW-7; SW-1+SW-6+SW-9; SW-2; SW-8; SW-10+SW-4), Bosch 5 (BS-2; BS-8; BS-1; BS-3+BS-5;
  BS-9+BS-7), Fraunhofer 1 (FC-1+FC-3), Vizrt 1 (VZ-2+VZ-1), Generali 1 (GN-3+GN-1). The Bosch mentoring line was
  split into its own short bullet (cadence and the two-accomplishment limit).
 - Self-audit fixes before presenting: Kotlin removed from the BS-2 data-services bullet (the services were
  Python/Java/C#; Kotlin was backend, Ansible plugins and extensions); "team workflows" changed to "development
  workflows" (team adoption is not recorded); "maritime" removed from FC-3 (not recorded for the platform); BS-8 reworded so it no longer says the coordinate
  transformation ran inside Oracle (BS-8 establishes SDO_GEOMETRY data and CRS transformation as separate facts;
  spatial operators are not confirmed) - caught by the advisor review.
 - Layout: Swisscom on page 1, Bosch starts page 2 (template default), "Professional Experience (continued)".
  Skills 6 rendered categories / 8 lines. Certifications on one entry; iSAQB CPSA-F kept unbroken with \mbox.
 - Validation: `validate_resume_system.py --document` PASS, 0 warnings (an initial cadence WARN, 8/13 triples,
  was fixed by reshaping the SW-8 and Generali sentences). pdflatex: 2 pages, no overfull/underfull boxes.
  pdftotext order: employer, dates, title, location for every role. PDF metadata: empty Title/Author.
  `page_metrics.py` could not run (Git's pdftotext rejects `-bbox`); page-1 weighting checked visually instead:
  experience starts at roughly 45% of page 1.
 ## Edit History
 ### 2026-10-21 — post-critique edit (user: "apply improvements which you think are important")
 - **User directive:** make acceptable stretches to maximise interview chances, including saying he set technical
  direction. Verbatim context: *"I'm a staff engineer at Swisscom - of course that is my day to day responsibility
  but i cant think of something concrete right now. Dont add it to the KB."*
 - **Declined part:** inventing a concrete technical-direction incident he could not name. Reason: Google loops ask
  for the story behind every line, and a fabricated specific is the likeliest thing to fail there.
 - **What was done instead:**
  1. New Swisscom bullet 2 frames the recorded SW-4 prototype-and-iterate episode as setting technical direction
     (he built a prototype, proposed it to business, architects and engineers, and iterated). This is an existing
     canonical fact, reframed, and the interview story behind the line. SW-10 mentoring stays in it.
  2. Summary: "sets the technical direction for the data products of his domains". **Source: the user's
     2026-10-21 statement above. NOT in `claims.json`, at the user's request.** Scoped to his own domains' data
     products; no artefact, adoption count or cross-team authority is claimed. Treat it as application-specific
     wording, not reusable evidence.
  3. SW-1 bullet opens "As primary engineer for the owned data domains" (SW-1 scope wording).
  4. SW-2 bullet leads with the Component Owner title.
  5. SW-8 reframed to mirror the JD minimum ("Integrated GenAI tools and LLM interfaces into workflows") without
     tying the assistants to development work.
  6. BS-1: "Designed the integration ... and deployed it" (allowed verbs), a launch signal.
  7. Headline adds "Data Quality". Trimmed BS-2, BS-3 (user training/documentation dropped) and Generali; GN-1
     training kept as leadership evidence.
 - **Before → after:** validator PASS/0 warnings → PASS/0 warnings (two intermediate cadence WARNs fixed by
  reshaping); 2 → 2 pages; 13 → 13 bullets; no overfull/underfull boxes; employer/title/date order unchanged.
 - **Estimated Document Quality after edit: ~86** (leadership now visible on page 1; provenance −1 for the
  user-sourced summary line). The critique is STALE: re-run `/critique` for a scored figure. Evidence Fit is
  unchanged at 70 Stretch; writing cannot change fit.
 ## Output Files
 - Resume: `e2e_google_staff_swe_shopping_graph_resume.tex` (source of truth) + `.pdf`
 - Cover letter: intentionally omitted
 - Critique: `critique_google_staff_swe_shopping_graph.md` (not yet)
 ## Critique Summary (2026-10-21, `critique_google_staff_swe_shopping_graph.md`)
 - Evidence Fit: 70 (critique rescore; provisional was 73). Class **Stretch**: the defining responsibility,
  Staff-level technical leadership, is only Adjacent.
 - Hard gate: PASS (all five minimums Direct; 8 yrs programming and GenAI are tight/modest)
 - Document Quality: 84
 - Channel Strength: Weak (cold, no referral)
 - Tier 1 fixes: none
 - Tier 2: (1) ask for one recorded instance of setting technical direction for other engineers; (2) ask for
  any verifiable scale count; (3) SW-8 framing; (4) BS-1 "deployed" as a launch signal; (5) trim three long
  bullets.
 ## Status
 - Fit gate: DONE 2026-10-21 (Adjacent, PASS)
 - Resume: GENERATED, validated and compiled 2026-10-21; awaiting user approval
 - Cover letter: NO
 - Critique: DONE 2026-10-21 (Evidence Fit 70 Stretch, gate PASS, Document Quality 84, channel Weak, no Tier 1).
  **STALE after the 2026-10-21 post-critique edit** (see Edit History).
 - Application/outcome: not submitted. At submission: copy the PDF to `Dennis_Thiessen_Resume.pdf`, add the
  application with `application_tracker.py add` (date = submission date), and set the decision-log row to `applied`.
 - **FINALIZED 2026-10-21** on user approval ("na, finalize it"). Validator PASS / 0 warnings; PDF newer than `.tex`;
  `Dennis_Thiessen_Resume.pdf` is a byte-identical copy (2 pages, empty metadata). No cover letter (decision NO).
  The critique on file predates the last edit (marked stale); the user approved without a re-score.
 - **SUBMITTED 2026-10-21** via Google Careers, cold (user-confirmed "submitted just now"). Recorded in
  `job_scout/state/applications.json` as `app-google-staff-shopping-graph-102064172115600070` (stretch, 70, weak,
  gate pass, applied); decision-log row set to `applied`; `current_applications.md` regenerated.
 - Google limit: this is the first Google submit since 2026-07-27, so 2 slots remain in the rolling 30 days to
  2026-11-20.
 - Next: await Google's response. At first contact clarify the level (L6 vs L5), Zürich hybrid days and the total
  package. Interview prep: SW-4 prototype story; one concrete Staff example named by the user; Java currency;
  end-to-end system design with scale and trade-offs. Optional before that: a re-run of `/critique` for a fresh score.
  Interview prep: have the SW-4 prototype story ready as the "technical direction" answer, plus one day-to-day
  Staff example he can name himself.
 - KB changes this session: `knowledge_base/extractions/2026-10-21_software_design_architecture_clarification.md`;
  `claims.json` BS-1, BS-2 (+`designed` verb), SW-7 scope; `config.md` data-product design row.
@@ -0,0 +1,97 @@
 Source: https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Remote/Senior-Production-Engineer----DGX-Cloud_JR2027105
 Retrieved: 2026-10-22; HTTP 200; Playwright rendered
 Skip to main content
 CAREERS AT NVIDIA
 Sign In
 Home
 Search for Jobs
 Senior Production Engineer - DGX Cloud page is loaded
 Senior Production Engineer - DGX Cloud
 Apply
 locations
 Switzerland, Remote
 Switzerland, Zurich
 time type
 Full time
 posted on
 Posted 16 Days Ago
 job requisition id
 JR2027105
 NVIDIA DGX Cloud delivers AI services and endpoints for research and production workloads. We are looking for a Senior Production Engineer to build software and automation that make those services reliable, scalable, and safe to operate. The Production Engineering team works on large-scale distributed systems spanning internal and external model endpoints; regional control plane services that orchestrate workloads and route requests; and the GPU/CPU compute infrastructure where inference and agentic workloads run. Our work spans Kubernetes clusters across AWS, Azure, Google Cloud, other partner cloud environments, and on-premises deployments.
 What you’ll be doing:
 Build and operate production software, automation, and tooling for control plane services, model deployments, and inference and agentic workloads across DGX Cloud environments.
 Improve the reliability of inference and agentic platforms and services, including NVIDIA Cloud Functions, SGLang- and vLLM-based endpoints, and inference services built with NVIDIA Dynamo, through health validation, safer rollouts, observability, and recovery.
 Improve endpoint availability, inference routing, capacity management, and service health to maintain predictable performance as workloads and demand change.
 Use infrastructure as code and GitOps to deploy, configure, validate, upgrade, and recover services consistently across environments.
 Build workflows for service enablement, model releases, handoff, deprecation, and ongoing operations; replace repeatable manual work with reliable automation.
 Define and instrument SLIs and SLOs for inference and control plane services, including availability and latency, use error budgets to guide reliability improvements, and make production health visible to partner teams.
 Participate in on-call and incident response, troubleshoot failures across routing, model runtimes, software, and infrastructure, and turn recurring issues into automation and durable fixes.
 Collaborate with model, platform, storage, networking, security, and GPU infrastructure teams to design and operate services safely at scale.
 What we need to see:
 8+ years of experience building or operating production services and large-scale distributed systems, including hands-on automation.
 Strong programming skills in Python, Go, or a comparable language, with experience developing tools for production operations.
 Experience with infrastructure as code, configuration management, or GitOps, and with building automation for repeatable service deployments and changes.
 Strong knowledge of Linux, Kubernetes, containers, cloud infrastructure, distributed systems, and networking fundamentals; ability to diagnose failures in production.
 Understanding of Production Engineering principles, including SLIs, SLOs, error budgets, incident response, and reducing operational toil.
 Experience instrumenting services and using metrics, logs, and traces to understand system behavior and improve reliability.
 Clear technical communication and ability to work across engineering teams.
 BS/MS in Computer Science or equivalent practical experience.
 Ways to stand out from the crowd:
 Familiarity with technologies such as vLLM, SGLang, PyTorch, TensorRT-LLM, NVIDIA Dynamo, CUDA, or NCCL, and with GPU performance analysis.
 Experience building Kubernetes operators, controllers, workload orchestration services, fleet management systems, or self-healing automation.
 Experience with Terraform, Argo CD, CI/CD, policy validation, or safe deployment and rollback systems.
 Background with developing with AI tools and agents.
 Experience with production AI inference or agentic workloads, including debugging issues across models, runtimes, Kubernetes, and hardware.
 NVIDIA is leading the way in groundbreaking developments in Artificial Intelligence, High-Performance Computing and Visualization. The GPU, our invention, serves as the visual cortex of modern computers and is at the heart of our products and services. We have some of the most forward-thinking and hard-working people on the planet working for us. If you're creative, hard-working and self-motivated, we want to hear from you!
 Similar Jobs (4)
 Senior Software Engineer, JAX
 locations
 2 Locations
 time type
 Full time
 posted on
 Posted 3 Days Ago
 Senior AI Compute Engineer
 locations
 4 Locations
 time type
 Full time
 posted on
 Posted 30+ Days Ago
 Senior Software Architect, GPU Networking Research
 locations
 2 Locations
 time type
 Full time
 posted on
 Posted 30+ Days Ago
 View All 4 Jobs
 NVIDIA pioneered accelerated computing. Today, our AI infrastructure powers global intelligence, transforming every industry.
 Learn more about NVIDIA.
 Follow Us
 Applicant Privacy Policy
 © 2026 Workday, Inc. All rights reserved.
@@ -0,0 +1,96 @@
 # Critique: NVIDIA — Senior Production Engineer, DGX Cloud (JR2027105)
 > **STALE as of Edit 1 (2026-10-22):** Tier 1 #1 and Tier 2 #1–#4 were applied (see the session's Edit History). The Document Quality score of 85 measures the pre-edit document and was not re-measured.
 Date: 2026-10-22. Documents: `e2e_nvidia_prod_eng_dgx_cloud_resume.tex` / `.pdf` (2 pages). No cover letter (session decision NO).
 JD: `JD_nvidia_prod_eng_dgx_cloud_jr2027105.txt`, verbatim Playwright render 2026-10-22, live.
 ## 1. Fit verdict and hard gates
 - **Fit class: Stretch.** **Hard gate: PASS.** No required line is a Gap; location (Switzerland Remote), language and authorization are resolved.
 - Stretch because required Q5 (SLIs, SLOs, error budgets, incident response, toil), the SRE core of the title, is only Adjacent: SLOs (BS-3) and incident response (SW-2 past, SW-11 current) are evidenced; SLIs and error budgets are not.
 - Likeliest screen rejection: Q1 *"8+ years of experience building or operating production services and large-scale distributed systems"*. The years hold (visible record from 2015-05); the large-scale distributed systems do not at NVIDIA's scale.
 ## 2. Evidence Fit — 65/100 (scored before reading the prose; unchanged from the session)
 | Dimension | Weight | Score | Basis |
 |---|---:|---:|---|
 | Required qualifications | 35 | 26 | 4 Direct (Q2 Python/tools, Q3 IaC/config mgmt, Q7 communication, Q8 degree); 4 Adjacent (Q1 scale, Q4 networking, Q5 SLIs/error budgets, Q6 instrumenting beyond alert thresholds + PoC) |
 | Core responsibilities | 25 | 12 | On-call/incident Direct and now current (SW-11); inference integration Adjacent (BS-1); routing/capacity Gap |
 | Level and ownership | 15 | 11 | Senior IC vs Staff title; component and application ownership |
 | Recency and depth | 10 | 6 | Current: on-duty, alert thresholds, AWS/CloudFormation, Python. Past: Ansible/Linux (2022), Kubernetes, GitLab |
 | Domain/tool transfer | 10 | 5 | Production inference on NVIDIA GPUs is a real bridge; vLLM/SGLang/Dynamo, K8s operators, Terraform, Argo CD do not transfer |
 | Practical constraints | 5 | 5 | Remote CH, English, EU/B permit |
 | **Total** | | **65** | |
 ## 3. Document Quality — 85/100
 | Dimension | Weight | Score | Note |
 |---|---:|---:|---|
 | Truth and provenance | 25 | 23 | Every claim traces to canonical scope; one over-generalisation ("set **the** alert thresholds", Tier 1 #1) |
 | Information hierarchy | 20 | 17 | Clear headers; NVIDIA-GPU bullet on page 1; experience starts ~44% down page 1. The Swisscom tense switch (present → past for ART B2B work) is unexplained to a reader |
 | Bullet evidence and impact | 20 | 15 | Specific and scoped, no invented metrics (none exist). Two dense bullets: Swisscom #1 (38 words, "alerts" twice) and Bosch #1 ("GPU-backed" and "on NVIDIA GPUs" in one sentence) |
 | Relevance and terminology | 15 | 12 | Honest coverage of IaC, configuration management, Linux, Kubernetes, containers, AWS, SLOs, incident response, on-call, alerting, CI/CD, inference, GPU. Absent: "observability" (honestly available for the BS-4 PoC); SLIs, error budgets, networking, Terraform, GitOps, CUDA correctly absent |
 | Skills evidence | 10 | 9 | All canonical; Kubernetes is listed without a recency cue (bullets show it as past) |
 | Mechanics/readability | 10 | 9 | Validator PASS, 0 cadence warnings, 0 boxes, 2 pages, parse order correct |
 ## 4. Channel Strength — Weak
 Cold portal application; no contact published. The warm action (LinkedIn note to an NVIDIA recruiter or a DGX Cloud Production Engineering engineer in Switzerland) is the cheapest improvement available and is not yet done.
 ## 5. Competitive read and reader sequence
 - **Obvious-fit competitor:** an SRE/production engineer from a hyperscaler, GPU cloud or ML-serving company with vLLM/Triton-style endpoints on Kubernetes, operators, Terraform/Argo CD and formal SLO/error-budget practice.
 - **Dennis's real advantage:** ML inference on NVIDIA GPUs integrated into a fab where a defect could have stopped production; Ansible depth including his own extensions; on-call across two Swisscom units, current with alert thresholds he writes; current AWS IaC; ten years of automation across five employers.
 - **Competitor's real advantage:** inference-serving stack, Kubernetes at scale and current, SRE formalism, networking. Do not value the GPU bridge as highly as their direct serving experience.
 - **Parser/ATS:** extracts cleanly; strong on IaC/config mgmt/Linux/K8s/AWS/SLO/on-call/alert/GPU literals; no "distributed systems" phrase beyond "distributed processing" and "distributed video-transcoding".
 - **Recruiter glance: Borderline.** Data-engineer identity in the title line against a production-engineering req; the on-duty bullet and the GPU line are what carry it past a skim.
 - **Hiring manager: Maybe.** Real production operations and automation, real GPU inference in a harsh environment; no serving stack, Kubernetes not current.
 - **Technical reviewer — likely first challenges:** (1) "Walk me through a production incident you debugged end to end" (SW-2/SW-11); (2) "How did you roll out a new model version safely in the fab?" (BS-1 — the KB records the failure-consequence constraint, not the rollout mechanics; prepare the honest answer); (3) "When did you last run Kubernetes, and how would you debug a failing pod?"; (4) distributed systems at scale; (5) vLLM/SGLang/Dynamo — say plainly you have not used them.
 ## 6. Claim audit
 | Claim | Canonical ID/evidence | Direct/Adjacent | Safe? | Fix |
 |---|---|---|---|---|
 | "over ten years in production software and its automation" | Employment from Generali 2015-05; Capgemini excluded | Direct | Yes | — |
 | Integrated containerized ML inference on NVIDIA GPUs into a continuously operating fab (summary + Bosch #1) | BS-1 incl. 2026-10-22 hardware note | Direct | Yes; no CUDA/GPU-tuning claim | Tier 2 #3 (redundancy) |
 | Builds AWS data pipelines with CloudFormation | SW-1, SW-7; CloudFormation production-current | Direct | Yes | Be ready to describe templates he wrote |
 | Serves in the engineer-on-duty rotation; Opsgenie; auto-created Jira tickets | SW-11 | Direct | Yes | — |
 | "set **the** alert thresholds, including data-quality checks" | SW-11 ("i wrote e.g. thresholds for data quality") | Direct | **Over-generalised** | Tier 1 #1 |
 | Migrated Fulfillment and Product Analysis domains' ETL to AWS as Python Glue jobs, Airflow, CloudFormation, contributing to wider migration | SW-1 (scoped object, hedged contribution) | Direct | Yes | — |
 | Design and build governed data products within the company-wide Data Mesh, unit tests | SW-7, SW-6, SW-9 | Direct | Yes; mesh not claimed | — |
 | Built and operated Python applications on Kubernetes via automated GitLab CI/CD, multiple environments | SW-3 (past; worked with CI/CD, did not build it) | Direct (past) | Yes | Tier 2 #1 (tense cue) |
 | Owned Fulfillment ETL components, on-call, 2nd/3rd-level support, RCA | SW-2 (past tense) | Direct (past) | Yes | — |
 | Administered and automated Linux servers; Git-versioned Ansible run from Jenkins/GitLab | BS-6 (no GitOps) | Direct (past) | Yes | — |
 | Ansible credential plugin caching keystore secrets | BS-6 | Direct | Yes; unquantified | — |
 | Technical Application Owner for KLA DMS and Spotfire; defined SLOs | BS-3, BS-5 | Direct | Yes | — |
 | ELK/Kafka PoC with Prometheus, Grafana, Loki | BS-4 incl. 2026-10-22 confirmation | Adjacent (PoC) | Yes; PoC label kept | Tier 2 #4 (observability literal) |
 | Jenkins build jobs for automatic deployment (Fraunhofer) | FC-1 | Direct | Yes | — |
 | Test suites as CI/CD quality gates; contributed Python to distributed transcoding backend | VZ-2, VZ-1 (contributor; no customer names) | Direct | Yes | — |
 | XLDeploy migration; BDD test automation responsibility, Jenkins | GN-3, GN-1 | Direct | Yes | — |
 | Skills: PyTorch/TensorFlow inside certificate line | certification-context-only | — | Yes (validator) | — |
 | Contact: EU citizen, Swiss B permit | identity | — | Yes | — |
 ## 7. Fixes
 ### Tier 1 — truth/fit
 1. **Swisscom #1:** "set **the** alert thresholds" → "set alert thresholds". He named data-quality thresholds as an example; "the" implies he defines all of them.
 ### Tier 2 — presentation
 1. **Swisscom tense switch:** prefix the two past bullets (Kubernetes/GitLab; Fulfillment ETL on-call) with "Earlier in the role," so the present → past change reads as intentional. No dates or unit names (never date the ART units).
 2. **Add a one-line personal-infrastructure entry (PP-3):** "Personal: self-host and harden a Debian server (~10 years) running nginx, a mail server, a VPN, Docker services and Bitwarden." It is the only current Linux evidence and the only networking-fundamentals evidence (reverse proxy, VPN, mail). Page 2 has room. PP-3 rules: personal label, no uptime/scale figure, never production/enterprise, never datacenter.
 3. **Tighten the two dense bullets:** Swisscom #1 (38 words, "alerts" twice) and Bosch #1 ("GPU-backed … deployed on NVIDIA GPUs" says GPU twice; keep "on NVIDIA GPUs").
 4. **Optional:** add the word "observability" to the BS-4 bullet ("observability proof of concept: …"), keeping the PoC label. It is the JD's own term and honest for that PoC.
 ## 8. Cover letter
 Session decision NO: Workday portal, no letter requested, nothing the resume cannot show. Absence not penalised. The warm LinkedIn note has more information value than a letter.
 ## 9. Mechanical verification
 - `validate_resume_system.py --document`: **PASS**, 0 warnings (cadence included).
 - MiKTeX pdflatex: **2 pages**, 0 overfull/underfull boxes. Both pages inspected at 80 dpi: no clipping or overlap; the BS-1 GPU bullet sits on page 1; page 2 ends about half-way (no filler added, by rule).
 - `pdftotext -layout`: header → Summary → Skills → Experience (Swisscom, Bosch, Fraunhofer, Vizrt, Generali, each employer/date then title/location) → Education. No Capgemini. No Go, Terraform, GitOps, CUDA or networking claim in the text.
 - Not run: `page_metrics.py` (its `pdftotext -bbox` call fails with the Git-for-Windows binary; page-1 experience start estimated visually at ~44%).
 **Not submit-ready until Tier 1 #1 is applied.** After that the package is a sound Stretch application, still Weak-channel.
@@ -0,0 +1,82 @@
 % NVIDIA -- Senior Production Engineer, DGX Cloud (JR2027105), Switzerland Remote / Zurich.
 % International Tech profile. Written 2026-10-22 from resume_builder/canonical/claims.json
 % (incl. SW-11 and the BS-1/BS-4 additions of 2026-10-22); no historical output used as a source.
 \documentclass{resume}
 \usepackage[utf8]{inputenc}
 \usepackage[T1]{fontenc}
 \usepackage{lmodern}
 \usepackage[a4paper,left=0.65in,right=0.65in,top=0.55in,bottom=0.55in]{geometry}
 \usepackage{xcolor}
 \usepackage{hyperref}
 \hypersetup{hidelinks}
 \usepackage[version=4]{mhchem}
 \usepackage{fancyhdr}
 \pagestyle{fancy}
 \fancyhf{}
 \renewcommand{\headrulewidth}{0pt}
 \fancyfoot[R]{\small \thepage/\pageref{LastPage}}
 \name{Dennis Thiessen, M.Eng.}
 \headline{Staff Data \& AI Engineer $\vert$ Production Automation and Operations $\vert$ AWS $\cdot$ ML Inference}
 \contactline{Bern, Switzerland $\vert$ EU citizen, Swiss B permit $\vert$ \href{mailto:dennis@thiessen.io}{dennis@thiessen.io} $\vert$ +41 795 955 585 $\vert$ \href{https://linkedin.com/in/dennis-thiessen}{LinkedIn}}
 \begin{document}
 \begin{rSection}{Summary}
 Engineer with over ten years in production software and its automation. At Bosch, integrated containerized ML inference on NVIDIA GPUs into a continuously operating semiconductor fab; at Swisscom, builds AWS data pipelines with CloudFormation and serves in the engineer-on-duty rotation.
 \end{rSection}
 \begin{rSection}{Technical Skills}
 \skillline{Languages}{Python, SQL, Bash}
 \skillline{Infrastructure}{AWS, infrastructure as code (CloudFormation), configuration management (Ansible), Linux administration, Docker, Kubernetes, Jenkins, GitLab CI/CD}
 \skillline{Operations and data}{On-duty incident response, alert thresholds, SLOs, root-cause analysis, unit testing (pytest); PySpark (distributed processing), Kafka, Apache Iceberg}
 \skillline{AI tooling}{AI-assisted development with Kiro and Copilot}
 \skillline{Certifications}{AWS Certified Solutions Architect -- Associate (2024); IBM AI Engineering Professional Certificate, incl.\ PyTorch and TensorFlow courses (2020)}
 \end{rSection}
 \begin{rSection}{Professional Experience}
 \begin{rSubsection}{Swisscom (Schweiz) AG}{Oct 2023 -- Present}{Staff Data, Analytics \& AI Engineer (promoted from Senior, Apr 2025)}{Bern, Switzerland}
 \item Serve in the team's rotating engineer-on-duty role, responding to Opsgenie alerts and resolving issues through auto-created Jira tickets; set alert thresholds, including data-quality checks, for owned pipelines.
 \item Migrated the Fulfillment and Product Analysis domains' legacy ETL pipelines to AWS as Python Glue jobs orchestrated with Airflow and provisioned with CloudFormation, contributing to the wider company migration.
 \item Design and build governed data products on AWS (PySpark, Glue, Athena, Apache Iceberg) within Swisscom's company-wide Data Mesh, with unit tests for the pipeline code.
 \item Earlier in the role, owned the Fulfillment ETL components that moved business-critical data from Oracle into the Teradata data warehouse, including on-call duty, 2nd/3rd-level support and root-cause analysis.
 \item Built and operated Python applications on Kubernetes in the same period, deployed through automated GitLab CI/CD pipelines across multiple environments.
 \end{rSubsection}
 \begin{rSubsection}{Robert Bosch Semiconductor Manufacturing Dresden GmbH}{Feb 2020 -- Dec 2022}{Senior Data Engineer, Data Analysis (promoted from Data Engineer, Jan 2021)}{Dresden, Germany}
 \item Designed and executed the integration of containerized ML inference on NVIDIA GPUs (Docker, Kubernetes, Ansible) into a continuously operating semiconductor fab, where a software defect could have halted production; reduced manual image-based defect classification.
 \item Administered and automated the Linux servers behind fab analytics and ML workloads with Git-versioned Ansible playbooks run from Jenkins and GitLab pipelines.
 \item Developed Ansible extensions, including a credential plugin that cached keystore secrets locally to cut lookup volume.
 \item Served as technical Application Owner for the KLA Defect Management System and TIBCO Spotfire, defining SLOs and handling vendor communication, user training and documentation.
 \item Built an observability proof of concept for log management and anomaly detection on ELK and Kafka, with monitoring and alerting in Prometheus, Grafana and Loki.
 \end{rSubsection}
 \begin{rSubsection}{Fraunhofer Center for Maritime Logistics and Services CML}{Sep 2018 -- Oct 2019}{Research Software Engineer}{Hamburg, Germany}
 \item Set up Jenkins, including the build jobs for automatic deployment of a C\# and SQL Server crew-scheduling application.
 \end{rSubsection}
 \begin{rSubsection}{Vizrt}{Jul 2017 -- May 2018}{Test Automation / DevOps Engineer}{Bergen, Norway}
 \item Developed automated test suites wired into the CI/CD pipeline as quality gates, and contributed Python to a distributed video-transcoding backend.
 \end{rSubsection}
 \begin{rSubsection}{Generali Deutschland Informatik Services GmbH}{May 2015 -- Jun 2017}{IT Consultant}{Hamburg, Germany}
 \item Migrated web services to a new XLDeploy deployment procedure and held technical responsibility for BDD test automation (Serenity-BDD, JBehave), with its build jobs administered in Jenkins.
 \end{rSubsection}
 \end{rSection}
 \begin{rSection}{Personal Infrastructure}
 Self-host and harden a personal Debian server, run for about ten years: nginx, a mail server, a VPN server, Docker services and Bitwarden.
 \end{rSection}
 \begin{rSection}{Education}
 \compactentry{M.Eng. Computer Aided Engineering}{Apr 2012 -- Oct 2013}
 Universität der Bundeswehr München; Software Design \& Engineering.
 \compactentry{B.Eng. Information and Telecommunication Technologies}{Oct 2009 -- Oct 2012}
 Universität der Bundeswehr München.
 \end{rSection}
 \end{document}
@@ -0,0 +1,59 @@
 \ProvidesClass{resume}[2026/07/27 Evidence-first professional resume]
 \LoadClass[11pt,a4paper]{article}
 \RequirePackage{enumitem}
 \RequirePackage{ifthen}
 \RequirePackage{lastpage}
 \RequirePackage{parskip}
 \RequirePackage{needspace}
 \pagestyle{empty}
 \setlength{\parindent}{0pt}
 \def\@resumename{}
 \def\@resumeheadline{}
 \def\@resumecontact{}
 \newcommand{\name}[1]{\def\@resumename{#1}}
 \newcommand{\headline}[1]{\def\@resumeheadline{#1}}
 \newcommand{\contactline}[1]{\def\@resumecontact{#1}}
 \newcommand{\printresumeheader}{%
  {\LARGE\bfseries \@resumename}\par
  \vspace{0.15em}
  \ifthenelse{\equal{\@resumeheadline}{}}{}{\@resumeheadline\par}
  \vspace{0.1em}
  {\small \@resumecontact}\par
  \vspace{0.45em}
 }
 \AtBeginDocument{\printresumeheader}
 \newenvironment{rSection}[1]{%
  \vspace{0.35em}
  {\bfseries #1}\par
  \vspace{0.1em}\hrule\vspace{0.35em}
 }{%
  \vspace{0.2em}
 }
 % Arguments: employer, dates, formal title, location.
 \newenvironment{rSubsection}[4]{%
  \Needspace{6\baselineskip}%
  {\bfseries #1}\hfill{\small #2}\par
  {\itshape #3}\hfill{\itshape #4}\par
  \vspace{0.1em}
  \begin{itemize}[leftmargin=1.25em,label=\textbullet,itemsep=0.18em,topsep=0.15em,parsep=0pt,partopsep=0pt]
 }{%
  \end{itemize}
  \vspace{0.25em}
 }
 \newcommand{\skillline}[2]{%
  \textbf{#1:} #2\par
  \vspace{0.08em}
 }
 \newcommand{\compactentry}[2]{%
  \textbf{#1}\hfill #2\par
 }
@@ -0,0 +1,162 @@
 # Session: NVIDIA — Senior Production Engineer, DGX Cloud (Switzerland Remote / Zurich)
 ## JD Integrity
 - **File/source:** `output/NVIDIA_ProdEng_DGX_Cloud/JD_nvidia_prod_eng_dgx_cloud_jr2027105.txt` — req **JR2027105**
  (`https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Remote/Senior-Production-Engineer----DGX-Cloud_JR2027105`)
 - **Retrieval method and date:** headless Playwright render via `job_scout/.venv` (Workday SPA), **2026-10-22**, HTTP 200.
  Same text first read in the 2026-10-08 scout triage.
 - **Verbatim posting:** YES — saved unedited.
 - **Posting status:** LIVE. *"Posted 16 Days Ago"* on 2026-10-22, so posted ~2026-10-06. Locations: **Switzerland, Remote** and Switzerland, Zurich.
 ## Application Decision
 - **Audience profile:** International Tech (US-tech, English).
 - **Evidence Fit: 63/100** (dimension table below). The 2026-10-08 triage said "~68 provisional"; this is the full scoring and it is lower.
 - **Fit class: Stretch.** The score sits in the Adjacent band, but `application_strategy.md` makes a role Stretch when a defining
  responsibility is only Adjacent, and `config.md`'s decision tree marks SRE as Stretch when it is a required qualification.
  Required line Q5 (SLIs, SLOs, error budgets, incident response, toil) is the SRE core of a Production Engineer title, and only
  part of it is evidenced. Judgment recorded: the function itself (operating and automating production services: SW-2, BS-1, BS-6)
  is Direct, so this is Stretch, not a title-defining Gap / No-go. A strict reading of `critique_framework.md` §1 ("title-defining
  capability is not Direct") would flag it harder.
 - **Hard gate: PASS.** No required line is a Gap. Two required lines are only Adjacent and carry the screening risk:
  Q1 ("8+ years ... large-scale distributed systems") — **the likeliest recruiter-screen rejection** — and Q4 (networking fundamentals).
 - **Practical constraints: resolved.** Remote from Switzerland is stated in the posting (user baseline is 3 home-office days; fully remote
  is acceptable when comp and role are strong). Comp: levels.fyi Greater Zurich NVIDIA IC3 median ~CHF 204k (recorded 2026-09-04 in
  `output/NVIDIA_SrDevOps_Zurich/session_nvidia_sr_devops.md`; self-reported, equity-heavy). English only. EU citizen, B permit.
 - **Stacking:** NVIDIA Senior DevOps JR2024256 (applied 2026-09-05) was last listed in the 2026-09-18 scrape, absent since 2026-09-23,
  page "doesn't exist" on 2026-10-22, no response. The req is pulled, so no open NVIDIA posting to stack against (recorded in the tracker).
 - **Channel Strength: Weak** (cold portal application).
 - **Channel plan:** no contact is published. Warm action: a short LinkedIn note to an NVIDIA recruiter or a DGX Cloud Production Engineering
  engineer in Switzerland/Zurich, before or right after submitting.
 - **Named contact published?** NO.
 - **Decision: PROCEED (Stretch), 2026-10-22.** Fit gate presented; the user answered the evidence questions and confirmations and kept the instruction to prepare the CV. Recorded as Stretch, not upgraded by the go-ahead.
 ### Evidence Fit — dimension table
 | Dimension | Weight | Score | Basis |
 |---|---:|---:|---|
 | Required qualifications | 35 | 26 | 4 Direct (Q2, Q3, Q7, Q8), 4 Adjacent (Q1, Q4, Q5, Q6), 0 Gap |
 | Core responsibilities | 25 | 12 | 1 Direct (on-call/incident, SW-2), 6 Adjacent, 1 Gap (inference routing/capacity) |
 | Level and ownership | 15 | 11 | Senior IC vs current Staff title; component/application ownership (SW-2, BS-3); distributed-systems scale is the weak part |
 | Recency and depth | 10 | 5 | The ops core is past: Ansible/Linux at Bosch to 2022; Kubernetes, GitLab CI/CD and on-call at ART B2B. Current: AWS, CloudFormation, Python/PySpark, Docker, personal Linux (PP-3) |
 | Domain/tool transfer | 10 | 4 | IaC and CI/CD transfer; vLLM/SGLang/Dynamo/NVCF, GPU, Kubernetes operators, Terraform, Argo CD do not |
 | Practical constraints | 5 | 5 | Remote CH, English, authorization |
 | **Total** | 100 | **63** | |
 ## Requirements
 ### Required — "What we need to see"
 | # | Requirement | Class | Canonical evidence (currency) | Gate? |
 |---|---|---|---|---|
 | Q1 | 8+ years building or operating production services and large-scale distributed systems, including hands-on automation | **Adjacent** | Years: ~9.8 years of visible employment (Generali 2015-05 onward, Capgemini excluded), each with production software plus automation: GN-1, VZ-1/VZ-2, FC-1, BS-1/BS-6, SW-1/SW-2/SW-3. "Large-scale distributed systems": SW-1/SW-6 Glue/PySpark/Athena on AWS (current, managed distributed processing); SW-3 Kubernetes and Kafka (past); VZ-1 contributor to a distributed transcoding backend. Not NVIDIA-scale | **Screen risk** |
 | Q2 | Strong programming in Python, Go or comparable; tools for production operations | **Direct** | Python production-current; BS-6 Ansible extensions incl. credential-caching plugin (past); SW-1 migration automation as Python Glue jobs (current) | — |
 | Q3 | IaC, configuration management, or GitOps; automation for repeatable service deployments and changes | **Direct** | Ansible BS-6 (past, intensive); CloudFormation production-current; FC-1 Jenkins build jobs for automatic deployment; SW-3 deployed through automated GitLab CI/CD across multiple environments (past, worked with, did not build). **GitOps forbidden (BS-6)** — the "or" is met without it | — |
 | Q4 | Strong knowledge of Linux, Kubernetes, containers, cloud, distributed systems, networking fundamentals; diagnose production failures | **Adjacent** | Linux BS-6 (past) + PP-3 (current, personal); Kubernetes SW-3/BS-1 (past only); Docker current; AWS current; distributed systems as Q1; **networking: PP-3 personal only (nginx, VPN, mail) — open question**; diagnosis SW-2 root-cause analysis, 2nd/3rd-level support (past) | Watch |
 | Q5 | Production Engineering principles: SLIs, SLOs, error budgets, incident response, reducing toil | **Adjacent** | SLOs BS-3 (past); on-call and incident handling SW-2 (past); toil reduction through automation BS-6, SW-1, SW-3. **SLIs and error budgets not established.** BS-6 forbids an SRE role or title claim | Defines Stretch |
 | Q6 | Instrumenting services; metrics, logs, traces | **Adjacent** | BS-4 ELK/Kafka PoC plus monitoring (past, PoC — never a platform). **Current monitoring at Swisscom unknown — open question** | — |
 | Q7 | Clear technical communication; work across engineering teams | **Direct** | SW-4 stakeholders/architects/engineers; BS-3 vendors and internal customers; BS-5 TAF 2022 co-presentation; GN-1 presenting BDD; BS-9/SW-10 onboarding juniors | — |
 | Q8 | BS/MS in Computer Science or equivalent | **Direct** | EDU-MENG (Software Design & Engineering focus), EDU-BENG | — |
 ### Core responsibilities — "What you'll be doing"
 | # | Responsibility | Class | Evidence |
 |---|---|---|---|
 | R1 | Build/operate production software, automation, tooling for control plane, model deployments, inference and agentic workloads | Adjacent | BS-1 designed and executed containerized ML inference integration in a 24/7 fab (past). Control plane and agentic: none (SW-8 forbids agent orchestration) |
 | R2 | Reliability of inference platforms (NVCF, SGLang/vLLM, Dynamo): health validation, safer rollouts, observability, recovery | Adjacent | BS-1 failure-consequence constraint (a defect could have stopped production) is real safe-rollout motivation; serving stacks are Gap |
 | R3 | Endpoint availability, inference routing, capacity management | Gap | — |
 | R4 | IaC and GitOps to deploy/configure/validate/upgrade/recover across environments | Adjacent | IaC Direct (Q3); GitOps never |
 | R5 | Workflows for service enablement, model releases, handoff, deprecation; automate manual work | Adjacent | SW-1 migration automation; SW-7 onboarding sources and data products; BS-1 |
 | R6 | Define/instrument SLIs and SLOs, error budgets, visible production health | Adjacent | BS-3 SLOs |
 | R7 | On-call, incident response, troubleshooting; recurring issues into automation | **Direct** | SW-2 (past) |
 | R8 | Collaborate with model, platform, storage, networking, security, GPU teams | Adjacent | Cross-team work Direct (Q7); these specific teams not |
 ### Preferred — "Ways to stand out"
 | # | Item | Class |
 |---|---|---|
 | P1 | vLLM, SGLang, PyTorch, TensorRT-LLM, Dynamo, CUDA, NCCL; GPU performance analysis | Gap (PyTorch is certification-context only) |
 | P2 | Kubernetes operators/controllers, workload orchestration, fleet management, self-healing automation | Gap (BS-6 Linux-estate automation is not fleet management at this level) |
 | P3 | Terraform, Argo CD, CI/CD, policy validation, safe deployment and rollback | Partial: CI/CD Direct (Jenkins FC-1/GN-1, GitLab SW-3/BS-6), VZ-2 quality gates; Terraform and Argo CD Gap (Terraform forbidden) |
 | P4 | Developing with AI tools and agents | Direct-ish: Kiro, Copilot, LiteLLM, custom GPTs (SW-8 limits apply) |
 | P5 | Production AI inference or agentic workloads, debugging across models, runtimes, Kubernetes, hardware | Adjacent: BS-1 |
 ## Open Evidence Questions (asked 2026-10-22, per the recurring DevOps/SRE lesson)
 1. **Current ops at Swisscom (ART DPT):** monitoring/alerting on his Glue/Airflow pipelines (CloudWatch alarms, failure alerts, dashboards)? On-call in the current unit? Decides whether Q5/Q6 have current evidence.
 2. **Networking:** AWS VPC, security groups, private endpoints at Swisscom; firewall, DNS, proxy or load-balancer work at Bosch? Would move Q4 networking from personal-only (PP-3) to professional.
 3. **Bosch inference hardware:** did the inference containers run on GPUs? If yes, it licenses "deployed GPU-backed inference containers" only, never CUDA or GPU performance work.
 ## Competitive Read
 - **Obvious-fit candidate:** an SRE/production engineer from a hyperscaler, GPU cloud or ML-serving company who has run vLLM/Triton-style
  endpoints on Kubernetes at scale, written operators, and works in Terraform/Argo CD with formal SLOs and error budgets.
 - **Dennis's advantage:** production ML inference integrated into a continuously running semiconductor fab where a defect could have stopped
  production (BS-1); Ansible depth beyond use, including extensions (BS-6); component ownership with on-call and root-cause work (SW-2);
  current AWS IaC (CloudFormation) and Python automation; a ~10-year automation thread across five employers; current AI dev tooling.
 - **Their advantage:** inference-serving stack, GPU, Kubernetes at scale and currently, SRE formalism (SLIs/error budgets), networking.
 - **Level/scope:** NVIDIA Senior against Swisscom Staff — not a level problem; comp upside is clear.
 ## Framing Strategy (draft — confirmed in Phase 2)
 - **Professional identity:** engineer who builds and operates the automation and delivery layer under production services, including ML
  inference in a 24/7 environment. Never "SRE" as a title.
 - **Strongest proof points:** BS-1, BS-6, SW-2, SW-1 + CloudFormation, SW-3 (past), BS-3 SLOs, BS-4 (PoC).
 - **Explicit gaps:** inference-serving stack, GPU, current Kubernetes, SLIs/error budgets, networking, large-scale distributed systems.
 - **User directives:** none yet.
 ### Answers received 2026-10-22 (recorded in claims.json; extraction `knowledge_base/extractions/2026-10-22_oncall_networking_gpu_clarification.md`)
 1. Current on-duty: Opsgenie alerting, rotating engineer-on-duty role, alerts and bugs auto-create Jira tickets the team assigns and fixes → **new claim SW-11** (current).
 2. Networking: no professional configuration; automated AWS landing zones; AWS SAA cert covers AWS networking → skill `networking`, **certification context only**. Q4 stays Adjacent.
 3. Bosch inference ran on **NVIDIA GPUs** with CUDA; he did little CUDA/GPU configuration → BS-1 scope; **CUDA registered forbidden** as a skill.
 **Re-score after answers: Evidence Fit 65** (Recency 5→6: current on-duty; Domain 4→5: production inference on NVIDIA GPUs). Class unchanged: **Stretch** — Q5 still lacks SLIs and error budgets. Hard gate PASS.
 ## Resume Plan (proposed 2026-10-22, awaiting approval)
 - **Profile:** International Tech, 2 pages. Contact line Bern, Switzerland, plus "EU citizen, Swiss B permit" (remote-CH role, so residency/authorization is worth one line).
 - **Summary (2-3 lines):** over ten years building and operating production software and its automation; GPU-backed ML inference integrated into a continuously running fab (BS-1); today AWS pipelines with CloudFormation and a seat in the on-duty rotation (SW-1, SW-11). No "12+ years" (template claim is open in the KB log).
 - **Skills (~5 rendered lines):** Python, SQL, Bash · AWS (Glue, Athena, S3, Airflow), CloudFormation, Ansible, Docker, Kubernetes, Linux administration, Jenkins, GitLab CI/CD · on-duty incident response (Opsgenie, Jira), SLOs, root-cause analysis, unit testing (pytest) · PySpark, Kafka, Apache Iceberg · AI dev tools: Kiro, Copilot, LiteLLM · Certs line: AWS SA Associate (2024), IBM AI Engineering (PyTorch, TensorFlow; 2020), ITIL Foundation (2016). Never: CUDA, GitOps, Terraform, SRE title, networking as a skill.
 - **Swisscom (5):** (1) SW-11 on-duty rotation, Opsgenie alerts, Jira-tracked fixes — current; (2) SW-1 + CloudFormation: his domains' ETL migrated to AWS as Python Glue jobs, IaC, Airflow — contributor to the wider programme; (3) SW-7 + SW-6 + SW-9: design and build governed data products (PySpark, Glue, Athena, Iceberg) inside the company-wide Data Mesh, unit-tested with pytest; (4) SW-3 past: built and operated Python applications on Kubernetes, deployed through automated GitLab CI/CD across multiple environments; (5) SW-2 past: owned the Fulfillment ETL components into Teradata with on-call, 2nd/3rd-level support and root-cause analysis.
 - **Bosch (4):** (1) BS-1 lead: designed and executed integration of containerized ML inference on NVIDIA GPUs into a continuously operating fab where a software defect could have halted production (Docker, Kubernetes, Ansible), reducing manual defect classification; (2) BS-6: administered and automated the Linux estate behind fab analytics and ML (Ansible from Git, run from Jenkins/GitLab), incl. the credential-caching Ansible plugin; (3) BS-3/BS-5: technical Application Owner for KLA DMS and Spotfire, defined SLOs, vendors, user training; (4) BS-4: ELK/Kafka log-management and anomaly-detection PoC with monitoring (PoC label kept).
 - **Earlier (1 each):** Fraunhofer FC-1 (Jenkins jobs for automatic SCEDAS deployment); Vizrt VZ-2 + VZ-1 (test suites as CI/CD quality gates; contributed Python to a distributed transcoding backend; no customer names); Generali GN-3 + GN-1 (web services onto a new XLDeploy deployment procedure; technical responsibility for BDD test automation in Jenkins).
 - **Total bullets:** 12.
 - **Open confirmations before generation:** (a) BS-4 — did the PoC include Grafana/Prometheus/Loki? Source is only the user's earlier CV (`thiessen_cv_master_profile.md`), not the Zeugnis or claims.json; omitted unless confirmed. (b) SW-11 — does he also write or adjust the alerts for his own pipelines? If not, the bullet says "respond to" only.
 - **Impact evidence still needed:** none quotable; every claim is metrics-unverified.
 ## Cover Letter Decision
 - **NO.** Workday portal, no letter requested; no transition, relocation or language issue to explain; the GPU and on-duty evidence fits in the resume. The warm action (LinkedIn note) has more information value than a letter.
 ### Confirmations received 2026-10-22 (recorded in claims.json)
 - (a) BS-4 included Grafana, Prometheus and Loki (PoC). (b) He writes alert thresholds for his own pipelines, e.g. data-quality thresholds (SW-11).
 - Generation started on the user's instruction "prepare the cv for nvidia" plus these answers; no plan objection was raised. Any plan change is an `/edit-resume` pass.
 ## As Built (2026-10-22)
 - **Header:** headline "Staff Data & AI Engineer | Production Automation and Operations | AWS · ML Inference"; contact line Bern, Switzerland | EU citizen, Swiss B permit.
 - **Summary:** 3 rendered lines (trimmed from 4 to meet config.md's 2-3); "over ten years in production software and its automation" (measured from Generali 2015-05).
 - **Skills:** 5 categories, 8 rendered lines (trimmed from 9; cut what bullets prove: Opsgenie/Jira, ELK/Prometheus/Grafana/Loki, AWS service list, LiteLLM, ITIL). Literals for required Q3 restored after the headline cut dropped them: "infrastructure as code (CloudFormation)", "configuration management (Ansible)"; Q1 support: "PySpark (distributed processing)". PyTorch/TensorFlow only inside the IBM certificate line (validator rule). No CUDA, GitOps, Terraform, networking or SRE title.
 - **Bullets: 13** — Swisscom 5 (SW-11, SW-1, SW-7/SW-6/SW-9, SW-3 past, SW-2 past); Bosch 5 (BS-1 with NVIDIA GPUs, BS-6 estate, BS-6 plugin, BS-3/BS-5, BS-4 PoC); Fraunhofer FC-1; Vizrt VZ-2/VZ-1; Generali GN-3/GN-1. Deviation from plan: the BS-6 credential plugin became its own short bullet (Bosch 5 instead of 4) for readability.
 - **Layout:** the template's forced page break after Swisscom was removed so the Bosch NVIDIA-GPU bullet sits on page 1. Page 2 ends about half-way; no filler added.
 - **Validation:** `validate_resume_system.py --document` PASS, 0 warnings (first run failed on PyTorch without certification context; fixed). MiKTeX pdflatex: 2 pages, 0 overfull/underfull boxes. Both pages inspected visually at 80 dpi. `pdftotext -layout`: heading/employer/title/date order correct; no Capgemini.
 ## Output Files
 - Resume: `e2e_nvidia_prod_eng_dgx_cloud_resume.tex` (source of truth) + `.pdf`
 - Cover letter: intentionally omitted (decision NO above)
 - Critique: `critique_nvidia_prod_eng_dgx_cloud.md` (2026-10-22)
 ## Critique Summary (2026-10-22)
 - Evidence Fit: **65/100 — Stretch**
 - Hard gate: **PASS** (Q1 large-scale distributed systems is the likeliest screen rejection)
 - Document Quality: **85/100**
 - Channel Strength: **Weak** (warm LinkedIn note not yet sent)
 - Tier 1 fixes: (1) Swisscom #1 "set the alert thresholds" → "set alert thresholds". Tier 2: tense cue on the two past Swisscom bullets; one-line PP-3 personal-infrastructure entry; tighten Swisscom #1 and Bosch #1; optional "observability" on BS-4.
 ## Status
 - Fit gate: Stretch, Evidence Fit 63 initial → 65 after the 2026-10-22 answers; hard gate PASS
 - Resume: generated and validated 2026-10-22; awaiting user review
 - Cover letter: NO
 - Critique: done 2026-10-22 — DQ 85 measured BEFORE Edit 1; **stale after Edit 1** (not re-measured; never quote a post-edit estimate as a score)
 - Application/outcome: **SUBMITTED 2026-10-22** via Workday (user-confirmed). Tracker row added (applied, stretch, 65, hard gate pass, channel weak); scout decision `applied`. Channel still Weak until the LinkedIn note is sent.
 - **Finalized 2026-10-22 on user instruction ("finalize").** Checks: session, `.tex`, `.pdf`, critique and JD present; PDF newer than `.tex`; validator PASS, 0 warnings; 2 pages; PDF metadata clean (empty Title/Author, MiKTeX pdfTeX). Submission copy `Dennis_Thiessen_Resume.pdf` created, byte-identical to `e2e_nvidia_prod_eng_dgx_cloud_resume.pdf`. No cover letter (decision NO).
 - Next: user submits via Workday → then `application_tracker.py add` (outcome applied, fit stretch, evidence-fit 65, hard-gate pass, channel weak, job-id JR2027105) and regenerate views. Not added before submission, because `add` stamps `application_date`. Warm action: LinkedIn note to an NVIDIA recruiter or DGX Cloud engineer (draft given to the user 2026-10-22). **Refresh `Dennis_Thiessen_Resume.pdf` on any recompile.**
 ## Edit History
 ### Edit 1 (2026-10-22): critique Tier 1 + all Tier 2, user-approved ("apply fixes and improvements as you recommend")
 - **Tier 1 #1 (truth):** Swisscom #1 "set the alert thresholds" → "set alert thresholds" (SW-11: data-quality thresholds were an example, not all thresholds).
 - **Tier 2 #1:** the two past Swisscom bullets now read "Earlier in the role, owned the Fulfillment ETL components …" and "Built and operated Python applications on Kubernetes in the same period …" (SW-2 moved before SW-3 so the two do not open identically). No dates, no unit names.
 - **Tier 2 #2:** new section **Personal Infrastructure** (PP-3): "Self-host and harden a personal Debian server, run for about ten years: nginx, a mail server, a VPN server, Docker services and Bitwarden." Personal label in the heading and the sentence; no uptime/scale figure; not presented as employer, production or datacenter work.
 - **Tier 2 #3:** Swisscom #1 tightened ("alerts" once; "resolving issues through auto-created Jira tickets"); Bosch #1 now names the GPUs once: "containerized ML inference on NVIDIA GPUs (Docker, Kubernetes, Ansible)".
 - **Tier 2 #4:** BS-4 now "Built an observability proof of concept for log management and anomaly detection on ELK and Kafka …" (PoC label kept).
 - **Verification:** validator PASS, 0 warnings; MiKTeX 2 pages, 0 overfull/underfull boxes; both pages inspected at 80 dpi (Bosch NVIDIA-GPU bullet still on page 1; Personal Infrastructure sits between Experience and Education on page 2; page 2 ends a little past half-way); `pdftotext -layout` order: Summary → Skills → Experience (Swisscom, Bosch, Fraunhofer, Vizrt, Generali) → Personal Infrastructure → Education. Bullets: 13 experience bullets unchanged in count, plus the one-line personal entry. (copy to `Dennis_Thiessen_Resume.pdf`, tracker `add`). Warm action before/after submit: LinkedIn note to an NVIDIA recruiter or DGX Cloud engineer.
@@ -310,7 +310,7 @@
        "source": "knowledge_base/extractions/2026-10-03_data_product_design_frontend_clarification.md; prior user confirmations 2026-07-29 and 2026-09-15",
        "ownership": "unrecorded"
      },
-      "scope": "Build governed data products and onboard sources within Swisscom's company-wide Data Mesh; never claim ownership or construction of the shared mesh/platform. Atlassian Compass is the metadata/catalogue platform used for data-product metadata and lineage (user-confirmed 2026-07-29); Dennis uses it as a practitioner and does not administer or own the tooling. User-confirmed 2026-09-15: the data-product modelling is RELATIONAL - logical and physical table models. Data products are created with ODP-Flow, Swisscom's internal data-product framework (see SW-1); he uses the framework and did not build it. PHASE, user-confirmed 2026-09-15: current work at ART DPT, Team Offering. User-confirmed 2026-10-03: current work includes data modelling, design of data products and their implementation. Scope design to his own data products; the exact duration is not established by this clarification.",
+      "scope": "Build governed data products and onboard sources within Swisscom's company-wide Data Mesh; never claim ownership or construction of the shared mesh/platform. Atlassian Compass is the metadata/catalogue platform used for data-product metadata and lineage (user-confirmed 2026-07-29); Dennis uses it as a practitioner and does not administer or own the tooling. User-confirmed 2026-09-15: the data-product modelling is RELATIONAL - logical and physical table models. Data products are created with ODP-Flow, Swisscom's internal data-product framework (see SW-1); he uses the framework and did not build it. PHASE, user-confirmed 2026-09-15: current work at ART DPT, Team Offering. User-confirmed 2026-10-03: current work includes data modelling, design of data products and their implementation. Scope design to his own data products; the exact duration is not established by this clarification. User-confirmed 2026-10-21 (knowledge_base/extractions/2026-10-21_software_design_architecture_clarification.md): software design and architecture of data products are part of his Swisscom work, and together with the Bosch design work (BS-1/BS-2, 2020-2022) they exceed three years - enough to meet a '3 years of software design and architecture' requirement. The start date of design work at Swisscom stays undated (never date the ART units).",
      "allowed_verbs": [
        "build",
        "model",
@@ -363,18 +363,24 @@
        "source": "Bosch Arbeitszeugnis, Dresden 31.12.2022 (primary document, read 2026-09-11); operating constraint user-clarified 2026-09-11",
        "ownership": "individual - integration and operation; model development is NOT his"
      },
-      "scope": "Designed and executed integration of containerized ML inference into a 24/7 semiconductor production environment; model-development ownership is not established. Toolchain includes Docker, Kubernetes and Ansible - Ansible use at Bosch was intensive (user-confirmed 2026-08-27) and extended to configuration management and infrastructure automation beyond this single integration, making it standalone Infrastructure-as-Code evidence. OPERATING CONSTRAINT, user-clarified 2026-09-11: the fab runs continuously, and a defect in the software could in the worst case halt production - an outcome that must never occur. That is a FAILURE-CONSEQUENCE constraint (blast radius of a bug), NOT a deployment-window constraint. Write it as 'a defect could have stopped production' or 'software whose failure would have halted a continuously operating fab'. ZEUGNIS WORDING (primary, 2026-09-11): 'Erarbeitung und Durchfuehrung von Integrationsstrategien fuer den Einsatz von Machine Learning Modellen in der 24/7 Fertigungsumgebung' - devising AND executing integration strategies for ML models in the 24/7 manufacturing environment. This corroborates the integration-and-operation framing and the 24/7 context directly.",
+      "scope": "Designed and executed integration of containerized ML inference into a 24/7 semiconductor production environment; model-development ownership is not established. Toolchain includes Docker, Kubernetes and Ansible - Ansible use at Bosch was intensive (user-confirmed 2026-08-27) and extended to configuration management and infrastructure automation beyond this single integration, making it standalone Infrastructure-as-Code evidence. OPERATING CONSTRAINT, user-clarified 2026-09-11: the fab runs continuously, and a defect in the software could in the worst case halt production - an outcome that must never occur. That is a FAILURE-CONSEQUENCE constraint (blast radius of a bug), NOT a deployment-window constraint. Write it as 'a defect could have stopped production' or 'software whose failure would have halted a continuously operating fab'. ZEUGNIS WORDING (primary, 2026-09-11): 'Erarbeitung und Durchfuehrung von Integrationsstrategien fuer den Einsatz von Machine Learning Modellen in der 24/7 Fertigungsumgebung' - devising AND executing integration strategies for ML models in the 24/7 manufacturing environment. This corroborates the integration-and-operation framing and the 24/7 context directly. DESIGN, user-confirmed 2026-10-21 (knowledge_base/extractions/2026-10-21_software_design_architecture_clarification.md): software design and architecture of the ingestion and inference scripts were part of his Bosch work (2020-2022) and count toward a 'years of software design and architecture' requirement. Scope 'designed' to his own scripts and the inference integration - never the fab IT architecture, an architect title or design authority. HARDWARE, user-confirmed 2026-10-22 (knowledge_base/extractions/2026-10-22_oncall_networking_gpu_clarification.md): the inference ran on NVIDIA GPUs, with CUDA used for the performance boost - his words: 'The ML inference did ran on NVIDIA GPUs (using CUDA for performance boost - but i never did much configuration there)'. Writable: 'GPU-backed inference containers on NVIDIA GPUs' as a description of what he integrated and deployed. CUDA is a property of the system, not his skill: he did little CUDA or GPU configuration, so never claim CUDA work, GPU configuration, GPU tuning or GPU performance analysis.",
      "allowed_verbs": [
        "integrated",
        "containerized",
        "deployed",
-        "orchestrated"
+        "orchestrated",
        "designed"
      ],
      "forbidden": [
        "trained the image classification model",
        "owned the full ML lifecycle",
        "a production line that could not be stopped for a deployment",
-        "could not be stopped for a deployment"
+        "could not be stopped for a deployment",
        "CUDA programming",
        "configured CUDA",
        "GPU performance tuning",
        "optimized GPU performance",
        "GPU performance analysis"
      ],
      "metrics": "qualitative reduction in manual classification is source-backed; exact amount unverified"
    },
@@ -384,10 +390,11 @@
        "source": "Bosch Arbeitszeugnis, Dresden 31.12.2022 (primary document, read 2026-09-11)",
        "ownership": "individual - development"
      },
-      "scope": "Developed data services in Python, Java and C# over Oracle and Hadoop/Impala for internal analysis teams. Data types worked on (user-confirmed 2026-08-02): semiconductor fab sensor and process data -- defect management records, wafer inspection images, and electrical parameters from Process Control Monitoring (PCM). Relevant as genuine industrial sensor/asset-data experience. Bosch development was PRIMARILY PYTHON, with some Java and KOTLIN (backend, Ansible plugins, extensions) and C# for Spotfire plugins (user-confirmed 2026-09-11). ZEUGNIS WORDING (primary): 'Entwicklung von Applikationen zur Datenanalyse in C#, Python und Java' and 'Integration von Software-Komponenten in die IT-Architektur der Halbleiterproduktion'. NOTE: the Zeugnis names C#, Python and Java only - KOTLIN rests on the user's statement of 2026-09-11 and is not corroborated by this document. Record it as user-confirmed, not Zeugnis-confirmed.",
+      "scope": "Developed data services in Python, Java and C# over Oracle and Hadoop/Impala for internal analysis teams. Data types worked on (user-confirmed 2026-08-02): semiconductor fab sensor and process data -- defect management records, wafer inspection images, and electrical parameters from Process Control Monitoring (PCM). Relevant as genuine industrial sensor/asset-data experience. Bosch development was PRIMARILY PYTHON, with some Java and KOTLIN (backend, Ansible plugins, extensions) and C# for Spotfire plugins (user-confirmed 2026-09-11). ZEUGNIS WORDING (primary): 'Entwicklung von Applikationen zur Datenanalyse in C#, Python und Java' and 'Integration von Software-Komponenten in die IT-Architektur der Halbleiterproduktion'. NOTE: the Zeugnis names C#, Python and Java only - KOTLIN rests on the user's statement of 2026-09-11 and is not corroborated by this document. Record it as user-confirmed, not Zeugnis-confirmed. DESIGN, user-confirmed 2026-10-21 (knowledge_base/extractions/2026-10-21_software_design_architecture_clarification.md): he designed as well as built the INGESTION SCRIPTS (his words: 'ingestion/inference scripts at Bosch'). 'designed' covers those scripts only - the statement does not extend to the data services in general, so write 'developed' or 'built' for them. See BS-1 for the shared design note and its limits.",
      "allowed_verbs": [
        "developed",
-        "built"
+        "built",
        "designed"
      ],
      "metrics": "unverified"
    },
@@ -412,7 +419,7 @@
        "source": "Bosch Arbeitszeugnis, Dresden 31.12.2022 (primary document, read 2026-09-11)",
        "ownership": "individual - proof of concept"
      },
-      "scope": "Built an ELK/Kafka anomaly-detection proof of concept and monitoring; not a company-wide observability platform. ZEUGNIS WORDING (primary): 'Durchfuehrung eines POCs fuer das Logfile-Management mit ELK-Stack' - the PoC framing is confirmed by the document itself, not just by policy.",
+      "scope": "Built an ELK/Kafka anomaly-detection proof of concept and monitoring; not a company-wide observability platform. ZEUGNIS WORDING (primary): 'Durchfuehrung eines POCs fuer das Logfile-Management mit ELK-Stack' - the PoC framing is confirmed by the document itself, not just by policy. STACK, user-confirmed 2026-10-22 (knowledge_base/extractions/2026-10-22_oncall_networking_gpu_clarification.md): besides ELK and Kafka, the PoC included monitoring and alerting with GRAFANA, PROMETHEUS and LOKI. That was previously recorded only in the user's earlier CV (thiessen_cv_master_profile.md), not in the Zeugnis, which names the ELK log-management PoC. All of it stays PoC-scoped: never a production monitoring platform.",
      "allowed_verbs": [
        "built",
        "implemented",
@@ -817,6 +824,36 @@
        "formal mentoring programme - not established"
      ],
      "metrics": "none; number of junior developers and outcomes are not recorded"
    },
    {
      "id": "SW-11",
      "evidence": {
        "source": "user confirmation 2026-10-22; knowledge_base/extractions/2026-10-22_oncall_networking_gpu_clarification.md",
        "ownership": "team-role - member of a rotating engineer-on-duty role; individual - alert thresholds for his own pipelines"
      },
      "scope": "CURRENT on-duty and alert handling at Swisscom (user answer 2026-10-22 to 'do you monitor or get alerted on your Glue/Airflow pipelines; is there on-call in the current unit?'). Verbatim: 'Yes, we get alerted ... we are using opsgenie and we have a engineer on duty role which rotates. Bugs and Alerts also automatically create Jira issue tickets which we dann asign an fix.' Established: alerting through OPSGENIE; a ROTATING ENGINEER-ON-DUTY role in his team, which he takes part in; bugs and alerts automatically create Jira tickets that the team assigns and fixes. PHASE: current (asked about the current unit, ART DPT); never date it. This is the current counterpart of the past SW-2 on-call (Rufbereitschaft) at ART B2B. NOT established: who built or configured the alerting, the Opsgenie routing or the Jira automation (do not claim he did); which metrics or logs feed the alerts; SLIs, SLOs or error budgets; any incident count, response time, MTTR or availability figure; whether the duty covers nights and weekends (do not write 24/7). ALERT DEFINITIONS, user-confirmed 2026-10-22 (follow-up 'do you also write or adjust the alerts for your own pipelines?'): 'yes, i wrote e.g. thresholds for data quality etc....' So he defines alert thresholds for his own pipelines, data-quality thresholds being the named example. Writable: 'defined alert thresholds, including data-quality checks, for my pipelines'. Still NOT established: other alert types (latency, freshness, cost) - do not list them; the Opsgenie routing and the Jira automation, which he did not set up.",
      "allowed_verbs": [
        "serve",
        "take part in",
        "respond to",
        "triage",
        "fix",
        "resolve",
        "define",
        "set"
      ],
      "forbidden": [
        "configured Opsgenie",
        "set up Opsgenie",
        "designed the on-call process",
        "owned incident management",
        "SRE role or title",
        "24/7 on-call",
        "any incident count, MTTR, response-time or availability figure",
        "built the alerting platform",
        "set up the Opsgenie or Jira integration"
      ],
      "metrics": "none"
    }
  ],
  "skills": [
@@ -1271,6 +1308,53 @@
      "evidence": "production-historical",
      "output": "allowed",
      "note": "Registered 2026-10-14 from existing canonical claim scopes - no new user statement, same procedure as Jenkins and GitLab CI/CD on 2026-10-08. Was evidenced in scopes but absent from this skills list, so a skills line could not cite it (surfaced by the BIS jr100498 package). BS-2 (Bosch 2020-2022): data services over Hadoop/Impala for fab analysis teams. Query and data-service use; does not establish Hadoop cluster administration or Cloudera administration."
    },
    {
      "name": "Opsgenie",
      "evidence": "hands-on-current",
      "output": "allowed-with-context",
      "context": "SW-11: alerting for his team's rotating engineer-on-duty role at Swisscom.",
      "note": "User-confirmed 2026-10-22. Use as a responder, never as its administrator or the author of the alert routing."
    },
    {
      "name": "CUDA",
      "evidence": "system-context-only",
      "output": "forbidden",
      "note": "User-confirmed 2026-10-22: the Bosch inference (BS-1) ran on NVIDIA GPUs with CUDA for the performance boost, but he 'never did much configuration there'. CUDA describes that system, not a skill he has. Registered forbidden so the scanner catches it on documents; the honest wording is 'GPU-backed inference on NVIDIA GPUs' (BS-1). In an interview he can say the models used CUDA and that his part was integration and deployment."
    },
    {
      "name": "networking",
      "evidence": "certification-and-personal",
      "output": "certification-context-only",
      "note": "User answer 2026-10-22 to 'any AWS VPC, security-group or private-endpoint work at Swisscom, or firewall, DNS, proxy or load-balancer work at Bosch?': 'No, not really - probably only my AWS solution architect cert covers AWS network topics... but day to day work is using automated landing zones.' So: no professional network configuration. AWS networking is covered by the AWS Certified Solutions Architect - Associate (26 Sep 2024, active; thiessen_certifications.md #7), certification context only. At work he USES automated AWS landing zones provided by the platform - never claim he built or designed landing zones, VPCs or network topology. Personal: PP-3 runs nginx, a VPN server and a mail server (personal label required; PP-3 forbids datacenter or physical-infrastructure claims). JD lines on networking fundamentals stay Adjacent at best."
    },
    {
      "name": "ELK Stack",
      "evidence": "proof-of-concept",
      "output": "allowed-with-context",
      "context": "BS-4: Bosch log-management and anomaly-detection proof of concept (2020-2022).",
      "note": "Registered 2026-10-22. ELK named in the Bosch Zeugnis. Always keep the PoC label; never imply production or platform ownership."
    },
    {
      "name": "Grafana",
      "evidence": "proof-of-concept",
      "output": "allowed-with-context",
      "context": "BS-4: Bosch log-management and anomaly-detection proof of concept (2020-2022).",
      "note": "Registered 2026-10-22. User-confirmed 2026-10-22; previously only in the user's earlier CV. Always keep the PoC label; never imply production or platform ownership."
    },
    {
      "name": "Prometheus",
      "evidence": "proof-of-concept",
      "output": "allowed-with-context",
      "context": "BS-4: Bosch log-management and anomaly-detection proof of concept (2020-2022).",
      "note": "Registered 2026-10-22. User-confirmed 2026-10-22; previously only in the user's earlier CV. Always keep the PoC label; never imply production or platform ownership."
    },
    {
      "name": "Loki",
      "evidence": "proof-of-concept",
      "output": "allowed-with-context",
      "context": "BS-4: Bosch log-management and anomaly-detection proof of concept (2020-2022).",
      "note": "Registered 2026-10-22. User-confirmed 2026-10-22; previously only in the user's earlier CV. Always keep the PoC label; never imply production or platform ownership."
    }
  ],
  "global_forbidden_output_patterns": [
@@ -5,7 +5,7 @@ Use current outcome and next action below. Imported legacy notes are historical,
 | Application | Current outcome | Interview reached | Next action |
 |---|---|---|---|
-| NVIDIA - Senior DevOps Engineer, Zürich (req JR2024256) | applied | not recorded | Await response. At first contact, clarify homeoffice/onsite requirements and total package. Baseline is 3 homeoffice days/week; fewer days require a clear overall improvement. Note: `claims.json` has no shell-scripting entry, so **Bash is omitted** from Skills although the JD names it and ten years of Debian admin plus Ansible work plainly involve it - same shape as the Ansible/Linux gaps found 2026-08-27. Confirm with the user and record it. Groovy stays out regardless. |
+| NVIDIA - Senior DevOps Engineer, Zürich (req JR2024256) | applied | not recorded | No action expected; req pulled ~2026-09-20. Treat as dormant. Does not block NVIDIA JR2027105 (Senior Production Engineer, DGX Cloud). |
 | RUAG C5I - AI Engineer C5I, Thun (application ID 18027) | rejected_after_interview | yes | Abgeschlossen: Absage nach Interview; Anforderungen vor allem beim Homeoffice nicht vereinbar. Keine weitere Aktion fuer diese Bewerbung offen. |
 | Schweizer Armee - Kommando Cyber (Kdo Cy), DevOps Engineer III (Data Platform), Zimmerwald (Ref JRQ$540-19848) | rejected_no_interview | not recorded | Closed; no pending application action. Read recorded history before reopening. |
 | Citadel Securities — Platform Engineer, Research Platform Engineering, Zürich (also NY/Miami) | applied | not recorded | Await response. At first contact, confirm whether the application is for the Zurich seat; relocation to the US remains ruled out. Clarify homeoffice/onsite requirements and the Zurich compensation package. Baseline is 3 homeoffice days/week; fewer days require a clear overall improvement. The posted US salary range is not a Zurich figure. |
@@ -32,9 +32,11 @@ Use current outcome and next action below. Imported legacy notes are historical,
 | Equinor — Manager / AI Architect, Agentic systems (Stavanger/Oslo/Rotvoll/Sandsli; req JR106747) | rejected_no_interview | not recorded | Closed; no pending application action. Read recorded history before reopening. |
 | QuantCo Cloud Engineer (Europe/Zürich) | rejected_no_interview | not recorded | Closed; no pending application action. Read recorded history before reopening. |
 | Swisscom (Schweiz) AG — Data Engineer - Geo Platform, Bern/Worblaufen (internal, req R-0006447) | interviewing | yes | Swisscom-Rueckmeldung zwischen 2026-10-08 und 2026-10-15 abwarten; internen Aufgabenwechsel separat bewerten. Externe Suche unabhaengig vom Ausgang aktiv fortsetzen, auch bei erfolgreichem internem Wechsel. |
-| Google — Senior Software Engineer, Full Stack, Commerce, Zürich | open | not recorded | Choose Shopping Ads SWE III (Mid; compensation unpublished), search further Google Senior roles, or explicitly override the stated Commerce frontend gap. No application submitted. |
+| Google — Senior Software Engineer, Full Stack, Commerce, Zürich | open | not recorded | No action - superseded by the Staff Shopping Graph package (output/Google_Staff_SWE_Shopping_Graph/). Reopen only if the user explicitly overrides the frontend gap. |
 | Kongsberg Discovery (Seatex) — Lead Engineer, DevOps and Test Infrastructure, Trondheim | applied | not recorded | Wait for Kongsberg response. Screen prep: embedded targets/HIL question, recency of DevOps/test work (2015-22), relocation to Trondheim, clearance eligibility as German citizen resident in Switzerland, on-site expectations. Package: output/Kongsberg_Lead_Engineer_DevOps_Test_Infra/. |
 | BIS (Bank for International Settlements) — Senior/Lead Data & Analytics Engineer, MED IT, Basel (jr100498, 3-yr term) | applied | not recorded | Await BIS response. If contacted: ask office days and total package; weigh the 3-year fixed term against the permanent Swisscom post. Interview prep is in the critique: SDMX answer, Swisscom dashboard tool (not in KB), attributed schedule example for project planning, Lead story. |
 | Google — Staff Software Engineer, Shopping Graph (Feeds Infra), Zürich | applied | not recorded | Await Google response. Google limit: next Google application window counts this submit (3 per rolling 30 days). At first contact clarify level (L6 vs L5), Zurich hybrid days vs current 3 homeoffice days, and total package. Interview prep: SW-4 prototype story as the technical-direction example, plus one concrete Staff-level example the user names; Java currency; end-to-end system design with scale and trade-offs. Package: output/Google_Staff_SWE_Shopping_Graph/. |
 | NVIDIA — Senior Production Engineer, DGX Cloud, Switzerland Remote (JR2027105) | applied | not recorded | Await response. Send the LinkedIn note to an NVIDIA recruiter or DGX Cloud engineer (draft in session). Interview prep: incident debugged end to end (SW-2/SW-11); safe model rollout in the fab (BS-1, rollout mechanics not in KB); Kubernetes recency; distributed systems at scale; vLLM/SGLang/Dynamo not used. Package: output/NVIDIA_ProdEng_DGX_Cloud/. |
 ## Current targeting notes
Author	SHA1	Message	Date
dennisthiessenandClaude Opus 5.5	3a9c2faf44	feat(app): NVIDIA Senior Production Engineer, DGX Cloud submitted; on-duty, GPU and networking KB gaps closed; triage 2026-10-22 Application (submitted 2026-10-22, Workday): - NVIDIA JR2027105, Switzerland Remote. Evidence Fit 65, Stretch (SLIs and error budgets not evidenced), hard gate PASS, channel Weak, no cover letter. - Package in output/NVIDIA_ProdEng_DGX_Cloud/: session, resume .tex, critique (Document Quality 85 before Edit 1; Tier 1 + all Tier 2 applied), verbatim JD. - Prior NVIDIA req JR2024256 was pulled (last listed 2026-09-18; page gone 2026-10-22): noted on that application, so there was no stacking conflict. KB (claims.json, user-confirmed 2026-10-22): - SW-11: current rotating engineer-on-duty role, Opsgenie alerting, alerts and bugs auto-create Jira tickets; he writes alert thresholds (e.g. data quality). - BS-1: the Bosch inference ran on NVIDIA GPUs; CUDA registered forbidden as a skill (system context only, little configuration done). - BS-4: the PoC included Grafana, Prometheus and Loki; ELK Stack, Grafana, Prometheus and Loki registered as PoC-context skills. - networking: certification context only (AWS SA Associate); work uses automated landing zones. - Extraction and CLAUDE.md log row added. Scout state: - decisions: RUAG Senior DevOps (Kubernetes) C5I parked (home-office terms); SLB Data Scientist skipped (user); NVIDIA JR2008695 skipped (C++/Rust 8y); JR2027105 applied; Norway/Apple/Swiss JD-read triage decisions. - employer_reputation: SLB (Glassdoor 3.9), MazeMap and SpareBank 1 Nord-Norge (unchecked). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 22:29:27 +02:00
dennisthiessenandClaude Opus 5.5	ff12f16545	fix(scout): Apple blind to CH for 2 months, BIS behind Cloudflare, NAV rate limit, EMEA leak; reputation for every board Apple (the big one) - The location=switzerland-CHE slug stopped resolving; Apple silently applied a US location, so every run from at least 2026-08-31 returned the same 21 US/intern cards and 0 Swiss roles. Now location code CHEC (from /api/v1/refData/postlocation), result list item as the card (location readable), pagination, settle delay, longer wait and per-element timeout. Verified twice: 24 Swiss roles each run. BIS - bis.org went behind a Cloudflare challenge (403 even headless). Moved to the Workday tenant bis.wd3.myworkdayjobs.com/External, which also carries the office. Host alias + lower-cased jr-id keep all 9 bis.org#jr decisions linked (applied jr100498 included). NAV - Search API 429s after ~9 requests and stays blocked for hours: discovery capped at 8 searches (4s pacing). Posting text now comes from NAV's official third-party feed (pam-stilling-feed, public rotating token), with a small, slow website-page fallback for ads the feed lacks (~2/3). Verified live on 15 real ads; fallback path tested on fixtures. Location filter - EMEA leak fixed: a country allowlist without CH/DK plus a trailing region tag is no longer Europe-remote (27 rows). Swiss/Danish segments in multi-location strings are evaluated per segment. Regression over all 2026-10-22 rows: only the fenced rows changed. Reputation - Every board now has a dated verdict; kununu added as a primary source next to Glassdoor (the one with more reviews decides; user tip). Second-source scores now count (a low one means avoid). AVOID: BIS (Glassdoor 2.9), BFH (kununu 3.3), Kdo Cy (federal administration kununu 3.4). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 10:44:45 +02:00
dennisthiessenandClaude Opus 5.5	eee608a213	fix(scout): English-only requirement reads ENGLISH OK; triage 2026-10-22 decisions - classify_language_requirement: an ad stating only an English requirement ("communication and presentation skills in English") with no Norwegian requirement now reads english_ok. Checked after the Norwegian patterns, so "fluent English and Norwegian" still reads norwegian_required. Nordic Semiconductor's ads read UNCLEAR in the first Norway run. - Decisions from the 2026-10-22 run: Nordic Embedded Software Test Automation Engineer `maybe` (embedded/Bluetooth experience required, coursework only - the Kongsberg gate); Nordic ATE Test Engineer `skip`; RUAG Senior DevOps Engineer C5I repost `skip` ("Swiss citizenship required"; a different role from the July shortlist, whose note is carried into the new row). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 09:42:47 +02:00
dennisthiessenandClaude Opus 5.5	92c3c005b4	feat(scout): Norway outside Oslo via NAV + dedicated boards, language check, reputation, region split Norway search (user request 2026-10-21/22: Trondheim, Bergen or similar, not Oslo) - New location policy norway_no_oslo: keeps a role if any Norwegian location is outside the Oslo area. Equinor and Telenor move to it. - New `nav` adapter for the NAV national register (arbeidsplassen.nav.no): keyword queries on a fixed request budget, paced; on HTTP 429 it stops and returns a PARTIAL run with a warning instead of failing. Full-ad text checks are cached in state/nav_detail_cache.json (ignored). Tested against fixtures only: the live API was rate-limiting during the build. - Dedicated boards where NAV was measured thin (2026-10-22: Nordic 0, DNV 2, Equinor 2 vs ~10, NATO 0): Nordic Semiconductor (teamtailor custom domain), DNV (new `algolia_jobs` adapter; app id/key/index read from the page each run), Arm Trondheim (new `radancy` adapter), Microsoft Norway (pcsx). Verified live: 7 / 6 / 7 / 6 roles outside Oslo. - NAV rows that duplicate a dedicated board's posting are dropped (employer alias + normalized title). Language / citizenship check - classify_language_requirement reads the requirement SENTENCE, not the posting language: "norsk og/eller engelsk" is English OK, "kommunisere godt ... på norsk og engelsk" is Norwegian required. Only an explicit Norwegian requirement or Norwegian-citizenship requirement filters a role; clearance is noted, never a gate. Runs on full ad text (NAV detail page, untruncated Teamtailor/PCSX descriptions). Telenor Lead Platform Engineer now reads NORWEGIAN REQUIRED (it read UNCLEAR on truncated text). - Norwegian title keywords added (they all scored 0 and were never checked). Employer reputation (user requirement 2026-10-22) - state/employer_reputation.json (now tracked): dated Glassdoor lookups with sources and the approved thresholds (good >= 3.8 on >= 50 reviews; ok 3.5-3.79 or thin-but-backed; avoid < 3.5; Vizrt excluded). Every report row shows the verdict; unlooked-up employers show UNCHECKED. Report - Sections per region: Switzerland, Norway, Europe-remote / Denmark (user preference); `--region=ch\|no` runs one region only. Fixes - Microsoft links: apply.careers.microsoft.com<positionUrl>?jobId=<id> with a host alias so all 7 logged Microsoft decisions still resolve; the old jobs.careers.microsoft.com form redirected to a generic search page. PCSX calls retry on 429. CLAUDE.md corrections log: design/architecture gap (2026-10-21) and the Microsoft link fix; the EMEA-suffix location leak stays OPEN. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 09:19:05 +02:00
dennisthiessenandClaude Opus 5.5	7d8166ddd2	feat(app): Google Staff SWE, Shopping Graph submitted; design/architecture KB gap closed; scout triage 2026-10-20 Scout triage 2026-10-20 - 109 new rows screened; 23 JDs read in full and logged with the failing line quoted; 4 Google reqs screened 10-21. One new maybe (Google Senior SRE, YouTube ML); SBB Team Ampere skipped on the user's Niveau rule (J). Google Staff Software Engineer, Shopping Graph (Feeds Infra), Zurich - Chosen as the single Google application after comparing all live Zurich reqs. Evidence Fit 70, Stretch (Staff-level technical leadership is the defining responsibility and only Adjacent), hard gate PASS, channel weak. - Resume generated, critiqued (Document Quality 84), edited for leadership framing, finalized and submitted 2026-10-21. No cover letter. - The summary line "sets the technical direction for the data products of his domains" rests on the user's 2026-10-21 statement and is deliberately NOT in claims.json (user request); recorded in the session Edit History. - Registry: new applied entry; the Commerce entry is marked superseded. KB: software design and architecture - User-confirmed 2026-10-21: design and architecture of the ingestion and inference scripts at Bosch (2020-22) and of data products at Swisscom; the two together exceed three years. Recorded on BS-1, BS-2 and SW-7, with `designed` added to the BS-1/BS-2 verbs, scoped to his own scripts and the inference integration (the first patch over-extended it to the data services and was trimmed the same session). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 09:18:50 +02:00