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>

resume_builder/canonical/claims.json

@@ -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,12 +363,13 @@
         "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.",
       "allowed_verbs": [
         "integrated",
         "containerized",
         "deployed",
-        "orchestrated"
+        "orchestrated",
+        "designed"
       ],
       "forbidden": [
         "trained the image classification model",
@@ -384,10 +385,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"
     },

resume_builder/reference/current_applications.md

@@ -32,9 +32,10 @@ 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/. |
 
 ## Current targeting notes