Walk me through an architecture you designed that you are proud of. What were the biggest trade-offs, and what would you change now?

What the interviewer is looking for

• This question tests solution design & trade-offs. Compares options clearly, explains trade-offs in cost, complexity, risk and time, and reflects honestly on past designs.
• Strong answers: Clear problem and constraints, options considered, reasoned trade-offs, results achieved, and honest reflection on what did not age well.
• Likely follow-up: How did you get the team to agree with those decisions?

Another way it may be asked: Pick a system you designed. Talk me through the key decisions and anything you would do differently today.

A structure to follow: Requirements, sketch, deep-dive, trade-offs

1. Step 1

   Requirements

   Ask who uses it, what it must do, and which qualities matter most: speed, reliability, cost, consistency.

2. Step 2

   Sketch

   Draw the main parts and the path one request takes through them before adding detail.

3. Step 3

   Deep-dive

   Pick the riskiest part (storage, queueing, failure handling) and go deeper there.

4. Step 4

   Trade-offs

   Name what you gave up for each choice, and what you would do first if it needed to grow.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Naming tools before establishing requirements.
• Drawing every box at the same depth instead of going deep where it matters.
• Presenting one design as the only answer, with no trade-offs.

How to practise it

Time yourself: two minutes on requirements, five on the sketch, five on one deep-dive, two on trade-offs.

Related questions

• What is the difference between a monolith and microservices, and when would you advise a client to stay with a monolith?
• A customer says they want to modernise their system. What questions would you ask before suggesting anything?
• How would you explain what an API is to a business stakeholder with no technical background?
• A client needs their new online store to sync orders with an old inventory system that only exports nightly files. How would you design that?
• How do you bring security and compliance requirements, like data privacy rules, into a design from the start rather than at the end?

Browse all questions