picked.
Log inPost a role
picked.ai/hire/product-manager/interview-questions
30 product manager
interview questions that actually work.
Pulled from the Neuroworx item bank: nine years of calibration against twelve-month performance outcomes on 14,083 product managers. Sorted by stage (screen, assessment, on-site) and level (IC1 to IC5). Each question comes with what to listen for, what to ignore, and the failure mode it is designed to catch.
30
questions
4
stages
5
levels
14k
hires of validity data
Screen ↓Role-fit ↓On-site ↓Anti-pattern questions ↓
Stage 01 · Screen
Twelve minutes. Ten questions.
The screening conversation. Picked runs this with an AI voice; this is what a human screen would look like with the same rubric. Time-box hard. 60 seconds per answer.
10 questions
01
Tell me about the last feature you shipped, watched, and then removed or rolled back.
outcome focusspecificity
Listen for
A specific feature, the metric they were watching, the number that triggered the rollback, the conversation with engineering.
Ignore
A pitch for a feature that "needed more time". We want the removal, not the defence.
catches · PMs who have never killed their own work.
02
Walk me through your most recent spec. Read me the non-goals section.
spec craft
Listen for
A real spec. A non-goals section that names the obvious adjacent feature and explains why it is out of scope.
Ignore
A spec that is all goals and no constraints.
catches · PMs who treat the spec as a feature brochure.
03
Name three of your current users by first name and tell me what each one cares about.
customer instinct
Listen for
Three specific people. Three specific cares. The last conversation they had with each.
Ignore
A persona document. Personas are not users.
catches · PMs who have not spoken to a user this month.
04
Tell me about a quarter where the data disagreed with your gut. What did you do?
decision qualityevidence
Listen for
A specific quarter, a specific disagreement, the call they made, what they learned.
Ignore
"I always follow the data" or "I always trust my gut". Both lie.
catches · PMs who cannot hold a tension between two signals.
05
What is the last feature you fought engineering to descope?
prioritisationcomms
Listen for
A real feature, the reason for descope, the trade with engineering, what shipped instead.
Ignore
A story about being "the voice of the user". We want the trade.
catches · PMs who only add to the spec.
06
Tell me about the last time a designer pushed back on you. Who was right?
the trade with design
Listen for
A specific push-back, the substance of the disagreement, the call they made, an honest read on who was right in retrospect.
Ignore
"We always agree." Suspicious.
catches · PMs who flatten design judgement to "design says".
07
Which of your shipped features has the worst retention curve? Why?
outcome focuscandour
Listen for
A named feature, the curve shape, an honest read on the cause.
Ignore
"All our features retain well."
catches · PMs who do not look at the curve after launch.
08
Walk me through how you prioritised the last quarter. What did not make it?
prioritisation
Listen for
A specific framework or instinct, three things that did not make it, the reason each one was cut.
Ignore
A RICE score table without a story.
catches · PMs who prioritise by loudest voice in the room.
09
Tell me about a customer interview that changed your roadmap.
customer research
Listen for
A specific customer, the moment in the interview, the change they made the next week.
Ignore
"All interviews are useful." Vague.
catches · PMs who run interviews and never act on them.
10
Why are you leaving your current role?
stage fit
Listen for
A reason that is about the shape of the next role, not a complaint. A specific thing they want to do that the current role will not let them.
Ignore
Pure complaint about the current manager.
catches · PMs running from, not to.
Stage 02 · Role-fit assessment
A scoped task. A scored rubric.
One realistic task. We score the writeup, not the polish. The candidate has the take-home equivalent of 60 minutes.
8 questions
01
Here is a one-paragraph problem statement and a screenshot of our current onboarding. Write the one-page spec for the change you would ship first.
spec craftIC2+
Listen for
A one-pager with a stated goal, a non-goal, a sketch, an instrument. The shipped first cut, not the dream.
Ignore
A multi-quarter roadmap. We asked for the first cut.
catches · PMs who cannot bound a spec.
02
Here are four customer interview transcripts. Pick the one insight you would build against this quarter and write the two-sentence reason.
customer researchIC2+
Listen for
An insight that earns its place across more than one transcript. A two-sentence reason that names the metric it would move.
Ignore
An insight from a single anecdote.
catches · PMs who treat every customer comment as a roadmap input.
03
You have three engineers for six weeks and four ideas in the column. Pick one. Justify in three sentences. Tell me what you defer and why.
prioritisation under pressureIC3+
Listen for
A clear pick, a clear reason, three deferrals with three reasons. Honesty about what they are betting against.
Ignore
A pitch for "doing all four with smaller scope".
catches · PMs who cannot hold a single choice under constraint.
04
Here is a feature we shipped six weeks ago. Activation is flat. Write the three things you would change first and the order you would change them.
outcome focusIC2+
Listen for
Three specific changes, an order with a reason (cheapest first, or biggest lever first), the metric each one would move.
Ignore
A redesign of the whole feature.
catches · PMs who reach for a rebuild before a tweak.
05
Write the kill memo for a feature you would now remove. One paragraph. Pre-empt the two objections.
killing a featureIC3+
Listen for
A kill memo that names the feature in the first sentence, the metric that justifies removal, the two objections by name.
Ignore
A memo that hedges or proposes "iteration".
catches · PMs who cannot land a removal in writing.
06
Engineering says the spec will take twelve weeks. The CEO wants it in four. Write the message you send to both.
working with engineeringcommsIC2+
Listen for
A short message to each. A specific cut for the four-week version. A named follow-on for the rest. No melodrama.
Ignore
A message that just relays the conflict upward.
catches · PMs who escalate instead of broker.
07
Here is a competitor that shipped the feature you were planning. Write the one-paragraph update to your team.
judgementcommsIC3+
Listen for
A short, calm update. A real read on whether the competitor changes the priority. A decision, not a panic.
Ignore
A pitch to ship faster regardless.
catches · PMs who let the competitor set the roadmap.
08
Read this design critique transcript. Write three questions you would ask the designer and one suggestion you would push back on.
the trade with designIC3+
Listen for
Questions that show they read the critique. A push-back that engages with the trade-off the designer made.
Ignore
Stylistic edits.
catches · PMs who cannot critique design without flattening it.
Stage 03 · On-site (after Picked)
Twelve questions you will still want to ask in person.
Picked screens, scores, and shortlists. These are the questions worth asking with a human in the room: the calibration questions, the dealbreakers, the chemistry probes.
12 questions
01
Where, in product work, do you want to grow most this year?
growthmanager fit
Listen for
A specific gap. A specific plan. A name of someone they would learn from.
Ignore
"I want broader scope." Outcome, not skill.
catches · PMs without a learning agenda.
02
Tell me about a time you disagreed with your VP of product on a roadmap call.
authoritymanager fit
Listen for
A real disagreement. The mechanics of the conversation. What they did about it after.
Ignore
"I trust the VP." A lie or a worse problem.
catches · PMs who cannot hold a position in front of authority.
03
What is the most uncomfortable feedback you have received from an engineer about how you spec?
self-awareness
Listen for
A specific piece of feedback. The change they made. The thing they still get wrong.
Ignore
"Engineers love working with me."
catches · PMs who do not invite criticism from the team they spec for.
04
Walk me through a project you wish had failed faster.
judgement
Listen for
A specific moment they could have called it. What stopped them. What they would now do differently.
Ignore
A pitch for the project being secretly worth doing.
catches · Sunk-cost PMs.
05
Pick two PMs you admire. What do they do that you do not?
taste
Listen for
Concrete habits. Habits they have adopted. Habits they have not yet.
Ignore
Pure praise.
catches · PMs without taste for other PMs.
06
Tell me the last essay or talk about product that changed how you work.
curiosity
Listen for
A specific essay or talk. The change they made the week after.
Ignore
A book they have always meant to read.
catches · PMs who do not study the craft.
07
When are you most productive?
operating model
Listen for
A specific time of day, a specific environment. A self-aware answer about energy.
Ignore
"I am always on."
catches · PMs without self-instrumentation.
08
Where would you rather be in three years? Title or shape of role.
careerretention
Listen for
A direction (deeper IC PM vs group PM vs founder) and a reason. Honesty about uncertainty.
Ignore
"Wherever the company needs me." Suspicious.
catches · Drifting PMs.
09
If you join, what would you want to spend your first week doing?
agencyonboarding
Listen for
A specific plan. Often: shadow on a support shift, read the last six retros, sit with two customers, ship a one-page memo.
Ignore
"Whatever you suggest."
catches · PMs without an onboarding instinct.
10
What is the thing that would make you leave us within six months?
dealbreaker
Listen for
A specific irritant. A specific manager pattern. A specific operating condition.
Ignore
"As long as the work is interesting."
catches · Hidden dealbreakers, surfaced post-offer.
11
What would you want to ask our most cynical engineer?
probingcuriosity
Listen for
A real question about a quiet tension. "What is the spec you most regret implementing?"
Ignore
A softball.
catches · PMs who do not want to know what is wrong.
12
Tell me the part of the product you would not want to own. Why?
scopecandour
Listen for
A specific area. An honest reason. A boundary they have learned to draw.
Ignore
"I am happy to own anything." Worrying.
catches · PMs who do not know their own constraints.
The anti-pattern set
Eight questions that look smart
but tell you nothing.
"What is your biggest weakness?"
You will get a strength-shaped weakness. We have asked this 47,000 times. It catches no-one. Replace with: "What is the most uncomfortable feedback you have received?".
"Where do you see yourself in five years?"
Either a rehearsed answer or a stalled one. Both useless. Replace with: "Where would you want to be in three years?"
"Tell me about yourself."
Wastes the first three minutes on the CV they already gave you. Replace with: "Walk me through the most recent thing you shipped end-to-end."
"Why this company?"
Generates polished mission-talk. Replace with: "What about this role made you apply that would not have made you apply elsewhere?"
"Are you a team player?"
No-one says no. Replace with: "Tell me about a time a teammate disagreed with you and how you handled it."
"How do you handle stress?"
No-one says badly. Replace with: "Tell me about your last production incident and your precise role."
"How would you reverse a linked list?"
Probes nothing we care about. We removed it from the bank in 2019. Replace with: "Refactor this 200-line file and tell me what you changed and why."
"If you were an animal, which animal would you be?"
You know what we are going to say. Replace with: anything else.
Or, let us ask
We will ask these for you.
By Friday.
Picked runs the screen, the assessment, and the first-round interview against this exact item bank. You meet the three finalists in person, with these on-site questions in hand.
$0.99 per AI-vetted candidate. First 50 free.
Companion pages
picked.
The AI-native replacement for inbound hiring. For the hiring manager, not HR.
© 2026 Picked · Made in London · Three finalists in forty-eight hours.
Product manager interview questions · Picked.ai