feat: rebuild evidence-first application workflow

This commit is contained in:
2026-07-27 17:56:15 +02:00
parent c24892f381
commit fe5f24704f
57 changed files with 3815 additions and 3555 deletions
@@ -21,14 +21,14 @@ Each achievement has a **Significance** line (why it matters to any reader) and
---
### 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.
**Significance:** Demonstrates hands-on migration delivery for pipelines in Dennis's owned domains and contribution to a wider enterprise programme. It is a strong AWS/data-engineering signal without implying ownership of the company-wide migration.
| 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 |
| Data Platform/Infra | HIGH | Migrated / implemented | Lead with verified AWS services and the owned-domain scope; do not claim company-wide architecture ownership |
**Overclaiming warning:** No specific throughput/volume numbers available — do not invent. Use qualitative impact (operational overhead reduction, scalability improvement).
@@ -72,15 +72,15 @@ Each achievement has a **Significance** line (why it matters to any reader) and
---
### 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.
### SW-5: Security Champion — 2025/2026 (team role, NOT an award)
**Significance:** Modest. This is a **rotating team role** (security point of contact), held for **2025/2026 only** — corrected 2026-07-27. It is not an award, not a distinction, and not "3 consecutive years" (an earlier version of this file claimed that; it was wrong).
**DEFAULT: OMIT.** Include only when the JD explicitly requires security or DevSecOps experience. Never place under Awards/Honors.
| 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 |
| All role types (JD silent on security) | OMIT | — | Leave it out — it costs a bullet slot and reads as padding |
| Any role type (JD explicitly requires security/DevSecOps) | MED | Serve as | State plainly as a team role for 2025/2026; cite the 100h training + assessment, claim no more |
---
@@ -298,7 +298,7 @@ Each achievement has a **Significance** line (why it matters to any reader) and
| 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-5 Security Champion | LOW | LOW | LOW | LOW |
| SW-6 PySpark | MED | LOW | MED | MED |
| BS-1 ML Inference | HIGH | LOW | HIGH | HIGH |
| BS-2 Data Services | HIGH | MED | MED | HIGH |