Citadel interview notes, page 2 of 14

“Classic problem, the kind you've either drilled or you haven't.” The rest of the author's notes on Software Engineer interview at Citadel, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew the 'why Citadel' part was coming and had a decent answer ready.” The rest of the author's notes on Software Engineer interview at Citadel, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The translation-only constraint is what makes this interesting.” The rest of the author's notes on Software Engineer interview at Citadel, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is one question but it's really like six questions stapled together.” The rest of the author's notes on Software Engineer interview at Citadel, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This ate the whole interview.” The rest of the author's notes on Software Engineer interview at Citadel, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The key insight is that U(0,a) is just U(0,1) conditioned on being less than a, which is a clean way to think about it but not where my brain went first.” The rest of the author's notes on Software Engineer interview at Citadel, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went with a sorted structure per exchange, like a max-heap for bids and min-heap for asks, which felt right until they pushed on cancellations.” The rest of the author's notes on Software Engineer interview at Citadel, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Went with union-find pretty quickly, which felt right.” The rest of the author's notes on Software Engineer interview at Citadel, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The add and executeNext parts came pretty naturally, heap with a sequence counter for tie-breaking.” The rest of the author's notes on Software Engineer interview at Citadel, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one ate up most of the session.” The rest of the author's notes on Software Engineer interview at Citadel, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.