feat(applications): submit Microsoft ISE Senior SWE Zürich (2026-07-03)
Microsoft — Senior Software Engineer, Industry Solutions Engineering (ISE), Zürich, req 200040836. Applied 2026-07-03, ~7 days after posting. - Package: 2pp resume (18 bullets) + 1pp CL (299 words), critiqued to 85.8/100 (Pass 2). Same-day cycle: verbatim Eightfold JD fetch -> build -> critique 83.3 -> Tier 1+2 fixes -> 85.8 -> submit. - Fixes applied: "model evaluation" completes the JD's RQ triple verbatim; open-source stack labeled in skills; summary gains LLM + cross-functional, on-call bound to Component Owner (precision). - CL hooks all web-verified: ISE Engineering Fundamentals Playbook, SharePoint-permissions-to-RAG blog, USD 400M Swiss datacenter. - Logs 'applied' in job_scout decisions.json, flips the CLAUDE.md Active Sessions row to SENT, archives the JD under JDs/. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -143,8 +143,9 @@ _Update this section when starting/finishing a JD._
|
||||
|
||||
| Session | Status | Next Command |
|
||||
|---------|--------|-------------|
|
||||
| Microsoft — Senior SWE, Industry Solutions Engineering (ISE), Zürich (req 200040836) | **SENT 2026-07-03** (85.8/100 Pass 2; 2pp resume + 1pp CL; verbatim Eightfold JD; IC4 base CHF 146.2–245.9k; applied ~7 days after posting). Same-day build→critique→submit. Decisions.json logged as applied | Done — await response |
|
||||
| Kraken (Payward) — SRE, AI Agents (remote, CH-eligible) | **CLOSED — REJECTED 2026-06-17** (applied 2026-06-15 ~87.2/100, no interview). Honest gaps (NO Terraform/SRE-title/LangGraph) likely the filter; 4th Kraken req declined/rejected to date | Done |
|
||||
| Google — Senior Data Engineer (Merchant Data Science), Zürich/MV | **ADVANCED 2026-06-17 — invited to 30-min Google Hiring Assessment** (applied 2026-06-15, 85.5/100). Resume cleared recruiter screen. Next: complete the online assessment (likely SQL/coding + situational; confirm format from invite email). Still open at recruiter stage: clarify L4/L5 + comp clears 180k+ | Prep + complete assessment |
|
||||
| Google — Senior Data Engineer (Merchant Data Science), Zürich/MV | **PASSED HIRING ASSESSMENT 2026-06-20 — Recruiting reviewing candidacy for next steps** (applied 2026-06-15, 85.5/100; cleared recruiter screen + assessment). Pass valid 24 months for future Google reqs. Possible additional role-knowledge OA may follow. Next: await recruiter outreach for interview scheduling; clarify L4/L5 + comp clears 180k+ when recruiter re-engages | Await recruiter next-step; prep for recruiter/tech screen |
|
||||
| Snowflake — Sr SWE, Enterprise (Observe by Snowflake), Zürich | **SENT 2026-06-06** (~86/100; 2pp resume + 1pp CL; real Ashby JD; comp CHF 176–253k base; NO C++ gate). Tier 1+2 applied; Vizrt low-latency skipped per user. Best-fit role in the 2026-06 search | Done — await response |
|
||||
| Isovalent (Cisco) Sr Data Engineer, Observability | **CLOSED — role pulled** (live Cisco scrape 2026-06-02: not on board; Recruitee link dead). Package finalized ~86/100, SHELVED for reuse | Done — retarget PDFs to next live data-eng req (QuantCo/Grafana/Confluent) |
|
||||
| Google Zürich Sr SWE Infrastructure (Data Pipeline) | **CLOSED — DROPPED + DELETED 2026-06-02** (poor fit). Live JD = Core infra/systems SWE with **C++ as a MINIMUM qual**, off-thesis vs `user_positioning`. Output folder deleted (was built on a fabricated JD). | Done — do not reattempt this req |
|
||||
|
||||
@@ -0,0 +1,97 @@
|
||||
# Microsoft — Senior Software Engineer, Industry Solutions Engineering (ISE), Zürich
|
||||
# Source: https://jobs.careers.microsoft.com/global/en/job/200040836
|
||||
# Fetched 2026-07-03 via Eightfold PCSX API (apply.careers.microsoft.com), verbatim.
|
||||
|
||||
Overview
|
||||
Do you enjoy solving problems, writing software, and working with customers? Do you want to join a team where learning about new technology is part of our work every day? Then, come join us!
|
||||
|
||||
The Industry Solutions Engineering (ISE) team is a global engineering organization that works directly with customers looking to leverage the latest technologies to address their toughest challenges.
|
||||
|
||||
|
||||
|
||||
We work closely with our customers’ engineers to jointly develop code for cloud-based solutions that can accelerate their organization. We work in collaboration with Microsoft product teams, partners, and open-source communities to empower our customers to do more with the cloud. We develop solutions side-by-side with our customers through collaborative innovation to solve their challenges. This work involves the development of broadly applicable, high-impact solution patterns and open-source software assets that contribute to the Microsoft platform.
|
||||
|
||||
|
||||
|
||||
We are hiring a Senior Software Engineer with deep experience and expertise in designing and delivering solutions using modern software engineering practices and cloud technologies. You will be part of a cross-functional team of software engineers, data scientists, technical program managers, and designers who work side-by-side with high-impact and strategic customers and their engineers to build innovative solutions.
|
||||
|
||||
|
||||
|
||||
As part of our team, you will thrive in working with a variety of technologies, not just Microsoft technology. You will solve exciting business problems, contribute to open source, and collaborate with Microsoft product teams.
|
||||
|
||||
|
||||
|
||||
Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees, we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond.
|
||||
|
||||
Responsibilities
|
||||
- Collaborates with appropriate stakeholders to determine user requirements for a scenario.
|
||||
|
||||
- Drives identification of dependencies and the development of design documents for a product, application, service, or platform.
|
||||
|
||||
- Creates, implements, optimizes, debugs, refactors, and reuses code to establish and improve performance and maintainability, effectiveness, and return on investment (ROI).
|
||||
|
||||
- Leverages subject-matter expertise of product features and partners with appropriate stakeholders (e.g., project managers) to drive a workgroup's project plans, release plans, and work items.
|
||||
|
||||
- Acts as a Designated Responsible Individual (DRI) and guides other engineers by developing and following the playbook, working on call to monitor system/product/service for degradation, downtime, or interruptions, alerting stakeholders about status and initiates actions to restore system/product/service for simple and complex problems when appropriate.
|
||||
|
||||
- Proactively seeks new knowledge and adapts to new trends, technical solutions, and patterns that will improve the availability, reliability, efficiency, observability, and performance of products while also driving consistency in monitoring and operations at scale.
|
||||
|
||||
- Embodies our culture and values
|
||||
|
||||
Qualifications
|
||||
Required/Minimum Qualifications (RQs/MQs)
|
||||
|
||||
- Bachelor's degree in computer science, or related technical discipline AND 4+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python
|
||||
|
||||
- Familiarity with deploying and operating AI systems in production environments
|
||||
|
||||
- Experience building or integrating AI/ML or LLM-based solutions, prompt engineering, RAG
|
||||
|
||||
- Understanding of model evaluation, data quality, and performance monitoring
|
||||
|
||||
|
||||
|
||||
Additional or Preferred Qualifications (PQs)
|
||||
|
||||
- Bachelor's degree in computer science OR related technical field AND technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python
|
||||
|
||||
- German language would be beneficial
|
||||
|
||||
- Enjoy travel and are comfortable with travel up to 25%
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Our team prides itself on embracing a growth mindset, inspiring excellence, and encouraging everyone to share their unique viewpoints and be their authentic self. Join us and help create life-changing innovations that impact billions around the world!
|
||||
|
||||
|
||||
|
||||
At Microsoft, we are seeking people who have a passion for the positive impact technology can have on communities and for making a difference in the world. Within ISE, you will find a wide range of backgrounds, perspectives, personal and cultural experiences which are vital to our success with our customers. It’s an informal and flexible work environment, and you’ll be welcome to work in a way that best enables you to get your job done.
|
||||
|
||||
|
||||
|
||||
We invest in your health, wellness, and financial future by offering a competitive package including a wide range of benefits built around your personal needs and those close to you.
|
||||
|
||||
|
||||
|
||||
Benefits/perks listed below may vary depending on the nature of your employment with Microsoft and the country where you work.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#ISEngineering
|
||||
|
||||
#WSS
|
||||
|
||||
|
||||
|
||||
Software Engineering IC4 - The typical base pay range for this role across Switzerland is CHF 146,200.00 - CHF 245,900.00 per year. Certain roles may be eligible for benefits and other compensation.
|
||||
|
||||
Find additional benefits and pay information here:
|
||||
https://careers.microsoft.com/v2/global/en/corporate-pay/switzerland-corporate-pay.html
|
||||
|
||||
This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled.
|
||||
|
||||
Microsoft is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to age, ancestry, citizenship, color, family or medical care leave, gender identity or expression, genetic information, immigration status, marital status, medical condition, national origin, physical or mental disability, political affiliation, protected veteran or military status, race, ethnicity, religion, sex (including pregnancy), sexual orientation, or any other characteristic protected by applicable local laws, regulations and ordinances. If you need assistance with religious accommodations and/or a reasonable accommodation due to a disability during the application process, read more about requesting accommodations.
|
||||
@@ -145,5 +145,152 @@
|
||||
"decision": "rejected",
|
||||
"note": "Crypto-native + production-ML edge; remote CH-eligible. Honest gaps: no Terraform/SRE-title/LangGraph. | SENT 2026-06-15 (87.2/100). REJECTED 2026-06-17, no interview — honest infra/SRE gaps likely the filter.",
|
||||
"date": "2026-06-15"
|
||||
},
|
||||
"https://jobs.careers.microsoft.com/global/en/job/200040836": {
|
||||
"company": "Microsoft",
|
||||
"title": "Senior Software Engineer (ISE, Zürich)",
|
||||
"decision": "applied",
|
||||
"note": "TOP CANDIDATE 2026-07-03 run. ISE = MSFT forward-deployed org (ex-CSE): co-engineering with strategic customers. IC4, published base CHF 146.2-245.9k clears bar; German explicitly beneficial; travel up to 25%; AI/LLM reqs are integration-side (RAG, prompt eng, model monitoring) not model-building. Zürich hybrid from Bern. | SENT 2026-07-03 (resume+CL finalized, 85.8/100).",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://jobs.ruag.ch/offene-stellen/senior-devops-engineer-c5i/3b3093ab-badc-4e95-8166-0f6ee32c18d0": {
|
||||
"company": "RUAG (Thun/Bern)",
|
||||
"title": "Senior DevOps Engineer C5I",
|
||||
"decision": "shortlist",
|
||||
"note": "Bern-local WLB-exception tier. English-first (German a plus); Linux/Docker+K8s/Python/GitLab CI/Prometheus-Grafana-ELK = core DevOps lane; analytics-platform ops for Army Cyber Command (C5I, 260p unit, DevSecOps). No citizenship gate in JD (only criminal-record/debt excerpts) but verify clearance as German citizen. Comp likely lateral (market + 13th month) — local tier has relaxed bar. Contact: recruiting-c5i@ruag.ch.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/gitlab/jobs/8522408002": {
|
||||
"company": "GitLab",
|
||||
"title": "Forward Deployed Engineer - Germany (Staff)",
|
||||
"decision": "shortlist",
|
||||
"note": "Remote-CH eligible Staff FDE (Duo Agent Platform adoption, regulated/self-managed envs). CAUTION: JD body says 'strategic accounts in the APJ region' despite Germany title — clarify region/timezone with recruiter before tailoring. Gaps: Ruby/Go ideal, Terraform/Ansible/Helm expected (Kraken-style honest gap), GitLab-internals depth. Travel up to 50%.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/135155660865053382-staff-research-generative-ai-cloud-ai-research-coscientist?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Staff Research, Generative AI, Cloud AI Research, Co-Scientist",
|
||||
"decision": "skip",
|
||||
"note": "Research-scientist role (model-building at top lab) — off-positioning per user_positioning. Scout top-score is a false positive.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/489f8e7d-e887-46a1-b524-223c8b537523": {
|
||||
"company": "Kraken (Payward)",
|
||||
"title": "Senior Product Manager - Trading-as-a-service",
|
||||
"decision": "skip",
|
||||
"note": "PM role, not engineering.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/3096a5c6-a4fc-4b09-9953-aefd72d423f3": {
|
||||
"company": "Kraken (Payward)",
|
||||
"title": "Web and Brand Designer - Breakout Prop",
|
||||
"decision": "skip",
|
||||
"note": "Design role; noise match on crypto/trading keywords.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://databricks.com/company/careers/open-positions/job?gh_jid=8598430002": {
|
||||
"company": "Databricks",
|
||||
"title": "Senior Forward Deployed Engineer - Full stack",
|
||||
"decision": "skip",
|
||||
"note": "UK-anchored (London / Remote-UK), not CH-eligible.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://databricks.com/company/careers/open-positions/job?gh_jid=8574912002": {
|
||||
"company": "Databricks",
|
||||
"title": "Sr. Manager, AI Forward Deployed Engineering - EMEA",
|
||||
"decision": "skip",
|
||||
"note": "People-manager req, NL/UK-anchored.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/grafanalabs/jobs/6095341004": {
|
||||
"company": "Grafana Labs",
|
||||
"title": "Senior Field Engineer | Germany | Remote",
|
||||
"decision": "skip",
|
||||
"note": "Germany-fenced + Grafana geo-indexed comp below bar (prior finding job_scout_overscoring_findings).",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/grafanalabs/jobs/6103688004": {
|
||||
"company": "Grafana Labs",
|
||||
"title": "Staff Software Engineer - Databases SRE | Germany | Remote",
|
||||
"decision": "skip",
|
||||
"note": "Germany-fenced + below-bar geo-indexed comp; SRE-internals off-lane.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/grafanalabs/jobs/6105595004": {
|
||||
"company": "Grafana Labs",
|
||||
"title": "Staff Software Engineer - Identity and Access | Ireland | Remote",
|
||||
"decision": "skip",
|
||||
"note": "Ireland-only.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/gitlab/jobs/8522265002": {
|
||||
"company": "GitLab",
|
||||
"title": "Forward Deployed Engineer - UK",
|
||||
"decision": "skip",
|
||||
"note": "UK-only; the Germany req (8522408002) is the CH-eligible one.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://novartis.wd3.myworkdayjobs.com/job/Basel-City/Associate-Director--Solution-Architect-Innovation---Delivery_REQ-10081010-1": {
|
||||
"company": "Novartis",
|
||||
"title": "Associate Director, Solution Architect Innovation & Delivery",
|
||||
"decision": "skip",
|
||||
"note": "HARD GATE: minimum 5+ years life-sciences/pharma industry — he has none. Role is innovation-scouting advisory in biomedical research. SA-overscoring pattern again; comp band 122.5-227.5k moot.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://novartis.wd3.myworkdayjobs.com/job/Basel-City/Associate-Director-and-Senior-Principal--AI-Methods---AI-for-Research--AI4R-_REQ-10080934-1": {
|
||||
"company": "Novartis",
|
||||
"title": "Associate Director and Senior Principal, AI Methods, AI4R",
|
||||
"decision": "skip",
|
||||
"note": "AI-research-methods role — off-positioning (thin core-AI/ML).",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://job.bkw.com/offene-stellen/strategy-manager-alle/4592fedf-fd86-436c-91d2-f1d2752f8b90": {
|
||||
"company": "BKW (Bern)",
|
||||
"title": "Strategy Manager (alle)",
|
||||
"decision": "skip",
|
||||
"note": "Non-engineering; BKW lateral tier already declined once.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/ashby/c3c7125d-7883-4dff-a2bf-f5a55de4a364": {
|
||||
"company": "Ashby (via getro 'Coinbase Ventures')",
|
||||
"title": "Staff Software Engineer, Product Engineering, EU",
|
||||
"decision": "skip",
|
||||
"note": "Ashby-the-company again (getro alias trap, prior finding); stale posting (2025-11); product full-stack off-lane.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://careers.datadoghq.com/detail/4599148/?gh_jid=4599148": {
|
||||
"company": "Datadog",
|
||||
"title": "Senior Software Engineer - Backend",
|
||||
"decision": "skip",
|
||||
"note": "France/EMEA-anchored; CH employment not offered on this req.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://jobs.elastic.co/jobs?gh_jid=8002555&gh_jid=8002555": {
|
||||
"company": "Elastic",
|
||||
"title": "Principal Software Engineer I - Distributed Systems - Elasticsearch",
|
||||
"decision": "skip",
|
||||
"note": "Elasticsearch-core internals (distributed systems / search engine) — depth mismatch vs data-platform profile despite Java.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/112755499450933958-software-engineer-iii-aiml-google-cloud-automotive?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Software Engineer III, AI/ML, Google Cloud, Automotive",
|
||||
"decision": "skip",
|
||||
"note": "SWE III = L4/mid — level-down vs senior target; automotive AI/ML flavor. Assessment pass reserved for L5 reqs.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/106146979301466822-staff-software-engineer-security-internal-developer-platform?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Staff Software Engineer, Security, Internal Developer Platform",
|
||||
"decision": "skip",
|
||||
"note": "8y security-specialization minimum — hard gate.",
|
||||
"date": "2026-07-03"
|
||||
},
|
||||
"https://jobs.sbb.ch/v2/offene-stellen/sap-consultant-invoice-to-pay-m-w-d/45bf64e8-fd05-4364-8fc8-da7002dd50d5": {
|
||||
"company": "SBB",
|
||||
"title": "SAP Consultant Invoice-to-Pay",
|
||||
"decision": "skip",
|
||||
"note": "SAP consulting, off-lane.",
|
||||
"date": "2026-07-03"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,97 @@
|
||||
# Microsoft — Senior Software Engineer, Industry Solutions Engineering (ISE), Zürich
|
||||
# Source: https://jobs.careers.microsoft.com/global/en/job/200040836
|
||||
# Fetched 2026-07-03 via Eightfold PCSX API (apply.careers.microsoft.com), verbatim.
|
||||
|
||||
Overview
|
||||
Do you enjoy solving problems, writing software, and working with customers? Do you want to join a team where learning about new technology is part of our work every day? Then, come join us!
|
||||
|
||||
The Industry Solutions Engineering (ISE) team is a global engineering organization that works directly with customers looking to leverage the latest technologies to address their toughest challenges.
|
||||
|
||||
|
||||
|
||||
We work closely with our customers’ engineers to jointly develop code for cloud-based solutions that can accelerate their organization. We work in collaboration with Microsoft product teams, partners, and open-source communities to empower our customers to do more with the cloud. We develop solutions side-by-side with our customers through collaborative innovation to solve their challenges. This work involves the development of broadly applicable, high-impact solution patterns and open-source software assets that contribute to the Microsoft platform.
|
||||
|
||||
|
||||
|
||||
We are hiring a Senior Software Engineer with deep experience and expertise in designing and delivering solutions using modern software engineering practices and cloud technologies. You will be part of a cross-functional team of software engineers, data scientists, technical program managers, and designers who work side-by-side with high-impact and strategic customers and their engineers to build innovative solutions.
|
||||
|
||||
|
||||
|
||||
As part of our team, you will thrive in working with a variety of technologies, not just Microsoft technology. You will solve exciting business problems, contribute to open source, and collaborate with Microsoft product teams.
|
||||
|
||||
|
||||
|
||||
Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees, we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond.
|
||||
|
||||
Responsibilities
|
||||
- Collaborates with appropriate stakeholders to determine user requirements for a scenario.
|
||||
|
||||
- Drives identification of dependencies and the development of design documents for a product, application, service, or platform.
|
||||
|
||||
- Creates, implements, optimizes, debugs, refactors, and reuses code to establish and improve performance and maintainability, effectiveness, and return on investment (ROI).
|
||||
|
||||
- Leverages subject-matter expertise of product features and partners with appropriate stakeholders (e.g., project managers) to drive a workgroup's project plans, release plans, and work items.
|
||||
|
||||
- Acts as a Designated Responsible Individual (DRI) and guides other engineers by developing and following the playbook, working on call to monitor system/product/service for degradation, downtime, or interruptions, alerting stakeholders about status and initiates actions to restore system/product/service for simple and complex problems when appropriate.
|
||||
|
||||
- Proactively seeks new knowledge and adapts to new trends, technical solutions, and patterns that will improve the availability, reliability, efficiency, observability, and performance of products while also driving consistency in monitoring and operations at scale.
|
||||
|
||||
- Embodies our culture and values
|
||||
|
||||
Qualifications
|
||||
Required/Minimum Qualifications (RQs/MQs)
|
||||
|
||||
- Bachelor's degree in computer science, or related technical discipline AND 4+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python
|
||||
|
||||
- Familiarity with deploying and operating AI systems in production environments
|
||||
|
||||
- Experience building or integrating AI/ML or LLM-based solutions, prompt engineering, RAG
|
||||
|
||||
- Understanding of model evaluation, data quality, and performance monitoring
|
||||
|
||||
|
||||
|
||||
Additional or Preferred Qualifications (PQs)
|
||||
|
||||
- Bachelor's degree in computer science OR related technical field AND technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python
|
||||
|
||||
- German language would be beneficial
|
||||
|
||||
- Enjoy travel and are comfortable with travel up to 25%
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Our team prides itself on embracing a growth mindset, inspiring excellence, and encouraging everyone to share their unique viewpoints and be their authentic self. Join us and help create life-changing innovations that impact billions around the world!
|
||||
|
||||
|
||||
|
||||
At Microsoft, we are seeking people who have a passion for the positive impact technology can have on communities and for making a difference in the world. Within ISE, you will find a wide range of backgrounds, perspectives, personal and cultural experiences which are vital to our success with our customers. It’s an informal and flexible work environment, and you’ll be welcome to work in a way that best enables you to get your job done.
|
||||
|
||||
|
||||
|
||||
We invest in your health, wellness, and financial future by offering a competitive package including a wide range of benefits built around your personal needs and those close to you.
|
||||
|
||||
|
||||
|
||||
Benefits/perks listed below may vary depending on the nature of your employment with Microsoft and the country where you work.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#ISEngineering
|
||||
|
||||
#WSS
|
||||
|
||||
|
||||
|
||||
Software Engineering IC4 - The typical base pay range for this role across Switzerland is CHF 146,200.00 - CHF 245,900.00 per year. Certain roles may be eligible for benefits and other compensation.
|
||||
|
||||
Find additional benefits and pay information here:
|
||||
https://careers.microsoft.com/v2/global/en/corporate-pay/switzerland-corporate-pay.html
|
||||
|
||||
This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled.
|
||||
|
||||
Microsoft is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to age, ancestry, citizenship, color, family or medical care leave, gender identity or expression, genetic information, immigration status, marital status, medical condition, national origin, physical or mental disability, political affiliation, protected veteran or military status, race, ethnicity, religion, sex (including pregnancy), sexual orientation, or any other characteristic protected by applicable local laws, regulations and ordinances. If you need assistance with religious accommodations and/or a reasonable accommodation due to a disability during the application process, read more about requesting accommodations.
|
||||
@@ -0,0 +1,288 @@
|
||||
# Critique: Microsoft — Senior Software Engineer, Industry Solutions Engineering (ISE), Zürich (req 200040836)
|
||||
|
||||
**Resume File:** `output/Microsoft_ISE_Senior_SWE/e2e_microsoft_ise_resume.tex` (2 pages, compiled clean)
|
||||
**Cover Letter File:** `output/Microsoft_ISE_Senior_SWE/e2e_microsoft_ise_cover_letter.tex` (1 page, 299 words)
|
||||
**JD:** `output/Microsoft_ISE_Senior_SWE/JD_microsoft_ise.txt` — verbatim live fetch 2026-07-03 via Eightfold PCSX API (JD integrity: PASS)
|
||||
**Date:** 2026-07-03 · **Pass:** 2 (lens reused from Pass 1 — do not rebuild)
|
||||
|
||||
---
|
||||
|
||||
## Changes Since Pass 1 (applied 2026-07-03, user-directed)
|
||||
|
||||
Resume only — CL untouched (passed all checks in Pass 1). Compile verified: 2 pages, summary 5 lines (no orphan), all skills lines single-line, page break identical to baseline.
|
||||
|
||||
1. **T1-1:** AI & ML in Production line now reads "…MLOps, model evaluation, data-quality & performance monitoring" — JD's RQ triple complete verbatim.
|
||||
2. **T1-2:** Software & Data Engineering line 3 now reads "Open-source stack: Apache Kafka, Apache Airflow, PySpark / Spark, Hadoop/Impala; batch & streaming" ("ingestion" dropped for line fit; no contribution claim made).
|
||||
3. **T2-1/2/3 (single summary rewrite):** "…for agentic AI and LLM workloads, run Python services on Kubernetes, and carry on-call duty as Component Owner." — adds LLM to the recruiter window and binds on-call to the Component Owner role (precision fix); "I work embedded in cross-functional customer and stakeholder teams." — adds the JD's pod descriptor. Tail clause "platform co-ownership, workshops, training" removed to hold the 5-line budget; that signal remains verbatim in BS-3 ("Co-owned the TIBCO Spotfire analytics platform… training engineering users") and GN-1.
|
||||
4. **T2-4 (conditional metric): NOT applied** — KB check of `experience_bosch.md` / `experience_swisscom.md` found no verified quantitative metric for BS-1/SW-1 beyond 24/7 and 300mm (already used). Adding one would violate anti-fabrication.
|
||||
|
||||
### Re-scored dimensions (others unchanged)
|
||||
| Dimension | Pass 1 | Pass 2 | Why |
|
||||
|---|---|---|---|
|
||||
| ATS Keywords (15%) | 8.0 | 9.0 | 20/20 — "model evaluation", "open source", "cross-functional" all present; remaining items semantic-only by nature |
|
||||
| Summary (10%) | 8.5 | 9.0 | LLM in the 10-second window, cross-functional added, on-call claim probe-proofed |
|
||||
| Skills (10%) | 8.5 | 9.0 | RQ vocabulary complete, open-source identity named, still zero fabrications |
|
||||
|
||||
**Score trajectory: 83.3 → 85.8/100.** At/above the 85+ submit band; theoretical max ~86.5 (residual: no hard metrics in KB, page-2 fill exception). Hard ceiling ~88 unchanged (Azure, OSS contributions — not resume-editable).
|
||||
|
||||
**Interview likelihood (updated):** ATS 95% · Recruiter 80% · HR 80% (RQ triple now checkbox-verbatim) · HM 65% (open-source affinity + model-eval line remove two objections) · Panel 70% (unchanged — depth questions remain; bridge points in Part 6 cover them).
|
||||
|
||||
---
|
||||
|
||||
## Part 1: Domain-Specialist Lens
|
||||
|
||||
### Reviewer Persona
|
||||
ISE engineering manager or principal SWE in EMEA running the hiring-manager screen for a Zürich IC4 req. Daily work: scoping customer engagements, unblocking cross-functional pods (SWE + DS + TPM + design), reviewing code on customer repos in whatever stack the customer runs. Has read 50+ CVs for this posting. Eye-rolls at: buzzword AI claims with no operational substance ("passionate about GenAI"), tool soup, solo-hero claims over org-scale systems, consultants who architect but don't code. Genuinely impressed by: production evidence under real constraints, breadth across stacks ("not just Microsoft" is in their own JD), customer-embedded engineering, scope-honest claims, and — for this specific req — German + already-in-Switzerland (no visa, no relocation).
|
||||
|
||||
### Company Context
|
||||
ISE is Microsoft's global non-billing co-engineering org inside MCAPS: engineers write production code side-by-side with strategic customers' engineers, then feed patterns back into Microsoft products and open source. Their public Engineering Fundamentals Playbook codifies the working style (code-with, testing, observability, agile ceremonies). Zürich req + "German beneficial" → Swiss/DACH strategic accounts (banks, pharma, industrials). Strategic backdrop: USD 400M Swiss datacenter expansion (June 2025) with in-country data residency — regulated Swiss enterprises are the customer base. Recent ISE publication themes: enterprise RAG with document-permission propagation (Entra ID → AI Search), coordinator-based multi-agent architectures, vector/hybrid search evaluation.
|
||||
|
||||
### JD Vocabulary Extraction (top 10, ranked)
|
||||
| # | JD Term | Freq/Placement | Meaning at ISE | Resume Match? |
|
||||
|---|---|---|---|---|
|
||||
| 1 | deploying and operating AI systems in production | RQ line | Not research demos — AI running for real customers, operated | SEMANTIC (ML inference in 24/7 fab; "Production AI Foundations" headline) |
|
||||
| 2 | LLM-based solutions, prompt engineering, RAG | RQ line | Hands-on LLM integration in enterprise settings | YES verbatim (LLM, RAG, prompt engineering in skills) |
|
||||
| 3 | model evaluation, data quality, performance monitoring | RQ line | Can you tell if the AI solution works and keeps working | PARTIAL — data quality + performance monitoring YES; **model evaluation ABSENT** |
|
||||
| 4 | modern software engineering practices | Overview + RQ | Playbook fundamentals: CI/CD, code review, testing, design docs | SEMANTIC (CI/CD, code review, TDD, quality gates) |
|
||||
| 5 | cloud technologies / cloud-based solutions | 4× | Azure-centric but explicitly polyglot org | YES (AWS named honestly, cloud-native) |
|
||||
| 6 | DRI, on call, monitor/restore, playbook | Responsibilities | Production ownership culture | SEMANTIC-STRONG ("on-call SLA", "incident response and restoration") |
|
||||
| 7 | cross-functional team (SWE + DS + TPM + designers) | Overview | Pod structure of every engagement | **NO verbatim** (semantic: stakeholder/product-owner partnering) |
|
||||
| 8 | open source | 3× | Contribution + "not just Microsoft" identity | **NO** (stack is open-source but never named as such) |
|
||||
| 9 | C, C++, C#, Java, JavaScript, Python | RQ + PQ | Polyglot flexibility, meet customers in their language | YES — 5 of 6 named |
|
||||
| 10 | observability, availability, reliability | Responsibilities | Operations-at-scale mindset | YES verbatim (skills group name) |
|
||||
|
||||
### Domain Vocabulary Map
|
||||
| Resume Currently Says | Should Say for This JD | Why |
|
||||
|---|---|---|
|
||||
| data-quality & performance monitoring | model evaluation, data-quality & performance monitoring | Completes the JD's RQ triple verbatim; backed by IBM AI Engineering cert + operating a production classifier |
|
||||
| Apache Kafka, Apache Airflow, … (unlabeled) | Open-source data stack: Kafka, Airflow, Spark… | JD says "open source" 3×; his stack IS open source — free honest keyword + "not just Microsoft" culture signal |
|
||||
| customer and stakeholder teams | cross-functional customer and stakeholder teams | JD's pod descriptor; true of his PO/analyst/domain-team work |
|
||||
| agentic AI workloads (summary) | agentic AI / LLM workloads | Puts "LLM" in the recruiter's 10-second window, not just skills |
|
||||
|
||||
### Gap Ranking
|
||||
- **Fatal:** none. Every RQ line is covered or truthfully bridgeable.
|
||||
- **Serious:** (1) "model evaluation" — RQ-line term, currently absent (bridgeable: JD asks only *understanding*); (2) Azure — competitors are Azure-native; resume/CL handle it honestly (AWS named, transfer argued) but it remains a real gap; (3) open-source *contributions* — JD says "contribute to open source"; he has none notable (cannot claim — only the stack can be named); (4) LLM depth is integration-side (LiteLLM APIs, custom GPTs), not solution-building — hedged correctly, but Azure-OpenAI-native candidates will out-depth him here.
|
||||
- **Cosmetic:** "design documents", "growth mindset", JavaScript depth, C.
|
||||
|
||||
### Methodology Transfer Test (top 5 achievements)
|
||||
| Achievement | How the ISE reviewer sees it |
|
||||
|---|---|
|
||||
| SW-7 governed data products for agentic AI | "He already solves the governed-grounding problem our enterprise-RAG engagements hit — permission-aware, metadata-managed data feeding LLM retrieval." ✓ natural |
|
||||
| BS-1 ML inference into 24/7 fab | "Deploying and operating AI in production under constraints harsher than most customer sites — no maintenance windows, yield on the line." ✓ natural — flagship |
|
||||
| SW-2 Component Owner, on-call ETL | "That's our DRI model: accountable, on call, restores service." ✓ natural |
|
||||
| BS-3 Spotfire platform co-ownership + training users | "Customer-facing platform engineering — internal customers, but the code-with muscle is there." ✓ natural |
|
||||
| SW-1 AWS migration of his domains' ETL | "Cloud migration delivery — wrong cloud for us, right shape of work; concepts transfer." ✓ with the honest-AWS framing doing the bridging |
|
||||
|
||||
All five transfer sentences write naturally — the reframing has landed. No bullet requires the reader to do the translation themselves.
|
||||
|
||||
### Competitive Landscape
|
||||
- **Obvious fit:** Azure-native senior SWE from a consultancy (Avanade/Accenture) or ex-product-team Microsoft engineer with OSS visibility and Azure OpenAI project work.
|
||||
- **Dennis's edge:** genuine enterprise data-platform depth (the *foundation* layer of every AI engagement), regulated-industry scars (telecom, insurance, semiconductor), production ML under 24/7 constraints, native German for DACH accounts, Bern-resident EU citizen (zero visa/relocation friction), cross-industry ramp record that mirrors ISE's engagement model.
|
||||
- **Their edge:** Azure service fluency, LLM solution-building portfolios, public OSS contributions.
|
||||
|
||||
---
|
||||
|
||||
## Part 2: Five-Perspective Read-Through
|
||||
|
||||
### ATS Robot (keyword scan)
|
||||
| # | Keyword | Match |
|
||||
|---|---|---|
|
||||
| 1 | Python | YES verbatim (bold, multiple) |
|
||||
| 2 | Java | YES verbatim |
|
||||
| 3 | C# | YES verbatim |
|
||||
| 4 | C++ | YES verbatim |
|
||||
| 5 | JavaScript | YES verbatim |
|
||||
| 6 | AI systems in production | SEMANTIC (ML inference deployment; Production AI Foundations) |
|
||||
| 7 | LLM | YES verbatim |
|
||||
| 8 | RAG | YES verbatim |
|
||||
| 9 | prompt engineering | YES verbatim |
|
||||
| 10 | model evaluation | **NO** |
|
||||
| 11 | data quality | YES verbatim |
|
||||
| 12 | performance monitoring | YES verbatim |
|
||||
| 13 | cloud | YES verbatim |
|
||||
| 14 | modern software engineering practices | SEMANTIC (CI/CD, code review, TDD) |
|
||||
| 15 | DRI / on-call / restore | SEMANTIC-STRONG (on-call SLA, incident response and restoration) |
|
||||
| 16 | observability | YES verbatim (group name) |
|
||||
| 17 | open source | **NO** |
|
||||
| 18 | cross-functional | **NO** |
|
||||
| 19 | stakeholders | YES verbatim |
|
||||
| 20 | German | YES verbatim |
|
||||
|
||||
**Match rate: 17/20 = 85% — PASS.** Top 3 truthfully addable: model evaluation (RQ line), open source (3× in JD), cross-functional (pod descriptor).
|
||||
|
||||
### Recruiter Glance (10 seconds)
|
||||
**Verdict: FORWARD (~80%).** "Staff Data & AI Engineer" at Swisscom + tagline with Python/Java/AWS/Kubernetes + "Production AI Foundations & Co-Engineering" + Bern/German-citizen/Zürich-ready/travel-ready line answers every logistics question a Swiss recruiter has before they've read a bullet. Summary's first two lines land data products + AWS + agentic AI. Non-technical reader still understands what he does. Only soft spot: "Co-Engineering" is ISE-insider vocabulary that a generic recruiter may skim past — but this req's recruiter knows the org's own word.
|
||||
|
||||
### HR Screen (30 seconds)
|
||||
**Verdict: PHONE SCREEN (~75%).** Degree ✓ (M.Eng., thesis 1.0), 4+ years coding ✓ (11+), languages of the JD list visibly present ✓, AI-in-production familiarity visible in both summary and a dedicated "AI & ML in Production" skills group ✓, German ✓, travel ✓. First bullet per position is the strongest JD-relevant one in each block (SW-7 grounding for agentic AI; BS-1 production ML; FC-2 applied ML; VZ-1 scale; GN-1 ownership/training). The one RQ term a checklist-reader can't tick verbatim: "model evaluation."
|
||||
|
||||
### Hiring Manager (2 minutes)
|
||||
**Verdict: INTERVIEW (~60%).**
|
||||
**Top 3 observations:**
|
||||
1. The Bosch bullet is the credibility anchor — "deploying and operating AI systems in production" answered with a 24/7 wafer fab, which is harsher than most customer environments they scope.
|
||||
2. The Swisscom story maps onto their current engagement portfolio (governed data → enterprise RAG grounding), and the claims are scope-honest ("within Swisscom's company-wide Data Mesh", "my domains' ETL stack") — no solo-hero smell.
|
||||
3. The gap they'll price in: AWS not Azure, and LLM work that is integration-grade rather than solution-building-grade. The honest framing earns trust but doesn't erase the gap against Azure-native applicants.
|
||||
**Predicted first interview question:** "Your cloud depth is AWS — walk me through how you'd ramp onto Azure in the first weeks of a customer engagement."
|
||||
|
||||
### Technical Reviewer (10 minutes)
|
||||
**Truthfulness: PASS — all claims verified.**
|
||||
| Claim | Verified? | Source |
|
||||
|---|---|---|
|
||||
| Governed data products within company-wide Data Mesh (scoped) | ✓ | memory: swisscom_datamesh_ownership — verb/object scoped exactly as mandated |
|
||||
| ML inference into 24/7 fab, 300mm lines | ✓ | BS-1, bundle flagship |
|
||||
| Spotfire platform co-owned, Application Owner | ✓ | memory: taf_2022_spotfire ("co-owned" hedge correct) |
|
||||
| TAF 2022 co-presentation (CL only) | ✓ | memory-verified; correctly reserved for CL |
|
||||
| LiteLLM, custom GPTs, Copilot, Kiro; **no LangChain** | ✓ | config ban respected — verified toolchain only |
|
||||
| "Contributed" ML/NLP to ARTUS | ✓ | hedged verb as mandated |
|
||||
| Component Owner on-call, incident response | ✓ | his components only — scope-disciplined |
|
||||
| 11+ years | ✓ | May 2015 → present = 11.2 yrs (accurate; session file's "12+" was the estimate, resume is the corrected figure) |
|
||||
| AWS SAA active to Sep 2027; no Azure claim anywhere | ✓ | config + honest-AWS strategy |
|
||||
| Security Champion excluded | ✓ | forced exclusion honored (JD has no security gate) |
|
||||
| Capgemini absent, Generali = Hamburg, education dates/overlap | ✓ | memory corrections all honored |
|
||||
|
||||
**Consistency: 1 minor precision note.** Summary clause "run Python services on Kubernetes under on-call SLA" fuses two true facts (SW-3: operates Python apps on K8s; SW-2: on-call SLA as Component Owner for the Fulfillment ETL). A probing interviewer asking "what's the SLA on your K8s services?" gets an answer about the ETL pipelines instead. Defensible but worth a comma's worth of precision — Tier 2.
|
||||
**Over-saturation:** none. Highest-frequency terms: Python (~10 incl. skills — acceptable as the JD's lead language), AWS (~7), Kubernetes (~5). No term past the concern threshold in bullet prose.
|
||||
|
||||
---
|
||||
|
||||
## Part 3: Eight-Dimension Scoring
|
||||
|
||||
| Dimension | Score | Weight | Weighted | Notes |
|
||||
|---|---|---|---|---|
|
||||
| ATS Keywords | 8.0/10 | 15% | 1.20 | 85% match; misses "model evaluation" (RQ line), "open source" (3×), "cross-functional" — all truthfully addable |
|
||||
| Summary | 8.5/10 | 10% | 0.85 | Strong bridge (data products → AI foundation → customer-embedded); "LLM" absent from recruiter window; one precision nit |
|
||||
| Skills Section | 8.5/10 | 10% | 0.85 | Group names are domain-perfect ("AI & ML in Production", "Observability & Engineering Quality"); verified GenAI toolchain, zero fabrications |
|
||||
| Bullet Quality | 8.5/10 | 25% | 2.13 | 18 bullets, all char-clean, scope-disciplined, every top bullet passes the transfer test; light quantification is a KB limit, not a craft failure |
|
||||
| Publications / Credentials | 8.0/10 | 10% | 0.80 | No pubs (industry resume) — certs carry it: AWS SAA active, Udacity 2026 (fresh), IBM AI Engineering (props up model-eval claim), thesis 1.0 |
|
||||
| Narrative Coherence | 9.0/10 | 15% | 1.35 | The cross-industry arc IS the ISE pitch; headline → summary → position headers tell one uninterrupted story |
|
||||
| Page Fill & Visual | 7.0/10 | 5% | 0.35 | 2pp clean, no orphans; page 2 ends ~2/3 down — exceeds ≤3-line rule, documented as unavoidable without KB-unsupported padding (sent Google baseline had the same and cleared screens) |
|
||||
| Credibility Signals | 8.0/10 | 10% | 0.80 | CNN/BBC/Al Jazeera, 300mm fab, Component/Application Owner titles, AWS cert; no OSS/pubs, few hard metrics |
|
||||
| **Total** | | **100%** | **83.3** | |
|
||||
|
||||
**Score: 83.3/100** — Strong (80–84 band): 1–2 targeted improvements push toward ceiling.
|
||||
|
||||
---
|
||||
|
||||
## Part 4: Interview Likelihood
|
||||
|
||||
| Reader | Probability | Key Factor |
|
||||
|--------|------------|------------|
|
||||
| ATS | 90% PASS | 85% keyword rate; all languages verbatim |
|
||||
| Recruiter (10s) | 80% forward | Staff title + Zürich-ready/German/travel logistics line |
|
||||
| HR (30s) | 75% phone screen | Every RQ checkable except "model evaluation" verbatim |
|
||||
| Hiring Manager (2m) | 60% interview | Bosch 24/7 production-AI anchor + zero-friction Swiss hire vs. Azure-native competition |
|
||||
| Technical Panel (10m) | 70% yes | Claims will survive probing; model-eval/LLM-building depth is the soft spot |
|
||||
|
||||
**Ceiling analysis:**
|
||||
| Scenario | Score |
|
||||
|---|---|
|
||||
| Current | 83.3 |
|
||||
| + Tier 1 applied | ~85.3 |
|
||||
| Theoretical max (this candidate + this JD) | ~86.5 |
|
||||
| Hard ceiling (structural: Azure, OSS contributions, LLM solution-building) | ~88 |
|
||||
| What would close the rest | An Azure cert (AZ-104/AZ-305) or one public OSS contribution — not resume-editable today |
|
||||
|
||||
---
|
||||
|
||||
## Part 5: Actionable Improvements
|
||||
|
||||
### Tier 1 (HIGH — do these)
|
||||
1. **Add "model evaluation" to the AI & ML in Production skills line.** (+1.0)
|
||||
- Current: `\skilldash{\textbf{ML} inference deployment (Docker/Kubernetes), MLOps, data-quality \& performance monitoring}`
|
||||
- Proposed: `\skilldash{\textbf{ML} inference deployment (Docker/Kubernetes), MLOps, model evaluation, data-quality \& performance monitoring}`
|
||||
- Why: completes the JD's RQ triple ("model evaluation, data quality, and performance monitoring") verbatim. Truthful at the JD's own bar — it asks for *understanding*, backed by IBM AI Engineering Specialization (model building/eval coursework), operating an image classifier in production at Bosch, and thesis NN work. ~108 rendered chars — stays 1 line.
|
||||
2. **Name the open-source stack.** (+1.0)
|
||||
- Current (Software & Data Engineering, line 3): `\skilldash{\textbf{Apache Kafka}, \textbf{Apache Airflow}, batch \& streaming ingestion, \textbf{PySpark} / Spark, Hadoop/Impala}`
|
||||
- Proposed: `\skilldash{Open-source data stack: \textbf{Apache Kafka}, \textbf{Apache Airflow}, \textbf{PySpark} / Spark, Hadoop/Impala; batch \& streaming}`
|
||||
- Why: JD says "open source" 3× and "variety of technologies, not just Microsoft" is ISE identity. He cannot claim contributions (session tripwire — correctly not claimed), but the stack he runs *is* open source; naming it is a free, honest ATS + culture hit. Verify char count with char_count.py after edit.
|
||||
|
||||
### Tier 2 (MEDIUM — optional)
|
||||
1. **"cross-functional" in the summary.** "I work embedded with customer and stakeholder teams" → "I work embedded in cross-functional customer and stakeholder teams" (+0.5; check summary stays 5 lines).
|
||||
2. **Summary precision on on-call clause.** "…and run Python services on Kubernetes under on-call SLA" → "…run Python services on Kubernetes, and hold on-call responsibility as Component Owner" (+0.4 probe-proofing; the current phrasing binds the SLA to the K8s services, which the KB doesn't strictly support).
|
||||
3. **"LLM" into the summary's agentic clause.** "data foundation for agentic AI workloads" → "data foundation for agentic AI and LLM workloads" (+0.3 recruiter-window reinforcement).
|
||||
4. **Conditional:** if `experience_bosch.md` or `experience_swisscom.md` holds a verified metric (throughput, latency, cost, team count) for BS-1 or SW-1, add it (+0.5). Do NOT invent one.
|
||||
|
||||
### Tier 3 (COSMETIC — skip)
|
||||
1. Page-2 bottom whitespace (~1/3 page) — accepted limitation; padding would violate anti-fabrication.
|
||||
2. "design documents" / "growth mindset" keyword stuffing — reads as pandering.
|
||||
3. CL section "Certifications & Awards" contains only certifications — standard template heading, leave.
|
||||
|
||||
**Verdict: Apply Tier 1 (both edits, ~5 minutes via /edit-resume). Tier 2 items 1–3 are cheap and worth taking in the same pass. Tier 3 skip.**
|
||||
|
||||
---
|
||||
|
||||
## Part 6: Interview Bridge Points
|
||||
|
||||
| Resume Topic | ISE Equivalent | Opening Line |
|
||||
|---|---|---|
|
||||
| SW-7 governed data products for agentic AI | Enterprise RAG grounding / permission-aware retrieval | "The SharePoint-permissions-to-AI-Search problem your team blogged about is the problem I work daily: making governed, access-controlled data queryable by LLM workloads without breaking its contracts." |
|
||||
| BS-1 ML inference into 24/7 fab | "Deploying and operating AI systems in production" | "A wafer fab has no maintenance windows — a bad deployment costs yield. That constraint taught me the deployment discipline I'd bring to customer production systems." |
|
||||
| SW-2 Component Owner + on-call | DRI model | "Component Owner at Swisscom is your DRI: I monitor, I get paged, I restore, and I write the runbook so the next restore is faster." |
|
||||
| BS-3 Spotfire platform + TAF 2022 talk | Code-with / customer-facing engineering | "My customers were internal — fab engineers — but the loop was the same: co-own the platform, extend it in their stack, train them, present it publicly." |
|
||||
| AWS → Azure | Cloud-agnostic engagement readiness | "I'm certified on AWS at the architecture level; the primitives map — my first week on an Azure engagement is vocabulary, not concepts. ISE's own playbook says meet customers in their stack." |
|
||||
| LiteLLM + custom GPTs | LLM integration / prompt engineering | "I've built LLM API integrations through LiteLLM and grounded custom GPTs in domain knowledge — the unglamorous 80% of enterprise LLM work is data grounding, and that's my home turf." |
|
||||
| Cross-industry ramp (5 industries, 3 countries + Shanghai) | ISE engagement model | "Every 1–3 years my job has been: walk into an unfamiliar enterprise, learn its domain, ship production code. ISE just compresses that cycle." |
|
||||
| Model evaluation (prep for the probe) | Eval understanding | "Operating a defect classifier means watching its precision drift against fab ground truth; on the data side I enforce quality contracts — I know eval from the operational end, and IBM's AI Engineering curriculum covered the formal end." |
|
||||
|
||||
---
|
||||
|
||||
## Part 7: Cover Letter Critique
|
||||
|
||||
### 6A. Anti-Pattern Checklist — PASS 8/8
|
||||
- ✓ No generic opener (opens with the Engineering Fundamentals Playbook)
|
||||
- ✓ No CV rehash — adds context (yield framing, "one company at a time")
|
||||
- ✓ Names specifics: Playbook, ISE SharePoint→AI Search RAG post, USD 400M Swiss datacenter
|
||||
- ✓ Clear "why THIS role": "doing that across many enterprises instead of inside one" (P1)
|
||||
- ✓ Strongest qualification early (P1 working-style match, P2 opens with the Swisscom AI-data foundation)
|
||||
- ✓ No apologetic gap language — AWS handled positively ("the practices transfer, and I learn platforms quickly")
|
||||
- ✓ Active close ("glad to talk through where your current engagements need this profile")
|
||||
- ✓ Credentials woven into body (SAA in P4, TAF in P3)
|
||||
|
||||
### 6B. Tailoring Signals — PASS 5/5
|
||||
Playbook + ISE blog post + datacenter investment; JD terms supplementing resume (enterprise RAG, AI Search, side by side, observability as fundamentals, data residency); culture reference (code-with, languages-and-frameworks); specific candidate-method↔need connection (governed data ↔ permission-propagation RAG); institution type correctly industry, tone matches.
|
||||
|
||||
### 6C. Industry Checks — PASS
|
||||
Business value present ("a failed deployment costs yield"; data residency for regulated customers); no academia-exit framing needed; jargon technical but HM-readable per plan (deliberate choice, first reader is likely the ISE team, not central HR).
|
||||
|
||||
### 6D. CL ATS Keywords — PASS
|
||||
Supplements resume with: enterprise RAG, AI Search, LLM solutions, production code, observability, on-call, data residency, German, travel — 8+ of 10 high-priority terms present across the package.
|
||||
|
||||
### 6E. Structural — PASS
|
||||
299 words / 4 paragraphs / 1 page ✓ (industry 250–300). Every claim traceable to a resume bullet or verified memory (TAF 2022 = memory-verified; deliberately CL-only as a deepener of BS-3). Quantified: USD 400M, 24/7, 25%-travel-implied "ready for the travel", req number. Sentence lengths vary (8-word closer to 30-word openers); one contraction ("I'm"); human details land ("costs yield", "one company at a time"). 0 em-dashes.
|
||||
|
||||
### 6F. Package Cohesion — PASS
|
||||
Resume stands alone ✓ (interview-earning without CL). CL deepens rather than introduces ✓. No contradictions in dates, titles, claims ✓. Not a prose restatement ✓. Page budget 2+1=3 ✓.
|
||||
|
||||
**Hook verification (step 8b):** all three named artifacts verified live 2026-07-03 with URLs logged in the session file (Playbook; devblogs.microsoft.com/ise/sharepoint-doc-level-access; USD 400M announcement 2025-06-02). No factual errors found.
|
||||
|
||||
---
|
||||
|
||||
## Part 8: Post-Generation Verification
|
||||
|
||||
### Mechanical
|
||||
- [x] Char limits: 18/18 variable bullets within max (189–210, max 218, zero OVER)
|
||||
- [x] Orphan check: all 2L bullets fill line 2 ≥70% (visual PDF check)
|
||||
- [x] Page fill: **EXCEPTION** — page 2 ends ~2/3 down (> 3-line rule); documented accepted tradeoff, matches sent-and-cleared Google baseline
|
||||
- [x] Bullet ordering matches approved Phase 1 plan (incl. both authorized fillers FC-3, GN-2)
|
||||
|
||||
### Content
|
||||
- [x] ATS ≥70% (85%)
|
||||
- [x] Provenance flags respected (no false publication/award claims; Security Champion excluded; funding n/a)
|
||||
- [x] No forbidden terms (LangChain absent; no LOC/test counts; no code-folder names)
|
||||
- [x] No inflation (hedged: "Contributed" ARTUS, "Co-owned" Spotfire; scoped: "within company-wide Data Mesh", "my domains' ETL stack")
|
||||
- [x] Publications n/a (industry resume)
|
||||
- [x] CL claims traceable to resume/memory
|
||||
- [x] AI fingerprint: banned words CLEAN, 0 rendered em-dashes (both docs), no vague -ing bullet endings, no generic CL opener, sentence variety OK
|
||||
|
||||
### Structural
|
||||
- [x] "Microsoft", "Zürich", "Swisscom", "Fraunhofer" spelled correctly throughout
|
||||
- [x] Both .tex files compile standalone (MiKTeX, 2pp + 1pp)
|
||||
- [x] Date format consistent (Mon YYYY -- Mon YYYY); education overlap preserved as mandated
|
||||
- [x] Email dennis@thiessen.io in both ✓ (config match)
|
||||
- [x] Page counts: resume 2, CL 1 ✓
|
||||
|
||||
**Failures escalated to Tier 1: none.** (Page-fill exception documented, not escalated — padding would require KB-unsupported content.)
|
||||
|
||||
---
|
||||
|
||||
*End of critique — Pass 1, 2026-07-03. Lens persists for any re-critique.*
|
||||
@@ -0,0 +1,50 @@
|
||||
\documentclass[11pt,a4paper,roman]{moderncv}
|
||||
\usepackage[english]{babel}
|
||||
\moderncvstyle{classic}
|
||||
\moderncvcolor{green}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{ragged2e}
|
||||
\usepackage[scale=0.80]{geometry}
|
||||
\usepackage[version=4,arrows=pgf-filled]{mhchem}
|
||||
\renewcommand*{\makeletterclosing}{\par\vspace{2ex}\closingname\par}
|
||||
\microtypesetup{expansion=false}
|
||||
|
||||
% ========== HEADER ==========
|
||||
\name{Dennis}{Thiessen, M.Eng.}
|
||||
\address{Bern, Switzerland}{}{}
|
||||
\phone[mobile]{+41~795~955~585}
|
||||
\email{dennis@thiessen.io}
|
||||
\extrainfo{\href{https://linkedin.com/in/dennis-thiessen}{linkedin.com/in/dennis-thiessen}}
|
||||
% ============================
|
||||
|
||||
\begin{document}
|
||||
|
||||
\recipient{Hiring Team}{Industry Solutions Engineering (ISE)\\Microsoft Switzerland GmbH\\Z\"urich, Switzerland}
|
||||
\date{\today}
|
||||
\opening{Dear ISE Hiring Team,}
|
||||
\makelettertitle
|
||||
|
||||
\begin{justify}
|
||||
% P1 — Hook: Engineering Fundamentals Playbook / code-with model
|
||||
ISE's public Engineering Fundamentals Playbook describes a working style I recognize: production code written side by side with the customer's engineers, in their languages and frameworks, with testing and observability treated as fundamentals. Doing that across many enterprises instead of inside one is why I want the Senior Software Engineer position in ISE Z\"urich (req.\ 200040836).
|
||||
|
||||
% P2 — Swisscom: data foundation for agentic AI, LLM integration, production ownership
|
||||
At Swisscom I build governed data products with active metadata on AWS, inside the company-wide Data Mesh. They are the grounded data foundation our agentic AI workloads query. So when your team wrote about propagating SharePoint permissions into AI Search for enterprise RAG, that problem looked familiar: making governed, access-controlled data usable for LLM solutions is my daily work, from LiteLLM API integrations to custom GPTs grounded in domain knowledge. As Component Owner I carry on-call responsibility for business-critical pipelines.
|
||||
|
||||
% P3 — Cross-industry ramp record + Bosch production ML and customer-facing platform work
|
||||
Becoming productive fast inside an unfamiliar enterprise is the pattern of my career: applied research at Fraunhofer, semiconductor manufacturing at Bosch, insurance at Generali, broadcast in Norway at Vizrt, telecom at Swisscom, and a master's thesis written in Shanghai. At Bosch I moved containerized ML inference into a 24/7 wafer fab, where there are no maintenance windows and a failed deployment costs yield. I also co-owned the Spotfire analytics platform for internal engineering customers and co-presented it at the TIBCO Analytics Forum 2022. Embedded engineering with customer teams is what I already do, one company at a time.
|
||||
|
||||
% P4 — Why Microsoft Switzerland now + honest AWS positioning + call to action
|
||||
Microsoft's USD 400 million Swiss datacenter expansion, with in-country data residency for regulated customers, will bring ISE Z\"urich exactly the enterprises I know from the inside. My cloud depth is AWS (Solutions Architect certified); the practices transfer, and I learn platforms quickly. I'm a native German speaker in Bern, ready for the travel, and glad to talk through where your current engagements need this profile.
|
||||
\end{justify}
|
||||
|
||||
\vspace{0.3cm}
|
||||
% ========== CUSTOMIZE THESE ==========
|
||||
{Sincerely,\\
|
||||
Dennis Thiessen, M.Eng.\\
|
||||
Staff Data, Analytics \& AI Engineer\\
|
||||
Swisscom (Schweiz) AG}
|
||||
% ======================================
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,163 @@
|
||||
\documentclass{resume}
|
||||
\usepackage{hyperref}
|
||||
\usepackage{enumitem}
|
||||
\usepackage{fontawesome}
|
||||
\usepackage{tikz}
|
||||
\usepackage{graphicx}
|
||||
\hypersetup{
|
||||
colorlinks = true,
|
||||
linkcolor = [rgb]{0.9,0.4,0.4},
|
||||
anchorcolor = [rgb]{0.9,0.4,0.4},
|
||||
citecolor = [rgb]{0.4,0.4,0.4},
|
||||
filecolor = [rgb]{0.4,0.4,0.4},
|
||||
urlcolor = [rgb]{0.0,0.0,0.99},
|
||||
}
|
||||
\usepackage{xcolor}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage[version=4,arrows=pgf-filled]{mhchem}
|
||||
\usepackage[includefoot,left=0.5in,top=0.5in,right=0.5in,bottom=0.2in,textwidth=7.5in,textheight=10.8in]{geometry}
|
||||
\usepackage{fancyhdr}
|
||||
\pagestyle{fancy}
|
||||
\fancyhf{}
|
||||
\renewcommand{\headrulewidth}{0pt}
|
||||
\fancyfoot[R]{\hfill \thepage/\pageref{LastPage}}
|
||||
\newcommand{\tab}[1]{\hspace{.2667\textwidth}\rlap{#1}}
|
||||
\newcommand{\itab}[1]{\hspace{0em}\rlap{#1}}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% HEADER
|
||||
%----------------------------------------------------------------------------------------
|
||||
\name{Dennis Thiessen, M.Eng.}
|
||||
\address{\href{https://linkedin.com/in/dennis-thiessen}{LinkedIn}}
|
||||
\address{dennis@thiessen.io \\ +41 795 955 585}
|
||||
\address{Bern, Switzerland $\vert$ German citizen (EU) $\vert$ Open to Z\"urich (on-site / hybrid) $\vert$ Travel-ready}
|
||||
\address{{Staff Data \& AI Engineer $\vert$ Python $\cdot$ Java $\cdot$ AWS $\cdot$ Kubernetes $\vert$ Production AI Foundations \& Co-Engineering}}
|
||||
|
||||
|
||||
\begin{document}
|
||||
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% SUMMARY
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection}{Summary}
|
||||
Staff data \& AI engineer with 11+ years shipping production software across telecom, manufacturing, broadcast and insurance. At Swisscom I build governed \textbf{data products} on \textbf{AWS} (Glue, Athena/Iceberg, \textbf{Airflow}), the grounded data foundation for agentic \textbf{AI} and \textbf{LLM} workloads, run \textbf{Python} services on \textbf{Kubernetes}, and carry on-call duty as Component Owner. At Bosch I moved \textbf{ML} inference into a 24/7 semiconductor fab. I work embedded in cross-functional customer and stakeholder teams. \textbf{AWS} Certified Solutions Architect; native German, fluent English.
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% TECHNICAL SKILLS — Format C, 5 groups (4-3-2-2-2)
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection}{Technical Skills}
|
||||
|
||||
\begin{skillgroup}{Software \& Data Engineering}
|
||||
\skilldash{\textbf{Python} (expert), \textbf{Java}, C\#, SQL, Bash, JavaScript/TypeScript; REST APIs, FastAPI, pytest}
|
||||
\skilldash{ETL/ELT pipeline design, data modeling, \textbf{data products}, data governance \& data quality}
|
||||
\skilldash{Open-source stack: \textbf{Apache Kafka}, \textbf{Apache Airflow}, \textbf{PySpark} / Spark, Hadoop/Impala; batch \& streaming}
|
||||
\skilldash{Oracle, Teradata, Redshift, Athena, MS SQL, Postgres; SQL performance tuning, data warehousing}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Cloud Platform \& Infrastructure}
|
||||
\skilldash{\textbf{AWS} (S3, Glue, Athena/Iceberg, Redshift, Lambda, Step Functions, CloudWatch) -- SAA-certified}
|
||||
\skilldash{Infrastructure as Code (CloudFormation), serverless \& event-driven architecture, ECR/ECS}
|
||||
\skilldash{\textbf{Kubernetes}, \textbf{Docker}, \textbf{GitLab CI/CD}, Jenkins, Ansible, Linux, Git}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{AI \& ML in Production}
|
||||
\skilldash{\textbf{ML} inference deployment (Docker/Kubernetes), MLOps, model evaluation, data-quality \& performance monitoring}
|
||||
\skilldash{\textbf{LLM} API integration (\textbf{LiteLLM}), custom GPTs with domain grounding (RAG), prompt engineering, Copilot, Kiro}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Observability \& Engineering Quality}
|
||||
\skilldash{\textbf{Grafana}, \textbf{Prometheus}, Loki, ELK (Elasticsearch, Logstash, Kibana), alerting \& incident response}
|
||||
\skilldash{Test automation (pytest, BDD/Serenity, Selenium), CI/CD quality gates, code review, TDD}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Certifications}
|
||||
\skilldash{\textbf{AWS Certified Solutions Architect -- Associate} (active to Sep 2027), Data Engineering with AWS (Udacity)}
|
||||
\skilldash{iSAQB CPSA -- Foundation (2016), ITIL Foundation (2016), IBM AI Engineering Specialization}
|
||||
\end{skillgroup}
|
||||
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% PROFESSIONAL EXPERIENCE
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection}{Professional Experience}
|
||||
|
||||
% --- Swisscom (Oct 2023 -- Present) — SW-7, SW-3, SW-1, SW-2, SW-4, SW-6 ---
|
||||
\begin{rSubsection}{Governed Data Products \& AI-Ready Platform Engineering}{\textcolor{black!60}{Oct 2023 -- Present}}{Staff Data, Analytics \& AI Engineer, Swisscom (Schweiz) AG}{Bern, Switzerland}
|
||||
\item Build governed \textbf{data products} with active metadata management within Swisscom's company-wide \textbf{Data Mesh} on \textbf{AWS} (Glue, Athena, CloudFormation), the grounded data foundation that agentic \textbf{AI} workflows query.
|
||||
\item Design, deploy and operate \textbf{Python} data applications on \textbf{Kubernetes} with \textbf{GitLab CI/CD}, owning containerized delivery from build and test through production rollout and operation in an agile DevOps team.
|
||||
\item Migrated my domains' \textbf{ETL} stack from Teradata/Oracle to Swisscom's cloud-native \textbf{AWS} platform (Glue, Athena/Iceberg, Redshift, \textbf{Airflow}), cutting operational overhead with serverless, scalable processing.
|
||||
\item Own business-critical Fulfillment \textbf{ETL} pipelines (Oracle, \textbf{Kafka} to Teradata in \textbf{Python}) as Component Owner, accountable for data quality, governance, incident response and restoration under on-call SLA.
|
||||
\item Deliver data products, dashboards and analyses for B2B stakeholder teams, partnering with product owners on backlog priorities and running root-cause analysis under 2nd/3rd-level support duty.
|
||||
\item Apply \textbf{PySpark} and distributed data processing in the Swisscom Data Lake, extending \textbf{Python} and \textbf{SQL} pipelines to large-scale batch and streaming workloads across Fulfillment and Product Analysis data domains.
|
||||
\end{rSubsection}
|
||||
|
||||
% --- Bosch (Feb 2020 -- Dec 2022) — BS-1, BS-3+BS-5, BS-4, BS-2 ---
|
||||
\begin{rSubsection}{Production ML Deployment, Data Services \& Platform Ownership}{\textcolor{black!60}{Feb 2020 -- Dec 2022}}{(Senior) Data \& ML Engineer, Robert Bosch Semiconductor Manufacturing}{Dresden, Germany}
|
||||
\item Containerized and orchestrated \textbf{ML} inference (\textbf{Docker}, \textbf{Kubernetes}, Ansible) into Bosch's 24/7 semiconductor fab, operating automated image-based defect classification continuously on live 300mm wafer lines.
|
||||
\item Co-owned the TIBCO Spotfire analytics platform and the Defect Management System as Application Owner, building C\# extensions and wafer-map visualizations, defining SLOs and training engineering users.
|
||||
\item Built an anomaly-detection proof of concept (ELK with \textbf{Kafka} on \textbf{Docker}) plus \textbf{Grafana}, \textbf{Prometheus} and Loki monitoring, validating centralized log management and alerting for 24/7 manufacturing systems.
|
||||
\item Developed data services in \textbf{Python}, Java and C\# over OracleDB and Hadoop/ImpalaSQL, giving analysis teams structured, reliable access to defect-management and process-optimization data in a high-throughput fab.
|
||||
\end{rSubsection}
|
||||
|
||||
% --- Fraunhofer (Sep 2018 -- Oct 2019) — FC-2, FC-1 ---
|
||||
\begin{rSubsection}{Applied ML Research \& CI/CD Automation from Zero}{\textcolor{black!60}{Sep 2018 -- Oct 2019}}{Research Software Engineer, Fraunhofer-Center for Maritime Logistics CML}{Hamburg, Germany}
|
||||
\item Contributed \textbf{ML} and NLP components to ARTUS, a Fraunhofer research project developing automatic speech transcription for sea rescue operations, applying machine learning in a safety-critical maritime domain.
|
||||
\item Set up the team's first Jenkins \textbf{CI/CD} pipeline with quality gates independently, bringing build automation to the group; also developed the SCEDAS crew-scheduling system (C\#, .NET, MS SQL, Entity Framework).
|
||||
\item Built containerized microservices (Express.js, JavaScript, \textbf{Docker}, SQLite) for MISSION, a Fraunhofer maritime data-exchange platform connecting ports, operators and research partners across the logistics chain.
|
||||
\end{rSubsection}
|
||||
|
||||
% --- Vizrt (Jul 2017 -- May 2018) — VZ-1, VZ-2 ---
|
||||
\begin{rSubsection}{Distributed Real-Time Backend Engineering at Broadcast Scale}{\textcolor{black!60}{Jul 2017 -- May 2018}}{DevOps Engineer, Vizrt}{Bergen, Norway}
|
||||
\item Engineered distributed real-time video-transcoding backend components in \textbf{Python} (with legacy C++ modules) for Vizrt's broadcast platform, serving global media customers including CNN, BBC and Al Jazeera.
|
||||
\item Wrote an automated A/V integration and unit test suite in \textbf{Python} and wired quality gates into the \textbf{CI/CD} pipeline, which shortened the feedback loop for new features and raised release reliability.
|
||||
\end{rSubsection}
|
||||
|
||||
% --- Generali (May 2015 -- Jun 2017) — GN-1, GN-3 ---
|
||||
\begin{rSubsection}{Test Automation, CI/CD Ownership \& Java Backend}{\textcolor{black!60}{May 2015 -- Jun 2017}}{IT Consultant, Generali Deutschland Informatik Services}{Hamburg, Germany}
|
||||
\item Introduced BDD test automation to Generali (Serenity-BDD, Selenium, JBehave), ran the PoC and took technical ownership, administered Jenkins \textbf{CI/CD} jobs, and trained teams across the Java Community.
|
||||
\item Developed \textbf{Java}/J2EE features for the PIA-Postkorb workflow portal, migrated WebServices to the XLDeploy process, and contributed to an Apache Camel / Spring Boot dispatcher integration PoC.
|
||||
\item Pioneered UIPath RPA at Generali GDIS, building PoCs and serving as the internal RPA contact for group companies, extending automation from test tooling into broader business process automation.
|
||||
\end{rSubsection}
|
||||
|
||||
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% EDUCATION — FIXED
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection}{Education}
|
||||
{M.Eng.\ Computer Aided Engineering (Software Design \& Engineering)} \hfill {\textcolor{black!60}{Apr 2012 -- Oct 2013}}\\
|
||||
{Universit\"at der Bundeswehr M\"unchen}; thesis at Tongji University, Shanghai \hfill Thesis Grade: \textbf{1.0}\\
|
||||
{\small Thesis: \textit{Development of a Web-Based Remote Fault Diagnosis System} (Neural Networks, PSO, Fuzzy Logic)}
|
||||
|
||||
{B.Eng.\ Information and Telecommunication Technologies} \hfill {\textcolor{black!60}{Oct 2009 -- Oct 2012}}\\
|
||||
{Universit\"at der Bundeswehr M\"unchen}, Munich, Germany
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% CERTIFICATIONS & AWARDS — FIXED
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection2}{Certifications \& Awards}
|
||||
\item \textbf{AWS Certified Solutions Architect -- Associate}, Amazon Web Services (2024, active until Sep 2027).
|
||||
\item \textbf{Data Engineering with AWS Nanodegree}, Udacity (2026). AWS data pipeline architecture.
|
||||
\item \textbf{IBM AI Engineering Specialization}, Coursera. Deep learning, TensorFlow, Keras, Apache Spark ML.
|
||||
\item \textbf{iSAQB CPSA -- Foundation Level}, iSAQB (2016). Certified Professional for Software Architecture.
|
||||
\item \textbf{ITIL Foundation Certificate in IT Service Management}, PEOPLECERT / AXELOS (2016).
|
||||
\end{rSection2}
|
||||
|
||||
\begin{center}
|
||||
\vspace{0.1cm}
|
||||
\textit{Languages: German (native), English (fluent)}
|
||||
\end{center}
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,199 @@
|
||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
% Medium Length Professional CV - RESUME CLASS FILE
|
||||
%
|
||||
% This template has been downloaded from:
|
||||
% http://www.LaTeXTemplates.com
|
||||
%
|
||||
% This class file defines the structure and design of the template.
|
||||
%
|
||||
% Original header:
|
||||
% Copyright (C) 2010 by Trey Hunner
|
||||
%
|
||||
% Copying and distribution of this file, with or without modification,
|
||||
% are permitted in any medium without royalty provided the copyright
|
||||
% notice and this notice are preserved. This file is offered as-is,
|
||||
% without any warranty.
|
||||
%
|
||||
% Created by Trey Hunner and modified by www.LaTeXTemplates.com
|
||||
%
|
||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
|
||||
\ProvidesClass{resume}[2018/09/25 v1.0 Resume class]
|
||||
|
||||
\LoadClass[10pt, a4paper]{article} % Font size and paper type
|
||||
\usepackage{lastpage}
|
||||
\usepackage[parfill]{parskip} % Remove paragraph indentation
|
||||
\usepackage{array} % Required for boldface (\bf and \bfseries) tabular columns
|
||||
\usepackage{ifthen} % Required for ifthenelse statements
|
||||
\usepackage{enumitem}
|
||||
\pagestyle{empty} % Suppress page numbers
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% HEADINGS COMMANDS: Commands for printing name and address
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
\def \name#1{\def\@name{#1}} % Defines the \name command to set name
|
||||
\def \@name {} % Sets \@name to empty by default
|
||||
|
||||
\def \addressSep {$|$} % Set default address separator to a diamond
|
||||
|
||||
% One, two or three address lines can be specified
|
||||
\let \@addressone \relax
|
||||
\let \@addresstwo \relax
|
||||
\let \@addressthree \relax
|
||||
\let \@addressfour \relax
|
||||
|
||||
% \address command can be used to set the first, second, and third address (last 2 optional)
|
||||
\def \address #1{
|
||||
\@ifundefined{@addresstwo}{
|
||||
\def \@addresstwo {#1}
|
||||
}{
|
||||
\@ifundefined{@addressthree}{
|
||||
\def \@addressthree {#1}
|
||||
}{
|
||||
\@ifundefined{@addressfour}{
|
||||
\def \@addressfour {#1}
|
||||
} {\def \@addressone {#1}
|
||||
}
|
||||
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
% \printaddress is used to style an address line (given as input)
|
||||
\def \printaddress #1{
|
||||
\begingroup
|
||||
\def \\ {\addressSep\ }
|
||||
{#1}
|
||||
% \centerline{#1}
|
||||
\endgroup
|
||||
\par
|
||||
% \addressskip
|
||||
}
|
||||
|
||||
% \printname is used to print the name as a page header
|
||||
\def \printname {
|
||||
\begingroup
|
||||
% \MakeUppercase
|
||||
{\namesize\bf \@name} \hfil
|
||||
% \hfil{\MakeUppercase{\namesize\bf \@name}}\hfil
|
||||
\nameskip\break
|
||||
\endgroup
|
||||
}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% PRINT THE HEADING LINES
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
\let\ori@document=\document
|
||||
\renewcommand{\document}{
|
||||
\ori@document % Begin document
|
||||
% \begin{center}
|
||||
\printname % Print the name specified with \name
|
||||
\@ifundefined{@addressone}{}{ % Print the first address if specified
|
||||
\printaddress{\@addressone}}
|
||||
\@ifundefined{@addresstwo}{}{ % Print the second address if specified
|
||||
\printaddress{\@addresstwo}}
|
||||
\@ifundefined{@addressthree}{}{ % Print the third address if specified
|
||||
\printaddress{\@addressthree}}
|
||||
\@ifundefined{@addressfour}{}{ % Print the third address if specified
|
||||
\printaddress{\@addressfour}}
|
||||
|
||||
% \end{center}
|
||||
}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% SECTION FORMATTING
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
% Defines the rSection environment for the large sections within the CV
|
||||
\newenvironment{rSection}[1]{ % 1 input argument - section name
|
||||
\sectionskip
|
||||
{\bf #1}
|
||||
% \MakeUppercase{\bf #1} % Section title
|
||||
\sectionlineskip
|
||||
\hrule % Horizontal line
|
||||
\begin{list}{}{ % List for each individual item in the section
|
||||
\setlength{\leftmargin}{0.50em} % Margin within the section
|
||||
}
|
||||
\item[]
|
||||
}{
|
||||
\end{list}
|
||||
}
|
||||
|
||||
\newenvironment{rSection2}[1]{ % 1 input argument - section name
|
||||
\sectionskip
|
||||
{\bf #1} % Section title
|
||||
\sectionlineskip
|
||||
\hrule % Horizontal line
|
||||
\medskip
|
||||
\begin{list}{$\bullet$}{\setlength{\leftmargin}{1.5em}}
|
||||
\itemsep -0.3em \vspace{-0.5em} % Compress items in list together for aesthetics
|
||||
}{
|
||||
\end{list}
|
||||
\vspace{0.5em}
|
||||
}
|
||||
|
||||
\newenvironment{rSection3}[1]{ % 1 input argument - section name
|
||||
\sectionskip
|
||||
{\bf #1} % Section title
|
||||
\sectionlineskip
|
||||
\hrule % Horizontal line
|
||||
\medskip
|
||||
\begin{enumerate}[]{\setlength{\leftmargin}{1.5em}}
|
||||
\itemsep -0.3em \vspace{-0.5em} % Compress items in list together for aesthetics
|
||||
}{
|
||||
\end{enumerate}
|
||||
\vspace{0.5em}
|
||||
}
|
||||
%----------------------------------------------------------------------------------------
|
||||
% WORK EXPERIENCE FORMATTING
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
\newenvironment{rSubsection}[4]{ % 4 input arguments - company name, year(s) employed, job title and location
|
||||
{\bf #1} \hfill {#2} % Bold company name and date on the right
|
||||
\ifthenelse{\equal{#3}{}}{}{ % If the third argument is not specified, don't print the job title and location line
|
||||
\\
|
||||
{\em #3} \quad {\em #4} % Italic job title and location
|
||||
}\smallskip
|
||||
\begin{list}{$\cdot$}{\leftmargin=1.5em} % \cdot used for bullets, no indentation
|
||||
\itemsep -0.2em \vspace{-0.2em} % Compress items in list together for aesthetics
|
||||
}{
|
||||
\end{list}
|
||||
\vspace{0.2 em} % Some space after the list of bullet points
|
||||
}
|
||||
|
||||
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% FORMAT C SKILLS COMMANDS
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
% Skills group environment: \begin{skillgroup}{Group Name} ... \end{skillgroup}
|
||||
% Renders bold header + indented dash sub-items. Each \skilldash = exactly 1 rendered line.
|
||||
\newenvironment{skillgroup}[1]{%
|
||||
\textbf{#1}\par\nopagebreak%
|
||||
\vspace{-\parskip}%
|
||||
\begin{list}{--}{\leftmargin=0.8em \labelsep=0.3em \itemsep=0pt \topsep=0.1em \parsep=0pt \partopsep=0pt}%
|
||||
}{%
|
||||
\end{list}%
|
||||
\vspace{-\parskip}\vspace{0.45em}%
|
||||
}
|
||||
|
||||
% Single dash sub-item within a skillgroup. Content must fit 1 rendered line.
|
||||
% Char limit: 119 - (0.5 x bold_char_count) at 10pt
|
||||
\newcommand{\skilldash}[1]{\item #1}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% EXPERIENCE SUB-THEME COMMAND
|
||||
%----------------------------------------------------------------------------------------
|
||||
|
||||
% Sub-theme underline header within rSubsection
|
||||
\newcommand{\subtheme}[1]{\item[] \underline{#1}}
|
||||
|
||||
% The below commands define the whitespace after certain things in the document - they can be \smallskip, \medskip or \bigskip
|
||||
\def\namesize{\huge} % Size of the name at the top of the document
|
||||
\def\addressskip{\smallskip} % The space between the two address (or phone/email) lines
|
||||
\def\sectionlineskip{\medskip} % The space above the horizontal line for each section
|
||||
\def\nameskip{\medskip} % The space after your name at the top
|
||||
\def\sectionskip{\medskip} % The space after the heading section
|
||||
@@ -0,0 +1,168 @@
|
||||
# Session: Microsoft Senior Software Engineer — Industry Solutions Engineering (ISE), Zürich
|
||||
|
||||
## JD Info
|
||||
- **File:** job_scout/jd_microsoft_ise.txt (copy: output/Microsoft_ISE_Senior_SWE/JD_microsoft_ise.txt)
|
||||
- **JD source:** live fetch 2026-07-03 via Eightfold PCSX API (apply.careers.microsoft.com, req 200040836), verbatim
|
||||
- **Role:** Senior Software Engineer, Industry Solutions Engineering (ISE) — IC4, Software Engineering profession
|
||||
- **Company:** Microsoft (ISE = global non-billing co-engineering org inside MCAPS; engineers code side-by-side with strategic customers)
|
||||
- **Bundle:** HYBRID — primary `bundle_ml_ai_engineer.md` (JD's decisive axis: production AI systems, LLM/RAG, model eval/monitoring), secondary `bundle_data_engineer.md` (strongest evidence; reframing map for bridging bullets)
|
||||
- **Format:** Resume (2-page, resume.cls) + 1-page cover letter
|
||||
- **Salary/Details:** Published base band CHF 146,200–245,900 (IC4, Switzerland). Zürich. Travel up to 25%. German "beneficial". Posted ~2026-06-26, "open minimum 5 days, ongoing until filled" — apply promptly.
|
||||
|
||||
## JD Analysis
|
||||
|
||||
### Requirements
|
||||
| # | Requirement | Match | Evidence |
|
||||
|---|-------------|-------|----------|
|
||||
| 1 | BS in CS/related + 4+ yrs engineering w/ coding (C, C++, C#, Java, JavaScript, Python) | Direct | B.Eng. + M.Eng. (Software Design & Engineering); 12+ yrs; Python + Java strong (per feedback_cpp_emphasis: lead Python/Java, do NOT oversell C++; C#/.NET minor via Fraunhofer — secondary mention only) |
|
||||
| 2 | Familiarity with deploying and operating AI systems in production environments | Bridge (high) | Swisscom: governed data products + metadata mgmt on AWS as the data foundation for company agentic-AI programme (SW-7); operates production pipelines feeding AI workloads; LiteLLM gateway API usage. NOT model-serving ownership — hedge verbs |
|
||||
| 3 | Experience building or integrating AI/ML or LLM-based solutions, prompt engineering, RAG | Bridge (medium-high) | Verified toolchain ONLY: Kiro (spec-driven AI dev), VS Code + Copilot, LiteLLM (created/used LLM API integrations), custom GPTs fed with domain knowledge (prompt engineering + grounding = RAG-adjacent). NEVER LangChain/LangGraph/LlamaIndex (config ban) |
|
||||
| 4 | Understanding of model evaluation, data quality, and performance monitoring | Bridge (high) | Data quality is core Swisscom work (data products with contracts/metadata); monitoring/observability from DevOps history (Bosch/Swisscom pipelines). Model evaluation specifically = thin — claim "data quality & performance monitoring" side confidently, model-eval only as understanding |
|
||||
| 5 | Design/deliver solutions with modern software engineering practices + cloud technologies | Direct | AWS-heavy platform work (Swisscom), CI/CD, IaC-adjacent DevOps at Bosch/Swisscom; Azure = gap (AWS-primary — frame cloud skills as transferable, name AWS honestly) |
|
||||
| 6 | Customer-facing co-engineering, cross-functional teams (SWE + data scientists + TPMs + designers) | Direct | Bosch: co-owned Spotfire analytics platform for internal customers, co-presented TIBCO Analytics Forum 2022; Swisscom: onboarding domain teams onto data products, guiding producers; Fraunhofer: applied research with industry partners |
|
||||
| 7 | DRI/on-call: monitor systems, restore service, playbooks | Bridge (high) | Application Owner / Component Owner roles = production ownership incl. incident response for his components (scope-disciplined: HIS components, not org-wide) |
|
||||
| 8 | Open source contribution / variety of technologies "not just Microsoft" | Bridge (medium) | Polyglot record (Python/Java/C#, AWS/on-prem, Spotfire/TIBCO); personal Solidity work. No notable OSS contributions — do not claim |
|
||||
| 9 | Travel up to 25% | Direct | Explicitly matches mobility appetite (user_international_mobility: travel-OK from Bern, cross-cultural work history NO/DE/CH/Shanghai) |
|
||||
| 10 | German language beneficial (preferred qual) | Direct | Native German + fluent English — differentiator for Swiss/DACH customer engagements |
|
||||
|
||||
### ATS Keywords
|
||||
- **ML/AI:** AI systems in production, LLM, RAG, prompt engineering, model evaluation, AI/ML solutions, Copilot, agentic
|
||||
- **Domain:** co-engineering, customer engagements, industry solutions, cloud solutions, open source
|
||||
- **Methods:** modern software engineering practices, CI/CD, code review, design documents, observability, monitoring, incident response (DRI), playbooks, reliability, performance, maintainability
|
||||
- **Tools:** Python, Java, C#, cloud (AWS→Azure bridge), Kubernetes/containers, Git/GitHub
|
||||
- **Soft skills:** cross-functional collaboration, stakeholder requirements, growth mindset, mentoring/guiding engineers
|
||||
|
||||
### Gap Assessment
|
||||
- **Direct:** coding depth (Python/Java, 12+ yrs), cloud data/platform engineering, customer-facing co-engineering, cross-functional work, German, travel appetite
|
||||
- **Bridge (confidence):** production AI operations via data-foundation-for-AI (high); LLM integration via LiteLLM/custom GPTs/Kiro (medium-high — verified tools only); DRI/on-call via Application/Component Owner (high); model-eval understanding (medium — hedge as "understanding")
|
||||
- **Gap (cannot claim):** Azure-specific services (AWS-primary — say so honestly), model training/fine-tuning ownership, notable OSS contributions, C++ depth, JavaScript/front-end depth
|
||||
- **Fabrication tripwires:** NO LangChain/LangGraph (config ban); no "built the Data Mesh" (scope discipline); no claiming model-serving/MLOps platform ownership
|
||||
|
||||
## Company Context
|
||||
- **Mission:** Empower every person and organization to achieve more. ISE specifically: non-billing global engineering org (inside MCAPS) that co-develops production code side-by-side with strategic customers' engineers, then feeds learnings back into Microsoft products. Public Engineering Fundamentals Playbook (microsoft.github.io/code-with-engineering-playbook) codifies how they work: agile ceremonies, code-with, testing, observability fundamentals.
|
||||
- **This role:** Zürich-based Senior SWE (IC4) embedded in customer engagements — likely Swiss/DACH strategic accounts (banks, pharma, industrials) given the German-beneficial flag. Recent ISE publication themes: enterprise RAG with document-permission propagation (Entra ID → AI Search), coordinator-based multi-agent architectures in production, vector/hybrid search evaluation frameworks, multimodal RAG fine-tuning experiments.
|
||||
- **Culture:** "Meet customers where they are — their languages, their frameworks, their OS." Explicitly not-just-Microsoft tech. Growth mindset, informal/flexible, travel ~25%. Cross-functional pods (SWE + DS + TPM + design).
|
||||
- **Swiss context (CL-relevant):** Microsoft committed USD 400M (June 2025) to expand Swiss datacenter capacity near Zürich and Geneva with in-country data residency for 50k+ customers; AI Tour Zürich April 2026 (3,000+ attendees); Swiss AI Tech Accelerator cohort 3 (Jan 2026).
|
||||
- **"Why them" angle:** ISE is the rare role where a platform/data engineer with enterprise-scale AI-foundation experience gets to do hands-on engineering ACROSS companies instead of inside one — Dennis's multi-country, multi-industry ramp (Fraunhofer research → Bosch automotive → Generali insurance → Swisscom telecom) is exactly the "walk into a new enterprise and be productive fast" profile ISE hires for.
|
||||
|
||||
## Framing Strategy
|
||||
- **Lead narrative:** Staff-level data & AI platform engineer (12+ yrs, telecom/automotive/research) who builds the governed data and platform foundations that make production AI work inside large enterprises — now bringing that enterprise-hardened, customer-embedded engineering to ISE's co-engineering model.
|
||||
- **Reframing map:**
|
||||
- "data products / Data Mesh contribution (SW-7 agentic-AI foundation)" → "data foundations for production AI / agentic systems" (scope-disciplined)
|
||||
- "LiteLLM gateway APIs + custom GPTs with domain grounding" → "integrating LLM-based solutions; prompt engineering and knowledge grounding" (verbatim-verified tools only)
|
||||
- "Application Owner / Component Owner incident duty" → "DRI-style production ownership: monitoring, incident response, restoration playbooks" (his components only)
|
||||
- "Bosch Spotfire platform co-ownership + TAF 2022 co-presentation" → "customer-facing platform engineering and technical evangelism with internal customers"
|
||||
- "AWS Glue/Athena/Redshift stack" → "cloud-native engineering (AWS; concepts transferable to Azure)" — name AWS, never claim Azure depth
|
||||
- **Emphasize:** Python/Java polyglot depth; enterprise data/AI platform work; customer-embedded collaboration (Bosch analytics platform, Swisscom domain onboarding); production ownership/reliability; German+English; cross-industry adaptability (4 industries, 3 countries + Shanghai)
|
||||
- **Downplay:** C++ (per feedback_cpp_emphasis), C#/.NET (one mention max), Spotfire/BI tooling specifics, security-champion badge (JD doesn't gate on security)
|
||||
- **CL hooks:** (1) ISE Engineering Fundamentals Playbook — "code-with" model matches how he onboards domain teams onto data products; (2) ISE blog's enterprise-RAG/permission-propagation work — mirrors his governed-data-products + metadata/access-control reality at Swisscom; (3) Microsoft's CHF 400M Swiss datacenter/data-residency investment — he builds exactly the kind of regulated, in-country data platforms Swiss customers will bring to ISE; (4) German-native for DACH accounts + 25% travel appetite.
|
||||
- **User directives:** None given (autonomous Friday-run build). Defaults from hybrid priority matrix.
|
||||
|
||||
## Critique Context
|
||||
- **Reviewer persona:** ISE engineering manager or senior/principal SWE in EMEA doing hiring-manager screen. Reads 50+ CVs per req. Daily work: scoping customer engagements, unblocking pods, code reviews. Impressed by: production evidence, breadth across stacks, customer-facing engineering signals, crisp scope-honest claims. Bored/annoyed by: buzzword AI claims without operational substance, tool soup, solo-hero claims over org-scale objects.
|
||||
- **Competitive landscape:** Other applicants = senior SWEs from consultancies (Accenture/Avanade), Azure-native engineers, ex-FAANG generalists. The "obvious fit" has Azure depth + OSS visibility. Dennis's edge: genuine enterprise data-platform depth + regulated-industry scars + German + already-Swiss (no visa/relocation friction — EU/EFTA citizen in Bern).
|
||||
- **Domain vocabulary:** "code-with" / co-engineering, engagement, crew/pod, engineering fundamentals, DRI, game days, grounding, RAG, agentic workflows, Foundry/Copilot ecosystem (use sparingly — only where honest).
|
||||
|
||||
## Cover Letter Plan
|
||||
- **Institution type:** Industry (big tech, customer-facing engineering org)
|
||||
- **Paragraph count:** 4 paragraphs, 250–300 words, 1 page
|
||||
- **P1 hook:** ISE's co-engineering model ("code-with", Engineering Fundamentals Playbook) + why an enterprise data/AI platform engineer wants to do it across customers; Zürich req + German-beneficial fits him natively
|
||||
- **P2 evidence:** Swisscom — governed data products on AWS as the data foundation for the company-wide agentic-AI programme (scope-disciplined); LLM integration via LiteLLM APIs + domain-grounded custom GPTs; production ownership (Application Owner, incident response)
|
||||
- **P3 evidence:** cross-industry, cross-country ramp record (Fraunhofer → Bosch → Generali → Swisscom; NO/DE/CH + Shanghai) = productive-fast-in-new-enterprise; Bosch: co-owned analytics platform for internal customers, co-presented at TIBCO Analytics Forum 2022
|
||||
- **Domain pivot:** "The foundations that make enterprise AI actually work — governed data, metadata, reliable pipelines — are what I build; ISE is where that work meets customers directly."
|
||||
- **Jargon level:** Technical (hiring-manager-readable, not HR-safe fluff)
|
||||
- **"Why them" hook:** Microsoft's USD 400M Swiss datacenter/data-residency expansion → the regulated Swiss enterprises he knows from the inside are exactly ISE Zürich's customer base
|
||||
- **Hook verification (2026-07-03, all VERIFIED):**
|
||||
- Engineering Fundamentals Playbook / "code-with" → https://microsoft.github.io/code-with-engineering-playbook/ (GitHub repo tagline: "the playbook for 'code-with' customer or partner engagements")
|
||||
- ISE blog enterprise RAG / permission propagation → https://devblogs.microsoft.com/ise/sharepoint-doc-level-access/ ("Propagating SharePoint Document Permissions to AI Search and RAG Pipelines")
|
||||
- USD 400M Swiss datacenter expansion, in-country data residency → announced 2025-06-02; https://www.itpro.com/infrastructure/data-centres/microsoft-invests-usd400-million-to-expand-swiss-data-centers
|
||||
|
||||
## Bullet Plan
|
||||
|
||||
Calibration: sent Google DE resume = 17 bullets (SW 6, BS 4, FC 2, VZ 2, GN 3), 2 pages clean. Recommended here: **16 confirmed + 2 fillers pending Page Fill Gate.**
|
||||
|
||||
### Position 1 — Swisscom · Staff Data, Analytics & AI Engineer (6 bullets, 12 lines)
|
||||
| # | ID | Achievement (ISE framing) | Variant | JD Match |
|
||||
|---|----|--------------------------|---------|----------|
|
||||
| 1 | SW-7 | LEAD — governed data products + active metadata on AWS **within Swisscom's company-wide Data Mesh** (scoped verb per feedback_swisscom_datamesh_ownership) — the grounded-retrieval data foundation downstream AI/agentic workflows query | 2L | Req 2+3 (AI systems in production, RAG/grounding) — Bridge high |
|
||||
| 2 | SW-3 | Python apps on Kubernetes + GitLab CI/CD — containerized, ML-ready delivery, agile DevOps | 2L | Req 1+5 Direct |
|
||||
| 3 | SW-1 | AWS migration of legacy Teradata/Oracle ETL → S3/Glue/Athena+Iceberg/Redshift/Airflow/CloudFormation | 2L | Req 5 Direct (cloud) |
|
||||
| 4 | SW-2 | Component Owner, business-critical Fulfillment ETL — on-call SLA, governance, data quality | 2L | Req 7 (DRI) Bridge high + Req 4 (data quality) |
|
||||
| 5 | SW-4 | B2B data products/dashboards, stakeholder partnership, root-cause analysis under 2nd/3rd-level support | 2L | Req 6 Direct (cross-functional, customer-facing) |
|
||||
| 6 | SW-6 | PySpark distributed processing (scale signal) | 2L | Req 5 supporting |
|
||||
|
||||
x SW-5 Security Champion — FORCED EXCLUSION (memory: team role not award, only when JD gates on security; JD doesn't)
|
||||
|
||||
### Position 2 — Bosch · title "(Senior) Data & ML Engineer" per title-flexibility rule (4 bullets, 8 lines)
|
||||
| # | ID | Achievement (ISE framing) | Variant | JD Match |
|
||||
|---|----|--------------------------|---------|----------|
|
||||
| 1 | BS-1 | LEAD — containerized ML inference (Docker/K8s/Ansible) into 24/7 semiconductor production; automated image-based defect classification | 2L | Req 2 DIRECT ("deploying and operating AI systems in production") — flagship |
|
||||
| 2 | BS-3+BS-5 | Application Owner + co-owned Spotfire analytics platform for internal customers — SLOs, C# extensions, training, vendor mgmt (TAF 2022 talk reserved for CL) | 2L | Req 6 Direct (customer-facing platform eng) + Req 7 |
|
||||
| 3 | BS-4 | ELK+Kafka anomaly-detection PoC with Grafana/Prometheus/Loki | 2L | Req 4 (performance monitoring/observability) |
|
||||
| 4 | BS-2 | Multi-language data services (Python/Java/C#) over OracleDB + Hadoop/ImpalaSQL | 2L | Req 1 Direct (polyglot: 3 of the JD's 6 languages) |
|
||||
|
||||
### Position 3 — Fraunhofer · Research Software Engineer (2 bullets, 4 lines)
|
||||
| # | ID | Achievement | Variant | JD Match |
|
||||
|---|----|-------------|---------|----------|
|
||||
| 1 | FC-2 | "Contributed" ML/NLP components to ARTUS sea-rescue transcription research (hedged verb MANDATORY) | 2L | Req 3 supporting (applied ML) |
|
||||
| 2 | FC-1 | SCEDAS C#/.NET development + independently established Jenkins CI/CD with quality gates | 2L | Req 1 (C#) + Req 5 (modern practices, initiative) |
|
||||
|
||||
o FC-3 MISSION microservices (Express.js/JavaScript/Docker) — FILLER #1 if Page Fill Gate needs it (JavaScript checkbox)
|
||||
|
||||
### Position 4 — Vizrt · DevOps Engineer, Bergen NO (2 bullets, 4 lines)
|
||||
| # | ID | Achievement | Variant | JD Match |
|
||||
|---|----|-------------|---------|----------|
|
||||
| 1 | VZ-1 | Python/C++ distributed video transcoding backend (CNN/BBC/Al Jazeera scale) | 2L | Req 1 (languages, distributed systems) + intl breadth |
|
||||
| 2 | VZ-2 | A/V test automation + CI/CD quality gates integration | 2L | Req 5 (engineering fundamentals — ISE playbook resonance) |
|
||||
|
||||
### Position 5 — Generali GDIS · Software Engineer → IT Consultant (2 bullets, 4 lines)
|
||||
| # | ID | Achievement | Variant | JD Match |
|
||||
|---|----|-------------|---------|----------|
|
||||
| 1 | GN-1 | Introduced BDD + technical ownership + Java Community evangelism/training | 2L | Req 6 (knowledge sharing/mentoring — strong ISE culture fit) |
|
||||
| 2 | GN-3 | Java/J2EE workflow-portal features, XLDeploy migration, Camel/Spring Boot PoC | 2L | Req 1 (Java checkbox early career) |
|
||||
|
||||
o GN-2 UIPath RPA — FILLER #2 (automation breadth; weakest)
|
||||
x CA-1 Capgemini — FORCED EXCLUSION (user preference: never list, 6-month stay)
|
||||
|
||||
**Budget:** 16 recommended 2L bullets (32 rendered lines) + up to 2 fillers → 16–18 vs proven 17-bullet 2-page layout. PASS range.
|
||||
**Skills plan (4-3-2-2-2):** (1) Programming & Data Engineering, (2) Cloud & Infrastructure (AWS + K8s/Docker), (3) AI/ML & GenAI tooling — incl. memory-verified LiteLLM, GitHub Copilot, custom GPTs, Kiro (NOT in taxonomy — flagged; NEVER LangChain), (4) DevOps & Observability, (5) Certifications (AWS SAA, IBM AI Engineering, Udacity).
|
||||
**Summary headline (draft):** "Staff Data & AI Engineer | Python · Java · AWS · Kubernetes | Production AI Foundations & Customer-Facing Platform Engineering"
|
||||
**Focus directive impact:** none given — hybrid priority-matrix defaults (ML/AI primary, DE secondary).
|
||||
|
||||
## Output Files
|
||||
- Resume: `output/Microsoft_ISE_Senior_SWE/e2e_microsoft_ise_resume.tex`
|
||||
- Cover Letter: `output/Microsoft_ISE_Senior_SWE/e2e_microsoft_ise_cover_letter.tex`
|
||||
- Critique: `output/Microsoft_ISE_Senior_SWE/critique_microsoft_ise.md`
|
||||
|
||||
## Status
|
||||
- Phase 0: DONE (confirmed by user 2026-07-03)
|
||||
- Phase 1: DONE (16 bullets confirmed 2026-07-03 + fillers FC-3/GN-2 authorized for Page Fill Gate; headline + skills plan approved as drafted)
|
||||
- Phase 2 Resume: DONE (2026-07-03)
|
||||
- Summary: DONE (543 rendered chars, 5 lines, orphan OK)
|
||||
- Skills: DONE (4-3-2-2-2, 13 dashes; AI/ML group carries memory-verified GenAI toolchain: LiteLLM, custom GPTs w/ grounding (RAG), prompt engineering, Copilot, Kiro — NO LangChain)
|
||||
- Swisscom (6 bullets): DONE — SW-7 lead scoped ("within Swisscom's company-wide Data Mesh")
|
||||
- Bosch (4 bullets): DONE — title "(Senior) Data & ML Engineer"; BS-4 honest "proof of concept" restored (Google version had dropped it)
|
||||
- Fraunhofer (3 bullets): DONE — FC-2 "Contributed" hedge; filler FC-3 added at Page Fill Gate
|
||||
- Vizrt (2 bullets): DONE
|
||||
- Generali (3 bullets): DONE — filler GN-2 added at Page Fill Gate
|
||||
- Compile: DONE — 2 pages, MiKTeX clean, 18 variable bullets all 189–210 rendered chars (max 218, zero OVER)
|
||||
- Page fill: page 2 fuller than sent Google baseline by one 2L bullet (baseline scored 85.5, cleared recruiter screen); strict ≤3-line rule not achievable without KB-unsupported padding
|
||||
- AI fingerprint scan: banned words CLEAN, 0 rendered em-dashes, no vague -ing endings, dates consistent
|
||||
- Cover Letter: DONE (2026-07-03)
|
||||
- 4 paragraphs, 299 words, 1 page, moderncv, MiKTeX clean compile (T1 fontenc + microtype expansion=false fix, same as Google CL)
|
||||
- Hooks: Playbook "code-with" (P1), ISE SharePoint-permissions-to-RAG blog (P2), USD 400M Swiss datacenter/data-residency (P4) — all web-verified, sources in Cover Letter Plan
|
||||
- Em-dashes: 0; banned-word scan clean; no generic opener; TAF 2022 talk used in P3 as planned (reserved for CL); AWS named honestly (SAA), no Azure claim
|
||||
- All claims traceable to resume bullets or verified memory; awaiting user approval at /make-cl STOP
|
||||
- Critique: CURRENT (Pass 2, 2026-07-03) — **85.8/100** → `critique_microsoft_ise.md`
|
||||
- **APPROVED + FINALIZED 2026-07-03.** Submission PDFs: `Dennis_Thiessen_Resume.pdf` (2pp) + `Dennis_Thiessen_Cover_Letter.pdf` (1pp), verified identical to latest compiles. Package complete (12 files + 2 submission copies).
|
||||
- **SENT 2026-07-03** — application submitted at apply.careers.microsoft.com (req 200040836). Logged in CLAUDE.md Active Sessions + job_scout decisions.json (applied, 85.8/100).
|
||||
- **Next:** await Microsoft recruiter response
|
||||
|
||||
## Critique Summary (Pass 2, 2026-07-03)
|
||||
- **Score: 85.8/100** (Pass 1: 83.3 → Tier 1+2 applied same day, user-directed). ATS 20/20, truthfulness PASS, AI-fingerprint CLEAN, JD integrity PASS. In the 85+ submit band.
|
||||
- **Applied fixes (resume only, CL untouched):** (1) "model evaluation" added to AI & ML skills line — JD RQ triple now verbatim; (2) "Open-source stack:" label on Kafka/Airflow/Spark line; (3) summary rewrite: +LLM, +cross-functional, on-call bound to Component Owner (precision), tail "platform co-ownership, workshops, training" dropped for 5-line budget (signal retained in BS-3/GN-1)
|
||||
- **NOT applied:** conditional metric for BS-1/SW-1 — KB has no verified numbers beyond 24/7 and 300mm; adding one would fabricate
|
||||
- **Compile verified:** 2pp, summary 5 lines no orphan, skills lines single-line, page break matches baseline
|
||||
- **Interview likelihood:** ATS 95% / Recruiter 80% / HR 80% / HM 65% / Panel 70%. Max ≈ 86.5; hard ceiling ≈ 88 (Azure, OSS contributions — not resume-editable)
|
||||
- **CL: PASS all 6 sub-checks** — hooks verified same-day with URLs
|
||||
- **Known exception:** page-2 bottom whitespace ~1/3 page (documented, matches sent Google baseline; padding would violate anti-fabrication)
|
||||
Reference in New Issue
Block a user