# Bundle: ML / AI Engineer

> Target employers: AI product companies, R&D teams
> Tier: 2 — strong with targeted emphasis
> Config key: bundle_ml_ai_engineer.md

---

## S1: Role Profile & Priority Matrix

**Positioning:** Dennis is an ML Engineer who specializes in the *infrastructure and deployment* side of ML — not ML research or model training from scratch. His flagship signal is containerizing and orchestrating ML inference into a 24/7 semiconductor production environment (Bosch) — a production ML deployment in one of the most demanding operational contexts imaginable. This is paired with NLP/speech recognition research (Fraunhofer ARTUS), early deep learning exposure (IBM AI Engineering, Udacity AI for Trading), and current AWS/Kubernetes ownership at Swisscom.

**Honest framing:** Dennis is strongest in MLOps and ML infrastructure. He has real but limited model development experience (ARTUS NLP, image classification at Bosch). Do NOT position as a research ML scientist or model architect. DO position as "ML Engineer who can own the full deployment lifecycle and build reliable production ML infrastructure."

**Key differentiator:** Production ML in a 24/7 constrained environment (24h uptime, no deployment windows, hardware-in-the-loop) is a rare and credible signal.

### Priority Matrix

| Priority | Achievement IDs | Rationale |
|----------|----------------|-----------|
| HIGH | BS-1, SW-3, SW-1, SW-2 | Production ML deployment, K8s infrastructure, AWS data lake, pipeline ownership |
| MED | FC-2, SW-5, BS-2, BS-3, BS-4 | NLP research, DevSecOps, data services, app ownership, observability |
| LOW | SW-4, FC-1, FC-3, VZ-1, VZ-2, GN-1, GN-2 | Not core ML signal |

**2-page resume bullet allocation (typical):**
- Swisscom: 3 bullets (SW-3, SW-1, SW-2)
- Bosch: 3 bullets (BS-1, BS-2 or BS-3, BS-4)
- Fraunhofer: 1–2 bullets (FC-2 ARTUS; FC-1 if CI/CD is relevant)
- Vizrt: 1 bullet (compressed; or omit)
- Generali: 1 bullet (GN-1 or omit)

---

## S2: Summary Guide

**Headline pattern:**
> "ML Engineer | MLOps · Kubernetes · AWS | Production ML Deployment, Data Infrastructure & Applied NLP"

**Building blocks:**
- "production ML deployment" or "ML inference at scale"
- "containerized ML pipelines" (Docker, Kubernetes, Ansible)
- "ML infrastructure and data platform" (AWS, Airflow, Kafka)
- "applied NLP / speech recognition" (Fraunhofer ARTUS — hedged)
- "AWS Certified Solutions Architect" (infra credibility)

**Tone:** Pragmatic ML engineer who ships ML to production. Operational rigor. Infrastructure-first mindset. Not a researcher — an engineer who makes ML run reliably.

**Avoid:**
- Claiming deep model research or novel architecture contributions
- Overstating NLP depth (ARTUS was contributing developer, not solo)
- Leading with test automation or BI/analytics framing
- "Passionate about AI" clichés

---

## S3: Achievement Reframing Map

| ID | Default Framing | This Role's Framing | Key Metric / Signal |
|----|----------------|--------------------|--------------------|
| BS-1 | ML inference containerization | **LEAD bullet** — "Designed and deployed ML inference pipeline (Docker, K8s, Ansible) into 24/7 semiconductor fab; automated image-based defect classification" | Production ML in constrained 24/7 environment |
| SW-3 | K8s + GitLab CI/CD | "Deployed and operated ML-ready Python applications on Kubernetes with GitLab CI/CD automation — production-grade containerized delivery" | K8s ownership = MLOps infrastructure |
| SW-1 | AWS migration | "Built cloud-native data infrastructure on AWS (S3, Glue, Athena/Iceberg, Redshift, Airflow) — the scalable data layer that ML models depend on" | AWS data lake for ML workloads |
| SW-2 | Component Owner | "Owned business-critical ETL pipelines (Oracle/Kafka → Teradata) — reliable data supply for downstream ML and analytics" | Data reliability for ML input |
| FC-2 | ARTUS NLP | "Contributed ML and speech recognition components to ARTUS — Fraunhofer research project targeting automatic sea rescue transcription" | Applied NLP in safety-critical domain |
| BS-4 | ELK PoC | "Delivered anomaly detection PoC: ELK + Kafka pipeline with Grafana/Prometheus monitoring — ML-adjacent signal processing" | Anomaly detection / observability |
| SW-5 | Security Champion | "Swisscom Security Champion ×3 — security and compliance ownership for ML pipeline data governance and DevSecOps" | Security in ML data pipeline context |
| BS-2 | Data services | "Built data services (Python/Java/C#) over OracleDB and Hadoop enabling ML model input pipelines in semiconductor manufacturing" | Data infrastructure for ML |

