Interview Questions Generator

Structured interview guide

Interview purpose:

Hiring, customer research, and stakeholder discovery use different question styles.

Role or audience:

Use a specific title or audience segment, not a broad department.

Level or relationship:

Pick the closest seniority, user maturity, or stakeholder influence level.

Role or research brief:

Include the decision context, must-have evidence, and any real situations the interviewer should probe.

Focus areas:

List competencies, behaviors, research topics, or decision criteria to cover.

Question count:

Use 8 to 12 for a short screen and 12 to 18 for a deeper guide.

questions

Interview length:

Total minutes available for the interview, excluding post-interview debrief.

min

{{ warning }}

Question mix:

Balanced is the default for structured interviews.

Follow-up depth:

Use deep when the interviewer needs stronger evidence checks.

Interview round:

Pick the round closest to how this guide will be used.

Rubric weighting:

Use priority weighting only when the brief documents that one focus area matters most.

{{ guideText }}

#	Type	Focus area	Question	Follow-up	Listen for	Time	Copy
{{ row.number }}	{{ row.type }}	{{ row.focus }}	{{ row.question }}	{{ row.followUp }}	{{ row.listenFor }}	{{ row.timeLabel }}

Focus area	Weight	1 - Low evidence	3 - Proficient	5 - Exceptional	Copy
{{ row.focus }}	{{ row.weightLabel }}	{{ row.low }}	{{ row.proficient }}	{{ row.exceptional }}

Signal	Where to probe	Evidence to ask for	Interviewer guardrail	Copy
{{ row.signal }}	{{ row.probe }}	{{ row.evidence }}	{{ row.guardrail }}

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Structured interview questions turn a loose conversation into a repeatable guide. The goal is to ask planned, job-related, research-related, or decision-related questions, then listen for evidence that can be compared after the session. That matters when several people are interviewing candidates, customers, users, or stakeholders and need a shared record instead of scattered notes.

A good interview guide does not make every session identical. It gives the interviewer a common lead question, a useful follow-up, and a clear cue for what evidence to listen for. Hiring teams use that structure to reduce avoidable bias and compare candidates against role criteria. Product and research teams use it to hear real workflow details instead of steering people toward a preferred answer. Stakeholder teams use it to surface constraints, tradeoffs, dependencies, and decision paths before a plan hardens too early.

Interview questions are easy to overread. A polished guide can still ask about the wrong competency, lead a participant, or miss a local legal or policy rule. The value comes from pairing clear questions with consistent scoring, careful note-taking, and a review step that checks whether each answer actually supports the decision being made.

The safest starting point is concrete evidence. Ask about recent behavior, real decisions, visible constraints, and examples that another person could understand later. Treat speculative answers, rehearsed stories, and confident delivery as cues for follow-up, not as evidence by themselves.

Technical Details:

A structured interview guide has three technical jobs. It defines the topic coverage, gives each interviewer comparable lead questions, and names the evidence standard used after the conversation. In hiring, that evidence standard is usually tied to competencies from the job. In customer research, it is tied to observed workflow, pain, criteria, and validation signals. In stakeholder discovery, it is tied to outcomes, constraints, dependencies, tradeoffs, and decision process.

Question structure affects what can be compared later. Behavioral questions ask for past examples, situational questions ask how someone would handle a realistic condition, and evidence probes ask for artifacts, metrics, decisions, or observed behavior. Follow-up questions should test the same focus area rather than drifting into unrelated personal details or a preferred answer.

Rule Core:

The guide is deterministic from the current fields. Purpose selects the question library, focus areas set the coverage plan, timing sets pacing labels, and advanced settings alter the question type sequence, follow-up pressure, round label, and scoring weights.

Interview guide generation rules
Input or setting	Rule	Result in the guide
`Interview purpose`	Chooses hiring, customer research, or stakeholder discovery.	Changes the opening label, default focus areas, question type names, question wording, and risk guardrails.
`Role or audience` and `Role or research brief`	The role becomes the subject of the guide. The brief adds context and can add role hints such as customer discovery or stakeholder alignment.	Questions and the summary line become more specific to the role, participant group, or decision audience.
`Focus areas`	Entries are split from lines, commas, or semicolons, deduplicated, combined with role hints and purpose defaults, then capped at eight areas.	The question bank cycles through those areas, and the scoring rubric creates one row for each retained focus area.
`Question count`	The count is rounded and bounded from 4 to 24.	`Question Bank Ledger` receives that many numbered rows unless the value is corrected by the bounds.
`Interview length`	The duration is rounded to a 5-minute increment and bounded from 15 to 120 minutes.	Each question receives a pacing label after opening and closeout time are reserved.
`Question mix`	Balanced, evidence-heavy, scenario-heavy, and discovery-heavy modes use different repeating type sequences for the selected purpose.	`Interview Mix Map` shows how many questions fall into each type.
`Follow-up depth`	Light keeps some probes shorter, standard uses the default wording, and deep adds sharper evidence or tradeoff prompts.	The lead question stays tied to the focus area while the follow-up changes the pressure level.
`Rubric weighting`	Equal weights split 100% across focus areas. Priority-first weighting gives the first area 30% when more than one area exists and shares the remaining 70% across the rest.	`Scoring Rubric Anchors` displays the weight and the 1, 3, and 5 evidence anchors for every focus area.

