Citi system design interview
Experienced loops focus on backend depth more than whiteboard DSA: Spring Boot internals, Kafka ordering, memory and GC issues, and keeping data consistent across microservices. Formal system design shows up mostly at AVP and above.
| Progress | Question as candidates report it | Next step |
|---|---|---|
| Payment service with idempotency and network-failure handlingPayment system | Watch | |
| Chat applicationWhatsApp | Watch | |
| Webhook fan-out with per-endpoint isolation and backoffWebhook delivery | Watch | |
| Cross-microservice transactions without two-phase commitWalkthrough being added | Coming soon | |
| Kafka message ordering and consumer-group rebalancingWalkthrough being added | Coming soon |
Which levels get a design round
How to answer any design question: the LADDER method · How the design round is scored by level
Questions people ask
When does Citi ask system design?
A design round is part of the loop at Senior Software Engineer (SDE 3) (Senior Programmer Analyst / VP (C13)), Staff Software Engineer (SVP / Director (C14-C15)). Experienced loops focus on backend depth more than whiteboard DSA: Spring Boot internals, Kafka ordering, memory and GC issues, and keeping data consistent across microservices. Formal system design shows up mostly at AVP and above.
What system design questions does Citi ask?
Payment service with idempotency and network-failure handling; Chat application; Webhook fan-out with per-endpoint isolation and backoff; Cross-microservice transactions without two-phase commit; Kafka message ordering and consumer-group rebalancing.