Common Microservices Interview Scenarios & How to Approach Them
Last Updated: June 6, 2026
Most microservices design questions are variations on a small number of underlying shapes. A food delivery platform, a ride-sharing app, and a payment system look like three different prompts, but two of them share an order-lifecycle saga, all three need idempotent money movement, and all three reward the same opening move: name the bounded contexts before drawing a single box.
Once you have seen enough prompts, you stop solving each from scratch and start recognizing which archetype you are in. Each scenario in this chapter has a canonical answer: a default set of bounded contexts, a handful of patterns that almost always belong, and one or two decisions worth reasoning about out loud. The aim is not to recite a memorized solution but to get the obvious 70 percent right quickly, so the time you have left goes to the 30 percent that distinguishes a strong design.
Before the scenarios, here is the shape of a good answer, because every scenario reuses it:
- Clarify the requirements: Pin down scale, the handful of core use cases, and the one or two non-functional properties that dominate (consistency, latency, availability). A few minutes here changes everything that follows.
- Name the bounded contexts: Break the domain into services that own their data and their decisions. This is the spine of the whole design, and where most answers differentiate themselves.
- Decide data ownership and communication: For each context, what does it store, and how does it talk to its neighbors, synchronously for reads it needs now, asynchronously through events for everything else.
- Handle scale and failure: Where are the hot paths, where are the bottlenecks, and what happens when a dependency is slow or down.
- Name the trade-offs: Make the interesting decisions explicit and defend them. This is the part that turns a competent answer into a distinctive one.
The scenarios that follow are organized so the first four are "design a product" prompts, where the work is mostly in steps two and three, and the last four are "reason about a property" prompts, where the work is mostly in steps four and five.