dennisthiessen/claude-resume-kit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(citadel): working model unresolved - block Phase 2, 74 -> 71

Browse Source 
The user asked whether Citadel has a hybrid model. The JD is silent:
grepping the verbatim posting for hybrid, remote, onsite, in-office and
days per week returns zero matches. Phase 0 scored practical constraints
5/5 on an unexamined assumption that Zurich was workable. Withdrawn.

Ken Griffin is on record that Citadel returned to the office five days a
week, early and deliberately, and calls it his most important leadership
decision of the past seven years - framed as core apprenticeship culture
rather than a policy setting. The only contrary evidence is an anonymous
2022 Fishbowl post about Operations claiming three days minimum: four
years stale, wrong division, contradicted by the founder on record. No
official Citadel Securities Zurich policy statement could be found.

If five-day onsite holds for Zurich, it means roughly 2 to 2.5 hours of
commuting per day from Bern, or relocating - which breaks both the
Bern-based, 2-3 day hybrid bar in user_comp_bar and the "keep a Swiss
home base" constraint in user_international_mobility.

Practical constraints 5/5 -> 2/5 (language and authorization stay clean:
English working language, EU citizen, Swiss B permit). Evidence Fit
74 -> 71, still Adjacent but mid-band rather than a point below Core.

More consequential than the number: critique_framework.md treats an
unresolved location or relocation constraint as a NO-GO trigger, so the
qualifications gate passes while the practical gate does not. Phase 2 is
blocked pending an answer.

This has to be asked, not researched - the same class of question as the
SBB Anforderungsniveau K band. Recording the sequencing explicitly,
because SBB was submitted with its equivalent question still open and
that question is now a live screening topic instead of a settled fact.
Repeating it here should be a deliberate choice, not an oversight.

