From a22c6ff59798772487dbf9d2f6c4e03d2396f8ad Mon Sep 17 00:00:00 2001 From: Dennis Thiessen Date: Mon, 27 Jul 2026 20:21:09 +0200 Subject: [PATCH] feat(resume): add Google Business Home application package --- ...gle_software_engineer_iii_business_home.md | 168 ++++++++++++++++++ ...re_engineer_iii_business_home_post_edit.md | 103 +++++++++++ ...ngineer_iii_business_home_cover_letter.tex | 47 +++++ ...neer_iii_business_home_cover_letter_v2.tex | 47 +++++ ...ware_engineer_iii_business_home_resume.tex | 78 ++++++++ ...e_engineer_iii_business_home_resume_v2.tex | 78 ++++++++ ...gle_software_engineer_iii_business_home.md | 44 +++++ output/Google_Business_Home/resume.cls | 59 ++++++ 8 files changed, 624 insertions(+) create mode 100644 output/Google_Business_Home/critique_google_software_engineer_iii_business_home.md create mode 100644 output/Google_Business_Home/critique_google_software_engineer_iii_business_home_post_edit.md create mode 100644 output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter.tex create mode 100644 output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter_v2.tex create mode 100644 output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume.tex create mode 100644 output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume_v2.tex create mode 100644 output/Google_Business_Home/jd_google_software_engineer_iii_business_home.md create mode 100644 output/Google_Business_Home/resume.cls diff --git a/output/Google_Business_Home/critique_google_software_engineer_iii_business_home.md b/output/Google_Business_Home/critique_google_software_engineer_iii_business_home.md new file mode 100644 index 0000000..10bbab0 --- /dev/null +++ b/output/Google_Business_Home/critique_google_software_engineer_iii_business_home.md @@ -0,0 +1,168 @@ +# Critique: Google — Software Engineer III, Business Home + +**Critique date:** 2026-07-27 +**JD source:** Verbatim Google Careers posting, req 93922217108087494 +**Package:** Two-page International Tech resume plus one-page optional cover letter + +## 1. Fit Verdict and Hard-Gate Audit + +**Verdict: CORE — PROCEED** +**Evidence Fit: 89/100** +**Hard gate: PASS** + +All minimum qualifications are Direct. The candidate has the required degrees, substantially exceeds the software-development tenure threshold, and currently designs, builds, migrates, maintains and operates production data-processing pipelines. + +The material weaknesses are preferred or competitive rather than gating: + +- No canonical evidence for two years of formal data-structures and algorithms work. +- No accessible-technology development evidence. +- Design-review and code-review responsibility are Adjacent rather than explicitly canonicalized. +- Current work is primarily enterprise data/platform engineering, not consumer or merchant-facing product SWE. +- The advertised Mid level is below the current Staff title. This is a motivation/retention question, not a capability gap. + +| Requirement | Type | Classification | Evidence | Gate | +|---|---|---|---|---| +| Bachelor's degree or equivalent | Minimum | Direct | EDU-BENG, EDU-MENG | PASS | +| Two years of software development, or one with advanced degree | Minimum | Direct | BS-2, FC-3, VZ-1, GN-3; employment history | PASS | +| Design, build and maintain large-scale data-processing pipelines | Minimum | Direct | SW-1, SW-2, SW-3, SW-6, SW-7 | PASS | +| Master's degree or PhD in related technical field | Preferred | Direct | EDU-MENG | — | +| Two years of data structures and algorithms | Preferred | Gap | No canonical evidence | — | +| Accessible-technology development | Preferred | Gap | No canonical evidence | — | +| Product or system development code | Responsibility | Direct | SW-3, BS-2, FC-3, VZ-1, GN-3 | — | +| Design reviews with peers and stakeholders | Responsibility | Adjacent | SW-4, BS-3 | — | +| Code review and engineering-quality feedback | Responsibility | Adjacent | SW-2, SW-3, VZ-2, GN-1 | — | +| Documentation and educational content | Responsibility | Direct | BS-3, GN-1 | — | +| Triage, debug and resolve production issues | Responsibility | Direct | SW-2, SW-4, BS-3 | — | +| English, Zürich location and Swiss work authorization | Constraint | Direct | Identity record and config | PASS | + +## 2. Evidence Fit Score + +| Dimension | Weight | Score | Assessment | +|---|---:|---:|---| +| Required qualifications | 35 | 35 | Every minimum is Direct. | +| Core responsibilities | 25 | 19 | Strong production code, pipeline, documentation and incident evidence; formal design/code-review evidence is only Adjacent. | +| Level and ownership | 15 | 13 | Ownership exceeds Mid level, but the title mismatch creates motivation and retention scrutiny. | +| Recency and depth | 10 | 10 | Strongest pipeline and Python/Kubernetes evidence is current. | +| Domain/tool transfer | 10 | 7 | Excellent data-intensive-system transfer; limited direct merchant/consumer product, accessibility and formal algorithms evidence. | +| Practical constraints | 5 | 5 | Bern-to-Zürich and Swiss authorization are workable; no sponsorship required. | +| **Evidence Fit** | **100** | **89** | **Core** | + +## 3. Document Quality Score + +| Dimension | Weight | Score | Assessment | +|---|---:|---:|---| +| Truth and provenance | 25 | 25 | Canonical validator passes. Ownership, migration, Data Mesh, ML and historical-language scopes are preserved. | +| Information hierarchy | 20 | 18 | Employer/title/date hierarchy is excellent. Six skills lines and the deliberate page break delay the deeper software evidence slightly. | +| Bullet evidence and impact | 20 | 18 | Bullets are specific and interviewable. The absence of verified quantitative outcomes limits impact, correctly rather than artificially. | +| Relevance and terminology | 15 | 13 | Strong pipeline, Python, systems, documentation and operations alignment. Direct review/full-stack evidence remains less visible. | +| Skills evidence | 10 | 9 | Every skill is evidence-backed; historical languages are labelled. REST/distributed-system recency and the unexpanded AI line may invite clarification. | +| Mechanics/readability | 10 | 9 | Clean two-page parse, conventional layout and no clipping. There is noticeable but acceptable whitespace on both pages. | +| **Document Quality** | **100** | **92** | **Pass** | + +Truth/provenance is above the automatic-failure threshold. There is no document-quality hard failure. + +## 4. Channel Strength + +**Channel Strength: WEAK** + +The current package is a tailored cold application. The cover letter does not strengthen the channel rating. Attempt one warm action before or immediately after submission: + +1. Credible Google employee referral, if available. +2. Targeted note to a Zürich Shopping/Commerce recruiter. +3. Concise outreach to a Business Home or Merchant Shopping engineer, focused on the direct data-pipeline match. + +## 5. Competitive Read + +**Obvious-fit competitor:** A current product SWE with three to six years of recent Java/Python development, strong algorithms interview readiness, routine design/code reviews, direct large-product or Google-scale experience, and merchant/consumer product exposure. + +**Dennis's real advantage:** Substantially stronger production accountability than many Mid-level candidates: current Component Owner duties, on-call incident responsibility, pipeline migration delivery, governed data products, SLO/application ownership and cross-stack enterprise experience. + +**Competitor's real advantage:** More legible current product-SWE identity, direct code-review/design-review evidence, formal algorithms readiness, accessibility exposure and possibly an internal channel. + +**Level comparison:** Dennis exceeds the nominal organizational level. The cover letter correctly frames the application as an intentional hands-on choice, but the recruiter may still test compensation, motivation and retention. + +### Reader Sequence + +1. **Parser/ATS — PASS.** Employer/title/date order extracts correctly. Python, software, data pipelines, distributed backends, microservices, CI/CD, production operation and relevant degrees are visible. +2. **Recruiter glance — FORWARD, with one concern.** The minimum pipeline qualification is unmistakable; the question is why a current Staff data engineer wants a Mid product-SWE role. +3. **Hiring manager — MAYBE.** Strong evidence for data-intensive systems, production ownership and debugging; weaker direct evidence for current full-stack product code, design reviews and code reviews. +4. **Technical reviewer — CREDIBLE, with an immediate challenge.** Expect algorithms/coding calibration plus requests for detailed examples of current code, design decisions, review practices and production debugging. + +## 6. Canonical Claim Audit + +| Material claim | Canonical evidence | Fit | Safe? | Fix | +|---|---|---|---|---| +| Software/data engineer; 10+ years professional delivery | Employment chronology; BS-2, FC-3, VZ-1, GN-3 | Direct | YES | None | +| 5+ years designing/building/operating production pipelines | SW-1/2/3/7, BS-2/3 | Direct | YES | None | +| Distributed-systems headline | VZ-1; SW-6; current pipeline/platform work | Adjacent/Direct | YES | Optionally replace with “Production Operations” if a more current signal is preferred | +| Python and SQL current; Java/C#/C++/JavaScript historical | Canonical skills registry | Direct | YES | None; recency is stated accurately | +| Kafka, Airflow, PySpark, AWS, CloudFormation, Kubernetes, Docker | Canonical skills; SW-1/2/3/6/7 | Direct | YES | None | +| Distributed backends, REST services and quality gates | VZ-1/2, FC-1/3, GN-1 | Direct historical | YES | Consider adding “historical” context to the systems line | +| Production inference integration | BS-1 | Direct historical | YES | None | +| LLM assistant configuration and LiteLLM API use | SW-8; canonical skills | Direct hands-on | YES | Keep bounded; do not imply production LLM ownership | +| Own Fulfillment ETL components | SW-2 | Direct | YES | None | +| Migrated Fulfillment/Product Analysis pipelines to Swisscom's AWS platform | SW-1 | Direct | YES | Scope is correct; wider programme contribution is explicit | +| Build Python applications on Kubernetes with GitLab CI/CD | SW-3 | Direct | YES | None | +| Build products within company-wide Data Mesh | SW-7 | Direct | YES | Correctly avoids claiming ownership of the shared mesh | +| Internal B2B stakeholder/product-owner delivery | SW-4 | Direct | YES | Correctly avoids external-customer framing | +| Bosch multi-language data services | BS-2 | Direct historical | YES | None | +| Bosch Application Owner, SLOs, vendors, training, documentation | BS-3 | Direct historical | YES | None | +| Bosch automated inference and reduced manual classification work | BS-1 | Direct historical | YES | Qualitative outcome is source-backed; no invented percentage | +| ELK/Kafka anomaly detection proof of concept | BS-4 | Direct bounded PoC | YES | PoC scope is explicit | +| Fraunhofer software, microservices and Jenkins | FC-1, FC-3 | Direct historical | YES | None | +| Vizrt distributed backend contribution and CI/CD tests | VZ-1, VZ-2 | Direct historical | YES | Contribution verb and customer scope are correct | +| Generali BDD technical responsibility and training | GN-1 | Direct historical | YES | None | +| Cover-letter Business Home hook | Verbatim Google JD | Direct company context | YES | None | +| Staff title but hands-on IC, applying deliberately | Canonical title plus user-approved motivation | Context | YES | Keep concise and non-defensive | +| Cover-letter Swisscom evidence | SW-1/2/4/7 and resume | Direct | YES | Safe, but can be condensed to reduce resume repetition | + +## 7. Fixes + +### Tier 1 — Truth/Fit + +**None.** No unsupported claim, forbidden pattern, failed validator check or hard-gate problem was found. + +Do not add algorithms, accessibility, code-review or design-review claims unless the underlying experience is first confirmed and added to the canonical KB. + +### Tier 2 — Presentation and Competitive Positioning + +1. **Reorder the first three Swisscom bullets for this SWE audience.** Lead with the AWS pipeline migration or Python/Kubernetes application delivery, then Component Owner operations. This makes “writes and builds systems” visible before governance/on-call accountability. +2. **Tighten the cover letter's evidence paragraph.** It currently repeats several resume bullets. Retain one pipeline/product example and spend the saved space on the deliberate hands-on motivation—the letter's unique value. +3. **Clarify systems-skill recency.** “Distributed backends” and “REST services” are valid but historical. A small context marker would prevent them being read as current daily work. +4. **Evidence-enrichment opportunity, not a prose fix:** if Dennis currently reviews merge requests, participates in design reviews or mentors engineers, capture that evidence in the KB before adding it. These are the most valuable missing responsibilities for this JD. + +## 8. Cover-Letter Critique + +**Decision: KEEP, with a concise edit recommended.** + +The posting and Google process make the letter optional. It is justified here because it addresses a real issue the resume cannot: why a current Staff engineer is intentionally applying to a Mid role. The Business Home hook is current, first-party and accurately paraphrased. + +What works: + +- Directly connects the role to data-intensive product engineering. +- Explicitly resolves the title/level motivation concern. +- Uses only canonical claims already present in the resume. +- Avoids generic praise, company-news paraphrase and defensive gap discussion. + +What to improve: + +- The middle paragraph repeats four Swisscom resume claims. Reduce it to one compact evidence chain. +- Keep the level explanation to two sentences so it reads confident rather than anticipatorily defensive. + +Deleting the letter would remove the only explicit answer to the level-mismatch question. A shorter version is preferable to omission. + +## 9. Mechanical Verification + +- Canonical validator: **PASS — 0 warnings** for resume and cover letter. +- Resume compilation: **PASS — 2 pages**. +- Cover-letter compilation: **PASS — 1 page**. +- Resume text extraction: **PASS**; name, professional identity, employer, title, dates, location and bullets parse in the intended order. +- Cover-letter text extraction: **PASS**. +- Visual inspection: **PASS**; no clipping, overlap, isolated headings or broken page elements. +- Contact information: **PASS** and consistent across documents. +- Certifications: Listed once. +- AI-fingerprint review: **PASS**; concrete evidence dominates, no inflated adjectives, no mechanical JD-order mirroring, and no suspicious unsupported terminology. + +## Recommendation + +The package is viable for submission on fit and truth. Apply the Tier-2 ordering and cover-letter compression before finalization because they sharpen the exact recruiter concern for this role without changing any evidence. diff --git a/output/Google_Business_Home/critique_google_software_engineer_iii_business_home_post_edit.md b/output/Google_Business_Home/critique_google_software_engineer_iii_business_home_post_edit.md new file mode 100644 index 0000000..4f8cf18 --- /dev/null +++ b/output/Google_Business_Home/critique_google_software_engineer_iii_business_home_post_edit.md @@ -0,0 +1,103 @@ +# Post-Edit Critique: Google — Software Engineer III, Business Home + +**Date:** 2026-07-27 +**Documents:** `resume_v2.tex` and `cover_letter_v2.tex` +**Scope:** Approved Tier-2 hierarchy, recency and cover-letter edits + +## 1. Fit Verdict and Hard Gate + +**Evidence Fit: 89/100 — Core** +**Hard gate: PASS** + +The edits do not change candidate-role fit. Every minimum qualification remains Direct. The outstanding competitive gaps remain preferred data structures/algorithms, accessibility, and non-canonicalized design/code-review evidence. + +| Dimension | Weight | Score | +|---|---:|---:| +| Required qualifications | 35 | 35 | +| Core responsibilities | 25 | 19 | +| Level and ownership | 15 | 13 | +| Recency and depth | 10 | 10 | +| Domain/tool transfer | 10 | 7 | +| Practical constraints | 5 | 5 | +| **Evidence Fit** | **100** | **89** | + +## 2. Document Quality + +| Dimension | Weight | Score | Post-edit assessment | +|---|---:|---:|---| +| Truth and provenance | 25 | 25 | No claim changed in substance; validator passes with zero warnings. | +| Information hierarchy | 20 | 19 | Swisscom now leads with pipeline construction and current Python/Kubernetes delivery before operations/governance. | +| Bullet evidence and impact | 20 | 18 | Specific, scoped and interviewable; no metrics were invented. | +| Relevance and terminology | 15 | 14 | Current software construction is now more legible for the SWE audience. | +| Skills evidence | 10 | 9 | The systems line now distinguishes current incident response from prior distributed/REST/quality-gate work. | +| Mechanics/readability | 10 | 9 | Clean two-page resume and one-page letter with correct parsing and no visual defects. | +| **Document Quality** | **100** | **94** | **Pass** | + +## 3. Channel Strength + +**Weak — unchanged.** + +The v2 package remains a cold application unless a referral, recruiter interaction or targeted hiring-team connection is added. Document edits cannot upgrade channel strength. + +## 4. Competitive and Reader Read + +- **Parser/ATS:** PASS. Current Python, production pipelines, AWS migration, Kubernetes delivery, software systems and historical languages extract correctly. +- **Recruiter:** FORWARD. The first Swisscom evidence now answers the role's build/maintain pipeline minimum faster. +- **Hiring manager:** MAYBE. Strong data-intensive system ownership; direct current full-stack, design-review and code-review evidence remains less explicit. +- **Technical reviewer:** CREDIBLE. First challenge remains algorithms/coding calibration and detailed examples of current design/review practices. + +The obvious-fit product SWE retains an advantage in current product-code, algorithms and review evidence. Dennis retains the advantage in end-to-end production accountability, incident ownership and substantial data-pipeline depth. + +## 5. Claim Audit + +All unchanged material claims from the first critique were rechecked and remain safe. The edited claims are: + +| Edited claim | Canonical evidence | Safe? | Assessment | +|---|---|---|---| +| Current incident response; prior distributed backend, REST microservice and quality-gate engineering | SW-2; VZ-1/2; FC-1/3; GN-1 | YES | Recency is now explicit and accurate. | +| AWS pipeline migration moved to first Swisscom bullet | SW-1 | YES | Wording and owned-domain scope are unchanged. | +| Python/Kubernetes delivery moved to second Swisscom bullet | SW-3 | YES | Current hands-on code/deployment evidence is more visible. | +| Component Owner operations moved to third Swisscom bullet | SW-2 | YES | Accountability remains prominent without leading the section. | +| Condensed cover-letter Swisscom evidence | SW-1/2/7 and resume v2 | YES | Retains one coherent build-and-operate evidence chain. | +| Shortened Staff-to-Mid motivation | Canonical title plus user-approved motivation | YES | Clearer and less defensive; no new employment claim. | + +## 6. Fixes + +### Tier 1 + +**None.** + +### Tier 2 + +**Approved edits are complete. No further document edit is necessary before finalization.** + +Evidence enrichment remains optional: only add current merge-request review, design-review or mentoring scope after user confirmation and canonical KB entry. + +## 7. Cover Letter + +**Decision: KEEP.** + +The v2 letter is more useful than the original: + +- It retains the verified Business Home motivation. +- It reduces resume repetition to one build-and-operate evidence chain. +- It explains the Staff-to-Mid application in two confident sentences. +- It remains fully supported by the resume and canonical claims. + +Deleting it would remove the only direct explanation of the level mismatch. + +## 8. Mechanical Verification + +- Canonical validator: **PASS — 0 warnings**. +- Resume: **2 pages**. +- Cover letter: **1 page**. +- Employer/title/date extraction: **PASS**. +- Contact information: **PASS**. +- Visual inspection: **PASS**; no clipping, overlap or broken page elements. +- Bullet count: **12**, unchanged. +- Certifications: listed once. +- AI-fingerprint review: **PASS**; wording remains concrete, scoped and non-generic. + +## Recommendation + +The v2 package is recommended for finalization on both fit and document quality. Channel Strength remains Weak until a warm action occurs. diff --git a/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter.tex b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter.tex new file mode 100644 index 0000000..dc7ef2e --- /dev/null +++ b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter.tex @@ -0,0 +1,47 @@ +\documentclass[11pt,a4paper]{article} +\usepackage[utf8]{inputenc} +\usepackage[T1]{fontenc} +\usepackage{lmodern} +\usepackage[a4paper,left=0.85in,right=0.85in,top=0.7in,bottom=0.7in]{geometry} +\usepackage{parskip} +\usepackage{xcolor} +\usepackage{hyperref} +\hypersetup{hidelinks} +\pagestyle{empty} +\setlength{\parindent}{0pt} + +\begin{document} + +{\Large\bfseries Dennis Thiessen, M.Eng.}\par +Bern, Switzerland $\vert$ +\href{mailto:dennis@thiessen.io}{dennis@thiessen.io} $\vert$ +41 795 955 585 $\vert$ +\href{https://linkedin.com/in/dennis-thiessen}{LinkedIn} + +\vspace{1.5em} +Google Hiring Team\\ +Google\\ +Z\"urich, Switzerland + +\vspace{1em} +27 July 2026 + +\vspace{1em} +\textbf{Application for Software Engineer III, Business Home} + +\vspace{0.8em} +Dear Google Hiring Team, + +I am applying for the Software Engineer III role because it combines hands-on software engineering with the data-intensive product work I have built my career around. Business Home's goal of aggregating performance data and turning it into useful recommendations for merchants connects directly with the problems I enjoy: building reliable systems that make complex operational data usable. + +At Swisscom, I own business-critical Fulfillment ETL components as Component Owner, covering production operation, data quality, governance, incident resolution and on-call obligations. I migrated the Fulfillment and Product Analysis domains' pipelines onto Swisscom's AWS platform, build governed data products and metadata within its shared Data Mesh, and partner with internal B2B product owners to translate questions into data products and analyses. This work keeps me close to production code as well as the reliability and usability of the resulting systems. + +My current title is Staff Data, Analytics \& AI Engineer, but I remain a hands-on individual contributor. The work I value most is writing and operating software, partnering with product owners, and being accountable for systems in production. I am therefore applying deliberately: the role's product-development and data-pipeline scope matters more to me than matching titles across organizations. + +I would welcome the opportunity to discuss how this experience could support the Business Home team. + +Kind regards, + +\vspace{1.5em} +Dennis Thiessen + +\end{document} diff --git a/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter_v2.tex b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter_v2.tex new file mode 100644 index 0000000..55feacc --- /dev/null +++ b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_cover_letter_v2.tex @@ -0,0 +1,47 @@ +\documentclass[11pt,a4paper]{article} +\usepackage[utf8]{inputenc} +\usepackage[T1]{fontenc} +\usepackage{lmodern} +\usepackage[a4paper,left=0.85in,right=0.85in,top=0.7in,bottom=0.7in]{geometry} +\usepackage{parskip} +\usepackage{xcolor} +\usepackage{hyperref} +\hypersetup{hidelinks} +\pagestyle{empty} +\setlength{\parindent}{0pt} + +\begin{document} + +{\Large\bfseries Dennis Thiessen, M.Eng.}\par +Bern, Switzerland $\vert$ +\href{mailto:dennis@thiessen.io}{dennis@thiessen.io} $\vert$ +41 795 955 585 $\vert$ +\href{https://linkedin.com/in/dennis-thiessen}{LinkedIn} + +\vspace{1.5em} +Google Hiring Team\\ +Google\\ +Z\"urich, Switzerland + +\vspace{1em} +27 July 2026 + +\vspace{1em} +\textbf{Application for Software Engineer III, Business Home} + +\vspace{0.8em} +Dear Google Hiring Team, + +I am applying for the Software Engineer III role because it combines hands-on software engineering with the data-intensive product work I have built my career around. Business Home's goal of aggregating performance data and turning it into useful recommendations for merchants connects directly with the problems I enjoy: building reliable systems that make complex operational data usable. + +At Swisscom, I migrated the Fulfillment and Product Analysis domains' pipelines onto the company's AWS platform and build governed data products within its shared Data Mesh. As Component Owner for business-critical Fulfillment ETL pipelines, I also remain accountable for production operation, data quality, incident resolution and on-call support. This combination of building systems and operating them keeps me focused on the reliability and usability of the resulting data products. + +My current title is Staff Data, Analytics \& AI Engineer, and I remain a hands-on individual contributor focused on writing and operating software. I am applying deliberately because the role's product-development and data-pipeline scope matters more to me than matching titles across organizations. + +I would welcome the opportunity to discuss how this experience could support the Business Home team. + +Kind regards, + +\vspace{1.5em} +Dennis Thiessen + +\end{document} diff --git a/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume.tex b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume.tex new file mode 100644 index 0000000..53e56ab --- /dev/null +++ b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume.tex @@ -0,0 +1,78 @@ +\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{Software \& Data Engineer $\vert$ Production Data Pipelines $\vert$ Python $\cdot$ Distributed Systems} +\contactline{Bern, Switzerland $\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} +Software and data engineer with 10+ years of professional delivery and 5+ years designing, building and operating production data pipelines. Currently owns business-critical Fulfillment ETL components at Swisscom and has delivered multi-language data services, distributed backends and containerized production applications. +\end{rSection} + +\begin{rSection}{Technical Skills} +\skillline{Languages}{Python, SQL; Java and C\# (professional, historical); C++ and JavaScript (limited historical use)} +\skillline{Data engineering}{Apache Kafka, Airflow, PySpark, ETL/ELT, Oracle, Teradata, Hadoop/Impala, data products and governance} +\skillline{Cloud and platform}{AWS (S3, Glue, Athena/Iceberg, Redshift), CloudFormation, Kubernetes, Docker, GitLab CI/CD} +\skillline{Software systems}{Distributed backends, microservices, REST services, automated testing, CI/CD quality gates, incident response} +\skillline{Applied AI/ML}{Production ML inference integration; domain-grounded LLM assistant configuration and LiteLLM API use} +\skillline{Certifications}{AWS Solutions Architect -- Associate; Data Engineering with AWS; iSAQB CPSA Foundation} +\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 Own business-critical Fulfillment ETL components as Component Owner, covering production operation, data quality, governance, incident resolution and on-call obligations across Oracle, Kafka, Python and Teradata processing. +\item Migrated Fulfillment and Product Analysis pipelines from Teradata and Oracle to Swisscom's AWS platform using S3, Glue, Athena/Iceberg, Redshift, Airflow and CloudFormation; contributed to the wider migration programme. +\item Build and operate Python data applications on Kubernetes with Docker and GitLab CI/CD, taking containerized services through testing, deployment and production support. +\item Model and build governed data products, onboard source systems and maintain metadata within Swisscom's company-wide Data Mesh on AWS, supporting discoverable access for analytics and AI use cases. +\item Partner with product owners and internal B2B stakeholders to translate questions into data products, analyses and dashboards; support automation and root-cause analysis for production issues. +\end{rSubsection} +\end{rSection} + +\newpage + +\begin{rSection}{Professional Experience (continued)} + +\begin{rSubsection}{Robert Bosch Semiconductor Manufacturing Dresden GmbH}{Feb 2020 -- Dec 2022}{Senior Engineer, Data Analysis (Data \& ML Engineering)}{Dresden, Germany} +\item Developed data services in Python, Java and C\# over Oracle and Hadoop/Impala for internal semiconductor analysis teams, supporting process analysis and quality monitoring. +\item Served as Application Owner for assigned analytics applications and upstream pipelines, defining SLOs, coordinating vendors, and providing documentation and user training for reliable 24/7 operations. +\item Integrated containerized ML inference using Docker, Kubernetes and Ansible into 24/7 semiconductor production, enabling automated image-based defect classification and reducing manual classification work. +\item Built and validated an ELK/Kafka anomaly-detection proof of concept with Grafana, Prometheus and Loki monitoring for semiconductor manufacturing systems. +\end{rSubsection} + +\begin{rSubsection}{Fraunhofer-Center for Maritime Logistics and Services CML}{Sep 2018 -- Oct 2019}{Research Software Engineer}{Hamburg, Germany} +\item Developed C\#/.NET scheduling software and containerized JavaScript/Express microservices; set up Jenkins CI/CD with quality gates for maritime research platforms. +\end{rSubsection} + +\begin{rSubsection}{Vizrt}{Jul 2017 -- May 2018}{Test Automation / DevOps Engineer}{Bergen, Norway} +\item Contributed Python and C++ engineering to a distributed video-transcoding backend; developed automated audio/video integration tests and connected quality gates to CI/CD. +\end{rSubsection} + +\begin{rSubsection}{Generali Deutschland Informatik Services GmbH}{May 2015 -- Jun 2017}{IT Consultant}{Hamburg, Germany} +\item Introduced BDD through a proof of concept, held technical responsibility for test automation and Jenkins jobs, and trained colleagues in the Java community. +\end{rSubsection} + +\end{rSection} + +\begin{rSection}{Education} +\compactentry{M.Eng. Computer Aided Engineering (Software Design \& Engineering), Universit\"at der Bundeswehr M\"unchen}{Apr 2012 -- Oct 2013} +Thesis at Tongji University, Shanghai: \textit{Development of a Web-Based Remote Fault Diagnosis System}; grade 1.0. + +\compactentry{B.Eng. Information and Telecommunication Technologies, Universit\"at der Bundeswehr M\"unchen}{Oct 2009 -- Oct 2012} +\end{rSection} + +\end{document} diff --git a/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume_v2.tex b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume_v2.tex new file mode 100644 index 0000000..912ca33 --- /dev/null +++ b/output/Google_Business_Home/e2e_google_software_engineer_iii_business_home_resume_v2.tex @@ -0,0 +1,78 @@ +\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{Software \& Data Engineer $\vert$ Production Data Pipelines $\vert$ Python $\cdot$ Distributed Systems} +\contactline{Bern, Switzerland $\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} +Software and data engineer with 10+ years of professional delivery and 5+ years designing, building and operating production data pipelines. Currently owns business-critical Fulfillment ETL components at Swisscom and has delivered multi-language data services, distributed backends and containerized production applications. +\end{rSection} + +\begin{rSection}{Technical Skills} +\skillline{Languages}{Python, SQL; Java and C\# (professional, historical); C++ and JavaScript (limited historical use)} +\skillline{Data engineering}{Apache Kafka, Airflow, PySpark, ETL/ELT, Oracle, Teradata, Hadoop/Impala, data products and governance} +\skillline{Cloud and platform}{AWS (S3, Glue, Athena/Iceberg, Redshift), CloudFormation, Kubernetes, Docker, GitLab CI/CD} +\skillline{Software systems}{Current production incident response; prior distributed backend, REST microservice, automated testing and CI/CD quality-gate engineering} +\skillline{Applied AI/ML}{Production ML inference integration; domain-grounded LLM assistant configuration and LiteLLM API use} +\skillline{Certifications}{AWS Solutions Architect -- Associate; Data Engineering with AWS; iSAQB CPSA Foundation} +\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 Migrated Fulfillment and Product Analysis pipelines from Teradata and Oracle to Swisscom's AWS platform using S3, Glue, Athena/Iceberg, Redshift, Airflow and CloudFormation; contributed to the wider migration programme. +\item Build and operate Python data applications on Kubernetes with Docker and GitLab CI/CD, taking containerized services through testing, deployment and production support. +\item Own business-critical Fulfillment ETL components as Component Owner, covering production operation, data quality, governance, incident resolution and on-call obligations across Oracle, Kafka, Python and Teradata processing. +\item Model and build governed data products, onboard source systems and maintain metadata within Swisscom's company-wide Data Mesh on AWS, supporting discoverable access for analytics and AI use cases. +\item Partner with product owners and internal B2B stakeholders to translate questions into data products, analyses and dashboards; support automation and root-cause analysis for production issues. +\end{rSubsection} +\end{rSection} + +\newpage + +\begin{rSection}{Professional Experience (continued)} + +\begin{rSubsection}{Robert Bosch Semiconductor Manufacturing Dresden GmbH}{Feb 2020 -- Dec 2022}{Senior Engineer, Data Analysis (Data \& ML Engineering)}{Dresden, Germany} +\item Developed data services in Python, Java and C\# over Oracle and Hadoop/Impala for internal semiconductor analysis teams, supporting process analysis and quality monitoring. +\item Served as Application Owner for assigned analytics applications and upstream pipelines, defining SLOs, coordinating vendors, and providing documentation and user training for reliable 24/7 operations. +\item Integrated containerized ML inference using Docker, Kubernetes and Ansible into 24/7 semiconductor production, enabling automated image-based defect classification and reducing manual classification work. +\item Built and validated an ELK/Kafka anomaly-detection proof of concept with Grafana, Prometheus and Loki monitoring for semiconductor manufacturing systems. +\end{rSubsection} + +\begin{rSubsection}{Fraunhofer-Center for Maritime Logistics and Services CML}{Sep 2018 -- Oct 2019}{Research Software Engineer}{Hamburg, Germany} +\item Developed C\#/.NET scheduling software and containerized JavaScript/Express microservices; set up Jenkins CI/CD with quality gates for maritime research platforms. +\end{rSubsection} + +\begin{rSubsection}{Vizrt}{Jul 2017 -- May 2018}{Test Automation / DevOps Engineer}{Bergen, Norway} +\item Contributed Python and C++ engineering to a distributed video-transcoding backend; developed automated audio/video integration tests and connected quality gates to CI/CD. +\end{rSubsection} + +\begin{rSubsection}{Generali Deutschland Informatik Services GmbH}{May 2015 -- Jun 2017}{IT Consultant}{Hamburg, Germany} +\item Introduced BDD through a proof of concept, held technical responsibility for test automation and Jenkins jobs, and trained colleagues in the Java community. +\end{rSubsection} + +\end{rSection} + +\begin{rSection}{Education} +\compactentry{M.Eng. Computer Aided Engineering (Software Design \& Engineering), Universit\"at der Bundeswehr M\"unchen}{Apr 2012 -- Oct 2013} +Thesis at Tongji University, Shanghai: \textit{Development of a Web-Based Remote Fault Diagnosis System}; grade 1.0. + +\compactentry{B.Eng. Information and Telecommunication Technologies, Universit\"at der Bundeswehr M\"unchen}{Oct 2009 -- Oct 2012} +\end{rSection} + +\end{document} diff --git a/output/Google_Business_Home/jd_google_software_engineer_iii_business_home.md b/output/Google_Business_Home/jd_google_software_engineer_iii_business_home.md new file mode 100644 index 0000000..dab6a2b --- /dev/null +++ b/output/Google_Business_Home/jd_google_software_engineer_iii_business_home.md @@ -0,0 +1,44 @@ +# Google — Software Engineer III, Business Home + +- Source: https://www.google.com/about/careers/applications/jobs/results/93922217108087494-software-engineer-iii/ +- Retrieved: 2026-07-27 +- Retrieval method: Google Careers visible posting body via web fetch +- Posting status: LIVE — Apply control visible +- Location: Zürich, Switzerland +- Level: Mid + +## Minimum qualifications: + +* Bachelor’s degree or equivalent practical experience. +* 2 years of experience with software development in one or more programming languages, or 1 year of experience with an advanced degree. +* Experience designing, building, and maintaining large-scale data processing pipelines. + +## Preferred qualifications: + +* Master's degree or PhD in Computer Science or related technical fields. +* 2 years of experience with data structures and algorithms. +* Experience developing accessible technologies. + +## 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 team is building Business Home, a centralized and intelligent hub designed to help Small and Medium Businesses succeed across Google (Search, Maps, YouTube, and Ads). The team empowers merchants to overcome "content paralysis" and operational anxiety by proactively generating AI-driven content, aggregating performance data, and providing highly tailored, actionable recommendations. + +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 + +* Write product or system development code. +* Participate in, or lead design reviews with peers and stakeholders to decide amongst available technologies. +* Review code developed by other developers and provide feedback to ensure best practices (e.g., style guidelines, checking code in, accuracy, testability, and efficiency). +* Contribute to existing documentation or educational content and adapt content based on product/program updates and user feedback. +* Triage product or system issues and debug/track/resolve by analyzing the sources of issues and the impact on hardware, network, or service operations and quality. + +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. diff --git a/output/Google_Business_Home/resume.cls b/output/Google_Business_Home/resume.cls new file mode 100644 index 0000000..eca6ba0 --- /dev/null +++ b/output/Google_Business_Home/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 +}