feat(citadel): Phase 0 for Citadel Securities Platform Engineer, Zurich

Evidence Fit 74/100, Adjacent at the top of the band, hard gate PASS
with one flagged risk. Phase 1 not started - user asked for Phase 0 only.

The stack alignment is the best in the log: zero Gaps across all seven
minimum qualifications, and all five preferred technologies (Kafka,
Kubernetes, Spark, Airflow, distributed databases) are Direct and
production-current.

What holds it at 74 is that the title-defining function splits. R2 -
ingestion, transformation, storage and lifecycle management of large
datasets - is Direct and describes SW-1/SW-7 almost word for word. R1 -
design and build the distributed research platform itself - is Adjacent,
the same authoring-vs-building shape as Aker BP, and it cannot be
written around: Scope Discipline forbids pairing a full-ownership verb
with an org-scale object, so it can only be honestly bridged.

Recorded the classification conflict rather than hiding it.
application_strategy.md says a defining responsibility that is only
Adjacent makes the role Stretch; that strict reading applies to R1. It
is filed as Adjacent because R2 is equally title-defining and is Direct,
and because Aker BP set that precedent at 79. Both cohort slots are free
either way, so the label changes nothing operationally.

Corrections the user was right about, now recorded so a later run does
not repeat them: Go is NOT a gap, because Q3 is disjunctive and Python
satisfies it outright; and a production Kafka/K8s/Spark/Airflow estate
IS a distributed system, so Q4 is Direct rather than a stretch.

Two traps written down explicitly. The $175,000-350,000 base range is a
US pay-transparency disclosure under NY law and says nothing about the
Zurich figure - it must be asked, not assumed. And the sibling reqs that
web search surfaces as closer title matches (Research Platform - Data
Platform Engineer, Research Platform Infrastructure Engineer) are dead:
404 and Cloudflare-blocked, absent from the live board. Those Built In
listings are stale.

JD saved verbatim via Playwright; WebFetch returns 403 on this host.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MHtzyTKBcg6BWhD5qFegtK

output/CitadelSecurities_PlatformEngineer/JD_CitadelSecurities_PlatformEngineer.txt

@@ -0,0 +1,59 @@
+SOURCE URL: https://www.citadelsecurities.com/careers/details/platform-engineer/
+RETRIEVED: 2026-08-25 via job_scout/.venv Playwright (chromium, headless)
+METHOD NOTE: WebFetch returns HTTP 403 on this host; Playwright required.
+VERBATIM: yes - full visible posting body, unedited except removal of site
+  navigation chrome (menu, footer, cookie/legal links).
+========================================================================
+
+Platform Engineer
+
+New York, Miami, Zurich
+
+Job Description
+Role Overview:
+Citadel Securities is seeking an exceptional Platform Engineer to join our Research Platform Engineering team in Miami, Zurich or New York. Our Research Platform teams are at the forefront of designing and developing the distributed systems, data platforms, and research infrastructure that power large-scale simulations, analytics, and model development across the firm. These systems are critical in allowing researchers to transform data into actionable insights and alpha-generating trading strategies.
+Opportunities may be available from time to time in any location in which the business is based for suitable candidates. If you are interested in a career with Citadel, please share your details and we will contact you if there is a vacancy available.
+Responsibilities:
+Design and build distributed platforms and services that support quantitative research, simulations, AI-powered applications, and large-scale analytics workflows
+Develop scalable platform services and data systems for ingestion, transformation, storage, and lifecycle management of large datasets
+Build and maintain backend services, APIs, and SDKs that improve researcher productivity and self-service capabilities
+Improve performance, reliability, and scalability of critical research systems operating in high-throughput environments
+Collaborate closely with researchers and engineers to translate research requirements into production-read systems
+Qualifications:
+Bachelor’s degree in Computer Science or a related field
+3+ years of professional software engineering experience
+Strong programming skills in Python, Go, or C++, or similar systems-oriented languages
+Experience building and operating distributed systems in production environments
+Experience designing scalable backend services, APIs, and data-intensive applications
+Strong understanding of distributed systems, data-intensive applications, and system design fundamentals
+Experience with cloud platforms (AWS, GCP, Azure) and modern infrastructure technologies
+Experience with technologies such as Kafka, Kubernetes, Spark, Airflow, distributed databases, or similar systems is a plus
+
+
+In accordance with applicable law, the base salary range for this role is $175,000 to $350,000.
+
+In addition, the employee who fills this role will be eligible to participate in a discretionary incentive compensation program, as well as a wide array of benefit programs, such as medical and life insurance, retirement and tax-free savings plans, and access to other healthcare programs.
+
+About Citadel Securities
+
+Citadel Securities is a technology-driven, next-generation global market maker. We provide institutional and retail investors with world-class liquidity, competitive pricing and seamless front-to-back execution in a broad array of financial products. Our teams of engineers, traders and researchers harness leading-edge quantitative research and the accelerating power of compute, machine learning and AI to power our analytics and tackle the market’s and our clients’ most critical challenges. Together, we are forging the future of capital markets. For more information, visit citadelsecurities.com.
+
+About Citadel Securities
+
+Citadel Securities is a technology-driven, next-generation global market maker. We provide institutional and retail investors with world-class liquidity, competitive pricing and seamless front-to-back execution in a broad array of financial products. Our teams of engineers, traders and researchers harness leading-edge quantitative research and the accelerating power of compute, machine learning and AI to power our analytics and tackle the market’s and our clients’ most critical challenges. Together, we are forging the future of capital markets. For more information, visit citadelsecurities.com.
+
+Start Application
+Citadel Securities
+Counterparty Login
+Who We Are
+What We Do
+News & Insights
+Careers
+Privacy
+Terms of Use
+Fraud Notice
+Disclosures
+
+Copyright © Citadel Enterprise Americas LLC or one of its affiliates. All rights reserved.
+
+Citadel Securities is an equal opportunity employer. We provide all individuals consideration for employment and advancement opportunities without regard to race, religion, color, gender, pregnancy, national origin, age, disability, military or veteran status, sexual orientation, genetic information and any other classification protected by applicable federal, state and local laws.

