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 }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

An interview plan is useful only when it gives each conversation a fair chance to produce comparable evidence. Without structure, one session can drift into a relaxed story while another becomes a high-pressure test. The notes may look rich afterward, but the team is left comparing different questions, different follow-ups, and different standards.

Structured interviewing solves part of that problem by deciding the lead questions, evidence areas, follow-up style, and scoring anchors before people enter the room. The structure does not make every answer predictable. It gives the interviewer a stable path for asking, listening, probing, and scoring so that later review is based on what was actually heard.

The context still matters. A hiring interview needs job-related questions and consistent scoring. A customer research interview needs recent behavior, workflow detail, and neutral prompts. A stakeholder discovery interview needs decision context, constraints, dependencies, and agreement checks. Treating those sessions as the same generic question list usually produces weaker evidence.

Interview guide purposes and common evidence risks
Session type	Useful evidence	Common mistake
Hiring	Past behavior, job-relevant scenarios, role evidence, and comparable scoring notes.	Asking questions that drift away from documented job requirements.
Customer research	Recent actions, workflow steps, pain points, workarounds, and decision criteria.	Asking leading questions that invite agreement with a preferred idea.
Stakeholder discovery	Success criteria, constraints, dependencies, tradeoffs, and decision authority.	Collecting preferences without checking who can actually decide.

Good interview planning balances consistency with judgment. Comparable sessions should use the same lead prompts and scoring standard, especially in hiring. Follow-up probes still matter because people rarely give complete evidence on the first answer. The interviewer should be able to ask for a metric, artifact, timeline, owner, or consequence without changing the standard being applied to everyone else.

Context, questions, rubric anchors, and risk checks flow into a structured interview guide.

Rubrics work best when their anchors describe observable evidence instead of interviewer impressions. A low anchor can name vague claims or missing ownership, a middle anchor can require a relevant example with a credible result, and a high anchor can require repeatable judgment, limits, and adaptation to the role or context. That makes the debrief less dependent on confidence, recency, or a polished speaking style.

A guide is still only a plan. Hiring questions need a documented job-related basis and should avoid protected, medical, family, or other non-role topics. Research and discovery questions should leave room for the participant's own words, avoid harm, and avoid steering people toward the answer the team hopes to hear.

How to Use This Tool:

Start with the decision the conversation needs to support, then review the draft like an interviewer preparing for a live session.

Choose Interview purpose. Hiring, customer research, and stakeholder discovery use different question families, evidence cues, and guardrails.
Enter a specific Role or audience and select the closest Level or relationship. A concrete title, participant segment, or decision-maker group gives the draft clearer wording.
Paste a Role or research brief with priorities, constraints, success criteria, and real situations to probe. If the brief warning appears, add context before relying on the questions.
List Focus areas one per line. These become question coverage areas and rubric rows, so remove anything that is not part of the role, research plan, or decision.
Set Question count and Interview length. A pacing warning means each question has less than 2.5 minutes on average, which can leave follow-ups shallow.
Open Advanced when the session needs a different Question mix, lighter or deeper Follow-up depth, a named Interview round, or documented priority weighting for the first focus area.
Check Interview Guide Draft, Question Bank Ledger, Scoring Rubric Anchors, Risk Signal Briefing, and Interview Mix Map. The guide is ready to copy or export only when the warnings and evidence checks make sense for the session.

Interpreting Results:

The summary gives a fast shape check: role or audience, purpose, question count, duration, and retained focus areas. The badges show the round, dominant question type, weighting mode, and risk-signal count. Use those cues to catch mismatches before the guide reaches an interviewer.

How to interpret interview guide outputs
Output	What to trust	What to verify
Interview Guide Draft	A session-ready draft with purpose, round, level, duration, questions, anchors, and risk signals.	Check that the wording fits the audience and avoids sensitive, leading, or off-topic prompts.
Question Bank Ledger	Each row shows the lead question, follow-up, listen-for cue, focus area, type, and time label.	Confirm that each lead question can produce evidence the interviewer can actually judge.
Scoring Rubric Anchors	Each retained focus area gets a weight plus 1, 3, and 5 evidence anchors.	Make sure low, proficient, and exceptional evidence can be observed during the session.
Risk Signal Briefing	Common weak-evidence patterns with probing guidance and interviewer guardrails.	Apply the same follow-up standard across comparable candidates or participants.
Interview Mix Map	A count of question types, with the chart focused on the number of questions per type.	Check whether the mix fits the round. A screen usually needs fewer deep probes than a final decision.

A polished guide can still create false confidence. Weak focus areas, vague anchors, and undocumented priority weighting can make a poor process look consistent. Review the guide with the role owner, research lead, or decision owner before the first live session.

Technical Details:

Structured interviews control two sources of variation: what is asked and how answers are judged. Lead questions set the common evidence opportunity. Follow-up probes clarify incomplete answers without changing that opportunity. Scoring anchors describe evidence thresholds for each focus area, so the debrief can compare substance instead of memory, confidence, or speaking style.

Purpose changes the question library. Hiring prompts emphasize behavioral examples, situational judgment, role evidence, collaboration, motivation, tradeoffs, reference-style reflection, and closeout checks. Customer research prompts emphasize context, workflow, pain points, decision criteria, evidence, scenarios, workarounds, and closeout gaps. Stakeholder discovery prompts emphasize outcomes, constraints, tradeoffs, dependencies, decision process, evidence, scenario resilience, context, and closeout risk.

