# Session: Google — Software Engineer III, Business Home

## JD Integrity
- File/source: `output/Google_Business_Home/jd_google_software_engineer_iii_business_home.md`; Google Careers req 93922217108087494
- Retrieval method and date: Visible Google Careers posting retrieved via web fetch, 2026-07-27
- Verbatim posting: YES — job-specific posting body
- Posting status: LIVE — Apply control visible on 2026-07-27

## Application Decision
- Audience profile: International Tech
- Evidence Fit: 89/100
- Fit class: Core
- Hard gate: PASS — all minimum qualifications are Direct
- Channel Strength: Weak
- Channel plan: Seek one credible Google referral or send a concise targeted note to a Zürich Shopping/Commerce recruiter or team member before or immediately after applying
- Cohort slot: Core 1/7 - submitted 2026-07-27; not proceeding 2026-07-28
- Decision: PROCEED

## Requirements
| # | Requirement | Required/preferred | Direct/Adjacent/Gap/Constraint | Canonical evidence | Gate? |
|---|---|---|---|---|---|
| 1 | Bachelor's degree or equivalent | Required | Direct | EDU-BENG, EDU-MENG | PASS |
| 2 | 2 years software development, or 1 year with advanced degree | Required | Direct | EDU-MENG; BS-2; FC-3; VZ-1; GN-3 | PASS |
| 3 | Design, build and maintain large-scale data-processing pipelines | Required | Direct | SW-1, SW-2, SW-6, SW-7 | PASS |
| 4 | Master's degree or PhD in a related technical field | Preferred | Direct | EDU-MENG | — |
| 5 | 2 years data structures and algorithms | Preferred | Gap | No canonical evidence | — |
| 6 | Accessible-technology development | Preferred | Gap | No canonical evidence | — |
| 7 | Product or system development code | Responsibility | Direct | SW-3, BS-2, FC-3, VZ-1, GN-3 | — |
| 8 | Design reviews with peers and stakeholders | Responsibility | Adjacent | SW-4, BS-3 | — |
| 9 | Code review and engineering-quality feedback | Responsibility | Adjacent | SW-2, SW-3, BS-3; formal review scope is not canonicalized | — |
| 10 | Documentation or educational content | Responsibility | Direct | BS-3, GN-1 | — |
| 11 | Triage, debug and resolve production issues | Responsibility | Direct | SW-2, BS-3 | — |
| 12 | Versatility across full-stack problems and leadership qualities | Role context | Adjacent | SW-2, SW-3, SW-4, BS-2, BS-3, FC-3 | — |
| 13 | English proficiency | Required company-wide | Direct | English fluent | PASS |
| 14 | Zürich work location and Swiss authorization | Constraint | Direct | Bern location; German/EU citizen; Swiss B permit; no sponsorship required | PASS |
| 15 | Mid-level role alignment | Constraint | Constraint | Current Staff title materially exceeds advertised Mid level; user selected role after this risk was stated | PASS |

## Competitive Read
- Obvious-fit candidate: Current Google/large-product SWE with recent Java/Python, formal algorithms practice, code-review depth and direct consumer or merchant-product experience.
- Dennis's advantage: Current ownership of business-critical data pipelines plus production operation, stakeholder translation and broad software-engineering history.
- Their advantage: Direct Google-scale product engineering, current algorithms interview readiness, accessibility exposure and established access to the hiring team.
- Level/scope comparison: Dennis exceeds the advertised Mid level organizationally; the risk is downlevel motivation and SWE interview calibration rather than insufficient production ownership.

## Framing Strategy
- Professional identity: Staff data and software engineer with production pipeline ownership and cross-stack delivery experience.
- Strongest proof points: Swisscom Fulfillment/Product Analysis pipelines and operation; Kubernetes/Python delivery; Bosch production data services, ML integration and Application Owner scope.
- Honest adjacent bridges: Enterprise data-product stakeholders to merchant-product stakeholders; production application ownership to Google product/system engineering.
- Explicit gaps: No canonical evidence for two years of formal data structures/algorithms work or accessible-technology development; no claim of Google-scale consumer-product engineering.
- User directives: Test the repaired evidence-first workflow on this selected role.

## Resume Plan
- Summary: Software and data engineer focused on production pipelines, Python and distributed systems
- Skills: Current, evidence-backed software/data stack with historical languages explicitly scoped
- Swisscom: AWS migration, Kubernetes/Python delivery, component ownership and governed data products
- Bosch: Production data services, ML-inference integration, application ownership and observability proof of concept
- Earlier experience: Compact software-engineering evidence from Fraunhofer, Vizrt and Generali
- Total bullets: 14
- Impact evidence still needed: None identified at fit gate; use no unverified metrics

## Cover Letter Decision
- YES/NO: YES
- Reason: The optional letter added a specific Business Home and merchant-product motivation bridge
- Information it adds beyond resume: Motivation for the mission and the bridge from enterprise production-data ownership to merchant-facing product engineering
- Verified hook sources: Google Careers posting saved in this folder

## Output Files
- Resume: `e2e_google_software_engineer_iii_business_home_resume_v2.tex` / `Dennis_Thiessen_Resume.pdf`
- Cover letter: `e2e_google_software_engineer_iii_business_home_cover_letter_v2.tex` / `Dennis_Thiessen_Cover_Letter.pdf`
- Critique: `critique_google_software_engineer_iii_business_home_post_edit.md`

## Critique Summary
- Evidence Fit: 89/100
- Hard gate: PASS
- Document Quality: 94/100
- Channel Strength: Weak
- Tier 1 fixes: None remaining; approved Tier 2 edits applied

## Status
- Fit gate: COMPLETE — Core, 89/100, hard gate PASS
- Resume: FINALIZED - approved v2, 2 pages
- Cover letter: FINALIZED - approved v2, 1 page
- Critique: COMPLETE - post-edit critique 94/100 Document Quality
- Application/outcome: CLOSED - NOT PROCEEDING 2026-07-28; submitted 2026-07-27; no interview
- Next: Record as a Core/cold-channel cohort rejection; do not infer a document failure from this single rapid outcome
