i interviewed for an EM role at Citi in early 2026. director of engineering was the hiring manager. five rounds. here's what they were actually measuring, because the public info is all surface-level stuff.
full disclosure: i've been an EM for 8 years and have been on both sides of this kind of panel, so i had some baseline for calibrating.
round 1: intro + background with the hiring director. conversational but they're already evaluating you. they want to know your team sizes, the scope of what you've owned, and whether you can clearly articulate why things went the way they did. the honest answer is always better than the polished answer here. they've talked to enough managers to smell a sanitized answer.
round 2: technical depth. this caught some people off guard i think. they don't expect you to write code, but they do want to know you can hold a technical conversation with your senior engineers. they asked me questions about distributed systems concepts, how i'd evaluate architectural tradeoffs with my team, and how i've handled situations where i disagreed with my team's technical direction. i talked about a real situation where i overruled an IC4 on a database choice. the key was explaining how i made the call and how i kept the engineer's trust after.
round 3: people management and org design. this is the core of the EM loop. questions: how have you developed an engineer who was underperforming? how have you structured a team through a reorg? how do you handle a staff engineer who thinks they should be reporting to your director, not to you? that last one got specific fast. be ready to talk about navigating seniority and ego with grace.
round 4: cross-functional collaboration. how do you work with product, finance, risk, compliance? at Citi this matters a lot more than at a startup because regulatory constraints shape engineering decisions constantly. i talked about working with compliance teams to scope what was technically feasible within a legal constraint. that seemed to resonate.
round 5: panel presentation. they asked me to prepare a 20-minute talk on how i'd approach building out a new team from scratch. i covered hiring strategy, onboarding, technical roadmap, and success metrics. questions afterward were good. they pushed on how i'd handle slow hiring given that Citi's recruiting process is not fast.
the behavioral questions throughout were all STAR-format and they really pushed on "what was the outcome" with follow-up questions. vague outcomes get dug into.
comp for a VP/EM level in NYC: total comp was competitive for a large bank, meaningfully below FAANG but the stability trade is real. the role comes with real ownership and a team of 8 engineers.
process was about 7 weeks start to finish. slow but they were responsive.