By Remi · · 3 min read
How to choose an experience worth discussing
You’re asked about a difficult decision in a product manager interview. Two projects come to mind: a big launch you helped deliver and a smaller feature you persuaded the team to drop.
Which one do you choose?
Start with the experience that lets you answer the question clearly. For a difficult decision, you need to explain what you were choosing between, why the choice was hard, and how you reached it. Either project could work—if you have those details.
Examples are fictional illustrations, not testimonials or Remi’s in-product prompts. Use your own experience and leave out confidential information.
In this guide
Match the experience to the question
Before you start talking, take a moment to identify what the interviewer is asking about.
Small differences in the question change what your answer needs:
- “Tell me about a disagreement.” What did each person want, and how did you work through it?
- “Tell me about a difficult decision.” What were your options, and what made the choice difficult?
- “Tell me about a setback.” What went wrong, how did you respond, and what did you learn?
- “Tell me about something you owned.” What were you responsible for, and how did you follow it through?
One project might give you examples for several questions. Choose the part of the experience that answers the one you’ve been asked.
Compare the moments, not just the projects
Suppose the question is: “Tell me about a time you changed someone’s mind.”
Here are two illustrative options.
The big launch: You coordinated updates, kept track of dependencies, and helped the release go smoothly. You’re proud of the work, but you can’t recall a moment when someone changed their position because of something you did.
The smaller feature: Sales wanted a dashboard for demos. You spoke with customers and found that unreliable exports were a more immediate problem. You brought those examples to the sales lead, worked through their concerns, and agreed to prioritize the export fix.
The second experience gives you a clearer answer to this question. You can explain the original position, what you brought to the discussion, and how the decision changed.
Keep the launch example. It may fit a question about coordination or delivery much better.
Choose a story you can discuss beyond the opening answer
A story might sound strong in a short summary but become difficult when someone asks for details.
Before choosing it, check whether you can answer:
- What did I personally do?
- What made this difficult at the time?
- Why did I take that approach?
- What happened afterward?
You don’t need to remember every meeting or date. But you should be able to explain the main events without guessing.
If you mostly remember what your manager decided, look for a moment where you were more involved. If the outcome was disappointing, the story may still be useful—especially for a question about learning or adapting.
Prepare a few options you can find quickly
Give each experience a short, memorable label: “cutting launch scope,” “disagreeing with design,” or “the feature nobody used.”
Beside it, note the questions it could help you answer. This makes it easier to find a relevant example under pressure.
Avoid preparing only one favourite story. You may end up stretching it to fit questions it doesn’t really answer.
Try it with one interview question
Write down a question you expect to face. Then choose two possible experiences.
For each, finish:
“This fits because I…”
If you struggle to complete that sentence, try another example. If both fit, choose the one where you can explain your actions and reasoning most clearly.
Need more options? Start with these prompts for remembering examples from your work. Once you’ve chosen an experience, use Remi to work through the details.
This guide covers past-experience PM interview preparation. Interview expectations vary by employer; additional product, analytical, or technical preparation may be needed.