The question rows carry six decision-relevant fields: number, type, focus area, lead question, follow-up, listen-for cue, and time label. The listen-for cue is important because it tells the interviewer what kind of evidence should count. For a hiring guide, that may be ownership, tradeoff reasoning, collaboration, or measurable outcome. For research and discovery, it may be workflow sequence, success measure, constraint, dependency, or decision evidence.

Interview guide validation and review signals
Signal	Condition	Correction
`Question pacing is tight`	Interview minutes divided by question count is below 2.5.	Reduce `Question count`, increase `Interview length`, or use lighter follow-ups.
`Priority weighting should be documented`	`Rubric weighting` is set to `Priority first focus area`.	Record why the first focus area deserves extra weight before comparing interviews.
`Add more role or research context`	The brief is shorter than 40 characters after cleanup.	Add the decision context, must-have evidence, account background, or real situations to probe.
`Protected-topic drift`	The hiring risk table includes a guardrail against protected, family, medical, and other non-role questions.	Redirect to job requirements, documented criteria, work examples, or role-related availability only where appropriate.
`Leading-question drift`	Research and stakeholder guides warn when the interviewer may steer the answer.	Restate the prompt neutrally and ask for a recent example, workflow step, artifact, or decision record.

The output is a drafting aid. It does not conduct job analysis, verify policy compliance, validate a research plan, schedule participants, record consent, score interview answers, or decide which candidate, customer need, or stakeholder request should win.

Everyday Use & Decision Guide:

Start with Interview purpose and Role or audience. Use Hiring interview when the guide must compare candidates against role evidence. Use Customer research interview when the goal is workflow, pain, criteria, and validation detail. Use Stakeholder discovery interview when the session is about outcomes, constraints, dependencies, tradeoffs, and decision process.

Put the real setup in Role or research brief. A short title alone often produces generic questions. A useful brief names the decision context, must-have evidence, and situations worth probing, such as renewals, onboarding handoffs, incident reviews, budget approval, rollout risk, or cross-team dependency.

Use one focus area per line when the interview needs clear coverage, such as Escalation judgment, Renewal risk discovery, or Decision criteria.
Choose 8 to 12 questions for a screen or short research session, and use higher counts only when the interview length can support follow-ups.
Use Evidence heavy when claims need proof, Scenario heavy when judgment under pressure matters, and Discovery heavy when the session should surface unknown context.
Use Deep follow-ups for senior, executive, high-risk, or final-decision sessions where tradeoffs and verification matter.
Keep Equal weights unless the first focus area is explicitly more important and that choice can be documented.

Read the warning alert before using the results. Tight pacing usually means the interviewer will skip follow-ups or accept shallow answers. Priority weighting without a documented reason can make comparisons hard to defend. A thin brief means the question bank may sound polished but still miss the real decision.

Use Interview Guide Draft for the interviewer's running document, Question Bank Ledger for row-level review, Scoring Rubric Anchors for evidence standards, Risk Signal Briefing for guardrails, and Interview Mix Map to check whether the session is dominated by one question type.

Step-by-Step Guide:

Work from interview context to coverage, then review the generated guide before sharing it with interviewers.

Choose Interview purpose. Confirm the summary line changes to hiring, customer research, or stakeholder discovery wording.
Enter Role or audience and choose Level or relationship. These values shape question wording and the level badge in the guide.
Fill Role or research brief with enough context to avoid generic prompts. If the warning alert asks for more context, add real decision background before using the draft.
Add Focus areas as separate lines. Check Scoring Rubric Anchors to confirm each important focus area appears as a rubric row.
Set Question count and Interview length. If the pacing warning appears, reduce the count or increase the minutes before the interview plan is used.
Open Advanced and select Question mix, Follow-up depth, Interview round, and Rubric weighting. Recheck the summary badges after each change.
Review Question Bank Ledger for lead questions, follow-ups, listen-for cues, and time labels. Copy individual rows only after confirming the wording fits the session.
Use Risk Signal Briefing, Interview Mix Map, and JSON for final review before copying the guide text or handing the structured data to another workflow.

Interpreting Results:

The summary strip reports scope, not quality. 12 questions means the current count after bounds are applied. The summary line combines role or audience, interview purpose, duration, and retained focus-area count. The badges show round, dominant question type, weighting mode, and risk-signal count.

