Citadel · Primly Community

Citadel product manager interview questions: what got asked in my full loop

pm_priya · 4 replies

Did the PM interview loop at Citadel a couple months back for a role on their trading platform product side. It's not a typical PM interview and I want to save other PMs from walking in underprepared.

The loop structure I got: Recruiter screen, two product case rounds, one technical depth round, one cross-functional collaboration round, and a culture fit conversation with a senior leader.

Product cases: Both were financial products. One was: how would you redesign the portfolio risk dashboard for an experienced portfolio manager? The other was more analytical: a metric on our options pricing tool dropped 15%, walk me through how you'd investigate. These weren't gotcha questions but they required some working knowledge of financial concepts. I had to know what Greeks meant for the options question. You don't need to be a quant but you need to be comfortable in the domain.

Technical depth: They asked me to walk through how I'd spec an API for a new position data feed that traders and risk systems both consume. I'm not an engineer but they expected me to talk about versioning, schema design tradeoffs, backward compatibility. This round will separate PM candidates fast.

What they value, as far as I could tell: Speed. Comfort with ambiguity but also the ability to cut through it fast. A strong opinion paired with intellectual honesty about the limits of that opinion. They do not want a PM who needs three weeks to ship a spec.

What they're less into: Process for its own sake. I mentioned a framework once and got a mildly impatient response. They wanted to see me think, not reference a template.

I turned down the offer in the end, the culture is high-intensity in a way that works for some people and not others. But the interview itself was genuinely interesting.

4 replies

growth_gabe

The API spec question for a PM round is intense. Did they expect actual endpoint design or more of a product requirements flavor?

pm_priya

Somewhere between the two. They wanted me to talk about what fields the feed should expose, how versioning would work if downstream consumers needed backward compat, and how I'd handle schema drift over time. Not pseudo-code, but not vague requirements either. Think: what a really technical PRD section would look like.

apm_aisha

The financial domain knowledge bar sounds high. How much did you prep on options specifically before the loop?

brand_ben

That detail about framework impatience is important. I've been in rooms like that. Some interviewers have a physical reaction when you say "so I'll use the CIRCLES method." Better to just think out loud.