A free PM behavioural interview story template you can actually use

Start with one decision you can reconstruct

Choose a project where you had a meaningful part in a decision: reducing scope, changing a discovery plan, saying no to a request, recovering from a setback or influencing a team you did not manage. A large project is not automatically a useful story. A smaller decision with clear alternatives and evidence can be easier to explain.

Before drafting, write down the interview question you want this story to answer. A conflict story needs two reasonable positions. A prioritisation story needs something you chose and something you deferred. A failure story needs a mistaken assumption or decision, its consequence and what you changed. If the story does not fit the question, choose another example instead of forcing it.

Copy this six-part story card

Use these prompts as working notes, not a script. The first pass can be untidy. Your aim is to locate the facts you need before polishing the language. Put each answer in a separate line so gaps are easy to see.

STAR is a useful structure for presenting a behavioural answer. Amazon's official PM preparation material recommends it. This Supecoder worksheet adds decision and evidence prompts inside that structure; it is an editorial preparation aid, not an employer's scoring rubric.

• Situation: who had a problem, and what made it matter at that moment?
• Responsibility: what were you personally accountable for, and what belonged to other people?
• Decision: what did you recommend or decide, and what alternative did you consider?
• Trade-off: what constraint shaped the choice, and what did the chosen option leave unresolved?
• Outcome and evidence: what happened afterwards, how do you know, and what cannot you attribute to your work?
• Reflection: what would you repeat or change if you faced the situation again?

Worked example: a smaller release with a clear decision

Fictional worked example. This is an invented preparation scenario, not a customer result or a story about a real employer. A PM is asked to add a reporting feature before a customer review. Engineering has already committed to fixing an unreliable export. The PM compares a new report, a manual report and a smaller export fix.

A prepared answer could say: 'The customer team needed usable information for an upcoming review, while engineering was already addressing export failures. I was responsible for recommending the release scope. I checked which questions the customer team actually needed to answer and asked engineering to explain the dependency. I recommended fixing the export first and using a manual report for the review. We recorded an owner for that workaround and a separate review point for the report feature.'

The outcome still needs a boundary: 'The agreed scope was delivered and the customer team received the manual report. I can support those facts. I do not have evidence that this decision caused a renewal or a revenue change. Next time I would confirm the reporting requirement earlier, before it became an urgent release request.' Notice how the answer shows ownership without claiming the PM built the export or personally secured the customer.

Use evidence you could explain in a follow-up

Evidence can include a scope decision, a change in a customer workflow, an observed reduction in repeat issues or feedback with a clear source. Check what each item actually proves. A launch date proves that something shipped. It does not prove adoption. A positive comment proves someone expressed a view. It does not prove the whole customer base felt the same way.

If you lack a reliable metric, state the limitation and explain the observed outcome. Do not add a plausible percentage to make the story sound stronger. Also leave confidential documents, customer names and identifying details out of your preparation files. You can explain the decision without reproducing a private document.

Test the story with five uncomfortable questions

Rehearse a short version aloud, then let someone interrupt you. If every interruption sends you back to the beginning, the answer probably depends too much on a memorised order. Keep the decision clear enough that you can answer the question directly and return to the story.

Use the following prompts to find weak spots. A missing answer is a preparation task, not something to cover with confident language. You may need to check your memory, narrow a claim or use a different project.

• Why was the rejected option reasonable?
• Who had final decision authority?
• What did you personally do?
• What evidence would have changed your recommendation?
• What remained unresolved after the work?

Choose the preparation tool that fits the task

You can use the prompts on this page without buying anything. The free editable sample includes one worked story, a blank card and six follow-up questions. The browser story builder helps organise one example without sending your notes to an AI service.

If you want a repeatable system for several stories, the A$39 PM Interview Evidence Kit adds six editable story cards, an evidence workbook and role map, 24 follow-up questions and three annotated fictional examples. It is a self-guided toolkit for experience-based answers. Product cases, technical rounds and employer-specific assessments need their own preparation.

Sources and scope

Employer-specific guidance is linked below. This worksheet and its practice examples are original Supecoder editorial material, with no employer affiliation or endorsement.

• Amazon: official product manager interview preparation