output/CitadelSecurities_PlatformEngineer/session_citadel_securities_platform_engineer.md

@@ -0,0 +1,134 @@
+# Session: Citadel Securities — Platform Engineer, Research Platform Engineering
+
+## JD Integrity
+
+- File/source: `JD_CitadelSecurities_PlatformEngineer.txt` (this folder) — copied from `JDs/JD_CitadelSecurities_PlatformEngineer.txt`
+- Source URL: https://www.citadelsecurities.com/careers/details/platform-engineer/
+- Retrieval method and date: Playwright headless (chromium) via `job_scout/.venv`, 2026-08-25. **WebFetch returns HTTP 403 on this host** — Cloudflare-protected; do not use WebFetch here.
+- Verbatim posting: YES — full visible posting body, unedited except removal of site navigation chrome.
+- Posting status: **LIVE as of 2026-08-25.** Verified independently of the detail page: the role appears in the site's Zurich location filter, which returns 10 open Zurich roles. Board total 81 open roles.
+- Locations: **New York, Miami, Zurich** (JD body: "in Miami, Zurich or New York")
+- Team: Research Platform Engineering
+- **Evergreen caveat:** the posting carries standing-req boilerplate — *"Opportunities may be available from time to time in any location in which the business is based for suitable candidates… we will contact you if there is a vacancy available."* Most likely a continuously-open multi-location req. Less deadline pressure; higher chance of landing in a resume pool rather than against a named opening.
+- **Sibling reqs are dead — do not chase them.** Web results surfaced "Research Platform – Data Platform Engineer" (a closer title match) and "Research Platform Infrastructure Engineer" via Built In. Checked 2026-08-25: the first returns **HTTP 404**, the second is Cloudflare-blocked and absent from the live board. Those Built In listings are stale. **Platform Engineer is the live req.**
+
+## Application Decision
+
+- Audience profile: **International Tech, English** (config default). US market maker, English working language, ex-Google Zurich office. No Swiss/DACH conventions, no photo.
+- Evidence Fit: **74/100**
+- Fit class: **Adjacent (top of band, one point below Core)**
+- Hard gate: **PASS, with one flagged risk** — see Gap Assessment. No minimum qualification is a Gap; nothing required is `forbidden` in `claims.json`.
+- Channel Strength: **Weak (cold)** — no named contact on the posting, no known connection. Would be the 5th consecutive cold-channel application.
+- Cohort slot: Adjacent would be **2/2** (Aker BP holds 1/2). Note: a strict reading of `application_strategy.md` would class this **Stretch** (0/1 free) — see Gap Assessment.
+- Decision: **PENDING USER** — Phase 0 only, per user instruction. Phase 1 not started.
+
+## Requirements
+
+### Minimum qualifications — zero Gaps
+
+| # | JD requirement | Class | Evidence |
+|---|---|---|---|
+| Q1 | Bachelor's in CS or related field | **Direct** | B.Eng. Information & Telecommunication Technologies + M.Eng. Computer Aided Engineering (Software Design & Engineering), UniBw München |
+| Q2 | 3+ years professional software engineering | **Direct** | ~11 years (2015–present) |
+| Q3 | Strong programming in Python, **or** Go, **or** C++, or similar systems-oriented languages | **Direct** | Python `production-current`. Disjunctive requirement — Python alone satisfies it. C++ is `production-historical-limited` / `allowed-with-context`; usable as secondary colour only, never headlined |
+| Q4 | Building **and operating** distributed systems in production | **Direct** | Kafka, Kubernetes, Spark, Airflow carrying production traffic at Swisscom; Component Owner with data quality, incident handling and on-call (SW-1) |
+| Q5 | Designing scalable backend services, APIs, and data-intensive applications | **Adjacent** | Data-intensive applications Direct (BS-2 data services over Oracle/Hadoop; SW-4 Python data apps on K8s). Backend services/APIs partial. **SDKs: no evidence** |
+| Q6 | Strong understanding of distributed systems, data-intensive applications, system design fundamentals | **Adjacent** | iSAQB CPSA-F (software architecture) + AWS SA-Associate + production operation. But "distributed systems" as a *design discipline* has no canonical entry — 0 hits in `claims.json` |
+| Q7 | Cloud platforms (AWS, GCP, Azure) and modern infrastructure | **Direct** | AWS `production-current`. Disjunctive — AWS alone satisfies. (GCP and Azure are `forbidden` in `claims.json`; never list them) |
+
+### Preferred ("is a plus") — complete hit
+
+| JD | Class | Evidence |
+|---|---|---|
+| Kafka | **Direct** | `production-current` |
+| Kubernetes | **Direct** | `production-current-and-historical` |
+| Spark | **Direct** | PySpark `production-current` |
+| Airflow | **Direct** | `production-current` |
+| Distributed databases | **Direct** | Teradata, Redshift, Athena/Iceberg |
+
+**All five preferred technologies are Direct.** This is the strongest raw stack alignment in the application log.
+
+### Core responsibilities
+
+| # | JD responsibility | Class | Note |
+|---|---|---|---|
+| R1 | **Design and build distributed platforms and services** supporting quantitative research, simulations, AI-powered applications | **Adjacent** | Title-defining. He builds governed data products and pipelines *on* Swisscom's platform; authoring research-platform infrastructure at firm scale is a genuine stretch. **This is the risk.** |
+| R2 | Develop scalable platform services and **data systems for ingestion, transformation, storage and lifecycle management of large datasets** | **Direct** | Also title-defining, and a plain description of SW-1 / SW-7 |
+| R3 | Backend services, APIs and **SDKs** for researcher productivity and self-service | **Adjacent** | Data products for downstream self-service is adjacent; SDKs are a Gap |
+| R4 | Improve **performance, reliability, scalability** of critical research systems in **high-throughput** environments | **Adjacent** | Query performance tuning (BS-2), SLOs (BS-3), on-call reliability (SW-1). "High-throughput" in the HFT sense is not evidenced |
+| R5 | Collaborate with researchers to translate requirements into production-ready systems | **Direct** | SW-8 stakeholder requirements; Bosch delivery to analysis teams |
+
+## ATS Keywords
+
+- **Languages:** Python, C++ (context only), SQL
+- **Distributed/infra:** distributed systems, Kubernetes, Kafka, Spark, Airflow, containerization, CI/CD
+- **Data:** data platform, ingestion, transformation, storage, lifecycle management, large datasets, data-intensive applications, distributed databases, ETL/ELT, data modelling, query performance
+- **Cloud:** AWS, S3, Glue, Athena, Iceberg, Redshift, Lambda, Step Functions, CloudFormation
+- **Systems:** scalability, reliability, performance, backend services, APIs, production operation, on-call
+- **Domain:** quantitative research, simulations, backtesting, analytics workflows, model development
+- **Deliberately absent (no evidence):** Go, SDK authoring, low-latency/HFT, GCP, Azure, Terraform
+
+## Gap Assessment
+
+**Four real gaps, in severity order:**
+
+1. **Platform authoring at firm scale (R1) — the decisive one.** The JD wants someone to *design and build the platform researchers use*. Dennis owns components, pipelines and data products *within* Swisscom's company-wide Data Mesh. `CLAUDE.md` Scope Discipline forbids pairing a full-ownership verb with an org-scale object, so this gap **cannot be written around** — it can only be honestly bridged. Same shape as the Aker BP framework-authorship stretch (which scored 79 and still went out as Adjacent).
+2. **No professional quantitative/finance domain.** Now partially mitigated by **PP-1** (self-built momentum/signal platform) and **PP-2** (Udacity AI for Trading nanodegree), added to `claims.json` 2026-08-25. These are genuine self-directed depth — "residual 12-1 momentum, ATR stop/trail, quintile gating" is not JD-scraped vocabulary. But PP-1 is single-user and self-hosted: **never call it distributed, production or multi-user, and never quote a PnL, Sharpe, return or backtest figure.**
+3. **SDKs — no evidence at all.** 0 hits in `claims.json`. Appears in R3 only, not in the minimum quals, so it is not a gate.
+4. **Low-latency / high-throughput systems.** 0 canonical hits. The only throughput reference is the M.Eng. thesis, which `claims.json` `thesis_limits` explicitly flags as a methods prototype with no operational data — **not usable as high-throughput evidence.**
+
+**Non-gaps — do not score these as gaps:**
+- **Go.** Q3 is disjunctive ("Python, Go, **or** C++"). Python satisfies it. The "systems-oriented languages" phrasing is a cultural signal about the room, not a requirement.
+- **Distributed systems experience (Q4).** A production Kafka/K8s/Spark/Airflow estate *is* a distributed system. Do not undersell this.
+
+**Hard-gate verdict: PASS, with a flagged risk.** No minimum qualification is a Gap. This is materially cleaner than the AWS FDE NO-GO, where the title-defining capability was a flat Gap that `claims.json` globally forbids claiming. Here the title-defining function **splits**: R2 Direct, R1 Adjacent.
+
+**Classification caveat, stated plainly:** `application_strategy.md` says *"Stretch: below 60 **or a defining responsibility is only Adjacent**."* R1 is a defining responsibility and is Adjacent, so a strict reading classes this **Stretch**, not Adjacent. It is recorded as Adjacent because R2 — equally title-defining — is Direct, and because the Aker BP precedent (identical authoring-vs-building shape) was recorded as Adjacent at 79. **Both cohort slots are free either way**, so the label does not block the decision. Flagging it so the choice is deliberate, not accidental.
+
+## Company Context
+
+- **Citadel Securities** — technology-driven global market maker (equities, options, fixed income). Distinct from Citadel LLC, the hedge fund. Institutional and retail liquidity provision.
+- **Zurich office:** Klausstrasse 4, 8008 Zurich. Founded 2019. **Heavily ex-Google.** Platform research is led by **Costas Bekas**, former IBM distinguished researcher. **Ferenc Tóth joined June 2026** as a software engineer on the platform research team, from seven years as a Google staff engineer. Principal research is headed by **Nicolai Meinshausen**, the ETH statistician (returned August 2025).
+- **What the Zurich office actually is:** of 10 open Zurich roles, the large majority are quant researchers, ML researchers and quant interns — mostly PhD-gated. Platform Engineer is one of only ~3 experienced non-quant engineering seats there. It is a research-first office, and platform engineering exists to serve researchers.
+- **Role purpose (JD's own words):** systems that "power large-scale simulations, analytics, and model development" and let researchers "transform data into actionable insights and alpha-generating trading strategies." Platform work here is directly revenue-attached, which is unusual and worth understanding before an interview.
+- **Why them angle:** research-serving data platform work, at a firm where the platform's quality visibly determines research throughput — a sharper version of what he does at Swisscom, in a domain he already follows privately.
+
+## Framing Strategy
+
+- **Lead narrative:** *A production data-platform engineer who builds and operates the ingestion, transformation and storage systems analytical consumers depend on — and who independently built an end-to-end equity signal platform because the domain genuinely interests him.*
+- **Reframing map:**
+  - SW-1 / SW-7 → R2 (ingestion/transformation/storage/lifecycle at scale). **Strongest single mapping; lead with it.**
+  - SW-4 (Python apps on K8s + GitLab CI/CD) + Kafka/Spark/Airflow → Q4 distributed systems in production.
+  - BS-2 (data services over Oracle/Hadoop, query performance tuning) → Q5 data-intensive applications + R4 performance.
+  - BS-3 (Application Owner, SLOs, vendor coordination, training) → R4 reliability + R5 collaboration.
+  - PP-1 + PP-2 → domain credibility for R1's *"quantitative research, simulations"* and R3's self-service surfaces.
+- **Emphasize:** production ownership and on-call (they run revenue systems); the exact Kafka/K8s/Spark/Airflow/AWS stack; self-service data products for downstream consumers; genuine domain interest via PP-1.
+- **Downplay:** Data Mesh governance vocabulary (enterprise-flavoured, not their register); Spotfire/BI; ITIL; anything reading as enterprise-IT process.
+- **Never claim:** authoring/owning a company-wide platform; distributed-systems *design* at firm scale; SDK authoring; low-latency/HFT experience; professional quant work; any PP-1 performance number.
+- **Level note:** JD states "Bachelor's, 3+ years" — he is *above* the stated bar at Staff + Component Owner. Do not down-level the framing to match the JD's floor; the $175k–350k base band is wide enough to span several levels.
+
+## Critique Context
+
+- **Reviewer persona:** a platform engineer or eng manager on Research Platform Engineering — likely ex-Google/ex-big-tech, systems-oriented, in a research-first office. Reads for distributed-systems depth and production instinct, not for enterprise process maturity.
+- **Competitive landscape:** brutal. Citadel Securities' engineering bar is among the highest in the market, and the Zurich office is visibly staffed from Google and academia. Realistic competition is ex-FAANG infrastructure engineers and systems specialists. Dennis's differentiator is not raw systems pedigree — it is production data-platform ownership plus real domain interest.
+- **Domain vocabulary to get right:** alpha, signal, backtest, simulation, cross-sectional momentum, factor, research throughput, market making. Using these correctly is credibility; using them loosely is worse than not using them.
+- **Likely probes:** (1) "Describe a distributed system you designed" — the weakest ground, prepare an honest scoped answer about pipeline architecture rather than claiming platform authorship; (2) "What's your throughput/latency experience?" — genuinely thin, do not bluff; (3) PP-1 — expect real interest and real scrutiny, and expect to be asked about results, which must be answered honestly as "not a validated track record".
+- **Compensation caution:** the **$175,000–350,000 base range in the posting is a US pay-transparency disclosure** (NY law) and says nothing about the Zurich figure. Do not plan against it. Citadel Securities Zurich very likely clears the CHF 180k all-in bar, but that is inference, not evidence — ask.
+
+## Cover Letter Decision
+
+- **Decision: YES (recommended), if Phase 1 proceeds.**
+- Rationale: this is the rare case where a letter carries information the resume structurally cannot. The resume can list PP-1 only as a compact project line; it cannot convey *why* a Swisscom data engineer credibly wants a research-platform seat at a market maker. The domain-interest story is the single strongest differentiator against an ex-FAANG competitive field, and it needs prose.
+- Institution type: US market maker, research-first office. Register: direct, technical, unsentimental. No enterprise formality, no Swiss/DACH conventions.
+- Structure: (1) what he builds now, mapped to R2 in their words; (2) production ownership and on-call as the reason he thinks about reliability the way a revenue-system team does; (3) PP-1/PP-2 as honest self-directed domain grounding — explicitly labelled a personal project, no numbers; (4) short close on Zurich, no relocation needed, EU citizen + Swiss B permit.
+- Length: 1 page, 4 short paragraphs.
+- **Hard constraints:** never imply professional quant experience; never quote a PP-1 result; never claim platform authorship; check `bundle_data_engineer.md` §S5 before reuse — its opening hook contained an SW-1 scope violation (fixed 2026-08-21, but verify).
+
+## Status
+
+- Phase 0: **DONE** (2026-08-25)
+- Phase 1: **NOT STARTED** — user requested Phase 0 only
+- Resume: PENDING
+- Cover Letter: PENDING (decision YES)
+- Critique: PENDING
+- Next: user decision on whether to proceed