The Phase 1 bullet plan is written and unaffected: 11 recommended, 14
with options, budget PASS. Two items still open - the Vizrt VZ-1
C++/distributed bullet the user previously skipped on Snowflake, and
adding a Projects section for PP-1.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MHtzyTKBcg6BWhD5qFegtK
This commit is contained in:
dennisthiessen
2026-08-26 08:30:22 +02:00
co-authored by Claude Opus 5
parent ec5be5f2ed
commit 0eda29327a
2 changed files with 119 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
output/CitadelSecurities_PlatformEngineer/session_citadel_securities_platform_engineer.md
+118 -4
View File
@@ -15,9 +15,9 @@
## 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`.
- Evidence Fit: **71/100** (revised down from 74 on 2026-08-26 — see Working Model below)
- Fit class: **Adjacent (mid-band)**
- Hard gate: **QUALIFICATIONS PASS, but a PRACTICAL CONSTRAINT IS UNRESOLVED** — `critique_framework.md` flags a NO-GO when "location… or mandatory relocation is unresolved." The Zurich working model is unknown and the evidence points to 5-day onsite. **Resolve before Phase 2.**
- 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.
@@ -85,6 +85,38 @@
**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.
## Working Model — UNRESOLVED, decision-blocking (raised by user 2026-08-26)
**The JD is silent.** Grep of the verbatim posting for hybrid / remote / onsite / in-office /
days per week / office returns **zero matches**. Phase 0 scored practical constraints 5/5 by
assuming Zurich was workable; that assumption was unexamined and is now withdrawn.
**Evidence, and its quality:**
| Source | Says | Reliability |
|---|---|---|
| Ken Griffin, on record (Fortune 2023, repeated since) | Brought Citadel back **5 days a week**, early and against the grain; calls it his most important leadership decision; all employees in office full-time; remote work "hinders innovation" and costs early-career development | **High** — founder/CEO, on record, repeated, framed as core culture not policy |
| Fishbowl post, Nov 2022 | "usually 3 days minimum… depends on your manager" | **Low** — anonymous, 4 years stale, Operations not Engineering, contradicted by the CEO |
| Citadel Securities Zurich official policy | Not found | — |
**Consequence if 5-day onsite is correct:** Bern → Zurich is ~1h each way, so ~2–2.5h commuting
per day, five days a week — or relocation to Zurich. That breaks the standing constraint
(`user_comp_bar`: Bern-based, hybrid max 2–3 days) and `user_international_mobility` ("keep a
Swiss home base", no relocation).
**Scoring impact:** Practical constraints **5/5 → 2/5** (language and authorization remain clean:
English working language, EU citizen + Swiss B permit). Evidence Fit **74 → 71**. Still Adjacent,
now mid-band rather than one point below Core.
**This must be ASKED, not researched** — same class of question as the SBB Anforderungsniveau K
band. No amount of further searching produces an authoritative answer for the Zurich office
specifically, and the cost of guessing wrong is a full package plus a process built on a
commute the user has already declined elsewhere.
**Recommended sequence: resolve this BEFORE Phase 2, not after.** The SBB package was submitted
with its equivalent question still open, and that question is now a live screening topic instead
of a settled fact. Repeating that pattern here would be a deliberate choice, not an oversight.
## 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.
@@ -124,10 +156,92 @@
- 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).
## Resume Plan (Phase 1 — proposed 2026-08-26, awaiting confirmation)
Bundle: **`bundle_data_platform.md`** primary (Tier 3), `bundle_data_engineer.md` secondary.
Format: 2-page resume, International Tech, English.
Bullet lengths: **natural** per `resume_reference.md` §7 — the SKILL.md "all bullets 2L" line is stale,
superseded by the 2026-07-27 global correction. §7a cadence variety applies.
### Swisscom — Staff Data, Analytics & AI Engineer (5 bullets)
| | ID | Achievement | JD match |
|---|---|---|---|
| * | SW-7 | Governed data products in the company-wide Data Mesh; onboard sources; metadata + lineage in Atlassian Compass | **R2 Direct** — lifecycle mgmt; R3 self-service |
| * | SW-1 | Migrated owned Fulfillment/Product Analysis pipelines onto AWS (Glue, Athena/Iceberg, Redshift, Airflow, CloudFormation) | **R2 Direct**, Q7 cloud |
| * | SW-2 | Component Owner, business-critical Fulfillment ETL (Oracle/Kafka → Teradata): data quality, governance, incidents, on-call | **Q4 Direct**, R4 reliability |
| * | SW-3 | Build and operate Python data applications on Kubernetes with GitLab CI/CD | **Q4 Direct**, Q5 backend services |
| o | SW-4 | Deliver data products and analyses with internal stakeholders; translate requirements | R5 Bridge |
### Bosch Semiconductor Dresden — Senior Engineer, Data Analysis (4 bullets)
| | ID | Achievement | JD match |
|---|---|---|---|
| * | BS-2 | Data services in Python/Java/C# over Oracle and Hadoop/Impala; **query performance tuning**; fab sensor/process data | **Q5 Direct**, R4 performance |
| * | BS-1 | Integrated containerized ML inference (Docker/K8s/Ansible) into a 24/7 fab | **Q4 Direct**, R1 "AI-powered applications" |
| * | BS-4 | ELK/Kafka anomaly-detection PoC with Grafana/Prometheus/Loki monitoring | Kafka Direct, R4 reliability |
| o | BS-3 | Application Owner: SLOs, vendor coordination, training and documentation | R4 + R5 Bridge |
### Vizrt — Test Automation / DevOps Engineer (1 bullet) — **user decision needed**
| | ID | Achievement | JD match |
|---|---|---|---|
| ? | VZ-1 | Contributed **Python and C++** engineering to a **distributed video-transcoding backend** | **Q3 C++ bonus + Q4/Q6 distributed** |
| x | VZ-2 | Automated A/V integration tests as CI/CD quality gates | Weak for this JD |
**VZ-1 is unusually well-matched to this specific JD** — it is the only canonical evidence that pairs
C++ with a genuinely distributed backend, which is exactly Q3's bonus clause plus Q6. **But the user
explicitly skipped the Vizrt low-latency angle on the Snowflake package.** Raising it rather than
assuming. Verb must stay hedged ("contributed"); broadcaster names are `forbidden`.
### Fraunhofer CML — Research Software Engineer (1 bullet)
| | ID | Achievement | JD match |
|---|---|---|---|
| * | FC-3 | Developed containerized microservices for the MISSION **research** data-exchange platform | R1/R3 Bridge — closest canonical analogue to "research platform" |
| o | FC-1 | Jenkins CI/CD setup | Weaker here than FC-3 |
### Generali (0–1 bullets)
| | ID | Achievement | JD match |
|---|---|---|---|
| x | GN-1 | BDD test automation PoC, Jenkins ownership, training | Weak — recommend omit |
### Selected Project — PP-1 (1–2 bullets) — **new section, structural decision needed**
| | ID | Achievement | JD match |
|---|---|---|---|
| * | PP-1 | Self-built equity signal platform: price/fundamental/sentiment ingestion, cross-sectional momentum book, scheduled scan + backtest pipelines, dashboard + alerts | **Domain credibility for R1 "quantitative research, simulations"** |
| o | PP-2 | Udacity *AI for Trading* nanodegree | Certification-context only |
The current 2-page template has **no Projects section**. Adding one is a Phase 2 structural change.
PP-1 is the main differentiator against an ex-FAANG field, so it should appear — but it must be
labelled a personal project, and `claims.json` forbids calling it distributed/production/multi-user
or quoting any PnL, Sharpe, return or backtest figure.
### Budget
| Set | Bullets |
|---|---|
| Recommended (`*`) | **11** |
| With `o` options (SW-4, BS-3, PP-2) | 14 |
| Target (`resume_reference.md` §4) | 11–14 |
**Budget: PASS** at both ends.
### Forced exclusions (provenance)
- **SW-5 Security Champion** — omit by default; JD has no security requirement.
- **SW-8 LLM work** — configuration-level only; `forbidden` to imply built/deployed LLM systems. LLM
sentiment in PP-1 is fine as personal-project scope.
- **GCP / Azure / Terraform / TypeScript / FastAPI** — `forbidden` in `claims.json`; never list even
though the JD names GCP and Azure (Q7 is disjunctive; AWS satisfies it).
- **M.Eng. thesis throughput figure** — barred by `thesis_limits`; not usable as high-throughput evidence.
## Status
- Phase 0: **DONE** (2026-08-25)
- Phase 1: **NOT STARTED** — user requested Phase 0 only
- Phase 1: **PROPOSED 2026-08-26 — awaiting user confirmation**
- Resume: PENDING
- Cover Letter: PENDING (decision YES)
- Critique: PENDING