chore(applications): archive BIS + NATO submitted packages, ignore tmp/
Add BIS Basel and NATO JWC Stavanger application output (resume/CV, cover letter, session file, critique) plus the Bundeswehr experience file backing the NATO package; update session status tables in AGENTS.md/CLAUDE.md; record two new Bash allowlist entries for the job scout venv. tmp/ is scratch working files, now gitignored. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Claude Sonnet 5
@@ -0,0 +1,270 @@
|
||||
# Critique: Bank for International Settlements - Senior Data & Analytics Engineer - Artificial Intelligence
|
||||
|
||||
**Resume:** `output/BIS/e2e_bis_senior_data_analytics_ai_resume.tex`
|
||||
**Cover letter:** `output/BIS/e2e_bis_senior_data_analytics_ai_cover_letter.tex`
|
||||
**JD source:** `JDs/bis_senior_data_analytics_ai.txt` - live BIS careers scrape, 10 Jul 2026
|
||||
**Date:** 10 Jul 2026
|
||||
|
||||
---
|
||||
|
||||
## 1. Domain-Specialist Lens
|
||||
|
||||
### Reviewer persona
|
||||
|
||||
The likely first technical reader is a senior applied-AI or data-platform engineer in BIS Banking Technology's Architecture, Platforms and Intelligence team. They run reliable internal applications in a risk-sensitive international institution, translate business needs into services, and will have reviewed candidates with direct RAG/LLM, financial-data and model-lifecycle experience. They will discount generic “AI” language, but production ML operating experience in a 24/7 fab is a distinctive signal.
|
||||
|
||||
### Company context
|
||||
|
||||
BIS supports central banks and financial stability through banking services, research and technology. This is an applied engineering role in Banking Technology, not an academic ML role: dependable data, controlled integration, operational support, security and clear communication matter as much as model capability. Project Gaia and Project Voyager make LLM-enabled analysis of unstructured information a credible near-term context.
|
||||
|
||||
### JD vocabulary extraction
|
||||
|
||||
| # | JD term | Importance | Meaning here | Resume match |
|
||||
|---|---|---|---|---|
|
||||
| 1 | AI application testing and evaluation | Highest | Repeatable evidence that LLM applications behave as intended | No |
|
||||
| 2 | Data pipelines / engineering for AI | Highest | Reliable, governed preparation and supply of data to AI applications | Yes |
|
||||
| 3 | Python | Highest | Day-to-day application and data engineering | Yes |
|
||||
| 4 | Unstructured-data exploration / preprocessing | High | Preparing text, documents or other raw content for AI use | Partial |
|
||||
| 5 | APIs / model integration | High | Connecting AI capability safely to existing systems | Partial-to-yes |
|
||||
| 6 | Monitor, maintain and update models | High | Production ownership beyond deployment | Partial |
|
||||
| 7 | Applied AI applications / production support | High | Business-facing services that must keep operating | Yes |
|
||||
| 8 | Requirements and stakeholders | Medium | Turning business needs into maintainable applications | Yes |
|
||||
| 9 | Financial / banking environment | Nice to have | Financial structure, treasury or asset-management context | No |
|
||||
| 10 | Junior support / mentoring | Nice to have | Task-specific support and coaching | Partial |
|
||||
|
||||
### Domain vocabulary map
|
||||
|
||||
| Resume currently says | BIS-oriented reading | Why |
|
||||
|---|---|---|
|
||||
| Governed data products and metadata | Governed, discoverable data for AI applications | Closely maps data work to the role without claiming LLM ownership. |
|
||||
| Production ML inference | Applied-AI application operated in production | Shows operational discipline relevant to the Bank. |
|
||||
| REST APIs / data services | Interfaces for integrating AI-enabled services | Truthful bridge, but not evidence of owning a model-integration platform. |
|
||||
| Grafana / Prometheus / ELK | Observability and production support | Maps to maintaining deployed systems, not model retraining. |
|
||||
| ARTUS NLP / speech recognition | Unstructured audio and NLP bridge | Relevant adjacent experience; it must remain a contribution, not LLM expertise. |
|
||||
|
||||
### Gap ranking
|
||||
|
||||
- **Functional screen risk:** Formal LLM testing/evaluation methodology. This is a stated principal accountability and cannot be filled by the current evidence.
|
||||
- **Serious competitive gaps:** Direct LLM-application ownership; large unstructured-document preprocessing; model updating/lifecycle ownership; banking or financial-data experience.
|
||||
- **Cosmetic gaps:** Explicit mentoring evidence and external representation. The Bosch training and TIBCO co-presentation are helpful but do not establish a mentoring record.
|
||||
|
||||
### Methodology transfer test
|
||||
|
||||
| Resume achievement | How a BIS reviewer can map it |
|
||||
|---|---|
|
||||
| Bosch containerised ML inference | Evidence that Dennis can deploy an ML-dependent application under strict availability constraints; the missing piece is LLM-specific evaluation. |
|
||||
| Swisscom governed data products and metadata | A credible foundation for controlled, discoverable data used by downstream AI applications. |
|
||||
| Swisscom Python/Kafka ETL ownership | Direct evidence of Python, data quality, incidents and SLA ownership for data services. |
|
||||
| Bosch application ownership and observability | Relevant to operating AI-adjacent applications and stakeholder support, though not proof of model updating. |
|
||||
| Fraunhofer ARTUS and MISSION | A truthful bridge from NLP and API integration to LLM-enabled applications, without overstating depth. |
|
||||
|
||||
### Competitive landscape
|
||||
|
||||
- **Obvious fit candidate:** An LLM/RAG engineer from a bank, consultancy or regulated enterprise with evaluation harnesses, document pipelines, guardrails and model monitoring.
|
||||
- **Dennis's advantage:** Genuine deployment and operations of ML in a 24/7 industrial environment, current governed cloud data-platform work, and clear Python/data-pipeline ownership.
|
||||
- **Their advantage:** Direct financial-services context plus formal LLM evaluation and lifecycle experience.
|
||||
|
||||
---
|
||||
|
||||
## 2. Five-Perspective Read-Through
|
||||
|
||||
### ATS robot
|
||||
|
||||
| Keyword / phrase | Resume result |
|
||||
|---|---|
|
||||
| Python | Exact |
|
||||
| Data pipelines / ETL | Exact |
|
||||
| Data engineering | Exact |
|
||||
| Analytics / data analysis | Exact / semantic |
|
||||
| Applied AI / ML | Exact |
|
||||
| LLM applications | Partial: LiteLLM and custom GPTs, no application ownership |
|
||||
| LLM testing / evaluation | Absent |
|
||||
| Unstructured data preprocessing | Partial: image classification and speech transcription, no document-data claim |
|
||||
| APIs / interfaces | Exact |
|
||||
| Model integration | Partial |
|
||||
| Model monitoring / maintenance | Partial: observability and production support |
|
||||
| Production support | Exact |
|
||||
| Business requirements | Partial: stakeholder and product-owner work |
|
||||
| Stakeholders | Exact |
|
||||
| Financial / banking | Absent |
|
||||
| Mentoring junior staff | Partial: user training and colleague training |
|
||||
| Docker / Kubernetes | Exact |
|
||||
| AWS / cloud data platform | Exact |
|
||||
| Data governance / quality | Exact |
|
||||
| English | Exact |
|
||||
|
||||
**Match rate:** 16/20 exact or defensible semantic matches (80%). The four gaps are concentrated in the most differentiating LLM/financial requirements, so the numerical match overstates the practical fit somewhat.
|
||||
|
||||
### Recruiter glance (10 seconds)
|
||||
|
||||
**Verdict: Forward.** Current Staff Data & AI Engineer at Swisscom, 11+ years, Python/Kubernetes/AWS and production ML are immediately credible for a senior hybrid data/AI role; direct LLM depth is not visible in the first glance.
|
||||
|
||||
### HR screen (30 seconds)
|
||||
|
||||
**Verdict: Phone screen.** The summary and skills clear the degree, Python, data-engineering and applied-AI requirements. HR may use the mandatory portal answers to clarify that LLM integration is real but limited and that formal LLM evaluation is not yet a proven responsibility.
|
||||
|
||||
### Hiring manager read (2 minutes)
|
||||
|
||||
**Verdict: Maybe interview.**
|
||||
|
||||
1. Bosch production ML is the strongest differentiator and gives the application operational credibility.
|
||||
2. Swisscom makes the data-platform and production-support fit clear.
|
||||
3. The hiring manager will quickly test the gap between LiteLLM/custom GPT exposure and the role's request for LLM testing, evaluation, integration and model maintenance.
|
||||
|
||||
**Predicted first question:** “Describe how you would design an evaluation and monitoring approach for an LLM application that extracts information from unstructured documents.”
|
||||
|
||||
### Deep technical reviewer (10 minutes)
|
||||
|
||||
**Truthfulness: clean, with one documentation correction already respected.** The 2025/26 Security Champion wording follows `config.md`, which overrides outdated three-year wording in the historical Swisscom experience file. The package does not claim LangChain, RAG, direct LLM application ownership, banking experience, formal LLM evaluation, or model retraining.
|
||||
|
||||
| Claim family | Result | Evidence source |
|
||||
|---|---|---|
|
||||
| Swisscom AWS data products, Python/Kubernetes, Kafka/ETL, PySpark | Verified | `resume_builder/experience/experience_swisscom.md` (SW-2, SW-3, SW-6, SW-7) |
|
||||
| Bosch production ML, data services, application ownership, Spotfire | Verified | `resume_builder/experience/experience_bosch.md` (BS-1, BS-2, BS-3, BS-5) |
|
||||
| Fraunhofer ARTUS, MISSION and Jenkins | Verified and appropriately hedged | `resume_builder/experience/experience_fraunhofer.md` (FC-1, FC-2, FC-3) |
|
||||
| Vizrt and Generali Python/quality/integration work | Verified | `experience_vizrt.md`, `experience_generali.md` |
|
||||
| LiteLLM, custom GPTs, Kiro and Copilot | Verified scope: created/used LiteLLM APIs and custom GPTs; no framework substitution | `config.md` corrections log |
|
||||
|
||||
**Consistency:** Resume and cover letter agree on Bosch ML, Swisscom pipeline ownership, Fraunhofer NLP, and the LLM boundary. No inflated company-wide ownership or unsupported publication claim appears.
|
||||
|
||||
---
|
||||
|
||||
## 3. Eight-Dimension Scoring
|
||||
|
||||
| Dimension | Score | Weight | Weighted | Notes |
|
||||
|---|---:|---:|---:|---|
|
||||
| ATS keyword match | 8.0/10 | 15% | 1.20 | 80% coverage, but the missing terms are high-value. |
|
||||
| Summary | 8.4/10 | 10% | 0.84 | Strong production/data bridge; LLM limitation is necessarily outside the pitch. |
|
||||
| Skills section | 8.0/10 | 10% | 0.80 | Specific and accurate. LiteLLM scope could be made more explicit. |
|
||||
| Bullet quality | 8.0/10 | 25% | 2.00 | Strong evidence; limited quantified outcomes and no LLM-evaluation evidence. |
|
||||
| Publications / research selection | 8.0/10 | 10% | 0.80 | No publication section is appropriate for this engineering role; Fraunhofer research is used proportionately. |
|
||||
| Narrative coherence | 8.4/10 | 15% | 1.26 | Clear infrastructure-first applied-AI narrative from Bosch to Swisscom. |
|
||||
| Page fill and visual | 6.5/10 | 5% | 0.33 | Clean two-page rendering, but Bosch is split across pages and page 2 has visible unused space. |
|
||||
| Credibility signals | 8.2/10 | 10% | 0.82 | Swisscom, Bosch production ML, Application Owner and AWS certification are credible senior signals. |
|
||||
| **Total** | | **100%** | **8.05 / 10 = 80.5 / 100** | Strong, with structural background gaps. |
|
||||
|
||||
---
|
||||
|
||||
## 4. Interview Likelihood
|
||||
|
||||
| Reader | Probability | Key factor |
|
||||
|---|---:|---|
|
||||
| ATS | 70% | Strong general data/AI terms, but evaluation and banking terms are absent. |
|
||||
| Recruiter (10s) | 75% | Senior Swisscom title and production ML are easy to understand. |
|
||||
| HR (30s) | 70% | Clears core engineering requirements; portal answers need to frame LLM scope carefully. |
|
||||
| Hiring manager (2m) | 50% | Production engineering is strong, but direct LLM evaluation is the decisive gap. |
|
||||
| Technical panel (10m) | 55% | Credible engineering depth if invited; expect rigorous LLM-evaluation questions. |
|
||||
|
||||
| Ceiling scenario | Estimated score |
|
||||
|---|---:|
|
||||
| Current package | 80.5 |
|
||||
| With the recommended scope clarification and visual improvement | 82.0 |
|
||||
| Best possible truthful package today | 83.0 |
|
||||
| Structural ceiling without direct LLM evaluation / banking experience | 84.0 |
|
||||
|
||||
The ceiling is driven by background rather than resume quality. Do not try to close it with invented terminology.
|
||||
|
||||
---
|
||||
|
||||
## 5. Tiered Improvements
|
||||
|
||||
### Tier 1 - high impact
|
||||
|
||||
1. **Improve the page-two continuation and fill** - **+1.0 to 1.5 points.** The Bosch heading and first bullet land on page 1 while the remaining Bosch bullets start page 2, which interrupts the strongest evidence block. If the two-line-only preference can be relaxed, expand selected page-2 Bosch/Fraunhofer bullets using already verified details; otherwise accept the sparse page rather than adding unsupported claims. This needs an intentional layout edit, not a wording-only tweak.
|
||||
2. **Make LiteLLM integration scope exact in the skills line** - **+1.0 point.** Replace `LiteLLM API gateway` with `LiteLLM API gateway (created and used APIs)` if it fits the line. This adds truthful evidence for the portal's integration question without implying LLM evaluation or ownership.
|
||||
|
||||
### Tier 2 - optional
|
||||
|
||||
1. Add a precise AI-application phrase to the summary, for example: `I bring Python, data-pipeline, API and production-support experience for AI applications.` This improves exact JD-language matching without changing the claim. **+0.5 points.**
|
||||
2. In the cover letter, replace the broad phrase `AI-adjacent data systems` with `data and ML systems` to reinforce the real Bosch signal. **+0.3 points.**
|
||||
|
||||
### Tier 3 - cosmetic / skip
|
||||
|
||||
1. Add more quantification only if a source provides it. The current 24/7 and 300mm context is useful; invented percentage impacts would damage credibility.
|
||||
2. Add a banking keyword solely for ATS. This would be misleading and should not be done.
|
||||
|
||||
**Verdict:** Apply the two Tier 1 changes if you want the strongest possible presentation before submission. Do not modify the package to imitate direct LLM-evaluation or banking experience.
|
||||
|
||||
---
|
||||
|
||||
## 6. Interview Bridge Points
|
||||
|
||||
| Resume topic | BIS equivalent | Opening line for interview |
|
||||
|---|---|---|
|
||||
| Bosch production ML inference | Operating an AI application in a constrained environment | “At Bosch, the key lesson was that model inference only creates value when deployment, availability and support work alongside the live operation.” |
|
||||
| Swisscom data products and metadata | Governed AI-ready information foundation | “At Swisscom, I work on the part that makes downstream AI usable: data products have to be discoverable, governed and dependable before an application can rely on them.” |
|
||||
| Python/Kafka ETL ownership | Reliable data preparation and production support | “I own Python/Kafka pipelines with data-quality and on-call accountability, so I approach AI inputs as production dependencies rather than one-off datasets.” |
|
||||
| Bosch application ownership and observability | Maintaining deployed services | “Application ownership taught me to pair delivery with SLOs, user communication and monitoring; I would apply that same discipline to AI-enabled applications.” |
|
||||
| ARTUS NLP contribution | Bridge to unstructured information | “ARTUS gave me hands-on experience contributing NLP and speech-recognition components; I would be transparent that my next growth step is formal LLM evaluation.” |
|
||||
| MISSION REST microservices | Integration interfaces | “I have built containerised REST services for data exchange, which is the integration discipline I would bring when connecting model-enabled capabilities to existing systems.” |
|
||||
|
||||
---
|
||||
|
||||
## 7. Cover Letter Critique
|
||||
|
||||
### 7A. Anti-patterns
|
||||
|
||||
- Pass: opens with a specific BIS Project Gaia reference, not a generic application sentence.
|
||||
- Pass: strongest relevant evidence, Bosch production ML, appears in paragraph 2 and is prepared in paragraph 1.
|
||||
- Pass: no defensive or apologetic background-gap wording.
|
||||
- Pass: active close invites a conversation.
|
||||
- Pass: no AI-fingerprint banned words or generic-opener phrases found.
|
||||
- Partial: it uses a prose summary of Bosch/Swisscom/Fraunhofer evidence, but adds the required motivation and institution context rather than merely copying bullets.
|
||||
|
||||
### 7B. Tailoring and context
|
||||
|
||||
- Pass: names Project Gaia and Project Voyager.
|
||||
- Pass: uses applied AI, LLMs, unstructured disclosures, data, governance, integration and maintenance vocabulary.
|
||||
- Pass: accurately treats BIS as an international financial institution and Banking Technology as an applied engineering setting.
|
||||
- Pass: connects governed data and production ML operations to the Bank's needs.
|
||||
|
||||
### 7C. Industry-specific checks
|
||||
|
||||
- Pass: business and operational value is clear through dependable data, production operation and 24/7 manufacturing context.
|
||||
- Pass: jargon remains readable for a recruiter.
|
||||
- Partial: it has no quantified business outcome beyond the 24/7 operating context; do not fabricate one.
|
||||
|
||||
### 7D. CL ATS check
|
||||
|
||||
The letter covers 7/10 priority terms or close variants: AI/ML, LLMs, unstructured data, data, APIs/data services, production operation/maintenance, and Python/Kafka pipelines. It does not claim testing/evaluation methodology, model updates, financial experience or mentoring.
|
||||
|
||||
### 7E. Structural checks
|
||||
|
||||
- Pass: 281 words, one page, correctly addressed, consistent date and contact details.
|
||||
- Pass: claims trace back to resume bullets or the verified BIS project context.
|
||||
- Pass: three varied paragraphs and no generic opener.
|
||||
- Partial: one 24/7 operating context is the only quantitative signal, but that is preferable to unsupported impact numbers.
|
||||
|
||||
### 7F. Package cohesion
|
||||
|
||||
The resume stands alone for production ML and data engineering. The cover letter deepens why BIS through Gaia and Voyager, without introducing untraceable personal achievements. There are no contradictions. Total package length is three pages.
|
||||
|
||||
---
|
||||
|
||||
## 8. Post-Generation Verification
|
||||
|
||||
### Mechanical
|
||||
|
||||
- Pass: all 20 variable experience bullets are within the two-line character target; the five short certification entries are fixed content.
|
||||
- Pass: no overfull or underfull box warnings in the successful resume-check or cover-letter compilation.
|
||||
- Pass: resume compiles to two pages; cover letter compiles to one page.
|
||||
- Pass: all multi-line bullets have usable final-line fill; none ends in an `-ing` analysis phrase. The ARTUS bullet ends in the noun “setting”, not an analysis construction.
|
||||
- **Needs improvement:** the resume's Bosch block is split across pages and page 2 has more unused space than the stated page-fill preference allows.
|
||||
|
||||
### Content
|
||||
|
||||
- Pass: 80% exact or defensible semantic ATS coverage.
|
||||
- Pass: configured email is `dennis@thiessen.io` throughout.
|
||||
- Pass: provenance and verb discipline are correct; Fraunhofer contribution verbs are hedged and Swisscom scope is not company-wide ownership.
|
||||
- Pass: no LangChain, LangGraph, LlamaIndex, banking, direct LLM-evaluation, or model-retraining claim.
|
||||
- Pass: cover-letter claims are traceable to the resume or verified BIS project information.
|
||||
|
||||
### Structural and AI-fingerprint scan
|
||||
|
||||
- Pass: Bank for International Settlements and Banking Technology are spelled consistently.
|
||||
- Pass: both `.tex` files have standalone preambles and compiled successfully.
|
||||
- Pass: employment dates use a consistent month-year format.
|
||||
- Pass: no Tier-1 banned words, banned generic phrases or `---` em-dash tokens were found in either document.
|
||||
- Pass: cover letter has varied paragraph openings and no generic opener.
|
||||
|
||||
*End of critique.*
|
||||
@@ -0,0 +1,40 @@
|
||||
\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}
|
||||
|
||||
\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 Committee}{Architecture, Platforms and Intelligence\\Bank for International Settlements\\Basel, Switzerland}
|
||||
\date{\today}
|
||||
\opening{Dear Members of the Hiring Committee,}
|
||||
\makelettertitle
|
||||
|
||||
\begin{justify}
|
||||
BIS's Project Gaia caught my attention because it applies LLMs to a real data problem: extracting usable climate-risk indicators from unstructured corporate disclosures despite differing reporting frameworks. That emphasis on dependable data, explicit technical choices and useful applications for central banks fits the work I do today. As a Staff Data, Analytics \& AI Engineer at Swisscom, I build governed data products and metadata on AWS that make enterprise information discoverable for analytics and AI. I am applying for the Senior Data \& Analytics Engineer -- Artificial Intelligence role to bring that production mindset to Banking Technology.
|
||||
|
||||
My strongest production ML experience came at Bosch Semiconductor in Dresden. I designed and deployed Docker- and Kubernetes-based ML inference for automated image classification in a 24/7 wafer fab, where delivery had to operate alongside live manufacturing. I also built data services over OracleDB and Hadoop/ImpalaSQL for analysis applications, held Application Owner responsibility, and added observability through an ELK/Kafka proof of concept with Grafana and Prometheus. At Swisscom, I pair that operating discipline with Component Owner responsibility for business-critical Python/Kafka pipelines and their data quality, governance, incident response and on-call SLA.
|
||||
|
||||
Earlier, at Fraunhofer CML, I contributed ML and NLP components to ARTUS, an automatic sea-rescue transcription project, and built containerized REST microservices for maritime data exchange. This gives me a practical bridge from NLP research to the LLM-enabled application work BIS is pursuing through Project Voyager. I would welcome a conversation about how my experience deploying and operating AI-adjacent data systems can support your team as it evaluates, integrates and maintains applications for the Bank.
|
||||
\end{justify}
|
||||
|
||||
\vspace{0.3cm}
|
||||
{Sincerely,\\
|
||||
Dennis Thiessen, M.Eng.\\
|
||||
Staff Data, Analytics \& AI Engineer\\
|
||||
Swisscom (Schweiz) AG}
|
||||
|
||||
\end{document}
|
||||
@@ -0,0 +1,140 @@
|
||||
\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}}
|
||||
|
||||
\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$ Open to Basel hybrid work}
|
||||
\address{{Senior Data \& AI Engineer $\vert$ Production ML, Data Platforms \& Applied NLP}}
|
||||
|
||||
\begin{document}
|
||||
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Summary}
|
||||
Senior data \& AI engineer with 11+ years delivering software across telecom, manufacturing and applied research. At Swisscom I build governed data products and metadata on \textbf{AWS} for dependable analytics and AI, while operating \textbf{Python} services on \textbf{Kubernetes}. At Bosch I designed and deployed containerised \textbf{ML} inference for image classification in a 24/7 semiconductor fab; at Fraunhofer I contributed NLP for sea-rescue transcription. I bring Python, data-pipeline, API and production-support experience, backed by AWS Solutions Architect certification.
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Technical Skills}
|
||||
|
||||
\begin{skillgroup}{Applied AI \& Production ML}
|
||||
\skilldash{\textbf{Python}, production \textbf{ML} inference deployment, MLOps, image classification, Pandas, NumPy}
|
||||
\skilldash{\textbf{Docker}, \textbf{Kubernetes}, Ansible, containerised deployment, GitLab CI/CD, Jenkins}
|
||||
\skilldash{Applied NLP and speech recognition (Fraunhofer ARTUS contributor); PyTorch, Scikit-learn}
|
||||
\skilldash{\textbf{LiteLLM} API gateway, custom GPTs with domain knowledge, prompt engineering, Kiro, Copilot}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Data Engineering \& Analytics}
|
||||
\skilldash{ETL/ELT design and operations, \textbf{Apache Kafka}, \textbf{Apache Airflow}, PySpark / Spark, SQL}
|
||||
\skilldash{Data products, metadata management, data governance, data quality, data modelling, analytical services}
|
||||
\skilldash{Oracle, Teradata, Hadoop/Impala, Athena, Redshift, MS SQL; query tuning and data warehousing}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Cloud, APIs \& Operations}
|
||||
\skilldash{\textbf{AWS} (S3, Glue, Athena/Iceberg, Redshift, Lambda, Step Functions, CloudWatch), SAA-certified}
|
||||
\skilldash{REST APIs, FastAPI, Flask, Express.js; CloudFormation, serverless and event-driven architecture}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Observability \& Engineering Quality}
|
||||
\skilldash{\textbf{Grafana}, \textbf{Prometheus}, Loki, ELK; alerting, incident response and production support}
|
||||
\skilldash{pytest, BDD/Serenity, Selenium, CI/CD quality gates, code review and test automation}
|
||||
\end{skillgroup}
|
||||
|
||||
\begin{skillgroup}{Certifications}
|
||||
\skilldash{\textbf{AWS Certified Solutions Architect -- Associate} (active to Sep 2027), Data Engineering with AWS}
|
||||
\skilldash{iSAQB CPSA -- Foundation, IBM AI Engineering Specialization, AI for Trading Nanodegree}
|
||||
\end{skillgroup}
|
||||
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\begin{rSection}{Professional Experience}
|
||||
|
||||
\begin{rSubsection}{Governed Data Products, Metadata \& AI-Ready Platform Operations}{\textcolor{black!60}{Oct 2023 -- Present}}{Staff Data, Analytics \& AI Engineer, Swisscom (Schweiz) AG}{Bern, Switzerland}
|
||||
\item Build governed data products and manage metadata within Swisscom's Data Mesh on \textbf{AWS} (Glue, Athena, CloudFormation), creating dependable, discoverable sources for analytics and downstream AI workloads.
|
||||
\item Design, deploy and operate \textbf{Python} data applications on \textbf{Kubernetes} with \textbf{GitLab CI/CD}, owning containerised delivery from build and test through production rollout and operation in an agile DevOps team.
|
||||
\item Migrated my domains' Oracle/Teradata \textbf{ETL} to Swisscom's \textbf{AWS} platform (Glue, Athena/Iceberg, Redshift, \textbf{Airflow}), reducing manual operations with reliable, scalable serverless processing for analytics.
|
||||
\item Own business-critical Fulfillment \textbf{ETL} pipelines from Oracle and \textbf{Kafka} to Teradata in \textbf{Python}, accountable for data quality, governance, incident response and restoration under an on-call SLA.
|
||||
\item Deliver stakeholder data products, analyses and dashboards; partner with product owners on backlog priorities, automate recurring work and investigate production issues through 2nd/3rd-level support.
|
||||
\item Apply \textbf{PySpark} for distributed processing in the Swisscom Data Lake, extending Python and SQL pipelines to large-scale batch workloads across Fulfillment and Product Analysis business domains.
|
||||
\item Serve as Swisscom's 2025/26 Security Champion, the team's security point of contact, applying secure-development and risk-management training to enterprise data-pipeline delivery and operations.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Production ML Deployment, Data Services \& Application 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 with \textbf{Docker}, \textbf{Kubernetes} and Ansible in Bosch's 24/7 semiconductor fab, running automated image-based defect classification on 300mm wafer production lines.
|
||||
\item Built data services in \textbf{Python}, Java and C\# over OracleDB and Hadoop/ImpalaSQL, supplying semiconductor analysis applications with structured process and defect data for 24/7 manufacturing operations.
|
||||
\item Served as Application Owner for semiconductor analytics applications and pipelines, defining SLOs, training users, maintaining documentation and coordinating stakeholders for dependable 24/7 operations.
|
||||
\item Co-owned Bosch's TIBCO Spotfire analytics platform for semiconductor engineers, developing C\# extensions and wafer-map visualisations; co-presented this work at the TIBCO Analytics Forum 2022.
|
||||
\item Delivered an anomaly-detection proof of concept using ELK and \textbf{Kafka} on \textbf{Docker}, adding \textbf{Grafana}, \textbf{Prometheus} and Loki monitoring to validate centralised monitoring and alerting for manufacturing systems.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Applied NLP Research, API Integration \& CI/CD Automation}{\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 for automatic transcription of sea-rescue communications, applying speech recognition in a safety-critical maritime setting.
|
||||
\item Contributed to a Fraunhofer research-grant proposal for ML-based prediction of maintenance timing in maritime operations, applying AI concepts to equipment reliability in a critical logistics domain.
|
||||
\item Built containerised REST microservices with Express.js, JavaScript, \textbf{Docker} and SQLite for MISSION, a Fraunhofer platform that enabled structured data exchange between maritime logistics stakeholders.
|
||||
\item Independently set up the team's first Jenkins \textbf{CI/CD} pipeline with quality gates, establishing build automation while developing SCEDAS decision-support software in C\#, .NET, MS SQL and Entity Framework.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Distributed Backend Engineering \& Automated Quality Gates}{\textcolor{black!60}{Jul 2017 -- May 2018}}{DevOps Engineer, Vizrt}{Bergen, Norway}
|
||||
\item Engineered distributed real-time video-transcoding backend components in \textbf{Python} and C++ for Vizrt's broadcast platform, contributing to a production A/V processing pipeline for media customers.
|
||||
\item Built Python integration and unit tests for A/V streaming, then integrated quality gates into the \textbf{CI/CD} pipeline to improve developer feedback cycles and release reliability for broadcast software.
|
||||
\end{rSubsection}
|
||||
|
||||
\begin{rSubsection}{Engineering Quality, Application Development \& Integration}{\textcolor{black!60}{May 2015 -- Jun 2017}}{IT Consultant, Generali Deutschland Informatik Services}{Hamburg, Germany}
|
||||
\item Introduced BDD test automation at Generali using Serenity-BDD, Selenium and JBehave; ran the proof of concept, owned implementation, administered Jenkins jobs and trained colleagues in the Java community.
|
||||
\item Developed Java/J2EE workflow features, migrated WebServices to the XLDeploy deployment process and contributed to an Apache Camel / Spring Boot integration proof of concept for internal applications.
|
||||
\end{rSubsection}
|
||||
|
||||
\end{rSection}
|
||||
\vspace{-0.15cm}
|
||||
|
||||
\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}
|
||||
|
||||
\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,155 @@
|
||||
# Session: Bank for International Settlements — Senior Data & Analytics Engineer – Artificial Intelligence
|
||||
|
||||
## JD Info
|
||||
|
||||
- **File:** JDs/bis_senior_data_analytics_ai.txt
|
||||
- **JD source:** live scrape 2026-07-10 via BIS careers site
|
||||
- **Role:** Senior Data & Analytics Engineer – Artificial Intelligence
|
||||
- **Company:** Bank for International Settlements (BIS), Architecture, Platforms and Intelligence / Banking Technology
|
||||
- **Bundle:** ML / AI Engineer (primary) + Staff / Senior Data Engineer (hybrid)
|
||||
- **Format:** Resume (2-page) + 1-page cover letter
|
||||
- **Location / contract:** Basel, Switzerland; hybrid; 3-year fixed term; deadline 24 Jul 2026
|
||||
- **Salary / benefits:** BIS states that salaries and benefits are internationally competitive, normally tax-exempt in Basel, with a defined-benefit pension. Exact offer is not published.
|
||||
|
||||
## JD Analysis
|
||||
|
||||
### Requirements
|
||||
|
||||
| # | Requirement | Match | Evidence |
|
||||
|---|-------------|-------|----------|
|
||||
| 1 | Relevant degree or equivalent hands-on experience | Direct | M.Eng. in Software Design & Engineering; 10+ years professional engineering experience |
|
||||
| 2 | Proven record designing, building and optimising cutting-edge AI solutions | Bridge — MED | Designed and deployed ML inference for 24/7 Bosch semiconductor production; current AI-enabling data foundation at Swisscom. No claim of LLM solution ownership. |
|
||||
| 3 | Data pipelines, analytical models and data engineering for AI use cases | Direct | Swisscom Component Owner for Kafka/Python ETL and AWS data-platform migration; Bosch production ML data services. |
|
||||
| 4 | Python | Direct | Expert-level pipeline and application work at Swisscom; data services and ML/NLP contributions at Bosch and Fraunhofer. |
|
||||
| 5 | LLM application testing and evaluation methodology | Gap | Verified LiteLLM/custom-GPT exposure does not evidence a formal LLM evaluation framework. Do not claim. |
|
||||
| 6 | Pre-process large unstructured data for AI | Bridge — MED | Bosch image-classification production workflow and contributing NLP/speech-recognition work at Fraunhofer; no claim of large-scale LLM-corpus preparation. |
|
||||
| 7 | APIs/interfaces integrating AI models with existing platforms | Bridge — MED | Built Python/Java/C# data services and REST microservices; created/used LiteLLM APIs. No claim of owning a model-integration platform. |
|
||||
| 8 | Monitor and maintain deployed models | Bridge — MED | Operated production ML inference at Bosch plus observability PoC; no evidence of retraining/model-governance ownership. |
|
||||
| 9 | Financial/banking exposure | Gap — nice to have | No professional treasury, asset-management or banking experience. |
|
||||
| 10 | Mentor junior colleagues | Gap — nice to have | No verified mentoring evidence to claim. |
|
||||
| 11 | English | Direct | Fluent; BIS corporate language is English. |
|
||||
|
||||
### ATS Keywords
|
||||
|
||||
- **AI / ML:** applied AI, LLM applications, LLM evaluation, model integration, model monitoring, machine learning, NLP, speech recognition, MLOps
|
||||
- **Data engineering:** Python, data pipelines, analytical models, data exploration, preprocessing, unstructured data, APIs, production support
|
||||
- **Platform / operations:** Kubernetes, Docker, AWS, Kafka, Airflow, observability, CI/CD, reliability
|
||||
- **Domain:** Banking Technology, financial services, treasury, asset management, financial structure
|
||||
- **Collaboration:** requirements analysis, stakeholders, technical communication, junior support, continuous learning
|
||||
|
||||
### Gap Assessment
|
||||
|
||||
- **Direct:** Python; production data pipelines; cloud data infrastructure; deployed ML inference; Kubernetes/Docker; CI/CD; production support; stakeholder-facing application ownership.
|
||||
- **Bridge:** Applied-AI engineering through production image-classification inference (HIGH); NLP/speech-recognition contribution at Fraunhofer (MED); API/model-interface work via data services, microservices and LiteLLM (MED); model operations via Bosch production deployment and observability (MED); unstructured-data relevance through image and speech workflows (MED).
|
||||
- **Gap:** Formal LLM evaluation methodology; direct LLM application ownership; financial/banking domain; verified mentoring. These stay explicit gaps and will not be disguised as experience.
|
||||
|
||||
## Company Context
|
||||
|
||||
- **Mission:** BIS supports central banks and financial stability through international cooperation, banking services, research and technology innovation.
|
||||
- **This role:** Banking Technology's Architecture, Platforms and Intelligence team is expanding data, analytics and applied-AI applications. BIS has recently launched Project Voyager to build and integrate a portfolio of generative-AI technologies into its activities.
|
||||
- **Relevant work:** BIS's Project Gaia used LLMs, semantic search and systematic prompting to extract and harmonise climate-related disclosures; its AI work emphasises data quality, privacy, security and resilience in financial services.
|
||||
- **Culture:** International, English-first, public-purpose organisation with an explicit innovation mandate and hybrid work model. The role is Basel-based; hybrid does not mean fully remote.
|
||||
- **Why them angle:** Pair production-grade AI/data engineering with the institution's responsible, data-governed use of AI in central banking. Emphasise operating dependable data and ML systems, not claiming to be an LLM researcher.
|
||||
|
||||
## Framing Strategy
|
||||
|
||||
- **Lead narrative:** Infrastructure-first applied-AI engineer: deployed ML inference in a 24/7 manufacturing environment, then built and owned governed cloud data products and pipelines at Swisscom. Brings the operational discipline needed to integrate, run and monitor AI applications in a risk-sensitive institution.
|
||||
- **Reframing map:** Bosch production ML inference → deployed applied-AI application; Swisscom AWS data mesh / metadata → governed, discoverable data foundation for AI; Fraunhofer ARTUS → contributing NLP/speech-recognition experience; data services / MISSION microservices → APIs and interfaces for integrating AI-enabled services.
|
||||
- **Emphasize:** Bosch ML inference deployment; Swisscom Data Mesh, metadata and data products; Python/Kubernetes/AWS/Kafka; application/component ownership; stakeholder requirements and production support; responsible data governance.
|
||||
- **Downplay:** Generic dashboarding; legacy test automation; unverified LLM-evaluation claims; finance-domain claims.
|
||||
- **CL hooks:** Project Voyager's GenAI portfolio; Project Gaia's LLM-supported analysis of unstructured climate disclosures; BIS emphasis on data quality, privacy, security and resilience for AI in financial services.
|
||||
- **User directives:** Target BIS only; preserve accuracy over keyword match; do not imply fully remote work or guarantee a compensation upgrade.
|
||||
|
||||
## Critique Context (captured in Phase 0, used in /critique)
|
||||
|
||||
- **Reviewer persona:** Applied-AI/data-platform engineering lead in Banking Technology. They need a pragmatic builder who can make AI applications reliable, safe and usable in an international, risk-sensitive environment.
|
||||
- **Competitive landscape:** Obvious candidates will have direct LLM/RAG evaluation, financial-services data, and model-lifecycle experience. Dennis differentiates through genuine production ML deployment, enterprise data-platform ownership and operational accountability, but must not try to out-claim them on LLM depth.
|
||||
- **Domain vocabulary:** applied AI, LLM evaluation, data governance, unstructured data, model integration, production support, observability, financial stability, responsible innovation, central banking.
|
||||
|
||||
## Cover Letter Plan
|
||||
|
||||
- **Institution type:** International financial institution / applied-AI engineering team
|
||||
- **Paragraph count:** 3 paragraphs; 270–300 words
|
||||
- **P1 hook:** Production ML inference in Bosch's 24/7 semiconductor fab, paired with BIS's need to operate dependable applied-AI applications.
|
||||
- **P2–P3 evidence:** Bosch ML deployment and monitoring; Swisscom's governed data products, metadata and AWS data platform; Fraunhofer NLP contribution as supporting—not primary—LLM bridge.
|
||||
- **Domain pivot:** "While my production work has been in telecom and semiconductor manufacturing rather than banking, it has required the same discipline around reliable data, controlled deployment, observability and stakeholder-facing operation that responsible AI applications demand."
|
||||
- **Jargon level:** Technical but HR-safe
|
||||
- **Why them hook:** BIS's Project Voyager and Project Gaia show an institution applying LLMs where data quality, governance and resilience matter.
|
||||
|
||||
## Bullet Plan
|
||||
|
||||
### Swisscom — Staff Data, Analytics & AI Engineer (7 bullets, 14 rendered lines)
|
||||
|
||||
| # | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---:|---|
|
||||
| * | SW-7 | Governed data products and metadata within Swisscom's Data Mesh as the discoverable foundation for downstream AI workflows | 2L | 2 | Direct / Bridge |
|
||||
| * | SW-3 | Python applications on Kubernetes with GitLab CI/CD; full containerised delivery and operation | 2L | 2 | Direct |
|
||||
| * | SW-1 | Scoped migration of legacy Teradata/Oracle ETL to AWS serverless data platform | 2L | 2 | Direct |
|
||||
| * | SW-2 | Component ownership of Fulfillment Python/Kafka ETL, governance, incident response and on-call SLA | 2L | 2 | Direct |
|
||||
| o | SW-4 | Stakeholder-facing data products, backlog partnership, automation and production root-cause analysis | 2L | 2 | Direct |
|
||||
| o | SW-6 | PySpark distributed processing in the Data Lake for large-scale Python/SQL data workloads | 2L | 2 | Bridge |
|
||||
| + | SW-5 | 2025/26 Security Champion role: designated security point of contact for secure data-pipeline delivery | 2L | 2 | Direct / page-fill addition |
|
||||
|
||||
### Bosch Semiconductor — (Senior) Data & ML Engineer (5 bullets, 10 rendered lines)
|
||||
|
||||
| # | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---:|---|
|
||||
| * | BS-1 | Production ML inference: Docker/Kubernetes/Ansible image classification in a 24/7 semiconductor fab | 2L | 2 | Direct / strongest AI evidence |
|
||||
| * | BS-2 | Python/Java/C# data services over Oracle and Hadoop/Impala supplying manufacturing analysis applications | 2L | 2 | Direct / API bridge |
|
||||
| * | BS-3 | Application Owner for analytics applications and pipelines: SLOs, user enablement, vendor and stakeholder operations | 2L | 2 | Direct |
|
||||
| + | BS-5 | Co-owned Spotfire analytics platform, built C# extensions and co-presented at TIBCO Analytics Forum 2022 | 2L | 2 | Direct / page-fill addition |
|
||||
| o | BS-4 | ELK/Kafka anomaly-detection PoC plus Grafana/Prometheus/Loki monitoring for production systems | 2L | 2 | Bridge |
|
||||
|
||||
### Fraunhofer CML — Research Software Engineer (4 bullets, 8 rendered lines)
|
||||
|
||||
| # | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---:|---|
|
||||
| * | FC-2 | Contributed ML/NLP and speech-recognition components to ARTUS, a safety-critical sea-rescue transcription project | 2L | 2 | Bridge |
|
||||
| + | FC-4 | Contributed to a research-grant proposal for ML-based predictive maintenance in maritime operations | 2L | 2 | Bridge / page-fill addition |
|
||||
| o | FC-3 | Built containerised REST microservices for maritime data exchange, showing service/API integration | 2L | 2 | Bridge |
|
||||
| o | FC-1 | Independently introduced Jenkins CI/CD quality gates while developing decision-support software | 2L | 2 | Bridge |
|
||||
|
||||
### Vizrt — DevOps Engineer (2 bullets, 4 rendered lines)
|
||||
|
||||
| # | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---:|---|
|
||||
| o | VZ-1 | Python/C++ distributed real-time backend components for a production broadcast platform | 2L | 2 | Bridge |
|
||||
| o | VZ-2 | Python integration/unit tests and CI/CD quality gates, supporting a testing-discipline bridge without claiming LLM evaluation | 2L | 2 | Bridge |
|
||||
|
||||
### Generali — IT Consultant (2 bullets, 4 rendered lines)
|
||||
|
||||
| # | ID | Achievement | Variant | Lines | JD Match |
|
||||
|---|---|---|---|---:|---|
|
||||
| o | GN-1 | Introduced BDD automation, owned the technical implementation and trained colleagues across the Java community | 2L | 2 | Bridge |
|
||||
| o | GN-3 | Java/J2EE workflow features, WebService deployment migration and Spring Boot/Camel integration PoC | 2L | 2 | Bridge |
|
||||
|
||||
**Confirmed set:** 20 variable bullets / 40 rendered lines. The three marked additions were added at the 2-page fill gate: security responsibility, analytics-platform ownership and an accurately hedged ML research contribution.
|
||||
|
||||
**Forced exclusions:** No direct LLM-evaluation, RAG, LangChain/LangGraph/LlamaIndex, finance/banking, mentoring, or model-retraining claim. Do not use the outdated three-year Swisscom Security Champion wording. Do not imply solo ownership of Swisscom's company-wide Data Mesh.
|
||||
|
||||
**Focus impact:** Bosch production ML, Fraunhofer NLP, Swisscom data products/metadata and operations are elevated over generic dashboards, legacy test automation and RPA.
|
||||
|
||||
**Verified BIS hooks:** Project Gaia uses AI/LLMs and semantic search to extract climate-risk indicators from unstructured corporate disclosures; Project Voyager is BIS's two-year programme for integrating a GenAI technology portfolio into BIS activities.
|
||||
|
||||
## Output Files
|
||||
|
||||
- Resume: `output/BIS/e2e_bis_senior_data_analytics_ai_resume.tex`
|
||||
- Cover Letter: `output/BIS/e2e_bis_senior_data_analytics_ai_cover_letter.tex`
|
||||
- Critique: `output/BIS/critique_bis_senior_data_analytics_ai.md`
|
||||
|
||||
## Critique Summary
|
||||
|
||||
- **Score:** 80.5/100 (strong package; structural ceiling is direct LLM evaluation and financial-services experience, not a writing defect).
|
||||
- **Tier 1:** Improve the page-two Bosch continuation/fill if the two-line-only preference can be relaxed; clarify the documented LiteLLM scope as created/used APIs.
|
||||
- **Strengths:** Bosch 24/7 production ML, Swisscom governed data and pipeline ownership, clear Python and production-support evidence.
|
||||
- **Do not add:** LLM evaluation, direct LLM application ownership, banking, model retraining, or mentoring claims without new evidence.
|
||||
|
||||
## Status
|
||||
|
||||
- Phase 0: DONE
|
||||
- Phase 1: DONE (20 bullets confirmed; 3 page-fill additions documented)
|
||||
- Phase 2 Resume: DONE
|
||||
- Cover Letter: DONE (281 words, 1 page; compiled and visually verified)
|
||||
- Critique: DONE (80.5/100; user finalized without further edits)
|
||||
- Package: SUBMITTED (2026-07-10)
|
||||
- **Next:** Await BIS response; retain the critique and portal answers for interview preparation.
|
||||
Reference in New Issue
Block a user