Went through the Citadel EM interview loop earlier this year. 15 years in eng leadership, so I've been on both sides of this a lot. Sharing because I found the Citadel process notably different from what I expected.
Loop structure for EM: Initial call with the head of engineering recruiting, a technical round (yes, EMs code here), two leadership/management rounds, a cross-functional stakeholder round, and a final conversation with a director.
The technical round is real. I don't mean hard competitive programming. But you will be given a system design problem and expected to engage at a level that shows you still have engineering instincts, not just management platitudes. They're testing whether you can hold a credible technical conversation with senior ICs on your team. I got: design a real-time risk calculation system that aggregates positions across multiple trading desks. Familiar territory for me but the depth of follow-up was significant.
Management rounds focused on: How I've handled underperformance in a high-stakes environment. Specific decisions I've made about team structure that turned out to be wrong and what I changed. How I've managed conflict between engineering rigor and the need to ship fast. One question that stuck with me: "Tell me about a time you disagreed with a business decision and had to execute it anyway. What did you do with your own disagreement?"
Leveling context: The EM title at Citadel carries more weight than at many tech companies. You're expected to drive real business outcomes, not just shield your team from meetings. The role is close to what some companies would call a director. Comp for senior EMs in NYC is competitive, my offer was in the range of $500-600k TC but I have a lot of experience.
The culture: Unambiguous performance standards. They will tell you clearly what they expect and hold you to it. I've worked at places that talk about this and then soften everything in practice. Citadel doesn't soften.