How to interpret interview guide result cues
Result cue	Meaning	What to verify
`Interview Guide Draft`	Copy-ready guide text with purpose, round, level, duration, question mix, brief, question bank, scoring anchors, and risk signals.	Read it as an interviewer would and remove any wording that does not match the actual session.
`Question Bank Ledger`	Row-level questions, follow-ups, listen-for cues, and pacing labels.	Confirm every lead question is relevant to the role, participant group, or stakeholder audience.
`Scoring Rubric Anchors`	Focus-area weights plus 1, 3, and 5 evidence anchors.	Check whether the anchors describe observable evidence rather than personality impressions.
`Risk Signal Briefing`	Five common interview failure signals with a probe, evidence request, and guardrail.	Treat the guardrails as review cues, not as a complete legal, research, or policy checklist.
`Interview Mix Map`	Question type counts and minutes grouped for the current mix.	Look for an imbalance that conflicts with the interview purpose, such as too little evidence probing for a final hiring round.

A guide with no warnings can still be weak if the brief is inaccurate or the focus areas are wrong. The best verification step is to read the first three questions aloud, check whether the follow-ups would produce evidence, and confirm that the rubric rows match the decision criteria.

Worked Examples:

Senior customer success hiring round

A hiring manager keeps the default senior customer success context, uses Hiring interview, Senior or power user, Deep dive, Balanced, Standard, 12 questions, and 45 minutes. The guide should show 12 questions, a summary line for a hiring interview, and a dominant type badge such as Behavioral led. Question Bank Ledger should mix behavioral, situational, role evidence, collaboration, and motivation prompts, while Scoring Rubric Anchors gives equal weights across retained focus areas.

Customer research around onboarding drop-off

A researcher chooses Customer research interview, enters trial users who abandoned onboarding, adds focus areas for activation blockers, workaround behavior, decision criteria, and success measures, then sets Discovery heavy with 8 questions in 30 minutes. The useful outputs are the workflow and pain-point questions in Question Bank Ledger, the neutral guardrails in Risk Signal Briefing, and the mix chart showing whether discovery and validation prompts are represented.

Stakeholder discovery with priority weighting

A program lead sets Stakeholder discovery interview, puts budget owner and operations sponsor in Role or audience, and makes Success criteria the first focus area. If Priority first focus area is selected, Scoring Rubric Anchors should give that first area 30% when multiple focus areas exist. The warning alert should remind the user to document the weighting rationale before comparing notes across stakeholders.

Troubleshooting a generic or overpacked guide

If the brief is just TBD, the count is 24, and the duration is 30 minutes, the alert should ask for more context and warn that pacing is tight. Fix the brief first, then reduce the question count or increase the interview length until each question has enough time for a follow-up. After the warning clears, read Interview Guide Draft again rather than trusting the cleaner summary alone.

FAQ:

Why did extra focus areas appear?

The focus list combines your entries with role or brief hints and purpose defaults, removes duplicates, and keeps up to eight areas. That helps fill thin prompts, but you should remove or replace any area that does not fit the real interview.

Can the hiring guide prove an interview is compliant?

No. The hiring risk rows remind interviewers to stay job-related and avoid protected, family, medical, and other non-role questions. Organization policy, local law, recruiter training, and human review still matter.

Why did I get a pacing warning?

The warning appears when interview minutes divided by question count is below 2.5. Reduce Question count, raise Interview length, or use Light follow-ups if the session needs to stay short.

What does priority-first weighting do?

With multiple focus areas, the first retained focus area receives 30% and the rest share 70%. With one focus area, it receives 100%. Use this only when the brief explains why that area matters most.

Does the interview brief get sent to a server?

The guide is created in the page from the entered fields, and the available actions copy or download guide, table, chart, and JSON artifacts rather than submitting the brief through a server request.

Does the mix chart score interview quality?

No. Interview Mix Map counts question types and minutes. It can reveal imbalance, but quality still depends on the brief, focus areas, interviewer discipline, and how answers are scored after the session.

Glossary:

Structured interview: An interview that uses planned questions and common scoring standards so answers can be compared more consistently.
Focus area: A competency, behavior, workflow topic, constraint, or decision criterion that should receive question coverage.
Question mix: The balance of behavioral, situational, evidence, discovery, scenario, or decision-process question types used in the guide.
Follow-up depth: The pressure level of the probe that follows each lead question, from lighter clarification to deeper tradeoff or evidence checks.
Scoring anchor: A description of low, proficient, or exceptional evidence for one focus area.
Risk signal: A warning pattern such as generic evidence, unclear ownership, protected-topic drift, or leading-question drift that should slow interviewer review.

References:

Structured Interviews, U.S. Office of Personnel Management.
How do I score a structured interview?, U.S. Office of Personnel Management.
How do I create structured interview questions?, U.S. Office of Personnel Management.
Enforcement Guidance: Preemployment Disability-Related Questions and Medical Examinations, U.S. Equal Employment Opportunity Commission.
Step 4: Do your research, Digital.gov.
Public Participation Guide: Stakeholder Interviews, U.S. Environmental Protection Agency, January 6, 2026.
Discovery Sprint Guide - Conducting Interviews, U.S. Digital Service.