Questions to Ask
When To Use
"Do you have any questions for us?" and you ask about the culture. You get five minutes with each interviewer, and those minutes are your only chance to learn what the ad and the website leave out. It answers: what do I ask this person, in this role, that only they can tell me, and that helps me decide?
When Not To Use
For a conversation with an insider before you apply, where the aim is to learn, use Informational Interview Questions. If you know nothing yet about the people on the loop, run Interviewer Research Notes first; it supplies the facts, this writes the questions.
Inputs
- The interviewers by role, from your Interview Loop Map or the calendar invite
- Your Company Research Brief, the job ad, and anything already said to you earlier in the loop
- Your own criteria and deal-breakers from your Target Role Brief
If you have none of this, I start from the job ad and the interviewers' job titles and mark the output as a first draft.
Approach
Two rules from the University of Cambridge Careers Service page Networking: the website test (never ask what public information already answers) and questions by seniority (what you ask depends on who you ask). The judgment is that for an experienced candidate the questions work in both directions: the panel hears how you think about the job, and you collect what you need to weigh the role against your own criteria. The failure it prevents is asking a senior leader about the tech stack and a future peer about the five year vision, then leaving with nothing you can use.
Workflow
- Ask at most three questions: who is in each round and in what role, what you most need to find out before you could say yes, and what has already been said to you in the loop.
- Draft across four themes. The work: the problem this role owns and what is hardest now. The team: who you would work with and how product, design and engineering split decisions. How decisions get made: who decides the roadmap, what happens in a disagreement, how a project gets stopped. Success: what a good first year looks like and how anyone would know.
- Sort by interviewer role. A recruiter gets process, timeline and what AI use is allowed at each stage. The hiring manager gets expectations, scope and how they work with their reports. A peer in product or design gets day-to-day reality. An engineering or data counterpart gets how they like to work with this role. A senior leader gets direction and what would change their mind. Pay and contract questions go to the recruiter, never to a peer.
- Run the website test: drop every question the company's site, the ad or your research brief already answers, and name the source that answered it. A dropped question can come back only as a follow-up on something that source leaves open.
- Tighten what is left: open questions only, short enough to say in one breath, each built on something specific, such as a sourced fact or a remark from an earlier round. "What is the culture like" becomes a question about one real decision.
- Per interviewer, mark three to ask first and one to drop if time is short. Beside each question, note which of your own criteria its answer informs. A question that informs none, and shows nothing about how you think, goes.
Output Format
# Questions to Ask Interviewers
**Process:** [role title] · **Loop dates:** [dates] · **Criteria the answers must inform:** [from your Target Role Brief]
## [Interviewer role, e.g. hiring manager] · [round] · [date]
| Order | Question | Theme | Built on | Informs which criterion |
|---|---|---|---|---|
| Ask first (three rows) | [question] | [work / team / decisions / success] | [sourced fact or earlier remark] | [criterion] |
| If time | [question] | [theme] | [fact] | [criterion] |
| Drop if short | [question] | [theme] | [fact] | [criterion] |
## For the recruiter
- [Process, timeline, AI use allowed at each stage, pay and contract questions]
## Removed by the website test
| Question | Already answered by | Date read |
|---|---|---|
| [question] | [page, ad or brief section] | [date] |
## Still unknown after the loop
- [What no answer has covered yet, and who could tell you]
## Decision
You decide which three questions each interviewer gets, and which answers would change your mind about the role, by [date, before the first round].
Done When
- Every interviewer on the loop has a set, with three marked to ask first and one to drop.
- No remaining question is answered by the site, the ad or your research brief.
- Every question is open, fits in one breath, and names the fact or remark it is built on.
- Every question points to one of your criteria or is cut.
Quality Bar
- A question built to flatter an interviewer from research is removed; so is anything about their private life, pay or views.
- No leading questions: you are asking to find out, not to be agreed with.
- Listen first on the day. If an answer arrives before you ask, skip the question instead of reading it out.
- Five good questions per person is the ceiling; the three marked first are the ones that matter.
- Claude suggests questions from public facts and your criteria; you choose them and ask them yourself.
Next
Run pmjob-mock-interview (Mock Interview) to say it all out loud.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: pmjob-questions-to-ask3description: Writes your Questions to Ask Interviewers, a set for each interviewer by role across the work, the team, how decisions get made and what a good first year looks like, with anything the website already answers removed and three marked to ask first. Use for "run pmjob-questions-to-ask", "questions to ask at the end of an interview", "do you have any questions for us", "what should I ask the hiring manager", "questions for a product interview panel", "smart questions for the final round", "what to ask the recruiter", part of the Claude Guide for Product Interviews Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/pmjob-questions-to-ask6---78# Questions to Ask910## When To Use11"Do you have any questions for us?" and you ask about the culture. You get five minutes with each interviewer, and those minutes are your only chance to learn what the ad and the website leave out. It answers: what do I ask this person, in this role, that only they can tell me, and that helps me decide?1213## When Not To Use14For a conversation with an insider before you apply, where the aim is to learn, use Informational Interview Questions. If you know nothing yet about the people on the loop, run Interviewer Research Notes first; it supplies the facts, this writes the questions.1516## Inputs17- The interviewers by role, from your Interview Loop Map or the calendar invite18- Your Company Research Brief, the job ad, and anything already said to you earlier in the loop19- Your own criteria and deal-breakers from your Target Role Brief20If you have none of this, I start from the job ad and the interviewers' job titles and mark the output as a first draft.2122## Approach23Two rules from the University of Cambridge Careers Service page Networking: the website test (never ask what public information already answers) and questions by seniority (what you ask depends on who you ask). The judgment is that for an experienced candidate the questions work in both directions: the panel hears how you think about the job, and you collect what you need to weigh the role against your own criteria. The failure it prevents is asking a senior leader about the tech stack and a future peer about the five year vision, then leaving with nothing you can use.2425## Workflow261. Ask at most three questions: who is in each round and in what role, what you most need to find out before you could say yes, and what has already been said to you in the loop.272. Draft across four themes. The work: the problem this role owns and what is hardest now. The team: who you would work with and how product, design and engineering split decisions. How decisions get made: who decides the roadmap, what happens in a disagreement, how a project gets stopped. Success: what a good first year looks like and how anyone would know.283. Sort by interviewer role. A recruiter gets process, timeline and what AI use is allowed at each stage. The hiring manager gets expectations, scope and how they work with their reports. A peer in product or design gets day-to-day reality. An engineering or data counterpart gets how they like to work with this role. A senior leader gets direction and what would change their mind. Pay and contract questions go to the recruiter, never to a peer.294. Run the website test: drop every question the company's site, the ad or your research brief already answers, and name the source that answered it. A dropped question can come back only as a follow-up on something that source leaves open.305. Tighten what is left: open questions only, short enough to say in one breath, each built on something specific, such as a sourced fact or a remark from an earlier round. "What is the culture like" becomes a question about one real decision.316. Per interviewer, mark three to ask first and one to drop if time is short. Beside each question, note which of your own criteria its answer informs. A question that informs none, and shows nothing about how you think, goes.3233## Output Format34```markdown35# Questions to Ask Interviewers36**Process:** [role title] · **Loop dates:** [dates] · **Criteria the answers must inform:** [from your Target Role Brief]37## [Interviewer role, e.g. hiring manager] · [round] · [date]38| Order | Question | Theme | Built on | Informs which criterion |39|---|---|---|---|---|40| Ask first (three rows) | [question] | [work / team / decisions / success] | [sourced fact or earlier remark] | [criterion] |41| If time | [question] | [theme] | [fact] | [criterion] |42| Drop if short | [question] | [theme] | [fact] | [criterion] |43## For the recruiter44- [Process, timeline, AI use allowed at each stage, pay and contract questions]45## Removed by the website test46| Question | Already answered by | Date read |47|---|---|---|48| [question] | [page, ad or brief section] | [date] |49## Still unknown after the loop50- [What no answer has covered yet, and who could tell you]51## Decision52You decide which three questions each interviewer gets, and which answers would change your mind about the role, by [date, before the first round].53```5455## Done When56- Every interviewer on the loop has a set, with three marked to ask first and one to drop.57- No remaining question is answered by the site, the ad or your research brief.58- Every question is open, fits in one breath, and names the fact or remark it is built on.59- Every question points to one of your criteria or is cut.6061## Quality Bar62- A question built to flatter an interviewer from research is removed; so is anything about their private life, pay or views.63- No leading questions: you are asking to find out, not to be agreed with.64- Listen first on the day. If an answer arrives before you ask, skip the question instead of reading it out.65- Five good questions per person is the ceiling; the three marked first are the ones that matter.66- Claude suggests questions from public facts and your criteria; you choose them and ask them yourself.6768## Next69Run pmjob-mock-interview (Mock Interview) to say it all out loud.7071## About the makers7273This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).