A big marketing launch is expected to triple traffic in six weeks. How would you prepare the system and prove it is ready?

What the interviewer is looking for

• This question tests capacity & resilience design. Uses load testing, forecasting, redundancy, graceful degradation and failure testing to make systems survive spikes and outages.
• Strong answers: Forecasting, realistic load tests, finding bottlenecks including dependencies, autoscaling and headroom, load shedding, a launch runbook and a rollback plan.
• Likely follow-up: What would you do if the load test failed a week before launch?

Another way it may be asked: Marketing says three times the usual visitors are coming soon. How do you make sure the site holds up?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

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

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• How would you design a service so that losing an entire availability zone, or a key dependency, does not take the whole product down?
• What is the difference between a service level indicator, a service level objective and a service level agreement, and why would a team care about the difference?
• A Linux server is suddenly very slow. What are the first things you would check, and what would each one tell you?
• You are on call, and at two in the morning you get paged that the checkout page is returning errors. What do you do in the first ten minutes?
• How do you decide what deserves to page a human at night versus what can wait for a ticket in the morning?

Browse all questions