first commit
This commit is contained in:
@@ -0,0 +1,123 @@
|
||||
# Bundle: Analytics Engineer
|
||||
|
||||
> Target employers: Data-driven companies, BI/analytics teams
|
||||
> Tier: 2 — strong with targeted emphasis
|
||||
> Config key: bundle_analytics_engineer.md
|
||||
|
||||
---
|
||||
|
||||
## S1: Role Profile & Priority Matrix
|
||||
|
||||
**Positioning:** Dennis bridges the gap between pure data engineering and analytics — he has built and owned the pipelines *and* delivered the data products and dashboards that stakeholders actually use. His B2B analytics delivery at Swisscom (Switzerland's largest telco), Application Owner experience at Bosch (semiconductor analytics platforms), and domain depth in semiconductor data (defect management, parameter testing, process analysis) make him a credible Analytics Engineer candidate who understands both the technical infrastructure and the analytical outcomes.
|
||||
|
||||
**Key differentiator for this role type:** Most Analytics Engineer candidates are either BI-first (lighter on engineering) or DE-first (lighter on business context). Dennis has both: owned pipelines AND delivered B2B data products AND held application ownership for analytics platforms.
|
||||
|
||||
### Priority Matrix
|
||||
|
||||
| Priority | Achievement IDs | Rationale |
|
||||
|----------|----------------|-----------|
|
||||
| HIGH | SW-4, SW-1, SW-2, BS-3 | Core analytics signals: B2B products, AWS data infra, pipeline ownership, analytics platform owner |
|
||||
| MED | SW-3, SW-6, BS-1 (semi JDs), BS-2, FC-1 | Supporting: K8s delivery, PySpark, ML analytics at Bosch, data service depth |
|
||||
| LOW | SW-5, BS-4, FC-2, FC-3, VZ-1, VZ-2, GN-1, GN-2 | Infrastructure/testing — not primary signal for analytics audience |
|
||||
|
||||
**2-page resume bullet allocation (typical):**
|
||||
- Swisscom: 3–4 bullets (SW-4, SW-2, SW-1, SW-3)
|
||||
- Bosch: 2–3 bullets (BS-3, BS-2; +BS-1 for semi JDs)
|
||||
- Fraunhofer: 1 bullet (FC-1 compressed or omit)
|
||||
- Vizrt: 1 bullet (combined or omit)
|
||||
- Generali: 1 bullet (GN-1 or omit)
|
||||
|
||||
---
|
||||
|
||||
## S2: Summary Guide
|
||||
|
||||
**Headline pattern:**
|
||||
> "Analytics Engineer | Python · SQL · AWS · Teradata | Data Products, Pipeline Ownership & Stakeholder Analytics"
|
||||
|
||||
**Building blocks:**
|
||||
- "data products for business stakeholders" or "B2B analytics delivery"
|
||||
- "end-to-end pipeline ownership" (show both build and deliver)
|
||||
- "analytics platform ownership" (App Owner at Bosch)
|
||||
- "AWS cloud-native stack" (Athena, Glue, Redshift — standard analytics stack)
|
||||
- Semiconductor domain angle (for semi JDs): "semiconductor manufacturing analytics — defect management, parameter testing, process analysis"
|
||||
|
||||
**Tone:** Pragmatic engineer who cares about outcomes, not just pipelines. Business-aware. Bridges technical depth and analytical impact.
|
||||
|
||||
**Avoid:**
|
||||
- Leading with ML/AI framing (not the primary signal here)
|
||||
- Heavy infrastructure language (Kubernetes, Ansible) unless JD asks for it
|
||||
- Overplaying test automation background
|
||||
|
||||
---
|
||||
|
||||
## S3: Achievement Reframing Map
|
||||
|
||||
| ID | Default Framing | This Role's Framing | Key Metric / Signal |
|
||||
|----|----------------|--------------------|--------------------|
|
||||
| SW-4 | B2B products + automation | **Lead bullet** — "Delivered data products, analyses and dashboards for B2B stakeholders; drove automation of recurring technical workflows" | Stakeholder-facing delivery |
|
||||
| SW-2 | Component Owner ETL | "Owned Fulfillment ETL pipelines (Oracle/Kafka → Teradata) — ensuring data availability for downstream analytics with SLA accountability" | Pipeline → analytics link |
|
||||
| SW-1 | AWS migration | "Migrated ETL stack to AWS (S3, Glue, Athena/Iceberg, Redshift, Airflow) — enabling scalable, query-optimized analytics on a cloud data lakehouse" | Iceberg/Athena = analytics stack |
|
||||
| BS-3 | Application Owner | "Application Owner for semiconductor data analysis platforms — defined SLOs, trained users, managed vendor relationships and stakeholder expectations" | Ownership + analytics platform |
|
||||
| BS-2 (generic) | Data services | "Built data services supplying analysis teams with on-demand structured access to manufacturing process data" | Analytics enablement framing |
|
||||
| BS-2 (semi JD) | Data services | "Built data services enabling Defect Management, Parameter Testing and Process Analysis teams with on-demand data access" | Semiconductor domain specificity |
|
||||
| BS-1 (semi JD) | ML inference | "Automated image-based defect classification for semiconductor production — enabling defect management analytics without manual inspection" | Semi domain + analytics outcome |
|
||||
| SW-3 | K8s/CI/CD | "Deployed and operated Python data applications on Kubernetes with GitLab CI/CD automation" | Engineering credibility signal |
|
||||
|
||||
---
|
||||
|
||||
## S4: Skills Guide
|
||||
|
||||
**Bold tools (resume Technical Skills section):**
|
||||
Python, SQL (Oracle · Teradata · Athena), AWS (S3 · Glue · Athena · Redshift), PySpark, Airflow
|
||||
|
||||
**Must-include skills (ATS match):**
|
||||
- Python, SQL, data modeling
|
||||
- AWS (Athena, Glue, Redshift, S3), Apache Iceberg
|
||||
- Apache Airflow, ETL/ELT
|
||||
- Teradata, Oracle DB
|
||||
- PySpark, Pandas
|
||||
- Grafana or data visualization tools (Plotly/Matplotlib)
|
||||
|
||||
**Nice-to-have (include if JD mentions):**
|
||||
- Apache Kafka (pipeline depth signal)
|
||||
- dbt (not evidenced — do NOT claim; if JD requires, flag to user)
|
||||
- Tibco Spotfire (niche — only for Spotfire-specific JDs)
|
||||
- Kubernetes (engineering depth signal if JD asks for it)
|
||||
|
||||
**Omit:**
|
||||
- ELK Stack, Prometheus, Loki (infra monitoring — not analytics signal)
|
||||
- Ansible, IaC/CloudFormation (infra — not analytics signal)
|
||||
- RPA/UIPath, BDD, Selenium (testing — irrelevant)
|
||||
|
||||
**Certifications to highlight:**
|
||||
- AWS Certified Solutions Architect – Associate → supporting (confirms AWS stack)
|
||||
- Data Engineering with AWS (Udacity) → directly relevant
|
||||
- iSAQB CPSA Foundation Level → minor supporting signal
|
||||
|
||||
---
|
||||
|
||||
## S5: Cover Letter Guide
|
||||
|
||||
**Institution type:** Industry — data-driven product company, BI/analytics team, or data consultancy
|
||||
|
||||
**Opening hook pattern (generic):**
|
||||
> "At Swisscom, I own both sides of the analytics equation: I build and operate the Fulfillment ETL pipelines that feed our Teradata data warehouse, and I deliver the data products and dashboards that our B2B teams rely on for decision-making. [Tie to their specific analytics use case]."
|
||||
|
||||
**Opening hook pattern (semiconductor JD):**
|
||||
> "My experience at Bosch Semiconductor sits at the intersection of data engineering and semiconductor manufacturing analytics — I built the pipelines that fed defect management and parameter testing teams, owned the analytics platforms those teams relied on, and deployed ML-based image classification that automated defect analysis on the production line. I'd bring that same domain depth and ownership mentality to [Company]."
|
||||
|
||||
**Key narrative thread:**
|
||||
1. **Analytics platform ownership** — App Owner at Bosch: not just building queries, but owning the analytics software that teams depend on
|
||||
2. **Pipeline-to-insight chain** — Fulfillment Component Owner at Swisscom: show the full chain from raw Oracle/Kafka data → Teradata DWH → B2B analytics
|
||||
3. **Cloud analytics stack** — AWS migration with Athena/Iceberg/Glue: modern lakehouse architecture for analytics workloads
|
||||
4. **Semiconductor domain** (for semi JDs): Defect Management + Parameter Testing + Process Analysis — rare domain expertise in an Analytics Engineer candidate
|
||||
|
||||
**"Why them" angle to research:**
|
||||
- What business domain are their analytics teams serving? Map to Swisscom (telecom) or Bosch (manufacturing) experience
|
||||
- What is their analytics stack? AWS-heavy → your SW-1 migration is directly relevant
|
||||
- Do they use dbt? Flag if so — not in your stack, but Airflow/Glue is adjacent
|
||||
|
||||
**Avoid:**
|
||||
- Leading with infrastructure or DevOps framing
|
||||
- Overplaying ML/AI angle (secondary for analytics audience)
|
||||
- Mentioning ITIL, SCEDAS, or maritime research context
|
||||
@@ -0,0 +1,122 @@
|
||||
# Bundle: Staff / Senior Data Engineer
|
||||
|
||||
> Target employers: Tech companies, scale-ups, platform teams
|
||||
> Tier: 1 — strongest evidence, full portfolio
|
||||
> Config key: bundle_data_engineer.md
|
||||
|
||||
---
|
||||
|
||||
## S1: Role Profile & Priority Matrix
|
||||
|
||||
**Positioning:** Dennis is a Staff-level data engineer with 5+ years building production-grade ETL pipelines and data platforms at scale — from Oracle/Teradata DWH ownership at Swisscom (Switzerland's largest telco) to containerized ML inference in a 24/7 semiconductor fab at Bosch. His AWS certification (SAA, active), cloud migration ownership, and Kubernetes-based deployment experience position him as a senior-to-staff candidate across data engineering, data platform, and data infrastructure roles.
|
||||
|
||||
**Promotion signal to use:** "Promoted from Senior to Staff Engineer (Engineer IV) at Swisscom, April 2025."
|
||||
|
||||
### Priority Matrix
|
||||
|
||||
| Priority | Achievement IDs | Rationale |
|
||||
|----------|----------------|-----------|
|
||||
| HIGH | SW-2, SW-1, SW-3, BS-3, BS-1, BS-2 | Core DE ownership: component owner, AWS migration, K8s/CI/CD, app owner, ML pipelines, data services |
|
||||
| MED | SW-4, SW-5, SW-6, BS-4, FC-1, VZ-2, GN-1 | Breadth signals: stakeholder products, DevSecOps, PySpark, ELK PoC, CI/CD, BDD ownership |
|
||||
| LOW | FC-2, FC-3, VZ-1, GN-2, GN-3, CA-1 | Earlier career / non-core for this audience |
|
||||
|
||||
**2-page resume bullet allocation (typical):**
|
||||
- Swisscom: 3–4 bullets (SW-1, SW-2, SW-3, SW-4 or SW-5)
|
||||
- Bosch: 3 bullets (BS-1, BS-2, BS-3; +BS-4 if space)
|
||||
- Fraunhofer: 1–2 bullets (FC-1 compressed)
|
||||
- Vizrt: 1 bullet (VZ-1 + VZ-2 combined)
|
||||
- Generali: 1 bullet (GN-1)
|
||||
|
||||
---
|
||||
|
||||
## S2: Summary Guide
|
||||
|
||||
**Headline pattern:**
|
||||
> "Staff Data Engineer | AWS · Kafka · Kubernetes | ETL Pipelines, Cloud Migration & Production ML"
|
||||
|
||||
**Building blocks** (3–5 phrases that should appear in summaries for this role type):
|
||||
- "end-to-end ETL pipeline ownership" or "component ownership of business-critical data pipelines"
|
||||
- "cloud migration" or "legacy-to-AWS migration"
|
||||
- "Kafka-based event-driven ingestion"
|
||||
- "Kubernetes deployment" or "containerized data applications"
|
||||
- "AWS Certified Solutions Architect" (cert signal)
|
||||
|
||||
**Tone:** Engineer who owns systems, not just builds them. Accountability + delivery. Operator mindset.
|
||||
|
||||
**Avoid:**
|
||||
- Academic or research framing
|
||||
- "Passionate about data" clichés
|
||||
- Overemphasizing testing/QA background (earlier career)
|
||||
- Listing every tool — focus on the stack that matters for the JD
|
||||
|
||||
---
|
||||
|
||||
## S3: Achievement Reframing Map
|
||||
|
||||
| ID | Default Framing | This Role's Framing | Key Metric / Signal |
|
||||
|----|----------------|--------------------|--------------------|
|
||||
| SW-2 | Component Owner, Fulfillment ETL | **Lead bullet** — "owned business-critical Fulfillment pipelines end-to-end, on-call SLA, Data Governance compliance" | Component Owner title, on-call accountability |
|
||||
| SW-1 | AWS migration | "Migrated legacy Teradata/Oracle ETL stack to AWS (S3, Glue, Athena/Iceberg, Redshift, Airflow, CloudFormation)" | Cloud-native stack breadth; Iceberg signals modern data lakehouse |
|
||||
| SW-3 | K8s + GitLab CI/CD | "Deployed and operated Python data apps on Kubernetes with GitLab CI/CD in agile DevOps team" | K8s + CI/CD = full DevOps ownership |
|
||||
| BS-3 | Application Owner | "Application Owner for semiconductor analytics suite — SLOs, vendor management, training, documentation" | SLO ownership = senior signal |
|
||||
| BS-1 | ML inference in fab | "Containerized ML inference (Docker, K8s, Ansible) into 24/7 production; automated image-based defect classification" | Production ML in constrained environment |
|
||||
| BS-2 | Data services Oracle/Hadoop | "Built Python/Java/C# data services over OracleDB and Hadoop/ImpalaSQL for semiconductor analysis teams" | Multi-language, enterprise DB breadth |
|
||||
| SW-4 | B2B products | "Delivered data products and dashboards for B2B stakeholders; drove process automation" | Stakeholder-facing breadth |
|
||||
| BS-4 | ELK PoC | "Delivered anomaly detection PoC: ELK + Kafka, Grafana/Prometheus/Loki monitoring" | Observability initiative |
|
||||
|
||||
---
|
||||
|
||||
## S4: Skills Guide
|
||||
|
||||
**Bold tools (resume Technical Skills section):**
|
||||
Python, Kafka, AWS (S3 · Glue · Athena · Redshift · Airflow · CloudFormation), Kubernetes, Teradata
|
||||
|
||||
**Must-include skills (ATS match):**
|
||||
- Python, SQL, ETL/ELT
|
||||
- Apache Kafka, Apache Airflow
|
||||
- AWS (S3, Glue, Athena, Redshift), Apache Iceberg
|
||||
- Kubernetes, Docker, GitLab CI/CD
|
||||
- Teradata, Oracle DB
|
||||
- PySpark
|
||||
|
||||
**Nice-to-have (include if JD mentions):**
|
||||
- SAP BODS, Hadoop/Impala, Step Functions, Lambda
|
||||
- Grafana, Prometheus, ELK Stack
|
||||
- Ansible, IaC/CloudFormation
|
||||
- dbt (not evidenced — do NOT claim if not in JD; omit)
|
||||
|
||||
**Omit:**
|
||||
- RPA/UIPath, Camunda, IBM ODM (too early-career/non-core)
|
||||
- HP Quality Center, Serenity-BDD, JBehave (testing tools — irrelevant)
|
||||
- C++, J2EE (legacy — omit unless JD explicitly asks)
|
||||
|
||||
**Certifications to highlight:**
|
||||
- AWS Certified Solutions Architect – Associate (active, 2024–2027) → HIGH value for this role type
|
||||
- Data Engineering with AWS (Udacity, 2026) → supporting signal
|
||||
- iSAQB CPSA Foundation Level → supporting (architecture awareness)
|
||||
|
||||
---
|
||||
|
||||
## S5: Cover Letter Guide
|
||||
|
||||
**Institution type:** Industry — tech company, scale-up, or enterprise platform team
|
||||
|
||||
**Opening hook pattern:**
|
||||
> "As a Staff Data Engineer at Swisscom — Switzerland's largest telco — I currently own the business-critical Fulfillment ETL pipelines that feed our data warehouse, while simultaneously leading the migration of our legacy stack to a cloud-native AWS architecture. [Tie to their specific need / JD signal]."
|
||||
|
||||
**Key narrative thread:**
|
||||
1. **Ownership at scale** — Component Owner at Swisscom, Application Owner at Bosch: not just building pipelines, but running them in production with SLA accountability
|
||||
2. **Cloud-native evolution** — AWS migration (Athena/Iceberg, Glue, Airflow, CloudFormation): led the transition, not just participated
|
||||
3. **Production ML integration** — Bosch: ML inference containerized into 24/7 fab; demonstrates that "data engineer who can own the ML data layer"
|
||||
4. **Consistent seniority arc** — Bosch promotion (mid → Senior), Swisscom promotion (Senior → Staff)
|
||||
|
||||
**"Why them" angle to research:**
|
||||
- What is their data stack? Match Kafka/Airflow/AWS overlaps explicitly
|
||||
- Are they migrating to cloud or lakehouse architecture? → Your SW-1 experience is directly relevant
|
||||
- Do they operate pipelines in production SLAs? → Component Owner + on-call duty is your signal
|
||||
|
||||
**Avoid:**
|
||||
- Starting with "I am passionate about data"
|
||||
- Listing all tools in paragraph form
|
||||
- Mentioning Bundeswehr unless specifically relevant (leadership angle for management-adjacent roles)
|
||||
- Overplaying test automation background
|
||||
@@ -0,0 +1,127 @@
|
||||
# Bundle: Data Platform / Infra
|
||||
|
||||
> Target employers: Cloud-first companies, AWS-heavy orgs
|
||||
> Tier: 3 — viable with careful framing
|
||||
> Config key: bundle_data_platform.md
|
||||
|
||||
---
|
||||
|
||||
## S1: Role Profile & Priority Matrix
|
||||
|
||||
**Positioning:** Dennis's data platform and infrastructure experience is woven throughout his career rather than being a dedicated "platform engineer" role — but the evidence is substantive: Kubernetes ownership at two employers, AWS migration with CloudFormation/IaC, GitLab CI/CD automation, Docker containerization of ML workloads, observability stack (ELK + Grafana + Prometheus), and 3 consecutive years as Swisscom Security Champion (DevSecOps). Position as "Data Engineer with strong platform and infrastructure ownership" rather than a dedicated Platform/SRE/DevOps role.
|
||||
|
||||
**Note on Tier 3:** This bundle is viable but slightly less natural than Tier 1/2. The gap is: Dennis doesn't have a dedicated platform engineering title, and his infrastructure work is in service of data pipelines rather than standalone infrastructure. Frame accordingly — emphasize that his platform skills are production-proven, not academic.
|
||||
|
||||
### Priority Matrix
|
||||
|
||||
| Priority | Achievement IDs | Rationale |
|
||||
|----------|----------------|-----------|
|
||||
| HIGH | SW-3, SW-1, SW-2, BS-1, BS-2, BS-3, BS-4, SW-5 | K8s/GitLab, AWS/IaC, pipeline ownership, ML containerization, data services, ELK observability, DevSecOps |
|
||||
| MED | SW-4, SW-6, FC-1, FC-3, VZ-2, BS-5 | Automation, PySpark, CI/CD initiative, microservices, quality gates |
|
||||
| LOW | FC-2, VZ-1, GN-1, GN-2, CA-1 | Non-platform signals |
|
||||
|
||||
**2-page resume bullet allocation (typical):**
|
||||
- Swisscom: 3–4 bullets (SW-3, SW-1, SW-2, SW-5)
|
||||
- Bosch: 3 bullets (BS-1, BS-2 or BS-3, BS-4)
|
||||
- Fraunhofer: 1 bullet (FC-1 — CI/CD initiative)
|
||||
- Vizrt: 1 bullet (VZ-2 — quality gates in CI/CD)
|
||||
- Generali: 1 bullet (GN-1 or omit)
|
||||
|
||||
---
|
||||
|
||||
## S2: Summary Guide
|
||||
|
||||
**Headline pattern:**
|
||||
> "Data Platform Engineer | Kubernetes · AWS · Kafka | Cloud-Native Data Infrastructure, IaC & DevSecOps"
|
||||
|
||||
**Building blocks:**
|
||||
- "cloud-native data infrastructure" or "data platform ownership"
|
||||
- "Kubernetes-based containerized pipeline deployment"
|
||||
- "AWS IaC (CloudFormation)" — infrastructure-as-code signal
|
||||
- "AWS migration" — hands-on cloud platform experience
|
||||
- "DevSecOps / Security Champion" — security-aware platform engineer
|
||||
- "ELK + Grafana + Prometheus observability stack"
|
||||
|
||||
**Tone:** Infrastructure-minded engineer who thinks about reliability, observability, and security — not just data throughput. Platform thinking embedded in data work.
|
||||
|
||||
**Avoid:**
|
||||
- Leading with analytics or BI framing
|
||||
- Overemphasizing test automation background
|
||||
- Positioning as SRE or pure DevOps (the role was data engineering with platform ownership)
|
||||
|
||||
---
|
||||
|
||||
## S3: Achievement Reframing Map
|
||||
|
||||
| ID | Default Framing | This Role's Framing | Key Metric / Signal |
|
||||
|----|----------------|--------------------|--------------------|
|
||||
| SW-3 | K8s + GitLab | **Lead bullet** — "Deployed and operated Python data applications on Kubernetes with GitLab CI/CD; drove infrastructure automation in agile DevOps team" | K8s + CI/CD ownership = core platform signal |
|
||||
| SW-1 | AWS migration | "Migrated legacy ETL stack to cloud-native AWS (S3, Glue, Athena/Iceberg, Redshift, Airflow, CloudFormation) — full IaC stack provisioned via CloudFormation" | CloudFormation/IaC + full AWS service breadth |
|
||||
| SW-2 | Component Owner | "Owned Fulfillment ETL pipelines (Oracle/Kafka → Teradata) — platform reliability, Data Governance compliance, 2nd/3rd-level support and on-call duty" | Platform SLA + on-call = reliability engineer signal |
|
||||
| BS-1 | ML inference | "Containerized and orchestrated ML inference (Docker, K8s, Ansible) into 24/7 semiconductor production — zero-downtime constrained deployment" | Production-grade containerization under hardest constraints |
|
||||
| BS-4 | ELK PoC | "Designed and delivered observability stack: ELK + Kafka, Grafana dashboards, Prometheus metrics, Loki log aggregation — full monitoring suite for manufacturing infrastructure" | Full observability stack implementation |
|
||||
| SW-5 | Security Champion | "Swisscom Security Champion ×3 (2023–2026) — DevSecOps ownership, security compliance, risk monitoring and deviation tracking for Data Lake team" | Security ownership in platform context |
|
||||
| BS-2 | Data services | "Built multi-language data services (Python/Java/C#) over OracleDB and Hadoop/ImpalaSQL — platform-layer data access for semiconductor analysis teams" | Enterprise DB + Hadoop infrastructure |
|
||||
| BS-3 | App Owner | "Application Owner for semiconductor analytics platform — SLOs, reliability, vendor management, on-call coverage" | Platform SLA ownership |
|
||||
| FC-1 | CI/CD initiative | "Independently introduced Jenkins CI/CD pipeline with quality gates at Fraunhofer CML — first build automation adopted by the research team" | Initiative: built CI/CD from zero |
|
||||
|
||||
---
|
||||
|
||||
## S4: Skills Guide
|
||||
|
||||
**Bold tools (resume Technical Skills section):**
|
||||
Kubernetes, Docker, AWS (S3 · Glue · Athena · Redshift · CloudFormation), Kafka, GitLab CI/CD
|
||||
|
||||
**Must-include skills (ATS match):**
|
||||
- Kubernetes, Docker, Ansible
|
||||
- AWS (S3, Glue, Athena, Redshift, CloudFormation, Airflow), Apache Iceberg
|
||||
- GitLab CI/CD, Jenkins
|
||||
- Kafka, Apache Airflow
|
||||
- Python, SQL
|
||||
- ELK Stack, Grafana, Prometheus
|
||||
- IaC / CloudFormation
|
||||
- DevSecOps
|
||||
|
||||
**Nice-to-have (include if JD mentions):**
|
||||
- Terraform (not evidenced — do NOT claim; flag if JD requires)
|
||||
- Loki (log aggregation — from Bosch PoC)
|
||||
- PySpark (distributed processing on platform)
|
||||
- Ansible (Bosch ML orchestration)
|
||||
- Oracle DB, Teradata (enterprise data platform experience)
|
||||
|
||||
**Omit:**
|
||||
- BDD, Selenium, HP Quality Center, UIPath (testing — irrelevant)
|
||||
- Tibco Spotfire, SAP BODS (application tools — irrelevant)
|
||||
- RPA/Camunda (process automation — irrelevant)
|
||||
|
||||
**Certifications to highlight:**
|
||||
- AWS Certified Solutions Architect – Associate → HIGH (platform credibility, architecture knowledge)
|
||||
- Data Engineering with AWS → supporting
|
||||
- iSAQB CPSA Foundation Level → MED (software architecture — relevant for platform design decisions)
|
||||
|
||||
---
|
||||
|
||||
## S5: Cover Letter Guide
|
||||
|
||||
**Institution type:** Cloud-first tech company, scale-up with AWS-heavy stack, enterprise platform team, or data infrastructure consultancy
|
||||
|
||||
**Opening hook pattern:**
|
||||
> "Across my career at Swisscom and Bosch, I've owned data infrastructure at two ends of the spectrum: migrating Swisscom's legacy ETL stack to a cloud-native AWS platform (CloudFormation, Glue, Athena with Iceberg, Airflow) while operating Kubernetes-deployed Python applications with GitLab CI/CD — and containerizing ML inference into a 24/7 semiconductor production line at Bosch using Docker, Kubernetes, and Ansible. In both cases, the infrastructure had to be production-grade with no tolerance for downtime. [Tie to their platform challenge]."
|
||||
|
||||
**Key narrative thread:**
|
||||
1. **Production Kubernetes** — SW-3 + BS-1: K8s at two employers, in different contexts (data apps at Swisscom, ML inference at Bosch). Cross-employer K8s ownership is a strong signal.
|
||||
2. **Full AWS platform stack** — SW-1: Not just using one AWS service — migrating an entire ETL infrastructure to AWS with CloudFormation/IaC shows platform-level thinking.
|
||||
3. **Observability initiative** — BS-4: Self-initiated ELK + Prometheus + Grafana PoC shows platform engineer mindset (monitoring is not optional).
|
||||
4. **Security ownership** — SW-5: Security Champion ×3 = DevSecOps embedded in platform work, not an afterthought.
|
||||
|
||||
**"Why them" angle to research:**
|
||||
- What is their cloud stack? If AWS-heavy → your SAA cert + migration experience is directly relevant
|
||||
- Do they use Kubernetes in production? → Cross-employer K8s experience is the signal
|
||||
- Are they building their data platform from scratch vs. maintaining existing? → Tailor SW-1 (migration) vs. BS-4 (observability initiative) accordingly
|
||||
- Terraform vs. CloudFormation? → Note that your experience is CloudFormation; Terraform familiarity may need bridging
|
||||
|
||||
**Avoid:**
|
||||
- Leading with analytics or BI outcomes (platform audience cares about reliability and infrastructure)
|
||||
- Claiming SRE/pure DevOps title (you were a data engineer with platform ownership)
|
||||
- Overstating Terraform/Helm experience (not confirmed — do not claim)
|
||||
- Mentioning SCEDAS, maritime research, BDD, or RPA
|
||||
@@ -0,0 +1,127 @@
|
||||
# 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
|
||||
@@ -0,0 +1,153 @@
|
||||
# Experience: (Senior) Data Engineer / Data Analysis Engineer — Robert Bosch Semiconductor Manufacturing Dresden GmbH
|
||||
## February 2020 – December 2022 | Dresden, Germany
|
||||
|
||||
### Cross-Position Section
|
||||
|
||||
**Promotion within Bosch (confirmed by LinkedIn):**
|
||||
| Level | Period | Duration |
|
||||
|-------|--------|----------|
|
||||
| Data Engineer / Data Analysis | Feb 2020 – Jan 2021 | 1 year |
|
||||
| **Senior** Data Engineer / Data Analysis | Jan 2021 – Dec 2022 | 2 years |
|
||||
|
||||
**Title flexibility (IMPORTANT for generation):** The role was heavily data engineering in nature. Adapt the displayed title to the JD:
|
||||
- JD targets Data Engineer / Senior Data Engineer → use "(Senior) Data Engineer"
|
||||
- JD targets analytics-adjacent roles → use "(Senior) Data Analysis Engineer"
|
||||
- JD targets ML Engineer → use "Data & ML Engineer" (safe given BS-1 ML deployment work)
|
||||
- Show promotion when space allows: "Data Engineer → Senior Data Engineer" or "(Senior) Data Engineer"
|
||||
- Always show the promotion arc if the JD values seniority signals
|
||||
|
||||
**Career arc framing:** Bosch was Dennis's most technical pre-Swisscom role — applying data engineering and ML at scale in a 24/7 semiconductor manufacturing environment. He operated as Application Owner (not just developer), introduced containerized ML inference into production lines, and built monitoring infrastructure from scratch. Promoted from mid-level to Senior after one year. The Zeugnis rates performance as "sehr gut" (top tier) — employer deeply regrets departure.
|
||||
|
||||
**Semiconductor data domains (for targeting semi industry JDs):**
|
||||
Dennis worked across multiple data domains within the fab — these are domain signals for semiconductor company applications:
|
||||
- **Defect Management** — tracking, classifying, and analyzing wafer/chip defects; image-based defect detection
|
||||
- **Semiconductor Parameter Testing** — electrical parametric test data analysis across production lots
|
||||
- **Process Analysis** — correlating process parameters to yield and quality outcomes
|
||||
|
||||
This domain expertise is rare in data engineering candidates and is a strong differentiator for semiconductor company JDs (ASML, Infineon, TSMC, GlobalFoundries, etc.). Flag this domain when targeting semi roles.
|
||||
|
||||
**CL framing:** "At Bosch Semiconductor in Dresden, I worked at the intersection of data engineering and semiconductor manufacturing analytics — owning the data pipelines and applications that drove defect management, parameter testing analysis, and process optimization across 300mm wafer production. My most impactful project was containerizing ML inference for automated image-based defect classification, turning a manual quality inspection process into a fully automated, 24/7 production system."
|
||||
|
||||
---
|
||||
|
||||
### Achievement BS-1: ML Inference Containerization in 24/7 Production Environment
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md, thiessen_zeugnis_bosch.md
|
||||
**User's role:** Primary developer / strategy owner ("Erarbeitung und Durchführung" = designed AND executed)
|
||||
**Status:** Deployed to production
|
||||
|
||||
**Context:** 300mm semiconductor fab runs continuously. Manual image classification for wafer defect detection created a bottleneck for line engineers in the Defect Management domain. Dennis designed and implemented the strategy to containerize and orchestrate ML inference into the live production pipeline — enabling fully automated defect classification with no manual intervention.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Containerized and orchestrated ML inference (Docker, Kubernetes, Ansible) into 24/7 semiconductor production pipelines, enabling fully automated image-based defect classification and significantly reducing manual inspection workload for line engineers.
|
||||
- **3L:** Designed and executed the ML inference integration strategy for Bosch's 24/7 semiconductor fab — containerizing defect-detection models with Docker, orchestrating via Kubernetes and Ansible, and embedding automated image classification into the Defect Management pipeline; eliminated manual wafer inspection bottleneck and enabled continuous, unattended quality monitoring across active 300mm production lines.
|
||||
- **1L:** Containerized ML inference (Docker, K8s, Ansible) for automated image-based defect classification in 24/7 semiconductor fab.
|
||||
|
||||
**Key skills:** Docker, Kubernetes, Ansible, ML deployment, ML inference, containerization, MLOps, image classification, defect detection, production ML, semiconductor manufacturing
|
||||
**ATS keywords:** ML deployment, Kubernetes, Docker, Ansible, MLOps, inference, containerization, production ML, defect management, image classification, semiconductor
|
||||
**Reframing notes:**
|
||||
- ML/AI: this is the flagship bullet — always leads for ML/AI role type
|
||||
- Data Platform/Infra: emphasize K8s/Docker/Ansible infrastructure angle
|
||||
- Staff/Senior DE: include as evidence of ML pipeline ownership; frame around end-to-end delivery
|
||||
- Analytics Engineer: LOW — omit or condense
|
||||
|
||||
---
|
||||
|
||||
### Achievement BS-2: Data Services Over OracleDB and Hadoop/ImpalaSQL
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md, thiessen_zeugnis_bosch.md
|
||||
**User's role:** Primary developer
|
||||
**Status:** Deployed / operational
|
||||
|
||||
**Context:** Built Python, Java, and C# data services consuming from OracleDB and Hadoop/ImpalaSQL to supply internal analysis teams with structured data and insights for semiconductor process optimization.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Built data services in Python, Java and C# over OracleDB and Hadoop/ImpalaSQL, supplying semiconductor analysis teams with on-demand data access and insights for process optimization and quality monitoring.
|
||||
- **3L:** Developed multi-language data services (Python, Java, C#) on top of OracleDB and Hadoop/ImpalaSQL, providing analysis teams with reliable, structured access to manufacturing process data; optimized query performance and data availability for downstream analytics in a high-throughput 24/7 fab environment.
|
||||
- **1L:** Built Python/Java/C# data services over OracleDB and Hadoop/ImpalaSQL for semiconductor analysis teams.
|
||||
|
||||
**Key skills:** Python, Java, C#, OracleDB, Hadoop, ImpalaSQL, data services, query optimization
|
||||
**ATS keywords:** Python, Java, OracleDB, Hadoop, Impala, data pipeline, data services
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: supporting bullet — shows multi-language data service depth
|
||||
- Data Platform/Infra: include for OracleDB + Hadoop coverage
|
||||
- ML/AI: secondary — omit or condense; ML data feed angle if needed
|
||||
- Analytics Engineer: LOW — omit
|
||||
|
||||
---
|
||||
|
||||
### Achievement BS-3: Application Owner — Analytics Platforms
|
||||
|
||||
**Source:** thiessen_zeugnis_bosch.md, thiessen_cv_master_profile.md
|
||||
**User's role:** Application Owner — confirmed by Zeugnis as primary title/role
|
||||
**Status:** Ongoing ownership during employment
|
||||
|
||||
**Context:** Beyond development, Dennis held explicit Application Owner responsibility for the semiconductor data analysis software suite — managing SLOs, vendor communication, internal customer relationships, training, and documentation.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Served as Application Owner for semiconductor data analysis applications and upstream pipelines, defining SLOs, delivering user training and documentation, and managing vendor relationships to ensure reliable 24/7 system operations.
|
||||
- **3L:** Held Application Owner responsibility for the semiconductor analytics software suite and upstream data pipelines — defined SLOs, delivered training and technical documentation, managed communication with software vendors and internal stakeholders across Fertigungstechnologie teams; ensured stable 24/7 operations while coordinating adoption across analysis teams in a fast-moving production environment.
|
||||
- **1L:** Application Owner for semiconductor analytics software suite — SLOs, vendor management, user training, documentation.
|
||||
|
||||
**Key skills:** Application ownership, stakeholder management, SLO definition, vendor management, technical training, documentation
|
||||
**ATS keywords:** application owner, SLO, stakeholder management, technical documentation, vendor management
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: strong ownership signal — include to demonstrate senior-level accountability
|
||||
- All role types: valuable as a "breadth" bullet showing beyond pure development; usually included
|
||||
- Analytics Engineer: frame around "enabling reliable data access for analysis teams"
|
||||
|
||||
---
|
||||
|
||||
### Achievement BS-4: ELK Stack PoC — Anomaly Detection & Monitoring
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md (CV-2), thiessen_zeugnis_bosch.md
|
||||
**User's role:** Primary developer
|
||||
**Status:** Proof of concept — confirmed in CV-2 and Zeugnis
|
||||
|
||||
**Context:** Implemented a proof of concept using Elastic Stack (Elasticsearch, Logstash, Kibana) with Kafka for log ingestion and anomaly detection. Added Grafana, Prometheus, and Loki for monitoring and alerting across semiconductor manufacturing systems.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Delivered anomaly detection PoC using ELK Stack and Kafka (Docker) with Grafana, Prometheus and Loki monitoring — demonstrating centralized log management and alerting capability for 24/7 semiconductor manufacturing infrastructure.
|
||||
- **3L:** Designed and implemented an anomaly detection proof of concept using Elasticsearch, Logstash and Kibana (ELK) with Apache Kafka for log ingestion, containerized via Docker; added full observability stack with Grafana dashboards, Prometheus metrics and Loki log aggregation — validating centralized monitoring and alerting for high-volume 24/7 semiconductor production systems.
|
||||
- **1L:** ELK + Kafka PoC for anomaly detection; Grafana/Prometheus/Loki monitoring across semiconductor production.
|
||||
|
||||
**Key skills:** ELK Stack, Elasticsearch, Logstash, Kibana, Kafka, Grafana, Prometheus, Loki, Docker, observability, anomaly detection
|
||||
**ATS keywords:** ELK Stack, Elasticsearch, Kafka, Grafana, Prometheus, observability, monitoring, anomaly detection
|
||||
**Reframing notes:**
|
||||
- Data Platform/Infra: HIGH — leads with observability and monitoring stack
|
||||
- Staff/Senior DE: include as supporting signal for platform depth; PoC framing acceptable
|
||||
- ML/AI: frame anomaly detection angle for MLOps/monitoring fit
|
||||
- Analytics Engineer: LOW — omit
|
||||
|
||||
**Note:** This bullet appears in CV-2 only. Include when resume has budget; omit on tight 1-page version.
|
||||
|
||||
---
|
||||
|
||||
### Achievement BS-5: Tibco Spotfire C# Extensions
|
||||
|
||||
**Source:** thiessen_linkedin_profile.md
|
||||
**User's role:** Developer
|
||||
**Status:** Deployed
|
||||
|
||||
**Context:** Developed C# extensions for Tibco Spotfire data analysis tool, extending its visualization and analysis capabilities within the semiconductor manufacturing analytics environment.
|
||||
|
||||
**Bullet variants:**
|
||||
- **1L:** Developed C# extensions for Tibco Spotfire to extend analytics capabilities within the semiconductor data environment.
|
||||
|
||||
**Key skills:** C#, Tibco Spotfire, BI tooling, data visualization
|
||||
**ATS keywords:** Tibco Spotfire, C#, BI, data visualization
|
||||
**Reframing notes:**
|
||||
- Analytics Engineer: niche signal — include if JD mentions Spotfire or BI tooling
|
||||
- All other: LOW — omit; roll into skills section if relevant
|
||||
|
||||
---
|
||||
|
||||
## Position Summary
|
||||
|
||||
| Achievement | ID | Priority for DE | Priority for Analytics | Priority for ML/AI | Priority for Platform |
|
||||
|-------------|----|-----------------|-----------------------|--------------------|----------------------|
|
||||
| ML Inference Containerization | BS-1 | HIGH | LOW | HIGH | HIGH |
|
||||
| Data Services (Oracle/Hadoop) | BS-2 | HIGH | MED | MED | HIGH |
|
||||
| Application Owner | BS-3 | HIGH | HIGH | MED | HIGH |
|
||||
| ELK PoC / Monitoring | BS-4 | MED | LOW | MED | HIGH |
|
||||
| Tibco Spotfire Extensions | BS-5 | LOW | MED | LOW | LOW |
|
||||
@@ -0,0 +1,42 @@
|
||||
# Experience: Software Engineer — Capgemini Deutschland GmbH
|
||||
## November 2014 – May 2015 | Hamburg, Germany
|
||||
|
||||
### Cross-Position Section
|
||||
|
||||
**Career arc framing:** Capgemini was Dennis's first professional role after the Bundeswehr — a 6-month consulting engagement in the Technology Services APPS division, working on test automation for a transport logistics client. Despite its brevity, the Zeugnis rates performance as "sehr gut" (vollsten Zufriedenheit — top tier), and the employer deeply regrets departure. This role anchors the test automation thread that runs through Generali and Vizrt. Typically omitted from 2-page resumes; included in full CV for timeline completeness.
|
||||
|
||||
**Resume recommendation:** Omit from 2-page resume unless targeting roles where test automation breadth from earliest career adds value. Include on full CV (5-page) under early career section.
|
||||
|
||||
---
|
||||
|
||||
### Achievement CA-1: GUI Test Automation for Transport Logistics Client
|
||||
|
||||
**Source:** thiessen_zeugnis_capgemini.md
|
||||
**User's role:** Developer / implementer
|
||||
**Status:** Deployed
|
||||
|
||||
**Context:** Working on a Capgemini client project for a leading transport logistics company. Dennis planned and implemented test automation using Capgemini's internal GUI test framework and HP Quality Center (ALM), adapted existing automated test cases, implemented new ones from design specs, monitored automated runs, and coordinated bug fixes.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Implemented and managed GUI test automation suite for a transport logistics client using HP Quality Center (ALM) — planned, built and maintained automated test cases from design specifications, monitored test runs, and coordinated bug-fix cycles.
|
||||
- **1L:** Implemented GUI test automation (HP Quality Center) for transport logistics client; managed full test cycle from planning to bug-fix coordination.
|
||||
|
||||
**Key skills:** Test automation, GUI testing, HP Quality Center (ALM), test planning, defect management
|
||||
**ATS keywords:** test automation, HP Quality Center, ALM, GUI testing, defect management, quality assurance
|
||||
**Reframing notes:**
|
||||
- All roles: LOW on resume — too early-career and non-core for target roles
|
||||
- Full CV: include for timeline completeness and to show consistent test automation background from day one
|
||||
- Consulting context: frame as "client-facing" to show early consulting exposure
|
||||
|
||||
---
|
||||
|
||||
## Position Summary
|
||||
|
||||
| Achievement | ID | Priority for DE | Priority for Analytics | Priority for ML/AI | Priority for Platform |
|
||||
|-------------|----|-----------------|-----------------------|--------------------|----------------------|
|
||||
| GUI Test Automation | CA-1 | LOW | LOW | LOW | LOW |
|
||||
|
||||
**Resume inclusion guidance:**
|
||||
- 2-page resume: **Omit entirely**
|
||||
- 5-page CV: Include as single condensed bullet under "Early Career" or within timeline continuity section
|
||||
- Cover letter: Not relevant to mention
|
||||
@@ -0,0 +1,106 @@
|
||||
# Experience: Research Software Engineer — Fraunhofer-Center für Maritime Logistik und Dienstleistungen CML
|
||||
## September 2018 – October 2019 | Hamburg, Germany
|
||||
|
||||
### Cross-Position Section
|
||||
|
||||
**Career arc framing:** Fraunhofer CML bridges the test-automation / consulting era (Generali, Vizrt) with the data engineering / ML focus that defines Bosch and Swisscom. Here Dennis transitioned from pure software development into applied ML research — working on NLP for sea rescue transcription (ARTUS) and microservice architectures for maritime data exchange (MISSION). He also introduced CI/CD to the team independently. Fixed-term research contract, left by mutual agreement.
|
||||
|
||||
**CL framing:** "At Fraunhofer CML's maritime research center, I moved beyond product software into applied research — developing ML and NLP components for an automatic transcription system for sea rescue (ARTUS), and building the microservice backbone for a maritime data exchange platform (MISSION). I also brought CI/CD discipline to the team by independently setting up Jenkins-based build automation with quality gates."
|
||||
|
||||
---
|
||||
|
||||
### Achievement FC-1: SCEDAS Crew Scheduling System Development & CI/CD
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md, thiessen_zeugnis_fraunhofer.md
|
||||
**User's role:** Developer (C# app dev + CI/CD sole setup)
|
||||
**Status:** Deployed / operational software
|
||||
|
||||
**Context:** SCEDAS® is a Decision Support System for maritime crew scheduling with mathematical heuristics for optimal planning. Dennis developed features, fixed bugs, and independently set up the Jenkins CI/CD pipeline with quality gates — the first build automation at the team.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Developed and maintained SCEDAS crew scheduling software (C#, .NET, MS SQL, Entity Framework); independently established Jenkins CI/CD pipeline with quality gates, introducing build automation and continuous deployment to the team.
|
||||
- **3L:** Extended and maintained SCEDAS®, Fraunhofer CML's crew scheduling Decision Support System (C#, .NET, MS SQL Server, Entity Framework), improving runtime performance and correctness through increased test coverage; independently introduced Jenkins-based CI/CD pipeline with build automation and quality gates — the first deployment automation adopted by the team.
|
||||
- **1L:** Developed SCEDAS (C#/.NET/SQL) crew scheduling DSS; independently set up Jenkins CI/CD pipeline with quality gates.
|
||||
|
||||
**Key skills:** C#, .NET, Entity Framework, MS SQL Server, Jenkins, CI/CD, build automation, quality gates, software testing
|
||||
**ATS keywords:** C#, .NET, SQL Server, Jenkins, CI/CD, build automation, continuous deployment
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: frame CI/CD introduction as initiative signal — independent, not assigned
|
||||
- ML/AI: LOW — omit SCEDAS; mention only if CI/CD context is relevant
|
||||
- All roles: CI/CD setup is the key signal here; SCEDAS itself is context
|
||||
|
||||
---
|
||||
|
||||
### Achievement FC-2: ARTUS — ML/NLP for Sea Rescue Transcription
|
||||
|
||||
**Source:** thiessen_zeugnis_fraunhofer.md, thiessen_cv_master_profile.md
|
||||
**User's role:** Contributing developer (research team effort — hedge verbs)
|
||||
**Status:** Research project
|
||||
|
||||
**Context:** ARTUS was a Fraunhofer CML research project to develop an automatic transcription system for sea rescue operations using speech recognition and ML. Dennis contributed ML and NLP development components within the research team.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Contributed ML and NLP components to ARTUS, a Fraunhofer research project developing an automatic speech transcription system for sea rescue operations — applying speech recognition and machine learning to a safety-critical maritime domain.
|
||||
- **3L:** Developed ML and speech recognition components for ARTUS, a Fraunhofer CML research initiative targeting automatic transcription of sea rescue communications; contributed to the NLP pipeline and model development, bringing machine learning capabilities to a safety-critical domain with no prior automated transcription tooling at the center.
|
||||
- **1L:** Contributed ML/NLP components to ARTUS — sea rescue speech transcription system (Fraunhofer research).
|
||||
|
||||
**Key skills:** ML, NLP, speech recognition, Python, research, maritime safety
|
||||
**ATS keywords:** NLP, machine learning, speech recognition, Python, research
|
||||
**Reframing notes:**
|
||||
- ML/AI: HIGH — lead as evidence of applied ML/NLP research experience
|
||||
- Staff/Senior DE: MED — include as ML breadth signal; hedge verb "Contributed"
|
||||
- Analytics/Platform: LOW — omit
|
||||
|
||||
**Provenance:** "Entwicklungstätigkeiten" in Zeugnis = development work within a research team. Use "Contributed" not "Led". Do not claim sole ownership of ARTUS.
|
||||
|
||||
---
|
||||
|
||||
### Achievement FC-3: MISSION — Maritime Microservice Data Exchange Platform
|
||||
|
||||
**Source:** thiessen_zeugnis_fraunhofer.md, thiessen_cv_master_profile.md
|
||||
**User's role:** Developer (microservices for the platform)
|
||||
**Status:** Research prototype
|
||||
|
||||
**Context:** MISSION was a Fraunhofer CML research project to build a maritime data exchange platform. Dennis built microservices using Express.js, JavaScript, Docker, and SQLite to enable data exchange between maritime stakeholders.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Built microservices (Express.js, JavaScript, Docker, SQLite) for MISSION, a Fraunhofer research project creating a maritime data exchange platform — enabling structured data interchange between maritime logistics stakeholders.
|
||||
- **3L:** Developed the microservice layer for MISSION, a Fraunhofer CML research platform for maritime data exchange — built REST services in Express.js and JavaScript, containerized with Docker, and backed by SQLite; enabling data sharing across maritime logistics actors including ports, operators and research partners.
|
||||
- **1L:** Built Express.js/Docker microservices for MISSION — Fraunhofer maritime data exchange research platform.
|
||||
|
||||
**Key skills:** Express.js, JavaScript, Docker, SQLite, microservices, REST APIs, research prototyping
|
||||
**ATS keywords:** microservices, Docker, REST, Express.js, JavaScript, containerization
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: frame as microservice/Docker evidence from pre-Bosch period
|
||||
- ML/AI: LOW — omit
|
||||
- Data Platform/Infra: include for early Docker/microservice signal
|
||||
|
||||
---
|
||||
|
||||
### Achievement FC-4: Predictive Maintenance Research Grant Contribution
|
||||
|
||||
**Source:** thiessen_zeugnis_fraunhofer.md
|
||||
**User's role:** Contributor ("Mitarbeit" = participated)
|
||||
**Status:** Grant proposal (not an outcome claim)
|
||||
|
||||
**Context:** Contributed to a Fraunhofer research grant proposal targeting ML-based prediction of optimal maintenance timing for maritime equipment.
|
||||
|
||||
**Bullet variants:**
|
||||
- **1L:** Contributed to Fraunhofer research grant proposal for ML-based predictive maintenance in maritime operations.
|
||||
|
||||
**Key skills:** ML, predictive maintenance, research grant writing, maritime domain
|
||||
**ATS keywords:** predictive maintenance, machine learning, research
|
||||
**Reframing notes:**
|
||||
- ML/AI: include as minor signal if space allows
|
||||
- All others: LOW — omit; rarely warrants a dedicated bullet on resume
|
||||
|
||||
---
|
||||
|
||||
## Position Summary
|
||||
|
||||
| Achievement | ID | Priority for DE | Priority for Analytics | Priority for ML/AI | Priority for Platform |
|
||||
|-------------|----|-----------------|-----------------------|--------------------|----------------------|
|
||||
| SCEDAS + CI/CD | FC-1 | HIGH | LOW | LOW | MED |
|
||||
| ARTUS ML/NLP | FC-2 | MED | LOW | HIGH | LOW |
|
||||
| MISSION Microservices | FC-3 | MED | LOW | MED | MED |
|
||||
| Predictive Maintenance Grant | FC-4 | LOW | LOW | MED | LOW |
|
||||
@@ -0,0 +1,103 @@
|
||||
# Experience: Software Engineer → IT Consultant — Generali Deutschland Informatik Services GmbH (GDIS)
|
||||
## May 2015 – June 2017 | Hamburg/Cologne, Germany
|
||||
|
||||
### Cross-Position Section
|
||||
|
||||
**Career arc framing:** Generali (GDIS) was Dennis's first extended software role post-Bundeswehr — starting as a Graduate Trainee and progressing to IT Consultant in 9 months. He introduced BDD to the team (ran the initial PoC), held technical responsibility for test automation in a major workflow project, and pioneered Robotic Process Automation with UIPath. Also contributed to Apache Camel / Spring Boot integration PoC. Two-phase career: Graduate Programme (May 2015 – Sep 2016) then permanent IT Consultant role (Oct 2016 – Jun 2017). The Zeugnis rates performance as "gut" (good); employer regrets departure.
|
||||
|
||||
**CL framing:** "At Generali's IT subsidiary, I went from Graduate Trainee to IT Consultant within 9 months. I introduced BDD to the team — running the initial PoC, presenting to the Java Community, and training colleagues — and held technical ownership of the BDD test automation for the PIA-Postkorb/workflow project. I also built the first UIPath RPA PoC at GDIS, demonstrating initiative to extend the team's automation toolset beyond BDD."
|
||||
|
||||
---
|
||||
|
||||
### Achievement GN-1: BDD Technical Ownership & Team Evangelism
|
||||
|
||||
**Source:** thiessen_zeugnis_generali.md, thiessen_linkedin_profile.md
|
||||
**User's role:** Technical owner ("technische Verantwortung" — confirmed by Zeugnis)
|
||||
**Status:** Deployed / operational
|
||||
|
||||
**Context:** Generali had no BDD practice. Dennis introduced BDD to the team, ran an initial PoC, took technical ownership of BDD test automation for the PIA-Postkorb/SE-Projekt Workflow, trained colleagues, presented to the Java Community, and administered Jenkins build jobs.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Introduced and held technical ownership of BDD test automation at Generali GDIS (Serenity-BDD, Selenium, JBehave), including PoC, Jenkins CI/CD administration, team training and knowledge transfer across the Java Community.
|
||||
- **3L:** Pioneered BDD (Behaviour-Driven Development) at Generali GDIS — designed and ran the initial PoC, then assumed technical ownership of the full BDD test automation suite for the PIA-Postkorb/SE-Projekt Workflow using Serenity-BDD, Selenium, and JBehave; administered Jenkins build jobs, presented BDD to the Java Community, trained project team members, and advised business units on BDD adoption — elevating test automation maturity across the department.
|
||||
- **1L:** Introduced BDD to Generali GDIS; held technical ownership of Serenity-BDD/Selenium/JBehave suite and Jenkins CI/CD.
|
||||
|
||||
**Key skills:** BDD, Serenity-BDD, Selenium, JBehave, Jenkins, test automation, knowledge transfer, technical leadership, TDD
|
||||
**ATS keywords:** BDD, Selenium, Jenkins, test automation, CI/CD, JBehave, Java
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: frame as initiative + technical ownership signal; not core DE work but shows leadership
|
||||
- ML/AI: LOW — omit
|
||||
- All roles: useful as "introduced a practice" signal — shows initiative and cross-team influence
|
||||
|
||||
---
|
||||
|
||||
### Achievement GN-2: RPA / UIPath POC Development
|
||||
|
||||
**Source:** thiessen_zeugnis_generali.md, thiessen_linkedin_profile.md
|
||||
**User's role:** Primary developer ("Entwicklung von POCs mit UIPath" — confirmed Zeugnis)
|
||||
**Status:** Proof of concept
|
||||
|
||||
**Context:** Dennis developed UIPath RPA POCs at Generali GDIS, extending automation beyond test tooling into business process automation. Also served as point of contact for RPA/UIPath to Generali group companies.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Developed UIPath RPA proofs of concept at Generali GDIS and served as internal point of contact for RPA adoption across Generali group companies — extending automation from test tooling into business process automation.
|
||||
- **1L:** Developed UIPath RPA POCs; internal RPA contact for Generali group companies.
|
||||
|
||||
**Key skills:** UIPath, RPA, Robotic Process Automation, Camunda BPMN, business process automation
|
||||
**ATS keywords:** UIPath, RPA, Robotic Process Automation, business process automation
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: LOW — include only if JD asks for RPA or process automation breadth
|
||||
- Platform/Infra: LOW — omit
|
||||
- Any role: niche signal; include if JD targets automation broadly; otherwise omit from resume, include in CV
|
||||
|
||||
---
|
||||
|
||||
### Achievement GN-3: Java/J2EE Application Development
|
||||
|
||||
**Source:** thiessen_zeugnis_generali.md, thiessen_cv_master_profile.md
|
||||
**User's role:** Developer
|
||||
**Status:** Deployed / shipped
|
||||
|
||||
**Context:** Developed application features in Java/J2EE for PIA-Postkorb/SE-Projekt Workflow, implemented new requirements, and fixed bugs. Migrated WebServices to XLDeploy deployment process. Contributed to Apache Camel + Spring Boot Dispatcher POC.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Developed Java/J2EE application features for the PIA-Postkorb workflow portal; migrated WebServices to XLDeploy deployment process and contributed to an Apache Camel / Spring Boot integration PoC.
|
||||
- **1L:** Developed Java/J2EE features for PIA-Postkorb workflow; migrated WebServices to XLDeploy; contributed Apache Camel/Spring Boot PoC.
|
||||
|
||||
**Key skills:** Java, J2EE, JavaScript, Spring Boot, Apache Camel, XLDeploy, Oracle DB, web application development
|
||||
**ATS keywords:** Java, J2EE, Spring Boot, Apache Camel, Oracle DB
|
||||
**Reframing notes:**
|
||||
- All DE roles: LOW — Java/J2EE is legacy context; fold into skills if needed; rarely a standalone bullet at this career stage
|
||||
- Include only if JD explicitly requires Java backend or if filling page space on 2-page resume
|
||||
|
||||
---
|
||||
|
||||
### Achievement GN-4: IBM ODM Evaluation (Trainee Phase)
|
||||
|
||||
**Source:** thiessen_zeugnis_generali.md
|
||||
**User's role:** Evaluator / technical analyst
|
||||
**Status:** Internal evaluation (Trainee program)
|
||||
|
||||
**Context:** During the Graduate Trainee program, Dennis evaluated IBM Operation Decision Management (ODM) Decision Center v8.7 — a rules engine / decision management platform.
|
||||
|
||||
**Bullet variants:**
|
||||
- **1L:** Evaluated IBM ODM (Operation Decision Management) Decision Center v8.7 as part of Graduate Trainee program.
|
||||
|
||||
**Key skills:** IBM ODM, rules engine, decision management, IT consulting
|
||||
**ATS keywords:** IBM ODM, decision management, rules engine
|
||||
**Reframing notes:**
|
||||
- All roles: LOW — niche, legacy; include on CV only if targeting InsurTech or IBM-ecosystem roles
|
||||
- Omit from resume
|
||||
|
||||
---
|
||||
|
||||
## Position Summary
|
||||
|
||||
| Achievement | ID | Priority for DE | Priority for Analytics | Priority for ML/AI | Priority for Platform |
|
||||
|-------------|----|-----------------|-----------------------|--------------------|----------------------|
|
||||
| BDD Technical Ownership | GN-1 | MED | LOW | LOW | LOW |
|
||||
| UIPath RPA POC | GN-2 | LOW | LOW | LOW | LOW |
|
||||
| Java/J2EE App Dev | GN-3 | LOW | LOW | LOW | LOW |
|
||||
| IBM ODM Evaluation | GN-4 | LOW | LOW | LOW | LOW |
|
||||
|
||||
**Note:** Generali is the 5th position on a 2-page resume. Typically appears as 1–2 condensed bullets. Recommend: GN-1 as the primary bullet (BDD ownership + initiative), optionally fold GN-2 (RPA) as a clause within. GN-3 and GN-4 only for full CV.
|
||||
@@ -0,0 +1,155 @@
|
||||
# Experience: Staff Data, Analytics & AI Engineer — Swisscom (Schweiz) AG
|
||||
## October 2023 – Present | Bern, Switzerland
|
||||
|
||||
### Cross-Position Section
|
||||
|
||||
**Career arc framing:** Swisscom is Dennis's current and most senior role — a promotion from Senior to Staff (Engineer IV) in April 2025. This is the anchor position for all target role types. It demonstrates the full stack: owned pipelines, cloud migration, containerized delivery, security ownership, and stakeholder-facing data products. At a major national telco operating AWS-heavy infrastructure, this is the clearest signal for Staff/Senior Data Engineering, Data Platform, and ML Engineering roles.
|
||||
|
||||
**CL framing (for cover letters):** "My current role at Swisscom — Switzerland's largest telco — gives me end-to-end ownership of business-critical data pipelines at scale: from Oracle and Kafka ingestion through Teradata DWH to AWS cloud-native architecture. I've led the migration of legacy pipelines to serverless AWS services and own the full DevOps lifecycle including Kubernetes deployment, GitLab CI/CD, and on-call support."
|
||||
|
||||
---
|
||||
|
||||
### Achievement SW-1: AWS Migration of Legacy ETL Stack
|
||||
|
||||
**Source:** thiessen_swisscom_zwischenzeugnis.md, thiessen_cv_master_profile.md
|
||||
**User's role:** Primary owner / sole technical lead
|
||||
**Status:** Active / ongoing operational achievement
|
||||
|
||||
**Context:** Legacy ETL pipelines ran on Teradata and Oracle. Migration to AWS cloud-native stack reduces operational overhead, improves scalability, and positions the team for modern serverless workflows.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Migrated legacy Teradata/Oracle ETL pipelines to AWS cloud-native architecture (S3, Glue, Athena with Apache Iceberg, Redshift, Airflow, CloudFormation), reducing manual operational overhead and enabling scalable, serverless data processing for downstream analytics.
|
||||
- **3L:** Led migration of legacy Teradata/Oracle ETL stack to a fully cloud-native AWS architecture using S3, Glue Jobs and Tables, Athena with Apache Iceberg (open table format), Redshift, Lambda, Step Functions, Airflow, and CloudFormation for IaC; reduced operational overhead, improved pipeline observability, and enabled scalable serverless processing — directly accelerating data availability for B2B stakeholder analytics.
|
||||
- **1L:** Migrated legacy ETL stack to AWS (S3, Glue, Athena/Iceberg, Redshift, Airflow, CloudFormation) for scalable serverless data processing.
|
||||
|
||||
**Key skills:** AWS, S3, Glue, Athena, Apache Iceberg, Redshift, Lambda, Step Functions, Airflow, CloudFormation, IaC, ETL migration, cloud-native architecture
|
||||
**ATS keywords:** AWS, data pipeline migration, ETL, serverless, Airflow, Redshift, Glue, Athena, Apache Iceberg, CloudFormation, IaC
|
||||
**Reframing notes:**
|
||||
- Data Platform/Infra: lead with AWS architecture and serverless; de-emphasize downstream analytics angle
|
||||
- Staff/Senior DE: lead with ownership and scale; emphasize reduction in operational overhead
|
||||
- Analytics Engineer: lead with enabling analytics outcomes for B2B stakeholders
|
||||
- ML/AI: minor relevance — mention as infrastructure enabling ML data access
|
||||
|
||||
---
|
||||
|
||||
### Achievement SW-2: Component Ownership — Fulfillment ETL Pipelines
|
||||
|
||||
**Source:** thiessen_swisscom_zwischenzeugnis.md, thiessen_cv_master_profile.md
|
||||
**User's role:** Component Owner — primary responsible engineer
|
||||
**Status:** Active / ongoing
|
||||
|
||||
**Context:** Business-critical Fulfillment domain data flows from Oracle source systems into Teradata DWH via Kafka and Python pipelines. Dennis is Component Owner — accountable for data availability, SLA, quality, compliance and on-call duty.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Served as Component Owner for business-critical Fulfillment ETL pipelines (Oracle → Kafka → Teradata DWH in Python), ensuring data availability for downstream analysis under on-call SLA and full Data Governance compliance.
|
||||
- **3L:** Owned end-to-end component responsibility for Swisscom's Fulfillment domain ETL pipelines — ingesting business-critical data from Oracle and Kafka sources into Teradata DWH via Python; enforced Data Governance, security, and privacy standards; covered 2nd/3rd-level support and on-call duty to maintain SLA adherence at scale.
|
||||
- **1L:** Owned Fulfillment ETL pipelines (Oracle/Kafka → Teradata) as Component Owner under full on-call SLA and compliance accountability.
|
||||
|
||||
**Key skills:** ETL/ELT, Python, Kafka, Oracle, Teradata DWH, data governance, component ownership, on-call SLA, SAP BODS
|
||||
**ATS keywords:** ETL, Kafka, Teradata, Oracle, data pipeline, data governance, SLA, component ownership
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: this is the flagship ownership bullet — always include; leads with accountability signal
|
||||
- Data Platform/Infra: de-emphasize "Fulfillment domain" context; emphasize Kafka and Teradata scale
|
||||
- Analytics Engineer: frame around "enabling data availability for downstream analytics"
|
||||
- ML/AI: minor — mention as reliable data feed for ML models if needed
|
||||
|
||||
---
|
||||
|
||||
### Achievement SW-3: Python Applications on Kubernetes + GitLab CI/CD
|
||||
|
||||
**Source:** thiessen_swisscom_zwischenzeugnis.md, thiessen_linkedin_profile.md
|
||||
**User's role:** Primary developer / operator
|
||||
**Status:** Active / ongoing
|
||||
|
||||
**Context:** Python data applications deployed on Kubernetes clusters with GitLab CI/CD automation — containerized delivery in an agile DevOps team with full lifecycle ownership.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Designed, deployed and operated Python data applications on Kubernetes clusters with GitLab CI/CD automation, enabling reliable containerized pipeline delivery and continuous integration in an agile DevOps team.
|
||||
- **3L:** Built and operated Python-based data applications deployed to Kubernetes clusters; automated the full CI/CD lifecycle via GitLab, including build, test, and deployment pipelines — delivering containerized services reliably in an agile DevOps team with GitLab-managed quality gates and rollback controls.
|
||||
- **1L:** Deployed and operated Python data apps on Kubernetes with GitLab CI/CD in an agile DevOps team.
|
||||
|
||||
**Key skills:** Python, Kubernetes, GitLab CI/CD, Docker, containerization, DevOps, agile
|
||||
**ATS keywords:** Kubernetes, Python, GitLab, CI/CD, Docker, DevOps, containerization
|
||||
**Reframing notes:**
|
||||
- Data Platform/Infra: lead with K8s and CI/CD; emphasize infrastructure automation angle
|
||||
- Staff/Senior DE: pair with SW-2 to show pipeline + deployment ownership as a unit
|
||||
- ML/AI: frame as "deployed ML-ready Python services to Kubernetes"
|
||||
|
||||
---
|
||||
|
||||
### Achievement SW-4: B2B Data Products, Stakeholder Analytics & Process Automation
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md, thiessen_swisscom_zwischenzeugnis.md, thiessen_linkedin_profile.md
|
||||
**User's role:** Data product owner / analyst-engineer interface
|
||||
**Status:** Active / ongoing
|
||||
|
||||
**Context:** Delivered data products, dashboards and analyses for B2B stakeholders; also drove automation of technical processes and conducted root cause analysis under 2nd/3rd level support.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Delivered data products, analyses and dashboards for B2B stakeholders; drove automation of technical workflows and performed root cause analysis under 2nd/3rd-level support responsibility to maintain data platform reliability.
|
||||
- **3L:** Partnered with Product Owner to refine and prioritize backlog, enabling agile delivery of data products and dashboards for B2B stakeholders; proactively drove automation of recurring technical processes and conducted structured root cause analysis under 2nd/3rd-level support and on-call duty — bridging engineering depth with business delivery cadence.
|
||||
- **1L:** Delivered B2B data products and dashboards; drove process automation and root cause analysis under 3rd-level support.
|
||||
|
||||
**Key skills:** Data products, dashboards, stakeholder management, root cause analysis, agile backlog management, product ownership collaboration, PySpark
|
||||
**ATS keywords:** data products, stakeholder management, agile, backlog, dashboards, root cause analysis
|
||||
**Reframing notes:**
|
||||
- Analytics Engineer: this is the primary bullet for this role type — lead with stakeholder/product angle
|
||||
- Staff/Senior DE: supporting bullet; frame around reliability and automation
|
||||
- ML/AI: minor relevance unless JD asks for MLOps/data product ownership
|
||||
|
||||
---
|
||||
|
||||
### Achievement SW-5: Security Champion — 3 Consecutive Years
|
||||
|
||||
**Source:** thiessen_swisscom_security_champion.md, thiessen_swisscom_zwischenzeugnis.md
|
||||
**User's role:** Designated Security Champion (annually renewed)
|
||||
**Status:** Active (2025/26 badge current)
|
||||
|
||||
**Context:** Swisscom's Security Champion program requires 100h of structured training covering Cloud Security, DevSecOps, Security by Design, and Risk Management, plus a 40-question assessment (>80% passing grade). Dennis has held this role for 3 consecutive years.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Named Swisscom Security Champion for 3 consecutive years (2023/24–2025/26), owning security compliance, risk monitoring and deviation tracking for the team's pipelines; completed 100h annual DevSecOps training with >80% assessment score.
|
||||
- **3L:** Designated as Security Champion for Swisscom's Data Lake team for 3 consecutive years (2023/24, 2024/25, 2025/26) — responsible for security compliance in development and operation, risk monitoring, and deviation reporting; fulfilled annual 100h structured training across Cloud Security, DevSecOps, Security by Design, and Security Risk Management, passing a 40-question comprehensive assessment with >80% score each year.
|
||||
- **1L:** Swisscom Security Champion for 3 consecutive years (2023–2026) — DevSecOps, risk monitoring, 100h training + assessment.
|
||||
|
||||
**Key skills:** DevSecOps, security compliance, risk management, security awareness, Security by Design
|
||||
**ATS keywords:** DevSecOps, security champion, security compliance, risk management, cloud security
|
||||
**Reframing notes:**
|
||||
- Data Platform/Infra: HIGH relevance — embed security in infrastructure angle
|
||||
- Staff/Senior DE: include as supporting signal for senior-level ownership breadth
|
||||
- Analytics Engineer: LOW — de-emphasize or omit unless JD asks for security awareness
|
||||
- ML/AI: include for AI-adjacent roles where model security/compliance is relevant
|
||||
|
||||
---
|
||||
|
||||
### Achievement SW-6: PySpark Backend Engineering
|
||||
|
||||
**Source:** thiessen_linkedin_profile.md
|
||||
**User's role:** Developer
|
||||
**Status:** Active / ongoing (Staff-level confirmed)
|
||||
|
||||
**Context:** PySpark used in backend data engineering at Staff level at Swisscom. Confirms Big Data processing capability beyond standard Python/SQL.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Applied PySpark for large-scale backend data processing alongside Python and SQL, extending pipeline capabilities to distributed Big Data workloads within the Swisscom Data Lake platform.
|
||||
- **1L:** Applied PySpark for distributed data processing in the Swisscom Data Lake environment.
|
||||
|
||||
**Key skills:** PySpark, Apache Spark, big data, distributed computing
|
||||
**ATS keywords:** PySpark, Spark, big data, distributed processing
|
||||
**Reframing notes:**
|
||||
- This is a skills signal more than a standalone achievement; roll into skills taxonomy
|
||||
- Mention in bullet if JD explicitly requires Spark/PySpark
|
||||
- Can be folded into SW-2 or SW-3 bullet if space is tight
|
||||
|
||||
---
|
||||
|
||||
## Position Summary
|
||||
|
||||
| Achievement | ID | Priority for DE | Priority for Analytics | Priority for ML/AI | Priority for Platform |
|
||||
|-------------|----|-----------------|-----------------------|--------------------|----------------------|
|
||||
| AWS Migration | SW-1 | HIGH | HIGH | MED | HIGH |
|
||||
| Component Owner / Fulfillment ETL | SW-2 | HIGH | HIGH | MED | HIGH |
|
||||
| Kubernetes + GitLab CI/CD | SW-3 | HIGH | MED | HIGH | HIGH |
|
||||
| B2B Data Products + Automation | SW-4 | MED | HIGH | MED | MED |
|
||||
| Security Champion | SW-5 | MED | LOW | MED | HIGH |
|
||||
| PySpark | SW-6 | MED | LOW | MED | MED |
|
||||
@@ -0,0 +1,67 @@
|
||||
# Experience: DevOps Engineer — Vizrt
|
||||
## July 2017 – May 2018 | Bergen, Norway
|
||||
|
||||
### Cross-Position Section
|
||||
|
||||
**Career arc framing:** Vizrt was Dennis's only international role outside DACH — a Norwegian broadcast technology company (customers: CNN, BBC, Al Jazeera). He worked embedded in the Coder (software engineering) team, not a standalone QA/test team — his scope covered Python/C++ backend development, automated test suite development, and CI/CD pipeline integration with quality gates. The DevOps title reflects this full scope: engineering + test automation integrated into the delivery pipeline. The reference from Team Lead Raymond Hilseth explicitly states he "exceeded expectations" with "little to no supervision." Resigned voluntarily to return to Germany.
|
||||
|
||||
**Title flexibility:** Use "DevOps Engineer" as primary. For roles where CI/CD is the key signal, emphasize pipeline integration; for roles where software engineering is primary, emphasize backend development. Do NOT reduce to "Test Automation Engineer" — the role was broader.
|
||||
|
||||
**CL framing:** "At Vizrt in Bergen, I worked as a DevOps engineer embedded in the core software team — developing distributed video transcoding backend components in Python and C++, building the automated test suite for A/V streaming, and integrating tests and quality gates into the CI/CD pipeline. The reference from my team lead confirms I operated with minimal supervision and exceeded expectations throughout."
|
||||
|
||||
---
|
||||
|
||||
### Achievement VZ-1: Distributed Video Transcoding Backend
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md
|
||||
**User's role:** Primary developer
|
||||
**Status:** Shipped to production
|
||||
|
||||
**Context:** Vizrt's broadcast software requires a distributed backend for real-time video transcoding. Dennis engineered backend components in Python and C++ as part of the Coder team — contributing to the core transcoding pipeline used by global broadcast customers.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Engineered distributed video transcoding backend components in Python and C++ for Vizrt's broadcast platform (customers: CNN, BBC, Al Jazeera), contributing to the core A/V processing pipeline as part of the software engineering team.
|
||||
- **3L:** Developed Python and C++ backend components for Vizrt's distributed real-time video transcoding system, used in live broadcast workflows by major global media organizations including CNN, BBC, and Al Jazeera; contributed to the core A/V pipeline within the Coder (software engineering) team, operating with high autonomy under minimal supervision.
|
||||
- **1L:** Developed Python/C++ distributed video transcoding backend for Vizrt broadcast platform (CNN, BBC, Al Jazeera).
|
||||
|
||||
**Key skills:** Python, C++, distributed systems, A/V streaming, backend engineering
|
||||
**ATS keywords:** Python, C++, distributed systems, backend engineering, streaming
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: include as Python/C++ breadth signal; frame around distributed systems
|
||||
- ML/AI: LOW — omit or condense
|
||||
- Platform/Infra: include as distributed backend signal
|
||||
- All roles: customer name-dropping (CNN, BBC) adds credibility to the role's scale
|
||||
|
||||
---
|
||||
|
||||
### Achievement VZ-2: Test Automation + CI/CD Quality Gates Integration
|
||||
|
||||
**Source:** thiessen_cv_master_profile.md, thiessen_zeugnis_vizrt.md, user clarification
|
||||
**User's role:** Primary developer
|
||||
**Status:** Deployed / operational
|
||||
|
||||
**Context:** Dennis built integration and unit test suites for Audio, Video & Streaming in Python AND integrated them into the CI/CD pipeline with quality gates — ensuring automated checks ran on every build and blocked releases that failed quality thresholds. This is the DevOps angle: not just writing tests, but owning the quality gate mechanism in the delivery pipeline.
|
||||
|
||||
**Bullet variants:**
|
||||
- **2L:** Built automated integration and unit test suite for A/V streaming (Python) and integrated quality gates into the CI/CD pipeline, shortening the feedback loop for new features and bug fixes while improving release quality of Vizrt's broadcast software.
|
||||
- **3L:** Developed a comprehensive automated test suite (integration and unit tests in Python) for Vizrt's Audio, Video and Streaming components, and integrated these tests as quality gates into the CI/CD delivery pipeline — blocking failing builds, reducing time to market, and improving release-over-release reliability of broadcast software deployed to global media customers including CNN, BBC, and Al Jazeera.
|
||||
- **1L:** Built Python A/V test suite and integrated quality gates into CI/CD pipeline for Vizrt broadcast platform.
|
||||
|
||||
**Key skills:** Python, test automation, integration testing, unit testing, CI/CD, quality gates, A/V streaming, DevOps
|
||||
**ATS keywords:** test automation, Python, CI/CD, quality gates, integration testing, DevOps
|
||||
**Reframing notes:**
|
||||
- Staff/Senior DE: pair with VZ-1; frame as "DevOps ownership of test pipeline"
|
||||
- Data Platform/Infra: include for CI/CD quality gate signal
|
||||
- ML/AI: LOW — omit
|
||||
- All roles: CI/CD integration angle elevates this beyond pure test writing — always use this framing
|
||||
|
||||
---
|
||||
|
||||
## Position Summary
|
||||
|
||||
| Achievement | ID | Priority for DE | Priority for Analytics | Priority for ML/AI | Priority for Platform |
|
||||
|-------------|----|-----------------|-----------------------|--------------------|----------------------|
|
||||
| Video Transcoding Backend | VZ-1 | MED | LOW | LOW | MED |
|
||||
| Automated Test Suite | VZ-2 | MED | LOW | LOW | LOW |
|
||||
|
||||
**Note:** Vizrt is typically the 4th position on a 2-page resume and may appear as a condensed single bullet combining both achievements. Use 2L variants when space allows; condense to 1L if page-limited.
|
||||
@@ -0,0 +1,313 @@
|
||||
# Achievement Reframing Guide — Dennis Thiessen
|
||||
|
||||
> Generated: 2026-03-28
|
||||
> Role types from config.md: Staff/Senior Data Engineer | Analytics Engineer | ML/AI Engineer | Data Platform/Infra
|
||||
|
||||
---
|
||||
|
||||
## How to Use
|
||||
|
||||
Each achievement has a **Significance** line (why it matters to any reader) and a role-type table showing how to frame, which verb to lead with, and whether to include or omit for that audience. Use this guide when selecting and ordering bullets during resume generation.
|
||||
|
||||
**Priority tiers:**
|
||||
- **HIGH** — Lead bullet or include in all variants of this position
|
||||
- **MED** — Include if page budget allows; adjust framing per role type
|
||||
- **LOW** — Omit from resume; include in full CV or CL only
|
||||
|
||||
---
|
||||
|
||||
## SWISSCOM ACHIEVEMENTS
|
||||
|
||||
---
|
||||
|
||||
### SW-1: AWS Migration of Legacy ETL Stack
|
||||
**Significance:** Demonstrates hands-on cloud migration ownership at scale — a tier-1 signal for all data engineering and platform roles. AWS is the market-dominant cloud; owning a full migration from legacy to serverless is a top-of-market achievement.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | HIGH | Migrated | Lead with scale + operational impact (reduced overhead) |
|
||||
| Analytics Engineer | HIGH | Migrated | Lead with "enabling analytics outcomes" — tie to downstream stakeholder value |
|
||||
| ML/AI Engineer | MED | Migrated | Frame as "building the data infrastructure enabling ML workflows" |
|
||||
| Data Platform/Infra | HIGH | Architected | Lead with cloud-native architecture decisions; de-emphasize analytics framing |
|
||||
|
||||
**Overclaiming warning:** No specific throughput/volume numbers available — do not invent. Use qualitative impact (operational overhead reduction, scalability improvement).
|
||||
|
||||
---
|
||||
|
||||
### SW-2: Component Ownership — Fulfillment ETL Pipelines
|
||||
**Significance:** Component Owner is a staff-level accountability signal — owning reliability, compliance, and on-call for business-critical data. Demonstrates senior engineer maturity beyond pure development.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | HIGH | Owned | Lead with accountability: Component Owner, SLA, on-call. This is the flagship bullet. |
|
||||
| Analytics Engineer | HIGH | Owned | Frame as "ensuring data availability for downstream analytics" — business impact angle |
|
||||
| ML/AI Engineer | MED | Owned | Frame as "reliable data feed for ML model inputs" |
|
||||
| Data Platform/Infra | HIGH | Owned | Lead with Kafka/Teradata infrastructure; de-emphasize "Fulfillment domain" context |
|
||||
|
||||
**Overclaiming warning:** None — employer-confirmed via Zeugnis.
|
||||
|
||||
---
|
||||
|
||||
### SW-3: Python Applications on Kubernetes + GitLab CI/CD
|
||||
**Significance:** Kubernetes ownership at Staff level in a production environment — paired with GitLab CI/CD — is a strong infrastructure signal. Confirms the "SWE + Ops" hybrid identity from LinkedIn summary.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | HIGH | Deployed | Show DevOps ownership as part of the data engineering role |
|
||||
| Analytics Engineer | MED | Deployed | Include only if JD mentions platform ownership; otherwise de-emphasize |
|
||||
| ML/AI Engineer | HIGH | Deployed | Frame as "containerized ML-ready Python services on Kubernetes" |
|
||||
| Data Platform/Infra | HIGH | Built & operated | Lead with infrastructure automation; K8s + CI/CD is the core signal |
|
||||
|
||||
---
|
||||
|
||||
### SW-4: B2B Data Products, Stakeholder Analytics & Automation
|
||||
**Significance:** Demonstrates the bridge between engineering and business — delivering actionable data to stakeholders while automating operations. Key for Analytics Engineer positioning; supporting for others.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Delivered | Supporting bullet — shows stakeholder-facing breadth; pair with SW-2 |
|
||||
| Analytics Engineer | HIGH | Delivered | LEAD bullet for this role type — emphasize B2B stakeholder impact and dashboard delivery |
|
||||
| ML/AI Engineer | LOW | — | Omit or condense; not core ML signal |
|
||||
| Data Platform/Infra | LOW | — | Omit; not infrastructure-focused |
|
||||
|
||||
---
|
||||
|
||||
### SW-5: Security Champion — 3 Consecutive Years
|
||||
**Significance:** 3 consecutive years = institutional trust, not just a one-time training. Signals security ownership across the DevSecOps lifecycle — rare for a data engineer to hold this level of security designation.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Designated | Include as breadth signal for senior roles; shows accountability beyond code |
|
||||
| Analytics Engineer | LOW | — | Omit — not differentiating for this audience |
|
||||
| ML/AI Engineer | MED | Designated | Include for AI product companies where model security/compliance is relevant |
|
||||
| Data Platform/Infra | HIGH | Designated | Lead DevSecOps angle — infrastructure roles care about security compliance |
|
||||
|
||||
---
|
||||
|
||||
### SW-6: PySpark Backend Engineering
|
||||
**Significance:** Confirms Big Data / distributed processing capability at Staff level. Differentiates from Python-only data engineers when JD requires Spark.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| All role types | MED | Applied | Roll into skills section unless JD explicitly requires PySpark — then elevate to bullet |
|
||||
| Data Platform/Infra | MED | Applied | Include as distributed processing signal |
|
||||
|
||||
---
|
||||
|
||||
## BOSCH ACHIEVEMENTS
|
||||
|
||||
---
|
||||
|
||||
### BS-1: ML Inference Containerization in 24/7 Production (Defect Management Domain)
|
||||
**Significance:** Deploying ML models into a continuous, uninterruptible semiconductor production line is a uniquely high-stakes MLOps achievement — far beyond typical "model trained in notebook" experience. The defect management domain (image-based wafer defect classification) adds semiconductor industry specificity — a rare combination of MLOps depth + semiconductor domain expertise.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | HIGH | Containerized | Frame as data pipeline + ML integration — "production ML as part of data infrastructure" |
|
||||
| Analytics Engineer | MED | Containerized | For semi industry JDs: include with defect management domain framing — "automated defect classification analytics" |
|
||||
| ML/AI Engineer | HIGH | Containerized | FLAGSHIP bullet — lead with "24/7 production ML", automated inference, K8s orchestration, defect detection |
|
||||
| Data Platform/Infra | HIGH | Containerized | Lead with Docker/K8s/Ansible infrastructure; de-emphasize ML domain |
|
||||
| **Semiconductor JDs** | HIGH | Containerized | Lead with defect management domain — "automated image-based defect classification for 300mm fab"; this is the differentiating signal for semi industry applications |
|
||||
|
||||
**Overclaiming warning:** "Significantly reducing manual workload" is the claim — employer Zeugnis says "enabling fully automated image classification". Safe to use. No percentage available — do not invent.
|
||||
|
||||
---
|
||||
|
||||
### BS-2: Data Services Over OracleDB and Hadoop/ImpalaSQL
|
||||
**Significance:** Multi-language (Python/Java/C#) data service development over enterprise-grade databases in a high-throughput manufacturing environment confirms broad data engineering depth and platform-agnostic capability. For semiconductor JDs: these data services fed Defect Management, Parameter Testing, and Process Analysis teams directly.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | HIGH | Built | Lead with data service breadth; multiple languages + Oracle + Hadoop = enterprise DE depth |
|
||||
| Analytics Engineer | MED | Built | Frame as "supplying analysis teams with structured data access" |
|
||||
| Analytics Engineer (semi JD) | HIGH | Built | Lead with domain: "supplying defect management and parameter testing teams with on-demand data and insights" |
|
||||
| ML/AI Engineer | MED | Built | Frame as "data layer enabling ML model inputs" |
|
||||
| Data Platform/Infra | HIGH | Built | Lead with Oracle + Hadoop infrastructure combination |
|
||||
|
||||
---
|
||||
|
||||
### BS-3: Application Owner — Analytics Platforms
|
||||
**Significance:** Application Owner is a well-understood seniority signal in German/Swiss tech companies — it means owning the system's lifecycle, not just writing code. SLO definition + training + stakeholder management = staff-level maturity.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | HIGH | Owned | ALWAYS include — clearest seniority signal from Bosch period |
|
||||
| Analytics Engineer | HIGH | Owned | Frame as "enabling reliable data access for analysis teams" |
|
||||
| ML/AI Engineer | MED | Owned | Include as operational ownership signal |
|
||||
| Data Platform/Infra | HIGH | Owned | Frame around SLA + platform reliability angle |
|
||||
|
||||
---
|
||||
|
||||
### BS-4: ELK Stack PoC — Anomaly Detection & Monitoring
|
||||
**Significance:** Self-initiated observability work beyond the core job scope — demonstrates initiative and infrastructure curiosity. ELK + Kafka + Grafana/Prometheus is a recognizable modern observability stack.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Delivered | Supporting bullet — shows platform breadth; include if space allows |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | MED | Delivered | Frame as anomaly detection ML application |
|
||||
| Data Platform/Infra | HIGH | Delivered | Lead observability stack angle — ELK + Prometheus + Grafana |
|
||||
|
||||
**Note:** CV-2 only. Include when 2-page resume has budget; always in 5-page CV.
|
||||
|
||||
---
|
||||
|
||||
### BS-5: Tibco Spotfire C# Extensions
|
||||
**Significance:** Minor — niche BI tooling signal. Only relevant if JD specifically mentions Spotfire or C#-based analytics tooling.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| All role types | LOW | — | Omit from resume; include in skills taxonomy only |
|
||||
| Analytics Engineer | LOW | Developed | Include only if JD explicitly names Spotfire |
|
||||
|
||||
---
|
||||
|
||||
## FRAUNHOFER ACHIEVEMENTS
|
||||
|
||||
---
|
||||
|
||||
### FC-1: SCEDAS Development + CI/CD Pipeline Introduction
|
||||
**Significance:** Independently introduced CI/CD to a research team (no prior automation existed) — strong initiative signal. SCEDAS development confirms C# / .NET / SQL depth. The CI/CD angle is more valuable for target roles than the DSS domain.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Established (for CI/CD) | Lead with CI/CD independence; SCEDAS is context |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | LOW | — | Omit |
|
||||
| Data Platform/Infra | MED | Established | Lead with pipeline automation initiative |
|
||||
|
||||
---
|
||||
|
||||
### FC-2: ARTUS — ML/NLP for Sea Rescue Transcription
|
||||
**Significance:** Applied ML/NLP in a safety-critical domain as part of a named research project at a leading European applied research institute. Confirms early ML/NLP exposure (pre-Bosch) — establishes ML thread across career.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Contributed | Supporting signal — shows ML breadth from earlier career |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | HIGH | Contributed | Include — establishes NLP / ML research background; pair with Bosch ML deployment |
|
||||
| Data Platform/Infra | LOW | — | Omit |
|
||||
|
||||
**Verb:** ALWAYS use "Contributed" — this was research team work, not sole development.
|
||||
|
||||
---
|
||||
|
||||
### FC-3: MISSION — Maritime Microservice Platform
|
||||
**Significance:** Hands-on microservices + Docker in 2018–2019 — predates the containerization wave. Shows early adoption of modern architecture patterns.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Built | Early Docker/microservice signal — pair with FC-1 |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | LOW | — | Omit |
|
||||
| Data Platform/Infra | MED | Built | Early containerization signal |
|
||||
|
||||
---
|
||||
|
||||
### FC-4: Predictive Maintenance Grant Contribution
|
||||
**Significance:** Minimal — contributed to a grant proposal. Include only in CL for research-adjacent roles.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| All roles | LOW | Contributed | CL mention only — not a resume bullet |
|
||||
|
||||
---
|
||||
|
||||
## VIZRT ACHIEVEMENTS
|
||||
|
||||
---
|
||||
|
||||
### VZ-1: Distributed Video Transcoding Backend
|
||||
**Significance:** Python + C++ in a distributed backend for a globally-deployed broadcast platform (CNN, BBC, Al Jazeera scale). Confirms systems programming capability and international team experience.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Engineered | Include as backend systems depth signal |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | LOW | — | Omit |
|
||||
| Data Platform/Infra | MED | Engineered | Include for distributed systems signal |
|
||||
|
||||
---
|
||||
|
||||
### VZ-2: Test Automation + CI/CD Quality Gates Integration
|
||||
**Significance:** Owning the quality gate mechanism in a CI/CD pipeline for production broadcast software — more than just test writing. Shortening feedback loop and time-to-market at a company serving global broadcasters.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Built | Include as CI/CD quality ownership signal |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | LOW | — | Omit |
|
||||
| Data Platform/Infra | MED | Built | Include for CI/CD depth; quality gates framing |
|
||||
|
||||
**Note:** For tight 2-page budgets, combine VZ-1 and VZ-2 into a single 2L bullet for Vizrt position.
|
||||
|
||||
---
|
||||
|
||||
## GENERALI ACHIEVEMENTS
|
||||
|
||||
---
|
||||
|
||||
### GN-1: BDD Technical Ownership & Team Evangelism
|
||||
**Significance:** Introduced a practice (BDD) to an organization and then held technical ownership of it — demonstrates initiative, technical leadership, and knowledge-transfer capability. Strongest signal from Generali period.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| Staff/Senior Data Engineer | MED | Introduced | Include as initiative + technical leadership thread from earlier career |
|
||||
| Analytics Engineer | LOW | — | Omit |
|
||||
| ML/AI Engineer | LOW | — | Omit |
|
||||
| Data Platform/Infra | LOW | — | Omit |
|
||||
|
||||
---
|
||||
|
||||
### GN-2: UIPath RPA POC
|
||||
**Significance:** Early RPA experience — niche signal. Only relevant for roles explicitly targeting automation engineering.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| All roles | LOW | Developed | Omit from resume; include in CV if space |
|
||||
|
||||
---
|
||||
|
||||
### GN-3 & GN-4: Java/J2EE Development + IBM ODM
|
||||
**Significance:** Early-career Java and enterprise software context. Not differentiating at current career stage.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| All roles | LOW | — | CV only — early career context |
|
||||
|
||||
---
|
||||
|
||||
## CAPGEMINI ACHIEVEMENTS
|
||||
|
||||
---
|
||||
|
||||
### CA-1: GUI Test Automation — Transport Logistics Client
|
||||
**Significance:** Establishes the test automation thread from day one of career. Zeugnis rates "vollsten Zufriedenheit" (top tier) despite being only 6 months. Historical context only at current career stage.
|
||||
|
||||
| Role Type | Priority | Lead Verb | Framing Angle |
|
||||
|-----------|----------|-----------|---------------|
|
||||
| All roles | LOW | Implemented | CV only — do not include on 2-page resume |
|
||||
|
||||
---
|
||||
|
||||
## Master Priority Matrix (Cross-Role)
|
||||
|
||||
| Achievement | Staff/Senior DE | Analytics Eng | ML/AI Eng | Data Platform/Infra |
|
||||
|-------------|----------------|---------------|-----------|---------------------|
|
||||
| SW-1 AWS Migration | HIGH | HIGH | MED | HIGH |
|
||||
| SW-2 Component Owner | HIGH | HIGH | MED | HIGH |
|
||||
| SW-3 K8s + GitLab | HIGH | MED | HIGH | HIGH |
|
||||
| SW-4 B2B Products | MED | HIGH | LOW | LOW |
|
||||
| SW-5 Security Champion | MED | LOW | MED | HIGH |
|
||||
| SW-6 PySpark | MED | LOW | MED | MED |
|
||||
| BS-1 ML Inference | HIGH | LOW | HIGH | HIGH |
|
||||
| BS-2 Data Services | HIGH | MED | MED | HIGH |
|
||||
| BS-3 App Owner | HIGH | HIGH | MED | HIGH |
|
||||
| BS-4 ELK PoC | MED | LOW | MED | HIGH |
|
||||
| FC-1 SCEDAS + CI/CD | MED | LOW | LOW | MED |
|
||||
| FC-2 ARTUS ML/NLP | MED | LOW | HIGH | LOW |
|
||||
| FC-3 MISSION Microsvcs | MED | LOW | LOW | MED |
|
||||
| VZ-1 Video Backend | MED | LOW | LOW | MED |
|
||||
| VZ-2 CI/CD Quality Gates | MED | LOW | LOW | MED |
|
||||
| GN-1 BDD Ownership | MED | LOW | LOW | LOW |
|
||||
| GN-2 UIPath RPA | LOW | LOW | LOW | LOW |
|
||||
@@ -0,0 +1,58 @@
|
||||
# Publication Metadata — Dennis Thiessen
|
||||
|
||||
> Generated: 2026-03-28
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
- **Academic publications:** 0
|
||||
- **Peer-reviewed papers:** 0
|
||||
- **Conference papers:** 0
|
||||
- **Research projects (named, employer-confirmed):** 3 (ARTUS, MISSION, Predictive Maintenance grant)
|
||||
- **Personal projects:** 1 (RiskAhead — discontinued)
|
||||
|
||||
Dennis is a software and data engineering professional, not an academic researcher. His Fraunhofer CML period involved applied research, but as a software contributor — not a publishing author. Do not include a "Publications" section on resume or CV.
|
||||
|
||||
---
|
||||
|
||||
## Named Research Projects (for CV / CL context only)
|
||||
|
||||
| # | Project | Institution | Period | Dennis's Role | Output |
|
||||
|---|---------|-------------|--------|--------------|--------|
|
||||
| 1 | ARTUS | Fraunhofer CML | 2018–2019 | Contributing developer (ML/NLP components) | Internal research / prototype |
|
||||
| 2 | MISSION | Fraunhofer CML | 2018–2019 | Developer (microservice layer) | Internal research platform |
|
||||
| 3 | Predictive Maintenance Grant | Fraunhofer CML | 2018–2019 | Contributor ("Mitarbeit") | Grant proposal (outcome unknown) |
|
||||
|
||||
**Framing rule:** These are research *projects*, not publications. List them under the Fraunhofer experience entry (not a Publications section). Use "Research project" framing. Do NOT imply peer-reviewed output.
|
||||
|
||||
---
|
||||
|
||||
## Personal Projects
|
||||
|
||||
| # | Project | Period | Status | Notes |
|
||||
|---|---------|--------|--------|-------|
|
||||
| 1 | RiskAhead | 2015–2017 | Discontinued | Android app (Java, PHP, MySQL, Docker) — incident/hazard mapping. Featured in VICE Germany. Personal project only — not peer-reviewed, not commercial. |
|
||||
|
||||
**Framing rule:** If included, list under Projects section with explicit "Personal project" label. Media mention (VICE Germany) can be noted as: "Featured in VICE (Germany)". Do NOT list VICE as a publication credit.
|
||||
|
||||
---
|
||||
|
||||
## Master's Thesis (academic output)
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| Title | "Development of a Web-Based Remote Fault Diagnosis System" |
|
||||
| Institution | Tongji University, Shanghai (exchange thesis) + Universität der Bundeswehr München |
|
||||
| Year | 2013 |
|
||||
| Grade | 1.0 (Very Good — top German grade) |
|
||||
| Methods | Neural Networks, Particle Swarm Optimization, Fuzzy Networks |
|
||||
| Status | Completed academic thesis — not published as a paper |
|
||||
|
||||
**Framing rule:** List under Education section only. Grade 1.0 may be highlighted for roles where academic performance is valued (rare in industry). Methods can be mentioned in CL for ML/AI roles to show early exposure.
|
||||
|
||||
---
|
||||
|
||||
## Certifications as Evidence (not publications)
|
||||
|
||||
See `skills_taxonomy.md` Category 10 for full cert list. Certs replace publications as credentialing signals for industry roles — list in Certifications section, not Publications.
|
||||
@@ -0,0 +1,52 @@
|
||||
# Significance Research: Bosch Semiconductor — Data Analysis Engineer
|
||||
|
||||
> Use in cover letters and summaries — NOT in resume bullet text.
|
||||
> Particularly valuable for semiconductor industry JDs.
|
||||
|
||||
---
|
||||
|
||||
### BS-1: ML Inference in 24/7 Semiconductor Fab — Field Context
|
||||
|
||||
**The problem:** Semiconductor manufacturing generates enormous volumes of image data (SEM, optical inspection, parametric test data) that traditionally required manual review by process engineers to identify defects. Manual inspection is slow, inconsistent, and a bottleneck as wafer volumes scale.
|
||||
|
||||
**The industry direction:** Computer vision / image classification ML has been adopted by leading semiconductor manufacturers (Intel, TSMC, ASML, Infineon) to automate defect detection. The challenge is not building the model — it's deploying it reliably into a 24/7 production environment where downtime is measured in wafer yield loss.
|
||||
|
||||
**Competing approaches:**
|
||||
- Rule-based inspection systems (legacy — deterministic but limited to known defect patterns)
|
||||
- Offline ML analysis (batch — not real-time, misses process drifts)
|
||||
- Inline ML inference (real-time, containerized — current best practice)
|
||||
|
||||
**Why Dennis's experience matters:** Deploying ML inference into a 24/7 fab is operationally much harder than deploying to a web server. There are no maintenance windows, hardware is constrained, and a model failure affects production throughput. Dennis designed and executed the integration strategy for this environment — a level of MLOps maturity that few data engineers have encountered.
|
||||
|
||||
**Differentiation:** The combination of Docker containerization + Kubernetes orchestration + Ansible automation in a 24/7 constrained environment is a rare and credible production ML deployment signal.
|
||||
|
||||
---
|
||||
|
||||
### Semiconductor Data Domains — Field Context
|
||||
|
||||
**Defect Management:**
|
||||
Semiconductor defect management involves tracking, classifying, and correlating defects found during inline inspection (optical, SEM) and end-of-line electrical test. Key data challenges: high-dimensional spatial data (wafer maps), multi-step process correlation, and connecting defect signatures to root causes (process excursions, equipment issues). Dennis built data pipelines and ML systems directly in this domain.
|
||||
|
||||
**Semiconductor Parameter Testing:**
|
||||
Parametric testing measures electrical characteristics (threshold voltages, leakage currents, resistance) of test structures on each wafer. The data volume is massive — hundreds of parameters across thousands of dies per wafer, across thousands of wafers per day. Data engineering for parametric test requires efficient storage, fast query access, and statistical analysis capabilities. Dennis built data services that fed parametric testing analysis teams.
|
||||
|
||||
**Process Analysis:**
|
||||
Process analysis correlates equipment parameters (temperature, pressure, gas flow) with downstream wafer yield and defect outcomes. This is the domain where data engineering meets process engineering — the pipelines must be reliable and the data must be accurate, because process decisions (equipment maintenance, recipe adjustments) depend on it.
|
||||
|
||||
**Why this is rare:** Most data engineers have worked in SaaS, finance, or e-commerce. Semiconductor manufacturing data — with its specialized domain vocabulary, data types (wafer maps, SPC charts, lot genealogy), and operational constraints — is a niche that few candidates can credibly claim.
|
||||
|
||||
---
|
||||
|
||||
### Field Overview: Data & AI in Semiconductor Manufacturing (2024–2026)
|
||||
|
||||
The semiconductor industry is undergoing a major digital transformation driven by:
|
||||
1. **Process complexity:** 300mm fabs with 1000+ process steps generate petabytes of data; manual analysis can no longer keep pace
|
||||
2. **Yield pressure:** At leading-edge nodes, even 1% yield improvement has enormous economic value — data-driven yield optimization is a strategic priority
|
||||
3. **AI/ML adoption:** Computer vision for inline inspection, predictive maintenance for equipment, and ML-based process optimization are all actively deployed at tier-1 fabs (TSMC, Intel, Samsung)
|
||||
4. **Talent scarcity:** Candidates who combine data engineering depth with semiconductor domain knowledge are extremely rare — most data engineers lack the domain; most process engineers lack the data skills
|
||||
|
||||
**Target companies for semiconductor JDs:**
|
||||
ASML, Infineon, GlobalFoundries, ams OSRAM, Microchip Technology, ON Semiconductor, Renesas, NXP, STMicroelectronics, Bosch (again), TSMC (Europe fabs in Dresden area), Wolfspeed, SiCrystal, Elmos
|
||||
|
||||
**CL hook for semiconductor JDs:**
|
||||
> "Semiconductor manufacturing analytics is one of the most data-intensive and operationally demanding domains in industry. At Bosch Semiconductor in Dresden, I worked directly in the data domains that matter most — Defect Management, Semiconductor Parameter Testing, and Process Analysis — building the pipelines and analytics platforms that engineers relied on for real-time production decisions. That domain knowledge, combined with my experience deploying ML-based defect classification into a 24/7 fab, is what I'd bring to [Company]."
|
||||
@@ -0,0 +1,51 @@
|
||||
# Significance Research: Swisscom — Staff Data, Analytics & AI Engineer
|
||||
|
||||
> Use in cover letters and summaries — NOT in resume bullet text.
|
||||
> Provides field context demonstrating awareness of the data engineering landscape.
|
||||
|
||||
---
|
||||
|
||||
### SW-1: AWS Migration — Field Context
|
||||
|
||||
**The problem:** Legacy enterprise data warehouses (Teradata, Oracle) are expensive to scale, inflexible for modern analytics workloads, and difficult to integrate with ML pipelines. The industry-wide shift to cloud-native data platforms (AWS, Azure, GCP) is driven by cost, elasticity, and the rise of the data lakehouse pattern.
|
||||
|
||||
**Competing approaches:** Most enterprises face a choice between lift-and-shift (rehosting on cloud VMs — minimal benefit), re-platforming (moving to managed services like Redshift), or full re-architecture to a lakehouse (S3 + Athena/Iceberg + Glue). The lakehouse pattern (Apache Iceberg on S3 + Athena) is increasingly the de facto standard for cost-efficient, ACID-compliant analytics at scale.
|
||||
|
||||
**Why this matters:** Swisscom serves millions of Swiss customers across mobile, broadband, and enterprise — the data volume is significant. Moving Fulfillment data pipelines to a cloud-native architecture directly affects the speed and cost of analytics for business-critical processes.
|
||||
|
||||
**Differentiation:** Dennis didn't just configure existing pipelines in a new environment — he introduced Apache Iceberg (open table format with time-travel and schema evolution), AWS Glue Tables as the catalog, and CloudFormation for IaC provisioning. This reflects current best practices in data lakehouse architecture, not a basic ETL migration.
|
||||
|
||||
**Field overview: Data Lakehouse Architecture (2024–2026)**
|
||||
The data lakehouse pattern — combining the scalability of data lakes (S3, ADLS) with the ACID guarantees and query performance of data warehouses — has become the dominant architecture for new data platform builds. Apache Iceberg has emerged as the leading open table format, supported by AWS (Athena, Glue), Databricks (as Delta Lake alternative), and Snowflake. Engineers who have implemented Iceberg in production (not just read about it) are in high demand as organizations migrate off proprietary DWH systems.
|
||||
|
||||
---
|
||||
|
||||
### SW-2: Component Ownership at Scale — Field Context
|
||||
|
||||
**The problem:** In large data engineering teams at enterprise companies, the "Component Owner" model is how organizations assign accountability for production systems. Unlike a ticket-based dev model, Component Owners are responsible for a system's full lifecycle: reliability, compliance, SLA, on-call, and stakeholder communication. This is a Staff-engineer-level responsibility.
|
||||
|
||||
**Why this matters:** Swisscom's Fulfillment domain carries business-critical data — provisioning, activating, and tracking customer service orders for Switzerland's largest telecom. Pipeline failures in this domain directly impact customer experience and revenue.
|
||||
|
||||
**Differentiation:** Dennis holds this responsibility as a Staff Engineer (Engineer IV) — the same person building the pipelines is accountable for their reliability in production. This is the "full-stack data engineer" model that platform teams increasingly demand.
|
||||
|
||||
---
|
||||
|
||||
### SW-3: Kubernetes for Data Applications — Field Context
|
||||
|
||||
**The problem:** Data pipelines have traditionally been deployed on bare metal or VMs, leading to environment inconsistency, difficult scaling, and slow deployments. The shift to Kubernetes for data workloads (not just web services) reflects the maturation of the data platform discipline.
|
||||
|
||||
**Industry trend:** Running data applications (Airflow, Spark, custom Python pipelines) on Kubernetes is now standard practice at mature data organizations. GitLab CI/CD with Kubernetes deployment is the Swiss/European enterprise standard (as opposed to GitHub Actions + AWS ECS in US-heavy startups).
|
||||
|
||||
**Differentiation:** Swisscom's use of Kubernetes for Python data applications confirms production-grade container orchestration for data workloads — not just a dev/test environment.
|
||||
|
||||
---
|
||||
|
||||
### Field Overview: Modern Data Engineering (2024–2026)
|
||||
|
||||
The data engineering discipline has undergone a significant shift in the past 3 years:
|
||||
1. **From batch to streaming:** Kafka-based event-driven architectures have replaced many nightly batch processes
|
||||
2. **From proprietary DWH to open lakehouse:** Teradata/Oracle → S3 + Athena/Iceberg is the dominant migration pattern
|
||||
3. **From manual to automated infra:** CloudFormation, Terraform, and Pulumi have made IaC standard for data platform teams
|
||||
4. **From separated to embedded ML:** Data engineers who can own the ML data layer (not just supply data to a separate ML team) are increasingly valuable
|
||||
|
||||
Dennis's current stack (Kafka, PySpark, AWS S3/Glue/Athena/Iceberg, Kubernetes, GitLab CI/CD, CloudFormation) maps precisely to this modern paradigm.
|
||||
@@ -0,0 +1,195 @@
|
||||
# Skills Taxonomy — Dennis Thiessen
|
||||
|
||||
> Generated: 2026-03-28
|
||||
> Sources: All 10 extractions + 6 experience files
|
||||
> Use this file when populating the Technical Skills section of resume/CV.
|
||||
|
||||
---
|
||||
|
||||
## Summary Stats
|
||||
|
||||
- **Total unique skills:** 65+
|
||||
- **Proficiency levels:** Expert (daily use, owned systems) | Proficient (shipped work, comfortable teaching) | Familiar (used in project, not current)
|
||||
- **Certification-backed skills:** AWS (SAA cert + Udacity DataEng), Software Architecture (iSAQB), AI/ML (Udacity AI for Trading, IBM AI Engineering)
|
||||
|
||||
---
|
||||
|
||||
## Category 1: Programming Languages
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| Python | Expert | Swisscom (pipelines, apps), Bosch (data services), Fraunhofer (ML/NLP), Vizrt (backend + tests) | HIGH |
|
||||
| SQL (multi-dialect) | Expert | All positions — Oracle, Impala, Teradata, MS SQL, Postgres, MySQL | HIGH |
|
||||
| PySpark | Proficient | Swisscom Staff level (LinkedIn confirmed) | HIGH |
|
||||
| Java | Proficient | Fraunhofer (SCEDAS, MISSION), Bosch (data services), Generali (J2EE), Capgemini | MED |
|
||||
| C# | Proficient | Bosch (data services, Spotfire extensions), Fraunhofer (SCEDAS) | MED |
|
||||
| JavaScript / TypeScript | Proficient | Fraunhofer (MISSION, Express.js), CV skills list | MED |
|
||||
| C++ | Proficient | Vizrt (backend transcoding), Generali (CV) | LOW |
|
||||
| VBA | Familiar | Student assistant role (Bundeswehr Uni, 2013) — very minor | LOW |
|
||||
|
||||
---
|
||||
|
||||
## Category 2: Data Engineering & Pipelines
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| ETL/ELT design & operation | Expert | Swisscom (component owner), Bosch (data services) | HIGH |
|
||||
| Apache Kafka | Expert | Swisscom (ingestion pipelines), Bosch (ELK PoC) | HIGH |
|
||||
| Apache Airflow | Proficient | Swisscom (AWS migration stack) | HIGH |
|
||||
| SAP BODS | Proficient | Swisscom (legacy ETL) | MED |
|
||||
| Teradata DWH | Proficient | Swisscom (DWH architecture + operation) | MED |
|
||||
| Hadoop / ImpalaSQL | Proficient | Bosch (data services over Hadoop) | MED |
|
||||
| Data modeling | Proficient | Swisscom (data products), Bosch (pipeline design) | MED |
|
||||
| SQL performance tuning | Proficient | CV (explain plans, indexes, partitions) | MED |
|
||||
| Apache Spark / PySpark | Proficient | Swisscom (big data processing) | HIGH |
|
||||
| dbt | Not confirmed | Not in any extraction — do not claim | — |
|
||||
|
||||
---
|
||||
|
||||
## Category 3: Cloud & Infrastructure
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| AWS (overall) | Proficient | Swisscom (migration), AWS SAA cert (2024), Udacity DataEng cert (2026) | HIGH |
|
||||
| AWS S3 | Proficient | Swisscom AWS migration | HIGH |
|
||||
| AWS Glue | Proficient | Swisscom AWS migration | HIGH |
|
||||
| AWS Athena | Proficient | Swisscom AWS migration (with Apache Iceberg table format) | HIGH |
|
||||
| AWS Glue (Jobs + Tables) | Proficient | Swisscom — Glue jobs for ETL + Glue Data Catalog / Glue Tables | HIGH |
|
||||
| Apache Iceberg | Proficient | Swisscom — S3 + Athena with Iceberg table format (open table format, time-travel, schema evolution) | HIGH |
|
||||
| AWS Redshift | Proficient | Swisscom AWS migration | HIGH |
|
||||
| AWS Lambda | Proficient | Swisscom AWS migration | MED |
|
||||
| AWS Step Functions | Proficient | Swisscom AWS migration | MED |
|
||||
| AWS CloudFormation | Proficient | Swisscom — IaaS, infrastructure provisioning as code | HIGH |
|
||||
| Kubernetes (K8s) | Expert | Swisscom (Python app deployment), Bosch (ML inference orchestration) | HIGH |
|
||||
| Docker | Expert | Bosch (ML containerization, ELK PoC), Fraunhofer (MISSION), Swisscom | HIGH |
|
||||
| Ansible | Proficient | Bosch (ML orchestration) | MED |
|
||||
| GitLab CI/CD | Proficient | Swisscom (confirmed Zeugnis) | HIGH |
|
||||
| Jenkins | Proficient | Fraunhofer (independently set up), Generali (BDD build jobs) | MED |
|
||||
| CI/CD (general) | Expert | Swisscom, Fraunhofer, Vizrt, Generali — cross-position | HIGH |
|
||||
| IaC (Infrastructure as Code) | Proficient | Swisscom — AWS CloudFormation confirmed by user | HIGH |
|
||||
| DevSecOps | Proficient | Swisscom Security Champion ×3 (2023–2026), 100h training | MED |
|
||||
|
||||
---
|
||||
|
||||
## Category 4: Databases & Storage
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| Oracle DB | Expert | Swisscom (Fulfillment pipelines), Bosch (data services), Generali (web portal) | HIGH |
|
||||
| Teradata | Proficient | Swisscom (DWH target, architecture) | MED |
|
||||
| MS SQL Server | Proficient | Fraunhofer (SCEDAS — Entity Framework) | LOW |
|
||||
| PostgreSQL | Familiar | CV skills list | LOW |
|
||||
| MySQL | Familiar | CV skills list, RiskAhead project | LOW |
|
||||
| SQLite | Familiar | Fraunhofer (MISSION microservices) | LOW |
|
||||
| Hadoop / Impala | Proficient | Bosch (ImpalaSQL data services) | MED |
|
||||
|
||||
---
|
||||
|
||||
## Category 5: ML & AI
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| ML inference deployment | Proficient | Bosch (Docker/K8s in 24/7 fab — primary responsibility) | HIGH |
|
||||
| Image classification | Proficient | Bosch (automated quality monitoring in semiconductor fab) | MED |
|
||||
| NLP / Speech recognition | Familiar | Fraunhofer ARTUS research project (contributing role) | MED |
|
||||
| PyTorch | Familiar | CV skills list | LOW |
|
||||
| Scikit-learn | Familiar | CV skills list | LOW |
|
||||
| Pandas / NumPy | Proficient | CV (data analysis, pipeline work) | MED |
|
||||
| Matplotlib / Plotly | Proficient | CV (data visualization, dashboards) | LOW |
|
||||
| MLOps (general) | Proficient | Bosch (full ML lifecycle: containerize → deploy → monitor in production) | HIGH |
|
||||
| AI for Trading / Quant ML | Familiar | Udacity AI for Trading Nanodegree (2021) — personal study, not professional | LOW |
|
||||
| TensorFlow / Keras | Familiar | IBM AI Engineering Specialization (Coursera) | LOW |
|
||||
| Apache Spark ML | Familiar | IBM AI Engineering (Spark ML course) | LOW |
|
||||
|
||||
**Proficiency note:** For ML/AI roles, frame Bosch ML deployment as primary evidence. NLP/ARTUS and the Udacity/IBM certs as supporting signals. Do not overstate ML modeling depth — the core strength is ML *infrastructure and deployment*, not research.
|
||||
|
||||
---
|
||||
|
||||
## Category 6: Testing & Quality Engineering
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| Test automation | Expert | Capgemini, Generali, Vizrt — consistent across 3 positions | MED (earlier career) |
|
||||
| BDD (Behaviour-Driven Development) | Proficient | Generali — introduced PoC, held technical ownership | MED |
|
||||
| Serenity-BDD / JBehave | Proficient | Generali (confirmed Zeugnis) | LOW |
|
||||
| Selenium | Proficient | Generali (UI test automation) | LOW |
|
||||
| pytest | Proficient | CV skills list | MED |
|
||||
| TDD | Proficient | Capgemini, Generali (confirmed) | LOW |
|
||||
| HP Quality Center / ALM | Familiar | Capgemini (Zeugnis confirmed) | LOW |
|
||||
| UIPath RPA | Familiar | Generali (POC developer, confirmed Zeugnis + LinkedIn) | LOW |
|
||||
| Camunda BPMN | Familiar | Generali (LinkedIn confirmed) | LOW |
|
||||
| Quality gates (CI/CD) | Proficient | Vizrt (CI/CD integration), Fraunhofer (Jenkins quality gates) | MED |
|
||||
|
||||
---
|
||||
|
||||
## Category 7: Observability, Monitoring & DevOps Tooling
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| ELK Stack (Elasticsearch/Logstash/Kibana) | Proficient | Bosch (anomaly detection PoC — primary developer) | MED |
|
||||
| Grafana | Proficient | Bosch (monitoring dashboards) | MED |
|
||||
| Prometheus | Proficient | Bosch (metrics) | MED |
|
||||
| Loki | Familiar | Bosch (log aggregation, part of PoC) | LOW |
|
||||
| Git | Expert | All positions | HIGH |
|
||||
| Agile / Scrum | Proficient | Swisscom (confirmed Zeugnis — backlog, sprint planning, Product Owner collaboration) | MED |
|
||||
| Tibco Spotfire | Familiar | Bosch (C# extensions, LinkedIn confirmed) | LOW |
|
||||
|
||||
---
|
||||
|
||||
## Category 8: Frameworks & APIs
|
||||
|
||||
| Skill | Proficiency | Evidence | Resume Weight |
|
||||
|-------|-------------|----------|---------------|
|
||||
| Flask / FastAPI / Django | Proficient | CV skills list | MED |
|
||||
| Express.js | Familiar | Fraunhofer MISSION (microservices) | LOW |
|
||||
| Entity Framework (.NET) | Proficient | Fraunhofer SCEDAS | LOW |
|
||||
| Spring Boot | Familiar | Generali (Dispatcher PoC, Apache Camel) | LOW |
|
||||
| Apache Camel | Familiar | Generali (Dispatcher PoC) | LOW |
|
||||
| SQLAlchemy | Familiar | CV skills list | LOW |
|
||||
| Swagger / OpenAPI | Familiar | CV skills list | LOW |
|
||||
|
||||
---
|
||||
|
||||
## Category 9: Domain Knowledge
|
||||
|
||||
| Domain | Depth | Source | Resume Weight |
|
||||
|--------|-------|--------|---------------|
|
||||
| Telecom / Enterprise data platforms | Proficient | Swisscom (2+ years, current) | HIGH |
|
||||
| Semiconductor manufacturing / Industry 4.0 | Proficient | Bosch (3 years) — data domains: Defect Management, Semiconductor Parameter Testing, Process Analysis, Image-based Quality Inspection | MED |
|
||||
| Maritime logistics | Familiar | Fraunhofer CML (1 year research) | LOW |
|
||||
| Broadcast technology | Familiar | Vizrt (1 year) | LOW |
|
||||
| Insurance IT / Business process automation | Familiar | Generali (2 years) | LOW |
|
||||
| Security / DevSecOps | Proficient | Swisscom Security Champion ×3 | MED |
|
||||
| Blockchain / Web3 | Familiar | Personal — RPC APIs, basic Solidity, Kraken since 2017 | LOW (bonus only) |
|
||||
|
||||
---
|
||||
|
||||
## Category 10: Certifications (Skills Signals)
|
||||
|
||||
| Certification | Issuer | Year | Active | Resume Weight |
|
||||
|--------------|--------|------|--------|---------------|
|
||||
| AWS Certified Solutions Architect – Associate | AWS | 2024 | Yes (until Sep 2027) | HIGH |
|
||||
| Data Engineering with AWS (Nanodegree) | Udacity | 2026 | Yes | HIGH |
|
||||
| iSAQB Certified Professional for Software Architecture — Foundation Level | iSAQB | 2016 | Yes (no expiry) | MED |
|
||||
| ITIL® Foundation Certificate in IT Service Management | PEOPLECERT / AXELOS | 2016 | Yes (no expiry) | LOW |
|
||||
| AI for Trading Nanodegree | Udacity / WorldQuant | 2021 | Yes | LOW (niche) |
|
||||
| Swisscom Security Champion | Swisscom (internal) | 2023–2026 | Active | MED (as bullet, not cert line) |
|
||||
| IBM AI Engineering Specialization | IBM / Coursera | — | Yes | LOW |
|
||||
|
||||
---
|
||||
|
||||
## Skills Config Guide (for resume generation)
|
||||
|
||||
Refers to `config.md` skills layout: **4-3-2-2-2** (resume) or **4-4-3-3-3** (CV).
|
||||
|
||||
### Suggested Resume Skills Groups (5 groups)
|
||||
|
||||
| Group | Label | Skills to include |
|
||||
|-------|-------|------------------|
|
||||
| 1 (4 lines) | Languages & Data | Python, PySpark, SQL (Oracle · Impala · Teradata · Postgres), Java · C# |
|
||||
| 2 (3 lines) | Cloud & Infra | AWS (S3 · Glue · Athena · Redshift · Airflow), Kubernetes · Docker · Ansible, GitLab CI/CD · Jenkins |
|
||||
| 3 (2 lines) | Pipelines & Platforms | Kafka · Airflow · SAP BODS · Hadoop, Teradata DWH · ETL/ELT design |
|
||||
| 4 (2 lines) | ML & Observability | ML inference deployment · MLOps · PyTorch · Scikit-learn, ELK Stack · Grafana · Prometheus |
|
||||
| 5 (2 lines) | Certifications | AWS Certified Solutions Architect – Associate (active), iSAQB CPSA Foundation · ITIL v3 · Data Engineering with AWS (Udacity) |
|
||||
|
||||
**Adjust per JD:** For ML/AI roles, swap group 4 to lead with ML; for Platform/Infra roles, expand cloud group. The cert line (group 5) is fixed per `config.md`.
|
||||
Reference in New Issue
Block a user