0 day streak

Citi system design interview

Banking Global

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.

0%ready
ProgressQuestion as candidates report itWalkthroughPractice boardNext step
Payment service with idempotency and network-failure handlingPayment system Payment system – Watch
Chat applicationWhatsApp WhatsApp Open board Watch
Webhook fan-out with per-endpoint isolation and backoffWebhook delivery Webhook delivery Open board 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

SDE 1Programmer Analyst (C10)Usually none
SDE 2Intermediate Programmer Analyst / AVP (C11-C12)Usually none
SDE 3Senior Programmer Analyst / VP (C13)System design
StaffSVP / Director (C14-C15)System design

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.