Tell me about a time an experiment or launch did not go the way you expected. What did you learn and what did you change?

What the interviewer is looking for

• This question tests experimentation & launch. Uses tests, staged rollouts or betas deliberately, plans launches with go-to-market partners, and learns honestly from results that disappoint.
• What to bring out: Is honest about the result, digs into why, separates noise from signal, and shows a concrete change in approach.
• Expect a follow-up like: Looking back, what would you have set up differently before launching?

Another way it may be asked: Think of a launch or test where the results surprised you or disappointed you. What happened next?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the experimentation & launch you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

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

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• If you were asked to improve a product you had never used before, how would you figure out what its users actually need?
• Imagine you have three feature requests and time to build only one. How would you decide which to do first?
• Tell me about a time you had to explain a complicated idea to someone without your background. How did you make sure it landed?
• Walk me through how you defined success for a feature you recently shipped, and which numbers you watched after launch.
• How do you work with engineers and designers to turn a rough problem into something the team can build? Give me a recent example.

Browse all questions