feat: rebuild evidence-first application workflow
This commit is contained in:
@@ -17,7 +17,7 @@
|
||||
|
||||
| 3 | thiessen_swisscom_zwischenzeugnis.md | Swisscom interim reference (Oct 2025) — confirms Engineer IV/Staff grade, Data Lake dept, French+Italian languages, GitLab CI/CD, Fulfillment domain, top-tier rating | Employer reference | complete |
|
||||
|
||||
| 4 | thiessen_swisscom_security_champion.md | Swisscom Security Champion badge — 3 consecutive years (2023/24–2025/26), DevSecOps/security awareness, 100h training + assessment | Internal badge | complete |
|
||||
| 4 | thiessen_swisscom_security_champion.md | Swisscom Security Champion team role — 2025/26 only, DevSecOps/security awareness, 100h training + assessment | Internal team role | corrected |
|
||||
|
||||
| 5 | thiessen_certifications.md | All cert PDFs combined — ITIL v3 added; remaining 5 certs + CertMetrics to be appended as read | Certifications | in progress |
|
||||
|
||||
|
||||
@@ -62,7 +62,7 @@
|
||||
|
||||
---
|
||||
|
||||
### 2. BOSCH Semiconductor Manufacturing — Dresden, Germany | Feb 2020 – Jan 2023
|
||||
### 2. BOSCH Semiconductor Manufacturing — Dresden, Germany | Feb 2020 – Dec 2022
|
||||
**Title (CV-1):** (Senior) Data Analysis Engineer
|
||||
**Title (CV-2):** (Senior) Engineer Data Analysis
|
||||
|
||||
@@ -76,7 +76,7 @@
|
||||
|
||||
---
|
||||
|
||||
### 3. Fraunhofer CML — Hamburg, Germany | Sep 2018 – Jan 2020
|
||||
### 3. Fraunhofer CML — Hamburg, Germany | Sep 2018 – Oct 2019
|
||||
**Title:** Research Software Engineer
|
||||
|
||||
**Bullets (combined):**
|
||||
@@ -89,7 +89,7 @@
|
||||
|
||||
---
|
||||
|
||||
### 4. Vizrt — Bergen, Norway | Jul 2017 – Aug 2018
|
||||
### 4. Vizrt — Bergen, Norway | Jul 2017 – May 2018
|
||||
**Title:** DevOps Engineer
|
||||
|
||||
**Bullets (combined):**
|
||||
@@ -104,10 +104,9 @@
|
||||
**Title:** Software Engineer
|
||||
|
||||
**Bullets:**
|
||||
- CV-1: Python/C++ development for distributed backend components; implemented test automation and long-term maintainability practices
|
||||
- CV-2: Software Engineering for a process-oriented workflow web-portal using Java/J2EE, JavaScript and Oracle DB
|
||||
|
||||
**Key tech stack:** Python, C++, Java, J2EE, JavaScript, Oracle DB
|
||||
**Key tech stack:** Java, J2EE, JavaScript, Oracle DB, BDD/Selenium/JBehave, Jenkins, UIPath
|
||||
|
||||
---
|
||||
|
||||
@@ -123,26 +122,30 @@
|
||||
|
||||
## Skills Inventory
|
||||
|
||||
### Programming Languages
|
||||
Python, SQL (Postgres, MySQL, Oracle, Impala/Hadoop), Java, C#, TypeScript, C++, JavaScript
|
||||
This inventory is descriptive evidence, not resume-ready output. The canonical
|
||||
output policy in `resume_builder/canonical/claims.json` controls every use.
|
||||
|
||||
### Frameworks & APIs
|
||||
Flask, FastAPI, Django, Swagger/OpenAPI, Express.js, J2EE, .NET, Entity Framework, SQLAlchemy
|
||||
### Production-current
|
||||
Python, SQL, AWS (S3, Glue, Athena/Iceberg, Redshift), Airflow, Kafka, Oracle,
|
||||
Teradata, Kubernetes, Docker, GitLab CI/CD, CloudFormation, data products,
|
||||
metadata/governance and on-call production operation.
|
||||
|
||||
### Data & Pipelines
|
||||
ETL/ELT design, data modeling, Airflow, Kafka, SAP BODS, Hadoop/Impala, Teradata DWH, SQL performance tuning (explain plans, indexes, partitions)
|
||||
### Production-historical
|
||||
Java, C#, Jenkins, Ansible, Hadoop/Impala, ELK Stack and TIBCO Spotfire.
|
||||
C++ and JavaScript/Express.js were used in bounded historical roles.
|
||||
|
||||
### Cloud & Infra
|
||||
AWS (S3, Glue, Athena, Redshift, Lambda, Step Functions), Docker, Kubernetes, Ansible, CI/CD, IaC
|
||||
### Hands-on-current or proof-of-concept
|
||||
LiteLLM, custom GPTs, Kiro and VS Code/Copilot are hands-on current evidence.
|
||||
Grafana, Prometheus and Loki are supported as Bosch proof-of-concept work, not
|
||||
as current platform ownership.
|
||||
|
||||
### ML & AI
|
||||
PyTorch, SciKit-Learn, Pandas, NumPy, Matplotlib, Plotly, Mockito, ML inference deployment (Docker/K8s)
|
||||
### Certification/coursework context only
|
||||
TensorFlow/Keras and PyTorch are not professional production claims. Use only
|
||||
with explicit certification or coursework context.
|
||||
|
||||
### Observability / DevOps
|
||||
ELK Stack, Grafana, Prometheus, Loki, Jenkins, Git, pytest
|
||||
|
||||
### Blockchain (bonus)
|
||||
RPC APIs, public node operation, on-chain data via RPC/REST, basic Solidity, Kraken client since 2017
|
||||
### Unverified or forbidden in generated documents
|
||||
TypeScript, FastAPI, Flask, Django, LangChain/LangGraph/LlamaIndex, Terraform,
|
||||
Azure, GCP, formal model evaluation and LLM fine-tuning remain unsupported.
|
||||
|
||||
### Legacy / Enterprise
|
||||
Oracle, Teradata, SAP BODS
|
||||
@@ -178,8 +181,8 @@ Oracle, Teradata, SAP BODS
|
||||
|
||||
## Provenance Notes
|
||||
|
||||
- **Safe to claim (full ownership):** All items listed under each position — solo developer work clearly attributed
|
||||
- **Shared/team work:** Bosch ML pipeline integration — context suggests team effort; hedge as "led" or "owned end-to-end" only if confirmed
|
||||
- **Safe to claim:** Only facts that also appear in `resume_builder/canonical/claims.json`; this older CV synthesis is not authoritative.
|
||||
- **Shared/team work:** Apply the canonical claim's ownership scope and allowed verbs. Never infer solo ownership from a CV bullet.
|
||||
- **Do NOT claim:** Any results from collaborators at Fraunhofer research projects (NLP, Digital Twins) unless specific contribution confirmed
|
||||
- **RiskAhead:** Personal project framing only — not a commercial product, not peer-reviewed
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@
|
||||
### Bosch — Two Sub-Roles (CV showed as one)
|
||||
| Title | Period | Duration |
|
||||
|-------|--------|----------|
|
||||
| Senior Data Engineer / Data Analysis | Jan 2021 – Jan 2023 | 2 years 1 month |
|
||||
| Senior Data Engineer / Data Analysis | Jan 2021 – Dec 2022 | LinkedIn end month corrected to match official employer reference |
|
||||
| Data Engineer / Data-Analysis | Feb 2020 – Jan 2021 | 1 year |
|
||||
|
||||
**Additional Bosch details (LinkedIn only):**
|
||||
|
||||
@@ -26,8 +26,6 @@
|
||||
Dennis has earned this badge **three years running:**
|
||||
| Year | Badge |
|
||||
|------|-------|
|
||||
| 2023/24 | Swisscom Security Champion |
|
||||
| 2024/25 | Swisscom Security Champion |
|
||||
| 2025/26 | Swisscom Security Champion |
|
||||
|
||||
Three consecutive years = not a one-time training completion but a sustained role and annual re-certification. Strong signal of ongoing security ownership.
|
||||
@@ -45,12 +43,12 @@ Three consecutive years = not a one-time training completion but a sustained rol
|
||||
## Resume / CV Usage
|
||||
|
||||
**Option A — Bullet under Swisscom experience:**
|
||||
> "Designated Security Champion for 3 consecutive years (2023–2026), owning security compliance, risk monitoring, and deviation reporting for the team's data pipelines and applications."
|
||||
> "Serve as the team's Security Champion for 2025/2026, acting as the security point of contact for requirements, risks and deviation tracking."
|
||||
|
||||
**Option B — Honors/Recognition section (if present):**
|
||||
> "Swisscom Security Champion — 2023/24, 2024/25, 2025/26 (annual internal badge; 100h training + assessment)"
|
||||
> "Swisscom Security Champion team role — 2025/2026 (100h training + assessment)"
|
||||
|
||||
**Option C — Skills/Certifications footnote:**
|
||||
> "Swisscom Security Champion (×3, 2023–2026)" — brief mention, not standalone cert line
|
||||
> Omit by default. If a JD requires security experience, describe the 2025/2026 team role; never list it as an award or certification.
|
||||
|
||||
**Recommended:** Option A as a Swisscom bullet when targeting security-conscious employers or roles with DevSecOps component. Option B/C otherwise.
|
||||
|
||||
@@ -88,8 +88,8 @@ Use full-ownership verbs — these are confirmed as sole/primary responsibilitie
|
||||
|
||||
## Provenance Notes
|
||||
|
||||
- **Safe to claim:** All 7 bullet responsibilities — confirmed as primary owner
|
||||
- **Part-time flag:** Part-time from Sep 2021; overlap with Swisscom start. Only disclose if directly asked. Do not flag on resume.
|
||||
- **Safe to claim:** The seven responsibilities are employer-confirmed, but ownership verbs must follow `resume_builder/canonical/claims.json` rather than assuming solo ownership.
|
||||
- **Part-time flag:** Part-time from Sep 2021. There is no Swisscom overlap: Bosch ended Dec 2022 and Swisscom began Oct 2023.
|
||||
- **"Application Owner"** is a confirmed title/role — use it; strong ownership signal
|
||||
- **ELK Stack POC** is explicitly mentioned — safe to include as technical achievement
|
||||
- **ML deployment** — "Erarbeitung und Durchführung von Integrationsstrategien" = designed AND executed. Full ownership verb appropriate.
|
||||
|
||||
Reference in New Issue
Block a user