fix(citadel): apply Tier 1 relevance fixes, JD coverage 51% -> 68%

All three Tier 1 items from the critique, all honestly available, no
claim altered.

The R2 vocabulary now appears where R2 is actually evidenced: the SW-7
bullet carries ingestion and lifecycle, and SW-1 carries transformation
and storage. R2 was the single core responsibility scored Direct, and
the document had been proving it in substance while missing it in the
JD's own words. SW-2 now names the Oracle/Kafka/Python/Teradata estate a
distributed system he operates - not one he designed, which stays a gap.
The second skills line is relabelled "Distributed systems" and names
distributed databases explicitly, closing the fifth preferred-technology
hit that Phase 0 counted as Direct but the resume never actually wrote.

Recorded what was deliberately not added, because raising keyword
coverage is exactly where a later run would be tempted to overreach:
"scalable" is an unverified scale claim, and SDK, high-throughput,
data-intensive, simulation, model development and self-service have no
canonical evidence. Verified still absent after the edit.

Scope kept to what was approved. The user said "tier 1 fixes", so the
Tier 2 headline retitle - "Production Data Platforms on AWS", the line
most likely to draw the opening challenge from a technical reviewer -
was left in place for them to decide.

Validator PASS with zero warnings: the 58% cadence warning cleared as a
side effect, because restructuring two bullets with em-dashes broke the
comma-list pattern the checker keys on. Still exactly 2 pages, zero
overfull/underfull boxes, PDF re-inspected.

