In: the problem, the evidence it is real, the user and their current workaround, success metrics with a failure threshold, explicit non goals, and open questions. Out: the solution design and the implementation. If your document specifies the UI or the schema, you have taken the interesting decisions away from the people best placed to make them, and you will get compliance instead of ideas.
Why interviewers ask this
Writing is the core artifact of the job, so this reveals how you think as much as what you document. Interviewers watch for a problem first structure, for non goals (the single best predictor that someone has been burned by scope creep), and for restraint about prescribing solutions. It also shows whether your documents are living decision logs or one time handover specs that nobody opens again.
How to structure your answer
- List the sections and why each one exists.
- Highlight non goals as the scope creep defense.
- Say what you leave out and why that is deliberate.
- Mention keeping open questions visible as the doc evolves.
Example answer
My PRD is short and it is mostly evidence. Problem, who has it and how often, what they do today instead, why now, the metric with an explicit failure threshold, and a non goals list. The non goals section earns its space every time, because it is where you head off the scope creep that would otherwise arrive in week three. What I deliberately leave out is the solution. I do not put wireframes or a schema in there, because the moment I do, the engineers and the designer stop solving and start implementing my half formed idea. I learned that the hard way after writing a very detailed spec once and getting exactly what I asked for, which was worse than what the team would have built on their own. I also keep an open questions section at the top and update it as we go, so the doc shows what we still do not know rather than pretending to be finished.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- Who reviews your PRD before it is considered ready?
- How do you keep it current once the build starts?
- What is your non goals list on the last thing you shipped?
Related product manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions