A product manager interview script is the list of questions that assess how a person decides, prioritises, measures and works with other teams. This tool builds the script from a curated bank of 80 questions, filtered by the seniority of the role and by interview type (behavioural, product sense, execution and metrics, strategy, technical collaboration and leadership), and shows for each question what a good answer reveals.
How to use
- Choose the seniority of the role: junior, mid-level, senior or lead.
- Tick the interview types you want to cover, or none to mix them all.
- Set the number of questions (3 to 20) and, if you want others, change the set.
- Read, for each type, how to structure the answer and what each question needs to show.
- Export as PDF, DOCX, CSV or Markdown to practise or to take into the interview.
What each field asks for
| Field | What to enter |
|---|---|
| Seniority of the role | The questions and what is expected from the answer change with the level. |
| Interview types | Choose one or more. With none chosen, the script mixes them all. |
| Number of questions | From 3 to 20. Blank means 10. |
| Question set | Change the set to see other questions with the same filters. |
Example
For a mid-level product manager role, with behavioural, product sense and execution and metrics interviews, the script brings 9 questions, three of each type. Among them: describe a time you had to say no to an important request (a good answer shows an explicit criterion and care for the relationship), improve your city's public transport app (choosing a segment and a success metric) and investigate a 15% drop in conversion from one week to the next (checking the data before listing hypotheses).
When to use
- In the week before an interview, to practise answers out loud.
- When opening a role, to give every candidate the same questions.
- To prepare first-time interviewers, with what to look for in each answer.
- In mentoring, to simulate an interview and discuss the answers.
Frequently asked questions
What types of question come up in a product manager interview?
The most common are behavioural (real past situations), product sense (designing or improving a product), execution and metrics, strategy, collaboration with engineering and leadership. The weight of each type changes with the seniority of the role.
How do I structure a behavioural answer?
Tell a real situation in four parts: the context, what was yours to do, what you did and the result, ideally with a number. This is the structure known as situation, task, action and result. Close with what you learnt.
What changes between junior, mid-level, senior and lead?
At junior level, clarity of reasoning counts; at mid level, decisions of your own with results; at senior level, trade-offs across teams and business impact; at lead level, results through other people. The questions and what is expected from the answers follow that difference.
Are the questions useful for interviewers?
Yes. Use the same script with every candidate and note evidence, not impressions. The "what a good answer shows" column helps agree the criteria before the interviews.
How do I get other questions with the same filters?
Change the set (A, B or C): the script starts from another part of the bank. Ticking more interview types also widens the options.
Does memorising answers help?
Not much. Interviewers usually dig deeper with follow-up questions, and a memorised answer does not hold up. It is worth more to have three or four real situations you remember well, which serve several questions.