Critique marked STALE - it scored the pre-edit document.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MHtzyTKBcg6BWhD5qFegtK
This commit is contained in:
2026-08-26 09:17:47 +02:00
co-authored by Claude Opus 5
parent 7953884810
commit c94edbce44
2 changed files with 40 additions and 5 deletions
@@ -35,7 +35,7 @@ Staff data engineer who builds and runs the pipelines and governed data products
\begin{rSection}{Technical Skills}
\skillline{Programming}{Python, SQL, PySpark; Java and C\# (professional, historical); C++ (limited historical use)}
\skillline{Distributed data systems}{Apache Kafka, Apache Airflow, Spark/PySpark, ETL/ELT, data modelling, query performance tuning, Oracle, Teradata, Hadoop/Impala}
\skillline{Distributed systems}{Apache Kafka, Apache Airflow, Spark/PySpark, distributed databases (Teradata, Redshift, Athena/Iceberg), ETL/ELT, data modelling, query performance tuning, Oracle, Hadoop/Impala}
\skillline{Cloud and platform}{AWS (S3, Glue, Athena/Iceberg, Redshift, Lambda, Step Functions), CloudFormation, Kubernetes, Docker, GitLab CI/CD, Ansible}
\skillline{Reliability and operations}{Production operation and on-call, SLOs, incident and root-cause analysis; Grafana, Prometheus, ELK (proof of concept)}
\skillline{Trading domain (self-directed)}{Systematic/quantitative trading concepts, factor construction, backtesting -- personal project and coursework only, no professional experience}
@@ -45,9 +45,9 @@ Staff data engineer who builds and runs the pipelines and governed data products
\begin{rSection}{Professional Experience}
\begin{rSubsection}{Swisscom (Schweiz) AG}{Oct 2023 -- Present}{Staff Data, Analytics \& AI Engineer (promoted from Senior, Apr 2025)}{Bern, Switzerland}
\item Build and model governed data products within Swisscom's company-wide Data Mesh, onboarding source systems and maintaining their metadata and lineage in Atlassian Compass so downstream analytics and AI teams can find and reuse the data.
\item Component Owner for business-critical Fulfillment ETL running across Oracle, Kafka, Python and Teradata, accountable for its data quality, governance and on-call operation.
\item Migrated owned Fulfillment and Product Analysis pipelines onto Swisscom's AWS platform using Glue, Athena with Apache Iceberg, Redshift, Airflow and CloudFormation, contributing to the wider company migration programme.
\item Build and model governed data products within Swisscom's company-wide Data Mesh, from source-system ingestion through to the metadata and lineage in Atlassian Compass that keep each product discoverable across its lifecycle.
\item Component Owner for business-critical Fulfillment ETL -- a distributed system spanning Oracle, Kafka, Python and Teradata -- accountable for its data quality, governance and on-call operation.
\item Migrated owned Fulfillment and Product Analysis pipelines onto Swisscom's AWS platform -- transformation and storage on Glue, Athena with Apache Iceberg and Redshift, orchestration in Airflow -- contributing to the wider company migration programme.
\item Develop and operate Python data applications on Kubernetes, delivered through GitLab CI/CD from automated test to production support.
\item Translate stakeholder and product-owner requirements into delivered data products; run root-cause analysis in 2nd- and 3rd-level support.
\end{rSubsection}
@@ -272,13 +272,48 @@ comment explaining why they were excluded. The validator scans **raw file text**
all three. This is the exact failure the SBB `.tex` header warns about. Comment rewritten without
naming them.
## Edit History
### Edit 1 (2026-08-26): Tier 1 relevance fixes
- **Source:** `critique_citadel_securities_platform_engineer.md` Tier 1 items 1-3. User approved
"tier 1 fixes" only; the Tier 2 headline retitle was deliberately NOT applied.
- **Changes (all MODIFY, no budget change):**
1. SW-7 bullet -> now carries **ingestion** and **lifecycle**: "from source-system ingestion
through to the metadata and lineage in Atlassian Compass that keep each product discoverable
across its lifecycle."
2. SW-1 bullet -> now carries **transformation** and **storage**: "transformation and storage on
Glue, Athena with Apache Iceberg and Redshift, orchestration in Airflow". Scope hedge
("contributing to the wider company migration programme") retained.
3. SW-2 bullet -> names the estate a **distributed system** he operates, not designed.
4. Skills line 2 relabelled **"Distributed systems"** and now names **distributed databases
(Teradata, Redshift, Athena/Iceberg)** - closes the fifth preferred-technology hit that Phase 0
claimed as Direct but the document never wrote.
- **Not added, deliberately:** scalable (unverified scale claim), SDK / high-throughput /
data-intensive / simulation / model development / self-service (zero canonical evidence).
Verified still absent after the edit.
- **Verification:** validator **PASS, 0 warnings** (the cadence warning cleared as a side effect -
restructuring SW-1/SW-2 with em-dashes broke the comma-list pattern). Compiles to exactly
**2 pages**, zero overfull/underfull boxes, PDF re-inspected clean.
| Metric | Before | After | Delta |
|---|---|---|---|
| Pages | 2 | 2 | 0 |
| Validator errors | 0 | 0 | 0 |
| Validator warnings | 1 (cadence 58%) | **0** | -1 |
| Bullets | 13 | 13 | 0 |
| JD term coverage | 19/37 (51%) | **25/37 (68%)** | +6 |
**Estimated Document Quality ~91/100** (relevance 10 -> ~14, mechanics 9 -> 10). Estimate only -
not a re-scored critique.
## Status
- Phase 0: **DONE** (2026-08-25)
- Phase 1: **DONE** (2026-08-26) — 13 bullets confirmed
- Phase 2: **DONE** (2026-08-26) — resume compiled and verified
- Cover Letter: **PENDING** (decision YES — PP-1 domain story needs prose)
- Critique: **CURRENT** (2026-08-26) — **Document Quality 86/100**, Evidence Fit 71, Channel Weak.
- Critique: **STALE** (scored 86/100 on 2026-08-26, before Edit 1) — **Document Quality 86/100**, Evidence Fit 71, Channel Weak.
No Tier 1 truth findings; validator PASS. Three Tier 1 relevance fixes (~+4), all honestly
available: (1) R2's own vocabulary — ingestion/transformation/storage/lifecycle — is absent
despite R2 being the single Direct core responsibility; (2) "distributed systems" never appears