feat(resume): QuantCo Cloud Engineer package (sent, ~82/100)
- Full resume + cover letter + critique for QuantCo Cloud Engineer (Zürich) - Applied Tier 1+2 critique fixes: corrected education dates, hedged Data Mesh ownership, sharpened tagline/summary, added SRE token - Mark QuantCo Cloud Engineer + Equinor as sent in trackers - decisions.json: QuantCo Cloud Engineer -> applied Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -92,7 +92,29 @@
|
||||
"Bash(curl -s -m 20 -A Mozilla/5.0 -H 'X-Requested-With: XMLHttpRequest' 'https://bitcoin-suisse.onlyfy.jobs/candidate/job/ajax_list?display_length=50&page=1&sort=date&sort_dir=DESC&search=' -o /tmp/ajax.html)",
|
||||
"Bash(grep -oE 'icon-map-mark.{0,160}' /tmp/ajax.html)",
|
||||
"Bash(grep -oE 'job-title.*?icon-map-mark.{0,200}')",
|
||||
"Bash(grep -oiE '\\(icon-[a-z-]*\\).{0,80}\\(Zug|Switzerland|Schweiz|Copenhagen|Bratislava|Vaduz|Liechtenstein|Slovakia|Denmark\\)' /tmp/ajax.html)"
|
||||
"Bash(grep -oiE '\\(icon-[a-z-]*\\).{0,80}\\(Zug|Switzerland|Schweiz|Copenhagen|Bratislava|Vaduz|Liechtenstein|Slovakia|Denmark\\)' /tmp/ajax.html)",
|
||||
"Bash(job_scout/.venv/Scripts/python.exe job_scout/_probe.py)",
|
||||
"Bash(.venv/Scripts/python.exe -c ' *)",
|
||||
"Bash(grep -vE \"^$\")",
|
||||
"Bash(.venv/Scripts/python.exe -m py_compile scout.py)",
|
||||
"Bash(curl -s --max-time 20 \"https://api.lever.co/v0/postings/palantir?mode=json\")",
|
||||
"Bash(curl -s --max-time 20 \"https://api.smartrecruiters.com/v1/companies/QuantCo/postings?limit=1\")",
|
||||
"Bash(.venv/Scripts/python.exe _verify.py)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=palantir)",
|
||||
"Bash(echo \"exit=$?\")",
|
||||
"Bash(python -c \"import ast; ast.parse\\(open\\('scout.py',encoding='utf-8'\\).read\\(\\)\\); print\\('PARSE_OK'\\)\")",
|
||||
"PowerShell(Test-Path *)",
|
||||
"Bash(.venv/Scripts/python.exe _disc.py)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=swissgrid --include-weak)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=ruag --include-weak)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=ruag)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=sbb)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=bkw)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=quantco --include-weak)",
|
||||
"Bash(.venv/Scripts/python.exe -c \"import scout; print\\('automated:', len\\(scout.COMPANIES\\), '| manual:', len\\(scout.MANUAL_CHECK\\)\\)\")",
|
||||
"Bash(.venv/Scripts/python.exe scout.py)",
|
||||
"Bash(.venv/Scripts/python.exe scout.py --only=swissgrid)",
|
||||
"Bash(git push *)"
|
||||
]
|
||||
}
|
||||
}
|
||||
|
||||
@@ -137,7 +137,8 @@ _Update this section when starting/finishing a JD._
|
||||
| Apple Data Engineer (ISE, Zurich) | Critique DONE Pass 1 (78.5/100) | /edit-resume for Tier 1 fixes or submit |
|
||||
| Kraken AI Infrastructure | Critique DONE Pass 2 (84.5/100) — converged near max | Submit, or apply Tier 2 polish (agent orchestration / guardrails in skills) |
|
||||
| Google FDE GenAI (Zurich) | PAUSED — GenAI evidence gap too large; redirecting to data-eng/MLOps roles | Likely abandon |
|
||||
| Equinor AI Architect (Norway) | Critique DONE Pass 2 (80.0/100) — converged near ceiling ~81; Data Mesh overclaim fixed | Submit / finalize PDFs |
|
||||
| Equinor AI Architect (Norway) | **SENT** (~80/100) | Done — await response |
|
||||
| QuantCo Cloud Engineer (Europe/Zürich) | **SENT 2026-06-01** (~82/100, finalized PDFs) | Done — await response |
|
||||
|
||||
---
|
||||
|
||||
|
||||
+126
-126
@@ -1,128 +1,128 @@
|
||||
{
|
||||
"https://job-boards.greenhouse.io/anthropic/jobs/5204086008": {
|
||||
"company": "Anthropic",
|
||||
"title": "Solutions Architect, Applied AI",
|
||||
"decision": "shortlist",
|
||||
"note": "Top fit: applied-AI SA in Zurich, on-thesis (platform/SA, not model-building). Top comp. Candidate for tailored package.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/116958340671513286-staff-forward-deployed-engineer-genai-google-cloud?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Staff Forward Deployed Engineer, GenAI, Google Cloud",
|
||||
"decision": "paused",
|
||||
"note": "Overlaps the PAUSED 'Google FDE GenAI (Zurich)' session (GenAI evidence gap; was redirecting to data-eng/MLOps). Reassess via the Cloud/FDE platform angle rather than GenAI. Reuse existing FDE drafts.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://careers.cisco.com/global/en/job/2012401/Senior-Software-Engineer-Agent-Datapath-eBPF-Isovalent": {
|
||||
"company": "Cisco",
|
||||
"title": "Senior SW Engineer, Agent & Datapath (eBPF) - Isovalent",
|
||||
"decision": "shortlist",
|
||||
"note": "Cilium/eBPF cloud-native platform eng, CH-based. Strong on-thesis infra role.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.lever.co/quantco-/a7c4f142-b1ad-449c-a18e-bdbda41a3f86": {
|
||||
"company": "QuantCo",
|
||||
"title": "Cloud Engineer",
|
||||
"decision": "shortlist",
|
||||
"note": "k8s/cloud at high-comp boutique, Zurich hub. On platform thesis.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.lever.co/quantco-/67757fe8-3582-4bdd-aa7d-98fa490bde84": {
|
||||
"company": "QuantCo",
|
||||
"title": "AI Engineer",
|
||||
"decision": "maybe",
|
||||
"note": "High score but more ML-leaning than his platform thesis; prefer the Cloud Engineer role. Revisit only if framed as AI-platform/infra.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://nvidia.wd5.myworkdayjobs.com/job/UK-Remote/Senior-Solutions-Architect--HPC-and-AI_JR2007074": {
|
||||
"company": "NVIDIA",
|
||||
"title": "Senior Solutions Architect, HPC and AI",
|
||||
"decision": "shortlist",
|
||||
"note": "SA track (preferred over SWE at NVIDIA per profile). Remote UK/DE.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/5d344194-bbf0-48ce-bafd-f27c51b185b8": {
|
||||
"company": "Kraken",
|
||||
"title": "Solutions Architect - Payward Services",
|
||||
"decision": "shortlist",
|
||||
"note": "Architect + crypto + trading; remote incl. CH. Kraken has a prior package (AI Infrastructure session, 84.5/100) to draw on. Crypto background differentiating.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/4aacc5a1-a848-4b68-90b8-958b6e4a2d0b": {
|
||||
"company": "Kraken",
|
||||
"title": "AI Agents Solutions Architect - HR",
|
||||
"decision": "shortlist",
|
||||
"note": "Agentic + Python + crypto SA. HR-domain variant (also Finance/Compliance variants exist).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://bitcoin-suisse.onlyfy.jobs/job/fkt5dq31d58r2hdoa1pnyp6gykgpuu9": {
|
||||
"company": "Bitcoin Suisse",
|
||||
"title": "Solution Architect Trading",
|
||||
"decision": "shortlist",
|
||||
"note": "Crypto-native, architect, trading; Zug. Crypto background differentiating.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://job.bkw.com/offene-stellen/solution-architect-energiehandel-alle/99b88701-e999-4ff3-9585-b19963ed8237": {
|
||||
"company": "BKW (Bern)",
|
||||
"title": "Solution Architect Energiehandel",
|
||||
"decision": "shortlist",
|
||||
"note": "Bern WLB tier (lower comp OK). Energy-trading architect, local. The flagged Energiehandel role.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://job.bkw.com/offene-stellen/senior-quant-risk-modeller-all/1bb5e5b5-35d8-410f-b3d1-c156e6f9114c": {
|
||||
"company": "BKW (Bern)",
|
||||
"title": "Senior Quant Risk Modeller",
|
||||
"decision": "shortlist",
|
||||
"note": "Bern WLB tier; trading/quant, local. Fits energy-trading interest.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/100214884188201670-senior-research-data-scientist-merchant-shopping-data-science?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Senior Research Data Scientist, Merchant Shopping",
|
||||
"decision": "skip",
|
||||
"note": "Research / model-building, off-thesis (he targets data-eng/platform/infra, not DS research).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/anthropic/jobs/5197714008": {
|
||||
"company": "Anthropic",
|
||||
"title": "Senior Security SW Engineer, Linux Kernel Security",
|
||||
"decision": "skip",
|
||||
"note": "Kernel C / systems-security, off his stack (Python/Java/data-platform).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/e7480aaf-0a1b-4ed4-a047-37cc5b3b88a3": {
|
||||
"company": "Kraken",
|
||||
"title": "Account Executive, Trading-as-a-Service",
|
||||
"decision": "skip",
|
||||
"note": "Sales (AE), not engineering. Scored high on crypto/trading keywords only.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/083afacb-edf7-4920-8428-e6c6fb7aecc9": {
|
||||
"company": "Kraken",
|
||||
"title": "Senior Sales Trader, EMEA",
|
||||
"decision": "skip",
|
||||
"note": "Sales/trading desk, not engineering.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/ff2129b4-2fc9-4e8e-9c92-777279b377fe": {
|
||||
"company": "Kraken",
|
||||
"title": "Product Manager - Prop Trading - Breakout",
|
||||
"decision": "skip",
|
||||
"note": "PM, not engineering.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/2bb8285f-d45a-441b-8628-983a101006ce": {
|
||||
"company": "Kraken",
|
||||
"title": "Staff Product Designer - Consumer",
|
||||
"decision": "skip",
|
||||
"note": "Design, not engineering.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/126509648931889862-senior-staff-software-engineer-automotive-ai?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Senior Staff SW Engineer, Automotive AI",
|
||||
"decision": "skip",
|
||||
"note": "C++/automotive, weaker fit vs his Python/data-platform stack.",
|
||||
"date": "2026-06-01"
|
||||
}
|
||||
"https://job-boards.greenhouse.io/anthropic/jobs/5204086008": {
|
||||
"company": "Anthropic",
|
||||
"title": "Solutions Architect, Applied AI",
|
||||
"decision": "skip",
|
||||
"note": "BLOCKED on Phase 0 JD read: requires native/C1 German AND French (he has no French — config.md). Also a pre-sales role (5+ yrs SA/SE/TAM, partner with AEs, buying cycles), not his hands-on Staff Data/AI Eng profile. Keyword score masked both. Lesson: read JD before shortlisting SA-titled roles.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/116958340671513286-staff-forward-deployed-engineer-genai-google-cloud?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Staff Forward Deployed Engineer, GenAI, Google Cloud",
|
||||
"decision": "paused",
|
||||
"note": "Overlaps the PAUSED 'Google FDE GenAI (Zurich)' session (GenAI evidence gap; was redirecting to data-eng/MLOps). Reassess via the Cloud/FDE platform angle rather than GenAI. Reuse existing FDE drafts.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://careers.cisco.com/global/en/job/2012401/Senior-Software-Engineer-Agent-Datapath-eBPF-Isovalent": {
|
||||
"company": "Cisco",
|
||||
"title": "Senior SW Engineer, Agent & Datapath (eBPF) - Isovalent",
|
||||
"decision": "shortlist",
|
||||
"note": "Cilium/eBPF cloud-native platform eng, CH-based. Strong on-thesis infra role.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.lever.co/quantco-/a7c4f142-b1ad-449c-a18e-bdbda41a3f86": {
|
||||
"company": "QuantCo",
|
||||
"title": "Cloud Engineer",
|
||||
"decision": "applied",
|
||||
"note": "k8s/cloud at high-comp boutique, Zurich hub. On platform thesis. | SENT 2026-06-01 (resume+CL finalized, ~82/100).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.lever.co/quantco-/67757fe8-3582-4bdd-aa7d-98fa490bde84": {
|
||||
"company": "QuantCo",
|
||||
"title": "AI Engineer",
|
||||
"decision": "maybe",
|
||||
"note": "High score but more ML-leaning than his platform thesis; prefer the Cloud Engineer role. Revisit only if framed as AI-platform/infra.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://nvidia.wd5.myworkdayjobs.com/job/UK-Remote/Senior-Solutions-Architect--HPC-and-AI_JR2007074": {
|
||||
"company": "NVIDIA",
|
||||
"title": "Senior Solutions Architect, HPC and AI",
|
||||
"decision": "shortlist",
|
||||
"note": "SA track (preferred over SWE at NVIDIA per profile). Remote UK/DE.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/5d344194-bbf0-48ce-bafd-f27c51b185b8": {
|
||||
"company": "Kraken",
|
||||
"title": "Solutions Architect - Payward Services",
|
||||
"decision": "shortlist",
|
||||
"note": "Architect + crypto + trading; remote incl. CH. Kraken has a prior package (AI Infrastructure session, 84.5/100) to draw on. Crypto background differentiating.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/4aacc5a1-a848-4b68-90b8-958b6e4a2d0b": {
|
||||
"company": "Kraken",
|
||||
"title": "AI Agents Solutions Architect - HR",
|
||||
"decision": "shortlist",
|
||||
"note": "Agentic + Python + crypto SA. HR-domain variant (also Finance/Compliance variants exist).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://bitcoin-suisse.onlyfy.jobs/job/fkt5dq31d58r2hdoa1pnyp6gykgpuu9": {
|
||||
"company": "Bitcoin Suisse",
|
||||
"title": "Solution Architect Trading",
|
||||
"decision": "shortlist",
|
||||
"note": "Crypto-native, architect, trading; Zug. Crypto background differentiating.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://job.bkw.com/offene-stellen/solution-architect-energiehandel-alle/99b88701-e999-4ff3-9585-b19963ed8237": {
|
||||
"company": "BKW (Bern)",
|
||||
"title": "Solution Architect Energiehandel",
|
||||
"decision": "shortlist",
|
||||
"note": "Bern WLB tier (lower comp OK). Energy-trading architect, local. The flagged Energiehandel role.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://job.bkw.com/offene-stellen/senior-quant-risk-modeller-all/1bb5e5b5-35d8-410f-b3d1-c156e6f9114c": {
|
||||
"company": "BKW (Bern)",
|
||||
"title": "Senior Quant Risk Modeller",
|
||||
"decision": "shortlist",
|
||||
"note": "Bern WLB tier; trading/quant, local. Fits energy-trading interest.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/100214884188201670-senior-research-data-scientist-merchant-shopping-data-science?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Senior Research Data Scientist, Merchant Shopping",
|
||||
"decision": "skip",
|
||||
"note": "Research / model-building, off-thesis (he targets data-eng/platform/infra, not DS research).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://job-boards.greenhouse.io/anthropic/jobs/5197714008": {
|
||||
"company": "Anthropic",
|
||||
"title": "Senior Security SW Engineer, Linux Kernel Security",
|
||||
"decision": "skip",
|
||||
"note": "Kernel C / systems-security, off his stack (Python/Java/data-platform).",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/e7480aaf-0a1b-4ed4-a047-37cc5b3b88a3": {
|
||||
"company": "Kraken",
|
||||
"title": "Account Executive, Trading-as-a-Service",
|
||||
"decision": "skip",
|
||||
"note": "Sales (AE), not engineering. Scored high on crypto/trading keywords only.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/083afacb-edf7-4920-8428-e6c6fb7aecc9": {
|
||||
"company": "Kraken",
|
||||
"title": "Senior Sales Trader, EMEA",
|
||||
"decision": "skip",
|
||||
"note": "Sales/trading desk, not engineering.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/ff2129b4-2fc9-4e8e-9c92-777279b377fe": {
|
||||
"company": "Kraken",
|
||||
"title": "Product Manager - Prop Trading - Breakout",
|
||||
"decision": "skip",
|
||||
"note": "PM, not engineering.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://jobs.ashbyhq.com/kraken.com/2bb8285f-d45a-441b-8628-983a101006ce": {
|
||||
"company": "Kraken",
|
||||
"title": "Staff Product Designer - Consumer",
|
||||
"decision": "skip",
|
||||
"note": "Design, not engineering.",
|
||||
"date": "2026-06-01"
|
||||
},
|
||||
"https://www.google.com/about/careers/applications/jobs/results/126509648931889862-senior-staff-software-engineer-automotive-ai?location=Switzerland": {
|
||||
"company": "Google",
|
||||
"title": "Senior Staff SW Engineer, Automotive AI",
|
||||
"decision": "skip",
|
||||
"note": "C++/automotive, weaker fit vs his Python/data-platform stack.",
|
||||
"date": "2026-06-01"
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,20 @@
|
||||
TITLE: Cloud Engineer
|
||||
LOCATION: Europe | allLocations=['Europe']
|
||||
COMMITMENT: Full-Time or Part-Time | TEAM: Engineering | workplaceType=hybrid
|
||||
|
||||
=== DESCRIPTION (plain) ===
|
||||
QuantCo turns advances in artificial intelligence and statistical learning into real-world impact in leading enterprises and public sector organisations. Leveraging privileged data access and world-class expertise in AI, quantitative optimisation and engineering, we build scalable systems that drastically improve decisions that matter – from algorithmic pricing and data-driven claims management to precision medicine.
|
||||
|
||||
About the role
|
||||
QuantCo is expanding its cloud platform centred on AWS and Kubernetes to support an increasing range of production systems. You will help design, build, and operate this platform as we extend it beyond our existing customer production workloads to additional services and clusters, enabling future projects across the company.
|
||||
To support this growth, we are looking for an experienced engineer with deep cloud and Kubernetes expertise to strengthen our team. You will play a key role in scaling our platform, shaping architectural decisions, and driving best practices and automation across our infrastructure. As part of this role, you will collaborate closely with product teams to help deliver cloud-native applications that increase the business value of our most important products.
|
||||
|
||||
|
||||
=== Qualifications: ===
|
||||
3+ years of experience in DevOps, SRE, or related roles,Proficiency with containerization, Kubernetes, and Cloud Native technologies,Strong background in Linux and networking fundamentals.
|
||||
|
||||
=== ADDITIONAL ===
|
||||
About QuantCo
|
||||
At QuantCo, we leverage expertise in data science, engineering, and economics to help organizations turn data into decisions. Started by 4 PhDs from Harvard and Stanford, we are now more than 180 professionals with extensive quantitative, engineering, and business experience. We are globally distributed with offices in Berlin, Boston, Cologne, Karlsruhe, London, Munich, San Francisco, and Zurich.
|
||||
|
||||
Our solutions include algorithmic pricing, data-driven claims management, and high-dimensional forecasting systems. Our customers include some of the largest financial, retail, and hea
|
||||
@@ -0,0 +1,192 @@
|
||||
# Critique: QuantCo — Cloud Engineer (Zürich / Europe, hybrid)
|
||||
|
||||
**Resume File:** `output/QuantCo_Cloud_Engineer/e2e_quantco_cloud_engineer_resume.tex`
|
||||
**Cover Letter:** `output/QuantCo_Cloud_Engineer/e2e_quantco_cloud_engineer_cover_letter.tex`
|
||||
**Date:** 2026-06-01 · **Pass:** 1 (no prior critique)
|
||||
|
||||
---
|
||||
|
||||
## Domain-Specialist Lens (researched for this JD)
|
||||
|
||||
### Reviewer Persona
|
||||
A QuantCo platform/infra engineering lead (likely the person who owns the AWS+K8s platform today), backed by a Harvard/Stanford-PhD founder culture. Reads ~100–200 applicants for an "experienced engineer with deep cloud and Kubernetes expertise." Spends his day in Kubernetes manifests, AWS, IaC, CI/CD, and reliability work for high-stakes customer production (pricing, claims, healthcare). What makes him roll his eyes: buzzword salads, "data scientist who once touched K8s," vague "owned the cloud" with no operational detail. What impresses him: concrete owner-operator evidence — someone who has carried a pager, provisioned infra as code, and shipped to production where mistakes are expensive. He is allergic to overclaiming because he can detect shallow K8s in 30 seconds of conversation.
|
||||
|
||||
### Company Context
|
||||
QuantCo (~180 people, offices incl. Zürich) turns AI/statistical-learning into enterprise production: algorithmic pricing, data-driven claims, high-dimensional forecasting, precision medicine. Strong Python + open-source culture (tech.quantco.com blog; open-sources libs like **datajudge**). The role is explicitly owner-operator: design/build/operate the AWS+Kubernetes platform as it scales to more services/clusters, shape architecture, drive best practices + automation, partner with product teams on cloud-native apps.
|
||||
|
||||
### JD Vocabulary Extraction (ranked)
|
||||
| # | JD Term | Freq | Meaning at QuantCo | Resume Match? |
|
||||
|---|---------|------|--------------------|---------------|
|
||||
| 1 | Kubernetes (deep expertise) | 3× incl. title-line ask | Multi-cluster production K8s, operators, scaling | PARTIAL (honest "working," not deep — by design) |
|
||||
| 2 | AWS / cloud platform | 3× | Owner-operator of AWS production platform | YES (strong) |
|
||||
| 3 | DevOps / SRE | qual #1 | 3+ yrs hands-on ops + reliability | YES (DevOps) / PARTIAL (no SRE token) |
|
||||
| 4 | Cloud Native | 2× | Containerized apps, cloud-native delivery | YES |
|
||||
| 5 | design/build/operate + scale | body | Full platform lifecycle, scaling to new clusters | YES |
|
||||
| 6 | best practices + automation | body | IaC, CI/CD, quality gates | YES |
|
||||
| 7 | architecture / architectural decisions | body | Shape platform architecture | YES (iSAQB + IaC) |
|
||||
| 8 | collaborate with product teams | body | Deliver cloud-native apps for product teams | YES |
|
||||
| 9 | Linux + networking fundamentals | qual #3 | OS/network depth | PARTIAL (listed, no bullet evidence — networking light) |
|
||||
| 10 | production systems (high-stakes) | throughout | Reliability where errors are expensive | YES (on-call SLA, 24/7 fab) |
|
||||
|
||||
### Domain Vocabulary Map
|
||||
| Resume currently says | Could say for THIS JD | Why |
|
||||
|---|---|---|
|
||||
| "Cloud-focused **data engineer**" (summary open) | "Cloud & platform engineer" | JD wants a Cloud Engineer; leading with "data engineer" slightly under-signals the platform/infra identity the reviewer is scanning for |
|
||||
| "Data & Cloud Platform Engineer" (tagline) | "Cloud / Platform Engineer" | Same — the "Data &" prefix dilutes a pure cloud-infra read |
|
||||
| (no SRE token) | add "site reliability (SRE) practices" in skills | "SRE" is in the JD's first qualification; he does the work (on-call/SLOs), so the token is a truthful bridge |
|
||||
|
||||
### Gap Ranking
|
||||
- **Fatal:** None. The one fatal-adjacent risk — "deep Kubernetes expertise" (the JD's headline) — is a real depth gap, but it is a *spectrum* skill bridged with honest hands-on K8s at two employers, not a binary capability he lacks. Correctly NOT overclaimed.
|
||||
- **Serious:** Kubernetes *depth* relative to the "obvious fit" (multi-cluster/operators/GitOps); no SRE title; Terraform absent (CloudFormation instead); networking depth light.
|
||||
- **Cosmetic:** GitOps/service-mesh tooling (most non-specialist candidates also lack).
|
||||
|
||||
### Methodology Transfer Test
|
||||
| Achievement | How a QuantCo expert sees it |
|
||||
|---|---|
|
||||
| SW-1 AWS migration + CloudFormation IaC | "He's provisioned a production AWS platform as code — exactly the lifecycle we need him to own and scale." |
|
||||
| SW-3 K8s + GitLab CI/CD delivery | "He ships containerized Python to K8s through CI/CD — competent operator; question is cluster/operator depth." |
|
||||
| SW-7 Data Mesh for product teams | "He's built governed, discoverable services other teams consume — maps to our 'collaborate with product teams on cloud-native apps.'" |
|
||||
| SW-2 Component Owner + 2nd/3rd on-call | "He carries a pager for business-critical pipelines — real reliability ownership, not theoretical." |
|
||||
| BS-1 ML inference into 24/7 fab (Docker/K8s/Ansible) | "Zero-maintenance-window containerized deploy where mistakes cost yield — the high-stakes-production instinct we live by." |
|
||||
|
||||
### Competitive Landscape
|
||||
- **Obvious fit:** SRE/platform engineer with deep multi-cluster K8s + AWS + Terraform + GitOps + strong networking and an SRE title.
|
||||
- **Our advantage:** end-to-end owner-operator of a *business-critical* AWS platform (IaC + CI/CD + on-call) at national-telco scale, Staff level, plus a genuinely hard-mode production credential (24/7 semiconductor fab). Broader builder profile than a pure-ops SRE.
|
||||
- **Their advantage:** deeper K8s, Terraform, GitOps, networking, and the literal "SRE" pedigree the JD headlines.
|
||||
|
||||
---
|
||||
|
||||
## Five-Perspective Read-Through
|
||||
|
||||
### ATS Robot (keyword scan)
|
||||
| Keyword | Match |
|
||||
|---|---|
|
||||
| Cloud Engineer / cloud platform | ✓ (tagline, summary, exp header) |
|
||||
| AWS | ✓✓ (summary, skills, 2 bullets, CL) |
|
||||
| Kubernetes | ✓✓ (summary, skills, SW-3, BS-1) |
|
||||
| Cloud Native | ✓ (summary, skills, exp header) |
|
||||
| containerization / containerized | ✓ (skills, BS-1, FC-3) |
|
||||
| DevOps | ✓ (SW-3, Vizrt title) |
|
||||
| SRE | ✗ verbatim (semantic: on-call, SLA, SLO, reliability) |
|
||||
| Docker | ✓ |
|
||||
| Linux | ✓ (skills) |
|
||||
| networking fundamentals | ✓ verbatim (skills) |
|
||||
| IaC / CloudFormation | ✓✓ |
|
||||
| CI/CD / GitLab | ✓✓ |
|
||||
| automation | ✓ |
|
||||
| architecture | ✓ (skills, iSAQB, header) |
|
||||
| scalability / scale / clusters | ✓ (skills "scalability", CL "new services and clusters") |
|
||||
| product teams | ✓ (SW-7, SW-4, CL) |
|
||||
| Python | ✓✓ |
|
||||
| observability / Prometheus / Grafana | ✓ |
|
||||
| production systems | ✓✓ |
|
||||
| best practices | ✓ (DevSecOps, quality gates) |
|
||||
|
||||
**Match rate:** ~19/20 (SRE the only verbatim miss) = **~95% → PASS.**
|
||||
|
||||
### Recruiter Glance (10 seconds)
|
||||
**Verdict: Forward.** Staff engineer at Switzerland's largest telco, AWS SAA certified, tagline in target vocabulary, Bern→Zürich hybrid stated. Clears the bar instantly.
|
||||
|
||||
### HR Screen (30 seconds)
|
||||
**Verdict: Phone screen.** Summary bridges cleanly to cloud/AWS/IaC/K8s; 11+ years >> 3+ required; skills group names all signal platform/infra; first bullet per role is JD-relevant. Hybrid + citizenship resolve logistics.
|
||||
|
||||
### Hiring Manager (2 minutes)
|
||||
**Verdict: Interview (with K8s-depth probe).**
|
||||
**Top 3 observations:**
|
||||
1. Genuine owner-operator: IaC, CI/CD, and *on-call* together — not a data scientist cosplaying ops.
|
||||
2. The 24/7-fab containerized deploy is a memorable, high-stakes credential that mirrors QuantCo's "errors are expensive" ethos.
|
||||
3. Will immediately test Kubernetes depth — resume is honestly "hands-on delivery," not "deep," and he'll be asked to prove the ceiling.
|
||||
**Predicted first interview question:** "Walk me through the most complex thing you've operated on Kubernetes in production — cluster topology, how you handle rollouts/failures, and where CloudFormation stops and K8s begins."
|
||||
|
||||
### Technical Reviewer (10 minutes)
|
||||
**Truthfulness:** Mostly clean, **two issues** (see Tier 1):
|
||||
| Claim | Verified? | Note |
|
||||
|---|---|---|
|
||||
| "11+ years" | ✓ | Generali 2015 → 2026 = 11 yrs |
|
||||
| AWS SAA active to Sep 2027 | ✓ | 2024 cert, 3-yr validity |
|
||||
| K8s "deployed/operate," not "deep" | ✓ | Matches user directive — honest |
|
||||
| "**Built** a decentralized Data Mesh ... the discoverable platform foundation" | ⚠️ | Per KB, the ODP/Data Mesh is a **company-wide migration Dennis contributed to, NOT solo-built**. Resume verb over-owns the *platform*; CL correctly hedges ("helped build"). Inconsistent + overclaim. |
|
||||
| Education dates (M.Eng. Oct 2010–Jul 2013; B.Eng. Oct 2007–Sep 2010) | ✗ | **Contradicts `config.md` KB Corrections**: B.Eng. Oct 2009–Oct 2012; M.Eng. Apr 2012–Oct 2013 (intentional overlap). Current dates are factually wrong. |
|
||||
|
||||
**Consistency:** Resume vs CL Data Mesh ownership mismatch ("Built" vs "helped build") — align to the hedged version.
|
||||
**AI fingerprint:** Clean. 0 `---` em-dashes (rendered); no -ing analysis bullet endings; no Tier-1 banned words; CL opens company-specific (datajudge), sentence length varied. Pass.
|
||||
|
||||
---
|
||||
|
||||
## Eight-Dimension Scoring
|
||||
|
||||
| Dimension | Score | Weight | Weighted | Notes |
|
||||
|---|---|---|---|---|
|
||||
| ATS Keywords | 8.5/10 | 15% | 1.275 | ~95% match; SRE the only verbatim gap |
|
||||
| Summary | 8.0/10 | 10% | 0.80 | Strong bridge; opens "data engineer" — slightly under-signals cloud/platform |
|
||||
| Skills Section | 8.5/10 | 10% | 0.85 | Excellent group names + bold; networking listed; could add SRE token |
|
||||
| Bullet Quality | 8.0/10 | 25% | 2.00 | Well-reframed, honest K8s; quantification light (mostly qualitative); Data Mesh verb over-owns |
|
||||
| Credentials (pubs N/A) | 8.5/10 | 10% | 0.85 | AWS SAA + Udacity + iSAQB + ITIL — strong, JD-relevant cert stack |
|
||||
| Narrative Coherence | 8.0/10 | 15% | 1.20 | Clear platform/infra thread; "Data &" prefix mildly dilutes; clean reverse-chron arc |
|
||||
| Page Fill & Visual | 7.5/10 | 5% | 0.375 | 2pp, 0 overfull, clean; **page 2 ~⅓ white space** below ideal fill |
|
||||
| Credibility Signals | 7.5/10 | 10% | 0.75 | Staff title + telco scale + fab credential; dinged by edu-date error + Data Mesh overclaim |
|
||||
| **Total** | | **100%** | **81.0** | |
|
||||
|
||||
---
|
||||
|
||||
## Interview Likelihood
|
||||
|
||||
| Reader | Probability | Key Factor |
|
||||
|--------|------------|------------|
|
||||
| ATS | 95% | ~19/20 keyword match |
|
||||
| Recruiter (10s) | 90% | Staff @ telco + AWS cert + hybrid stated |
|
||||
| HR (30s) | 88% | Summary bridge + 11 yrs >> 3 required |
|
||||
| Hiring Manager (2m) | 70% | Owner-operator evidence strong; gated by K8s-depth question |
|
||||
| Technical Panel (10m) | 60% | Will probe deep K8s/networking; honest framing helps but depth is the ceiling |
|
||||
|
||||
**Ceiling:** Current **81.0** → with Tier-1 accuracy fixes + SRE token + summary sharpen **≈82.5** → hard ceiling **≈82–83** (the JD's "deep Kubernetes expertise" headline cannot be truthfully claimed; that gap caps the score regardless of polish). This is a *submit-grade* package — converged near its honest ceiling.
|
||||
|
||||
---
|
||||
|
||||
## Actionable Improvements
|
||||
|
||||
### Tier 1 (HIGH — accuracy; do these before submit)
|
||||
1. **Fix education dates** (`/edit-resume`). Current M.Eng. *Oct 2010–Jul 2013* and B.Eng. *Oct 2007–Sep 2010* contradict `config.md` KB Corrections. Correct to **B.Eng. Oct 2009–Oct 2012** and **M.Eng. Apr 2012–Oct 2013** (intentional overlap — do not "fix" the overlap). Note: Education is a FIXED template section, so the error is likely baked into the template/`.cls` source — fix at source so it stops re-appearing. **Accuracy > all.**
|
||||
2. **Hedge the Data Mesh verb** to match KB + the CL. Current: *"Built a decentralized Data Mesh of reusable, governed data products ... the discoverable platform foundation product teams query directly."* → e.g. *"Built reusable, governed data products with metadata management on Swisscom's decentralized Data Mesh (Glue, Athena, CloudFormation, CI/CD), now queried directly by product teams."* Owns his actual work (data products) without claiming he built the company-wide platform. Removes the resume↔CL inconsistency. **(+~0.5, accuracy)**
|
||||
|
||||
### Tier 2 (MEDIUM — optional polish)
|
||||
1. **Add an SRE token** to the Containers/CI-CD or Cloud skill line, e.g. "…site reliability (SRE) practices: on-call, SLOs, incident response." Truthful (he owns on-call/SLOs) and closes the only verbatim ATS gap. (+0.3)
|
||||
2. **Sharpen the summary open** from "Cloud-focused data engineer" → "Cloud and platform engineer" (keep the rest). Better matches what the reviewer scans for. (+0.3)
|
||||
3. **Tagline:** consider "Cloud / Platform Engineer" instead of "Data & Cloud Platform Engineer" to sharpen the infra identity. (+0.2)
|
||||
|
||||
### Tier 3 (COSMETIC — skip)
|
||||
1. Fill page 2 (~⅓ white space) — only if a strong reserve bullet exists; not worth padding. Acceptable as-is.
|
||||
2. Bullet 5 still surfaces "dashboards" — fine as the lowest-priority Swisscom bullet; not worth re-cutting.
|
||||
|
||||
### Verdict
|
||||
**Apply Tier 1 (both are accuracy fixes — mandatory before submit).** Tier 2 are nice-to-have and cheap; Tier 3 skip. After Tier 1, this is submit-ready at its honest ceiling (~82).
|
||||
|
||||
---
|
||||
|
||||
## Interview Bridge Points
|
||||
| Resume Topic | Target Equivalent | Opening Line |
|
||||
|---|---|---|
|
||||
| SW-1 AWS + CloudFormation | Owning/scaling QuantCo's AWS platform | "I've provisioned a production AWS estate as code end-to-end — the same lifecycle you need extended to more services and clusters." |
|
||||
| SW-3 K8s + GitLab CI/CD | Cloud-native delivery on their K8s | "I ship containerized Python to Kubernetes through CI/CD daily; here's exactly where my K8s depth is strong and where I'd ramp." |
|
||||
| SW-2 on-call / SLA | SRE/reliability for high-stakes prod | "I carry 2nd/3rd-level on-call for business-critical pipelines — reliability isn't abstract, it's my pager." |
|
||||
| BS-1 24/7 fab deploy | Production where errors are expensive | "I containerized ML inference into a fab line with no maintenance window — a bad deploy cost wafer yield, which is the mindset your pricing/claims work demands." |
|
||||
| SW-7 Data Mesh for product teams | Collaborating with product teams on cloud-native apps | "I built governed, discoverable data products other teams consume directly — the product-facing platform collaboration this role asks for." |
|
||||
| BS-4 ELK + Prometheus/Grafana | Observability best-practice | "I stood up centralized monitoring/alerting for 24/7 infra — observability as a default, not an afterthought." |
|
||||
| AWS SAA + iSAQB | Architectural decision-making | "My SAA and iSAQB background is why I think in trade-offs when shaping platform architecture, not just wiring services." |
|
||||
|
||||
---
|
||||
|
||||
## Cover Letter Critique
|
||||
|
||||
**Institution type:** Industry (high-comp engineering boutique). **Words:** 286 (target 250–300 ✓). **Pages:** 1 ✓.
|
||||
|
||||
- **6A Anti-patterns:** ✓ No generic opener (leads with QuantCo's platform expansion + datajudge); no CV-rehash-in-prose; names datajudge/tech.quantco.com; clear "why QuantCo"; strongest qual in P1; no apologetic gap language; active close ("talk about where you want to take the platform next"); no credential-dump.
|
||||
- **6B Tailoring:** ✓ Names datajudge, pytest, AWS+K8s expansion, Zürich; uses JD terms beyond the resume (open-source defaults, scaling to new services/clusters); references mission (high-stakes enterprise production).
|
||||
- **6C Industry:** ✓ Business value present ("a pricing or claims error is expensive," "a bad deploy costs wafer yield"); no "leaving X" framing; jargon appropriate for an engineering-led reader.
|
||||
- **6D ATS:** AWS, Kubernetes, CloudFormation, GitLab CI/CD, Data Mesh, Python, on-call — 7+ high-value terms. ✓
|
||||
- **6E Structural:** ✓ Varied sentence length; non-repeating paragraph openers; 286 words; results-driven tone; quantified-ish anchors. Clean.
|
||||
- **6F Package cohesion:** ✓ mostly — every CL claim traces to a resume bullet; complements (adds motivation + "why them") rather than repeats. **One flag:** CL says "**helped build** the company-wide Data Mesh" (correctly hedged) while the resume says "**Built** a decentralized Data Mesh." Fix the resume verb (Tier 1 #2) to align — the CL is the correct version.
|
||||
|
||||
---
|
||||
|
||||
*End of critique. Pass 1 — score 81.0/100. Submit-grade; apply 2 Tier-1 accuracy fixes first.*
|
||||
@@ -0,0 +1,41 @@
|
||||
\documentclass[11pt,a4paper,roman]{moderncv}
|
||||
\usepackage[english]{babel}
|
||||
\moderncvstyle{classic}
|
||||
\moderncvcolor{green}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage{ragged2e}
|
||||
\usepackage[scale=0.79]{geometry}
|
||||
\usepackage[version=4,arrows=pgf-filled]{mhchem}
|
||||
\renewcommand*{\makeletterclosing}{\par\vspace{2ex}\closingname\par}
|
||||
|
||||
% ========== CONTACT ==========
|
||||
\name{Dennis}{Thiessen}
|
||||
\address{Bern, Switzerland}
|
||||
\phone[mobile]{+41 795 955 585}
|
||||
\email{dennis@thiessen.io}
|
||||
% =============================
|
||||
|
||||
\begin{document}
|
||||
|
||||
\recipient{To}{QuantCo\\Engineering Team\\Z\"urich, Switzerland}
|
||||
\date{\today}
|
||||
\opening{Dear QuantCo Engineering Team,}
|
||||
\makelettertitle
|
||||
|
||||
\begin{justify}
|
||||
QuantCo is expanding the AWS and Kubernetes platform that already runs your customers' production pricing and claims systems, and your engineering blog sets a clear bar: open-source tooling with sensible defaults, like datajudge for testing database data inside pytest. That is the work I do now. As Staff Data, Analytics \& AI Engineer at Swisscom, Switzerland's largest telecom, I build and run the AWS data platform our business-critical pipelines depend on, and I'd bring that same builder-operator habit to your Cloud Engineer role in Z\"urich.
|
||||
|
||||
The throughline of my work is owning infrastructure end to end. At Swisscom I migrated a legacy Teradata and Oracle ETL estate to a cloud-native AWS stack (S3, Glue, Athena on Iceberg, Redshift, Airflow), provisioned as code with CloudFormation. I also helped build the company-wide Data Mesh that product teams now query directly: governed data products with metadata, shipped through GitLab CI/CD. I deploy and run our Python applications on Kubernetes, and I hold 2nd- and 3rd-level on-call for the pipelines, so reliability is not abstract to me. Earlier, in Bosch's 24/7 semiconductor fab in Dresden, I containerized ML defect-classification inference with Docker, Kubernetes, and Ansible into a line with no maintenance window, where a bad deploy costs wafer yield.
|
||||
|
||||
What draws me to QuantCo is the pairing: high-stakes enterprise production, where a pricing or claims error is expensive, alongside a small engineering-led team that open-sources its tools and argues about defaults. I'm AWS Solutions Architect certified, Bern-based, and glad to be in Z\"urich on a hybrid schedule. Where I'm most useful is the messy middle, running a platform while it scales to new services and clusters. I'd welcome the chance to talk about where you want to take the platform next.
|
||||
\end{justify}
|
||||
|
||||
\vspace{0.3cm}
|
||||
{Sincerely,\\
|
||||
Dennis Thiessen, M.Eng.\\
|
||||
Staff Data, Analytics \& AI Engineer\\
|
||||
Swisscom (Schweiz) AG}
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,162 @@
|
||||
\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 $\vert$ Open to Z\"urich (hybrid) $\cdot$ remote across DACH/EU}
|
||||
\address{{Cloud \& Platform Engineer $\vert$ AWS $\cdot$ IaC $\cdot$ CI/CD $\vert$ Cloud-Native Infrastructure \& Reliability}}
|
||||
|
||||
|
||||
\begin{document}
|
||||
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% SUMMARY
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection}{Summary}
|
||||
Cloud and platform engineer with 11+ years building and operating production infrastructure. Currently own Switzerland's largest telco's cloud-native data platform on \textbf{AWS} (S3, Glue, Athena/Iceberg, Redshift, \textbf{Airflow}) with \textbf{CloudFormation} IaC and \textbf{GitLab CI/CD}; earlier moved ML inference into a 24/7 Bosch semiconductor fab with \textbf{Docker} and \textbf{Kubernetes}. Build a decentralized \textbf{Data Mesh} of governed data products that downstream teams consume, and run pipelines under on-call SLA with strong observability and DevSecOps practice. \textbf{AWS Certified Solutions Architect}; \textbf{Python} expert.
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% TECHNICAL SKILLS — Format C, 5 groups (4-3-2-2-2)
|
||||
%----------------------------------------------------------------------------------------
|
||||
\begin{rSection}{Technical Skills}
|
||||
|
||||
\begin{skillgroup}{Cloud Platform \& Infrastructure as Code}
|
||||
\skilldash{\textbf{AWS} (S3, Glue, Athena/Iceberg, Redshift, Lambda, Step Functions, \textbf{Airflow}, CloudWatch, ECR/ECS)}
|
||||
\skilldash{\textbf{Infrastructure as Code} (\textbf{CloudFormation}), serverless and event-driven architecture, AWS SAA-certified}
|
||||
\skilldash{Cloud-native application delivery, multi-service platform operation, scalability and cost awareness}
|
||||
\skilldash{Linux, networking fundamentals, Bash / shell scripting, Git, software architecture (iSAQB)}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Containers, CI/CD \& Observability}
|
||||
\skilldash{\textbf{Kubernetes}, \textbf{Docker}, Ansible: containerized application deployment and orchestration}
|
||||
\skilldash{\textbf{GitLab CI/CD}, Jenkins: build, test and deploy automation, quality gates, DevSecOps}
|
||||
\skilldash{ELK Stack (Elasticsearch, Logstash, Kibana), \textbf{Grafana}, \textbf{Prometheus}, Loki, alerting, SRE on-call}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Data Engineering \& Pipelines}
|
||||
\skilldash{\textbf{Kafka}, \textbf{Airflow}, PySpark / Apache Spark, ETL/ELT design, data modeling, data governance}
|
||||
\skilldash{Teradata, OracleDB, Hadoop/ImpalaSQL, Data Mesh / data products, batch and stream processing}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Programming \& Tools}
|
||||
\skilldash{\textbf{Python} (expert), Java, SQL, JavaScript/TypeScript, FastAPI, Pandas, NumPy, pytest}
|
||||
\skilldash{C\# / .NET (legacy), C++ (legacy), Express.js, design patterns, Agile/Scrum, code review}
|
||||
\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-1, SW-7, SW-3, SW-2, SW-4, SW-6 ---
|
||||
\begin{rSubsection}{Cloud-Native AWS Data Platform: IaC, CI/CD \& Production Reliability}{\textcolor{black!60}{Oct 2023 -- Present}}{Staff Data, Analytics \& AI Engineer, Swisscom (Schweiz) AG}{Bern, Switzerland}
|
||||
\item Migrated Swisscom's legacy Teradata/Oracle ETL to a cloud-native \textbf{AWS} platform (S3, Glue, Athena/Iceberg, Redshift, \textbf{Airflow}) provisioned as code with \textbf{CloudFormation}, for serverless ML and analytics workloads.
|
||||
\item Built reusable, governed data products with metadata management on Swisscom's decentralized \textbf{Data Mesh}, served from \textbf{AWS} (Glue, Athena, CloudFormation, CI/CD) and queried directly by downstream product teams.
|
||||
\item Deployed and operate \textbf{Python} data applications on \textbf{Kubernetes} with \textbf{GitLab CI/CD}, owning containerized delivery from build and test through production rollout in an agile DevOps team across multiple data products.
|
||||
\item Own business-critical Fulfillment and Product Analysis ETL pipelines (Oracle, \textbf{Kafka} to Teradata in \textbf{Python}) as Component Owner, enforcing data governance and SLA compliance under 2nd/3rd-level on-call support.
|
||||
\item Deliver data products and dashboards for B2B product teams and drive \textbf{Python} process automation, running 3rd-level root cause analysis to keep platform pipelines reliable and available across recurring workflows.
|
||||
\item Apply \textbf{PySpark} and distributed computing in the Swisscom Data Lake, extending \textbf{Python} pipeline capabilities to large-scale batch workloads for Fulfillment and Product Analysis data.
|
||||
\end{rSubsection}
|
||||
|
||||
% --- Bosch (Feb 2020 -- Dec 2022) — BS-1, BS-4, BS-3, BS-2 ---
|
||||
\begin{rSubsection}{Production Containerization \& Observability in 24/7 Semiconductor Manufacturing}{\textcolor{black!60}{Feb 2020 -- Dec 2022}}{(Senior) Data \& ML Engineer, Robert Bosch Semiconductor Manufacturing}{Dresden, Germany}
|
||||
\item Containerized and orchestrated production deployment (\textbf{Docker}, \textbf{Kubernetes}, Ansible) of automated image-based defect classification in Bosch's 24/7 semiconductor fab across 300mm wafer lines without downtime.
|
||||
\item Delivered an anomaly-detection and observability stack (ELK with \textbf{Kafka} on \textbf{Docker}, plus \textbf{Grafana}, \textbf{Prometheus} and Loki), giving centralized monitoring and alerting for 24/7 manufacturing infrastructure.
|
||||
\item Served as Application Owner for the semiconductor analytics suite and upstream pipelines, defining SLOs, managing software vendors, and delivering user training and documentation to keep systems reliable 24/7.
|
||||
\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-1, FC-3 ---
|
||||
\begin{rSubsection}{CI/CD Automation \& Containerized Microservice Engineering}{\textcolor{black!60}{Sep 2018 -- Oct 2019}}{Research Software Engineer, Fraunhofer-Center for Maritime Logistics CML}{Hamburg, Germany}
|
||||
\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, \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, GN-2 ---
|
||||
\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 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 internal RPA contact for group companies, extending automation from test tooling into 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{iSAQB CPSA -- Foundation Level}, iSAQB (2016). Certified Professional for Software Architecture.
|
||||
\item \textbf{ITIL Foundation Certificate in IT Service Management}, PEOPLECERT / AXELOS (2016).
|
||||
\item \textbf{IBM AI Engineering Specialization}, Coursera. Deep learning, TensorFlow, Keras, Apache Spark ML.
|
||||
\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,124 @@
|
||||
# Session: QuantCo — Cloud Engineer
|
||||
|
||||
## JD Info
|
||||
- **File:** output/QuantCo_Cloud_Engineer/JD_QuantCo_Cloud_Engineer.txt
|
||||
- **Role:** Cloud Engineer
|
||||
- **Company:** QuantCo (AI/statistical-learning enterprise solutions boutique; ~180 people; Harvard/Stanford PhD founders; offices incl. Zürich)
|
||||
- **Bundle:** Data Platform / Infra (primary) + Staff/Senior Data Engineer (secondary, for reframing)
|
||||
- **Format:** Resume (2-page, resume.cls) + 1-page cover letter
|
||||
- **Salary/Details:** Europe, hybrid, full- or part-time, Engineering team. Zürich hub commutable from Bern. Clears comp bar (QuantCo Zürich is a high-comp boutique). Source: job_scout decision log (shortlist).
|
||||
|
||||
## JD Analysis
|
||||
### Requirements
|
||||
| # | Requirement | Match | Evidence |
|
||||
|---|-------------|-------|----------|
|
||||
| 1 | 3+ yrs DevOps, SRE, or related | **Direct** | Swisscom DevOps team (K8s deploys, GitLab CI/CD, on-call SLA) since 2023; Bosch ML orchestration. ~10 yrs total eng. |
|
||||
| 2 | Containerization, Kubernetes, Cloud Native | **Direct (working)** | Docker strong; deployed & operated Python apps on K8s (SW-3) + Bosch ML inference on Docker/K8s. K8s = working/hands-on proficiency, **not deep/expert** (user-corrected — do not oversell). |
|
||||
| 3 | Linux + networking fundamentals | **Bridge (MED)** | Linux across Swisscom/Bosch/Fraunhofer; networking is implicit (cluster/pipeline ops) — lighter explicit evidence. |
|
||||
| 4 | Design/build/operate AWS + Kubernetes platform; scale, shape architecture | **Direct** | SW-1 AWS migration (S3/Glue/Athena/Redshift/Airflow/CloudFormation); SW-3 K8s+CI/CD; SW-7 Data Mesh on AWS + IaC; AWS SAA cert (2024). |
|
||||
| 5 | Drive best practices + automation across infrastructure | **Direct** | IaC via CloudFormation (SW-1/SW-7); GitLab CI/CD automation (SW-3); DevSecOps / Security Champion (SW-5). |
|
||||
| 6 | Collaborate with product teams to deliver cloud-native applications | **Direct** | SW-4 (B2B data products w/ Product Owner); SW-7 (data products consumed downstream); SW-3 (containerized service delivery). |
|
||||
| 7 | "Deep cloud and Kubernetes expertise" / experienced engineer | **Bridge (MED-HIGH)** | Deep on AWS / IaC / CI-CD / reliability (SAA cert 2024, Udacity Data Eng 2026, Staff/Engineer IV). K8s is competent-not-deep — the **one area lighter** than the JD's headline ask; lead cloud/platform depth, keep K8s honest. |
|
||||
|
||||
### ATS Keywords
|
||||
- **Cloud/Infra:** AWS, Kubernetes, cloud-native, containerization, Docker, IaC, CloudFormation, S3, Glue, Athena, Redshift, Lambda, Step Functions
|
||||
- **DevOps/SRE:** DevOps, SRE, CI/CD, GitLab, automation, on-call, SLA, reliability, observability, DevSecOps
|
||||
- **Platform:** platform engineering, scalable systems, architecture, multi-cluster, production workloads
|
||||
- **Languages/OS:** Python, Linux, networking, Bash
|
||||
- **Domain:** data platform, data pipelines, Data Mesh, enterprise production systems
|
||||
|
||||
### Gap Assessment
|
||||
- **Direct:** Docker, AWS (S3/Glue/Athena/Redshift/CloudFormation), GitLab CI/CD, IaC, DevOps, on-call/reliability, Python, Linux, cloud-native delivery, AWS SAA cert, Staff-level ownership.
|
||||
- **Bridge:** Kubernetes **depth** (deployed/operated apps on K8s = working proficiency, NOT deep/expert per user — frame as hands-on delivery, never "deep K8s expertise") · SRE title (owns on-call SLA + reliability, not titled SRE — MED-HIGH) · Terraform (uses CloudFormation; IaC transfers — MED) · networking fundamentals (MED).
|
||||
- **Gap (do NOT claim):** "deep/expert Kubernetes" · Terraform specifically · advanced K8s operators / service mesh / GitOps tooling · multi-cluster ops at QuantCo's scale.
|
||||
|
||||
## Company Context
|
||||
- **Mission:** Turn advances in AI / statistical learning into real-world impact for leading enterprises + public sector (algorithmic pricing, data-driven claims management, high-dimensional forecasting, precision medicine).
|
||||
- **This role:** QuantCo is expanding its **AWS + Kubernetes** cloud platform beyond existing customer production workloads to more services/clusters. Owner-operator: design/build/operate the platform, shape architecture, drive best practices + automation, partner with product teams on cloud-native apps.
|
||||
- **Culture:** Rigorous, engineering-led (Harvard/Stanford PhD founders, ~180 people); strong Python + open-source tooling culture (tech.quantco.com blog; open-sources libs e.g. datajudge); "good defaults + automation for Python projects." High-stakes enterprise production (pricing/claims/healthcare).
|
||||
- **"Why them" angle:** His Swisscom work *is* building/operating the governed, scalable AWS platform (Data Mesh, IaC, K8s, CI/CD) that QuantCo is now expanding — same builder-operator profile, enterprise-production rigor, AWS+K8s stack. Zürich hub, hybrid, commutable from Bern; high-comp boutique clears his bar.
|
||||
|
||||
## Framing Strategy
|
||||
- **Lead narrative:** Staff-level platform/DevOps engineer who designs, builds, and operates **AWS** cloud platforms for business-critical production at a national telco — full lifecycle from IaC and CI/CD to on-call reliability — with hands-on containerized (Docker/Kubernetes) delivery. (Lead AWS/IaC/reliability depth; K8s is supporting, framed as hands-on delivery — NOT "deep/expert.")
|
||||
- **Reframing map:** Component Owner / on-call SLA → SRE & production reliability · AWS migration → design/build/operate cloud platform · Data Mesh data products → cloud-native services for product teams · CloudFormation → IaC / infrastructure automation · Security Champion → security best-practices embedded in platform.
|
||||
- **Emphasize (in order):** SW-1 (AWS migration), SW-7 (Data Mesh + metadata + IaC = platform for product teams), SW-3 (GitLab CI/CD + containerized delivery — framed as delivery automation, K8s present but not headline), SW-5 (DevSecOps best practices), Bosch ML inference on Docker/K8s, AWS SAA + Udacity Data Eng certs.
|
||||
- **Downplay:** pure analytics/BI/dashboards (SW-4 → secondary), academic/research, ML modeling depth.
|
||||
- **CL hooks:** QuantCo expanding AWS+K8s platform; open-source engineering culture (datajudge / tech.quantco.com); high-stakes enterprise production → his business-critical pipeline ownership under SLA.
|
||||
- **User directives:** Position as platform / infra / DevOps (on-thesis); NOT model-building. Crypto not relevant here.
|
||||
|
||||
## Critique Context (captured in Phase 0, used in /critique)
|
||||
- **Reviewer persona:** QuantCo platform/infra engineering lead. Values deep K8s + AWS, automation/IaC, production reliability, clean pragmatic engineering. Bored by buzzwords; impressed by concrete ownership, scale, and reliability discipline.
|
||||
- **Competitive landscape:** SRE / platform engineers with deep multi-cluster K8s + AWS + Terraform + strong networking. The "obvious fit" has Terraform, GitOps, and SLO/SLI ops. Our edge: end-to-end ownership of a business-critical AWS platform + IaC + CI/CD + DevSecOps at a national telco, Staff-level. Our soft spots: **Kubernetes depth (working, not deep — the JD's headline ask)**, Terraform (CloudFormation instead), networking depth, no SRE title.
|
||||
- **Domain vocabulary:** cloud-native, Kubernetes (controllers/operators), IaC, GitOps, observability, SLO/SLI, multi-cluster, platform engineering, automation.
|
||||
|
||||
## Cover Letter Plan
|
||||
- **Institution type:** Industry (high-comp engineering boutique)
|
||||
- **Paragraph count:** 3-4 paragraphs, ~250-300 words (1 page)
|
||||
- **P1 hook:** QuantCo expanding its AWS + Kubernetes platform / engineering-led, open-source culture → his fit as a builder-operator of exactly that stack.
|
||||
- **P2-P3 evidence:** AWS migration ownership (SW-1) + K8s & GitLab CI/CD (SW-3) + Data Mesh/IaC platform serving product teams (SW-7) + DevSecOps (SW-5); production reliability under on-call SLA.
|
||||
- **Domain pivot:** none major (already platform/infra). Light bridge: on-call SLA ownership → SRE/reliability.
|
||||
- **Jargon level:** Technical.
|
||||
- **"Why them" hook:** high-stakes enterprise production + rigorous engineering culture; Zürich hybrid.
|
||||
|
||||
## Bullet Plan (CONFIRMED 2026-06-01)
|
||||
|
||||
Lead AWS/IaC/CI-CD/reliability; K8s honest (delivery, not "deep"); downplay ML-modeling, GenAI/agent, analytics/BI.
|
||||
|
||||
### Swisscom (5 core + reserves)
|
||||
| # | ID | Achievement | Variant | Rationale |
|
||||
|---|----|-------------|---------|-----------|
|
||||
| 1 | SW-1 | AWS migration (S3/Glue/Athena·Iceberg/Redshift/Airflow/CloudFormation IaC) | 2L | Direct AWS/IaC |
|
||||
| 2 | SW-7 | Data Mesh + data products + metadata on AWS | 2L | platform/architecture, product-team foundation |
|
||||
| 3 | SW-3 | Containerized Python apps on K8s + GitLab CI/CD | 2L | CI/CD + delivery automation (K8s honest) |
|
||||
| 4 | SW-2 | Component Owner ETL + on-call SLA | 2L | reliability/SRE bridge |
|
||||
| 5 | SW-4 | Data products for product teams + automation | 2L | product-team collaboration |
|
||||
| (o) | SW-6 | PySpark | 2L | reserve |
|
||||
| (x) | SW-5 | Security Champion | — | omit per KB (JD ≠ security) |
|
||||
|
||||
### Bosch (4)
|
||||
| # | ID | Achievement | Variant | Rationale |
|
||||
|---|----|-------------|---------|-----------|
|
||||
| 1 | BS-1 | Containerized production deployment (Docker/K8s/Ansible) | 2L | cloud-native orchestration (NOT ML-modeling framing) |
|
||||
| 2 | BS-4 | Observability: ELK + Kafka + Grafana/Prometheus/Loki | 2L | observability best-practice |
|
||||
| 3 | BS-3 | Application Owner — SLOs, reliability, vendor mgmt | 2L | reliability ownership |
|
||||
| 4 | BS-2 | Multi-language data services over Oracle + Hadoop/Impala | 2L | data-access platform |
|
||||
|
||||
### Fraunhofer (2)
|
||||
| # | ID | Achievement | Variant | Rationale |
|
||||
|---|----|-------------|---------|-----------|
|
||||
| 1 | FC-1 | Jenkins CI/CD from zero + SCEDAS (C#/.NET) | 2L | CI/CD initiative |
|
||||
| 2 | FC-3 | MISSION microservices (Express.js/Docker/SQLite) | 2L | early containerized microservices |
|
||||
| (x) | FC-2 | ARTUS ML/NLP | — | off-thesis |
|
||||
|
||||
### Vizrt (2)
|
||||
| # | ID | Achievement | Variant | Rationale |
|
||||
|---|----|-------------|---------|-----------|
|
||||
| 1 | VZ-1 | Distributed real-time transcoding backend (Python, legacy C++) | 2L | distributed backend |
|
||||
| 2 | VZ-2 | A/V test suite + CI/CD quality gates | 2L | CI/CD |
|
||||
|
||||
### Generali (1 core + reserves)
|
||||
| # | ID | Achievement | Variant | Rationale |
|
||||
|---|----|-------------|---------|-----------|
|
||||
| 1 | GN-1 | BDD ownership + Jenkins CI/CD + team enablement | 2L | CI/CD/automation initiative |
|
||||
| (o) | GN-3 | Java/J2EE + XLDeploy + Camel/Spring PoC | 2L | reserve (legacy backend) |
|
||||
| (o) | GN-2 | UIPath RPA PoC | 2L | reserve |
|
||||
|
||||
**Budget:** 14 core (*) + reserves (SW-6, GN-3, GN-2) → target ~16-18 at page-fill gate. Forced exclusions: SW-5, Terraform, "deep/expert K8s", service-mesh/GitOps.
|
||||
|
||||
## Output Files
|
||||
- Resume: `output/QuantCo_Cloud_Engineer/e2e_quantco_cloud_engineer_resume.tex`
|
||||
- Cover Letter: `output/QuantCo_Cloud_Engineer/e2e_quantco_cloud_engineer_cover_letter.tex`
|
||||
- Critique: `output/QuantCo_Cloud_Engineer/critique_quantco_cloud_engineer.md`
|
||||
|
||||
## Status
|
||||
- Phase 0: DONE
|
||||
- Phase 1: DONE (17 bullets: Swisscom 6, Bosch 4, Fraunhofer 2, Vizrt 2, Generali 3)
|
||||
- Phase 2 Resume: DONE — Summary, Skills (4-3-2-2-2), 17 bullets, compiled 2 pages, 0 overfull, 0 em-dashes (rendered), char gate passed (no OVER)
|
||||
- Cover Letter: DONE — 1 page, 286 words, 3 paragraphs; 0 em-dashes; hooks verified (datajudge, AWS+K8s platform expansion). K8s honest, Data Mesh hedged.
|
||||
- Critique: CURRENT — Pass 1, **81.0/100** → Tier 1+2 fixes APPLIED 2026-06-01 (est. ~82, honest ceiling). Fixes: (1) education dates corrected to B.Eng. Oct 2009–Oct 2012, M.Eng. Apr 2012–Oct 2013 (overlap preserved); (2) Data Mesh bullet hedged to data-products framing (matches CL); (3) tagline → "Cloud & Platform Engineer"; (4) summary open → "Cloud and platform engineer"; (5) "SRE on-call" added to observability skills line. Recompiled: 2pp, 0 overfull, no orphans, char gate OK. ATS now ~20/20. AI fingerprint clean. CL unchanged (286w, 1pp, cohesive).
|
||||
- **NOTE for future JDs:** the resume template had education dates baked in WRONG (M.Eng. Oct 2010–Jul 2013, B.Eng. Oct 2007–Sep 2010). Fixed in this output only — check/fix template source so it stops recurring.
|
||||
- **Resume:** DONE — output/QuantCo_Cloud_Engineer/e2e_quantco_cloud_engineer_resume.pdf (2 pp)
|
||||
- **Cover Letter:** DONE — output/QuantCo_Cloud_Engineer/e2e_quantco_cloud_engineer_cover_letter.pdf (1 pp, 286 words)
|
||||
- **Next:** /clear, then /critique output/QuantCo_Cloud_Engineer/session_quantco_cloud_engineer.md
|
||||
- **Next Critique:** /critique output/QuantCo_Cloud_Engineer/session_quantco_cloud_engineer.md
|
||||
- **Note:** K8s deliberately framed as working/hands-on (NOT deep/expert) per user. SW-5 omitted per KB.
|
||||
Reference in New Issue
Block a user