Formula Core:

Rubric weights come from the retained focus areas. Equal weighting divides 100 percent across all retained areas. Priority weighting assigns 30 percent to the first retained area and divides the remaining 70 percent across the rest.

w_{i} = \frac{100}{n}

w_{1} = 30 %, w_{i} = \frac{70}{n - 1} % for i > 1

Here n is the number of retained focus areas and w is the displayed rubric weight. With five focus areas and equal weights, each area receives 20 percent. With priority weighting and five focus areas, the first receives 30 percent and each remaining area receives 17.5 percent before the label rounds to 18 percent.

Rule Core:

Interview guide rules and validation bounds
Rule area	Applied rule	Why it matters
Question count	Accepted count is bounded from 4 to 24 questions.	Prevents guides that are too thin to cover focus areas or too long to review.
Interview length	Duration is bounded from 15 to 120 minutes and rounded to a 5-minute interval.	Keeps pacing labels realistic for a live session.
Focus areas	Repeated entries are removed, then role-context hints and purpose defaults can fill gaps.	Prevents empty guides while still requiring human review of inferred coverage.
Pacing warning	A warning appears when duration divided by question count is less than 2.5 minutes.	Signals that follow-ups may be too shallow for useful evidence.
Brief warning	A warning appears when the brief is shorter than 40 characters.	Flags a guide that is likely to rely on generic role or purpose defaults.
Priority weighting	A warning appears when the first focus area receives priority weighting.	Prompts documentation before scores are compared across people or sessions.

Time labels reserve opening and closeout time before distributing minutes across questions. Sessions of 30 minutes or more reserve more setup and closeout time than shorter sessions. Treat the labels as planning guidance, not as a guarantee that every answer will fit the assigned minutes.

Limitations and Privacy Notes:

The guide is assembled from the settings and text in the browser; it does not validate the legal, research, or organizational quality of the interview plan. Treat role briefs, candidate context, customer notes, and stakeholder background as sensitive working material.

For hiring, document the job-related basis for focus areas, lead questions, and any non-equal weighting before comparing candidates.
For research, pilot the guide with one or two sessions to catch leading questions, missing consent language, or unclear probes.
For stakeholder discovery, confirm that the guide covers the actual decision owner, constraints, dependencies, and success evidence.
Copied text, downloaded files, and exported documents may contain the brief, so remove protected or confidential details before sharing them.

Worked Examples:

Hiring a senior customer success manager

A hiring team enters Senior customer success manager, selects Senior or power user, keeps Deep dive, sets 12 questions for 45 minutes, and lists focus areas such as renewal risk discovery, escalation judgment, and executive communication. Question Bank Ledger should include behavioral and role-evidence prompts, while Scoring Rubric Anchors should separate generic customer claims from measurable renewal or escalation outcomes.

Customer research for a reporting workflow

A product researcher chooses Customer research interview, enters an operations manager audience, and lists current workflow, reporting handoffs, export pain, and success measures. The useful check is whether Question Bank Ledger asks for recent behavior, artifacts, and workarounds instead of opinions about a hypothetical feature.

Priority weighting with five focus areas

If Priority first focus area is selected with five retained focus areas, Scoring Rubric Anchors gives the first area 30 percent and the remaining areas 17.5 percent before rounded labels display 18 percent. The warning is a cue to document why that first area deserves extra weight.

Troubleshooting a thin brief

When the brief is only "sales role" or "new dashboard research," the warning asks for more context. Add the decision background, must-have evidence, and real situations to probe, then recheck Interview Guide Draft for more specific questions and Risk Signal Briefing for relevant guardrails.

FAQ:

Can this replace job analysis for hiring?

No. The guide can draft questions and anchors, but the role owner still needs documented competencies, selection criteria, and a consistent scoring process.

Why did extra focus areas appear?

The guide can supplement your list with role-context hints and purpose defaults so the output is not empty. Remove any focus area that does not fit the session.

What should I do when pacing is tight?

Reduce Question count or increase Interview length. Tight pacing makes follow-ups shallow and weakens the evidence behind Scoring Rubric Anchors.

Should every interviewer use the same questions?

Comparable sessions should use the same lead questions and scoring anchors. Follow-ups can clarify answers, but they should not change the evidence standard.

Is the brief sent to a writing service?

No. The guide is assembled in the browser from the settings and text you enter. Review copied or downloaded outputs before sharing because they may include the brief.

Glossary:

Structured interview: An interview format that uses planned lead questions and consistent scoring criteria across comparable sessions.
Lead question: The main question asked to each comparable candidate, participant, or stakeholder.
Follow-up probe: A clarifying question used to request detail, evidence, context, or consequences without changing the lead question.
Focus area: The competency, behavior, topic, or decision criterion the guide is meant to cover.
Scoring anchor: A description of what low, proficient, or exceptional evidence looks like for a focus area.
Risk signal: A warning pattern such as generic evidence, unclear ownership, no tradeoff awareness, or leading-question drift.
Leading question: A question that nudges the participant toward a desired answer instead of leaving room for their own account.

References:

Structured Interviews, U.S. Office of Personnel Management.
How do I score a structured interview?, U.S. Office of Personnel Management.
Employment Tests and Selection Procedures, U.S. Equal Employment Opportunity Commission.
Step 4: Do your research, Digital.gov.
Build consensus to understand user needs, Digital.gov.