You need to plan a migration from an old system to a new one without downtime for customers. How would you approach sequencing and risk?

What the interviewer is looking for

• This question tests system & platform thinking. Reasons about dependencies, scale, migration risk and build versus buy trade-offs, and sequences work to reduce risk.
• Strong answers: Proposes phased rollout, running both systems in parallel, clear rollback plans, communication with dependent teams, and success checkpoints.
• Likely follow-up: What would make you pause the migration halfway?

Another way it may be asked: Your company is moving everyone off an old database onto a new one, and customers must not notice. How would you plan it?

A structure to follow: Frame, structure, analyse, recommend

1. Step 1

   Frame

   Restate the goal and ask what success is and what the constraints are.

2. Step 2

   Structure

   Split the problem into a few separate parts you can check one by one, and say what you will look at first and why.

3. Step 3

   Analyse

   Reason with the information you have, state your assumptions out loud, and say what data would change your mind.

4. Step 4

   Recommend

   Give a clear recommendation, the main risk, and the first step you would take.

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

• Listing ideas without choosing between them.
• Hiding assumptions instead of stating them.
• Finishing without a recommendation.

How to practise it

Answer in four spoken parts, one per step, then check you ended on a recommendation.

Related questions

• How do you decide whether to build a capability in house, buy a vendor tool, or adopt an open source option?
• In simple terms, how would you explain what happens behind the scenes when someone taps a button in an app and their data loads?
• If an engineer told you a feature would take three times longer than expected, what questions would you ask them?
• Imagine two engineering teams disagree about who should own a shared service. How would you help them reach a decision?
• Tell me about a technical spec or requirements document you wrote. How did you decide what level of detail engineers needed?

Browse all questions