---

## S4: Skills Guide

**Bold tools (resume Technical Skills section):**
Python, Kubernetes, Docker, AWS (S3 · Glue · Athena · Airflow), Kafka, PyTorch · Scikit-learn

**Must-include skills (ATS match):**
- Python, MLOps, ML inference deployment
- Docker, Kubernetes, Ansible
- AWS (S3, Glue, Athena, Redshift, Airflow), Apache Iceberg
- Apache Kafka
- PyTorch, Scikit-learn, Pandas, NumPy
- CI/CD (GitLab, Jenkins)

**Nice-to-have (include if JD mentions):**
- NLP, speech recognition (hedge — contributing developer at Fraunhofer)
- TensorFlow/Keras (IBM cert — familiarity level; note if JD requires)
- PySpark (Swisscom — Spark ML adjacent)
- Grafana, Prometheus (monitoring ML systems)
- Apache Spark ML (familiarity via cert)

**Omit:**
- BDD, Selenium, HP Quality Center (testing — irrelevant)
- RPA/UIPath, Camunda (process automation — irrelevant)
- Tibco Spotfire (BI tool — irrelevant)
- SAP BODS (legacy — omit for ML audience)

**Certifications to highlight:**
- AWS Certified Solutions Architect – Associate → HIGH (infra credibility for MLOps)
- AI for Trading Nanodegree (Udacity) → MED (quantitative ML exposure)
- IBM AI Engineering Specialization → MED (TensorFlow, Keras, Spark ML depth signal)
- Data Engineering with AWS → supporting

---

## S5: Cover Letter Guide

**Institution type:** AI product company, applied ML team, or R&D engineering team (not pure research lab)

**Opening hook pattern:**
> "My most defining ML engineering project was at Bosch Semiconductor in Dresden: I designed and deployed the strategy for containerizing ML inference models into a 24/7 wafer production line — orchestrating with Kubernetes and Ansible, running Docker-containerized image classification models continuously against production data, with no downtime tolerance. That production constraint is what sharpens MLOps thinking. [Tie to their ML deployment challenge]."

**Key narrative thread:**
1. **Production ML ownership** — BS-1: not a research demo, not a notebook — ML running uninterrupted in a semiconductor fab. Establish this credibility early.
2. **Infrastructure that ML depends on** — SW-1 + SW-2: the AWS data lake and reliable Kafka/ETL pipelines that feed ML models. Shows full-stack ML engineering thinking.
3. **Applied ML research background** — FC-2: Fraunhofer ARTUS NLP project establishes early research exposure (hedge: contributing developer)
4. **Certs as credibility** — AWS SAA + IBM AI Engineering + Udacity AI for Trading: show structured ML and cloud learning

**"Why them" angle to research:**
- What ML problems are they solving? Map to defect detection (vision ML), NLP (Fraunhofer), or infrastructure (Swisscom)
- How mature is their MLOps? If early-stage → your Bosch experience building from scratch is directly relevant
- Are they AWS-heavy? → Your migration and cert are strong signals

**Avoid:**
- Claiming to be a research ML scientist (your strength is deployment and infrastructure)
- Overstating NLP depth ("contributed to" not "led")
- Listing PyTorch/Keras without framing (cert exposure, not daily production use)
- Mentioning SCEDAS, maritime research, BDD, or RPA context