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>

output/NVIDIA_ProdEng_DGX_Cloud/JD_nvidia_prod_eng_dgx_cloud_jr2027105.txt

@@ -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.

output/NVIDIA_ProdEng_DGX_Cloud/critique_nvidia_prod_eng_dgx_cloud.md

@@ -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.

output/NVIDIA_ProdEng_DGX_Cloud/e2e_nvidia_prod_eng_dgx_cloud_resume.tex

@@ -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}

output/NVIDIA_ProdEng_DGX_Cloud/resume.cls

@@ -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
+}

output/NVIDIA_ProdEng_DGX_Cloud/session_nvidia_prod_eng_dgx_cloud.md

@@ -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.