AI with Michal

AI-generated interview questions

Interview questions created by an AI assistant from a job description, competency framework, or scorecard. When calibrated and reviewed before use, they give interviewers a consistent, role-relevant question set faster than building one from scratch.

Michal Juhas · Last reviewed June 14, 2026

What are AI-generated interview questions?

AI-generated interview questions are structured interview prompts drafted by an AI assistant, typically using a job description, scorecard, or competency framework as input. The output can include opening behavioral questions, follow-up probes, and hypothetical scenarios. The efficiency gain is real: a recruiter can have a draft interview guide in minutes. The risk is also real: without a calibration and review step, the questions are generic at best and legally problematic at worst.

Illustration: a job description and competency card feeding an AI assistant that outputs a structured interview guide with opening question and follow-up probes, passing a human review gate before reaching the interviewer

In practice

  • A recruiter pastes a job description and the three scorecard competencies into a Claude prompt, asking for five behavioral questions per competency with two probing follow-ups each. The output becomes the base interview guide, reviewed by HR before being loaded into the ATS.
  • A TA ops lead maintains a shared Notion library of approved AI-generated question cards, organized by competency. Each card shows the question, the expected answer signals, and a "do not ask" list of adjacent topics that could introduce bias.
  • An interviewer who has never hired a product manager before uses an AI-generated question set calibrated to the role. Post-debrief, two questions produced no useful signal; the team logs that and updates the prompt for the next round.

Quick read, then how hiring teams use it

This is for recruiters, hiring managers, and TA ops leads who design structured interviews. Skim the first section to understand what AI can and cannot do here. Use the second when you are building a question library or calibrating prompts for a new role family.

Plain-language summary

  • What it means for you: You can draft a structured interview guide in minutes instead of hours. The time you save belongs in calibration, not in hoping generic questions surface the right signal.
  • How you would use it: Write a specific prompt that names the competency, the level, and one or two context clues about the role. Review the output against your scorecard before sending to interviewers.
  • How to get started: Pick the next role where you need an interview guide. Pull the relevant competency from your scorecard. Feed that competency plus the JD into a prompt and ask for five behavioral questions with follow-ups. Review the output for legal risk and relevance.
  • When it is a good time: When you are building a new role family template, when a hiring manager complains that interviews feel inconsistent, and when your debrief notes show that different interviewers asked completely different things.

When you are running live reqs and tools

  • What it means for you: At scale, inconsistent interviews are a legal and quality risk. AI-generated question sets, reviewed and approved, give every interviewer the same structured starting point regardless of how often they hire.
  • When it is a good time: When you have a scorecard and a calibration session already in place. AI question generation accelerates those workflows; it does not replace them.
  • How to use it: Wire the question generation step into your intake workflow (see intake to JD AI for the parallel JD workflow). Store approved outputs in your agent knowledge base or ATS-linked doc. Log debrief signal quality to improve prompts over time.
  • How to get started: Pick your two highest-volume role families. Generate a question bank for each using a specific competency prompt. Run both through HR review. Load them into the tool interviewers use to prep. Collect signal-quality feedback from the first five debriefs.
  • What to watch for: Interview guides that no one actually uses. If interviewers bypass the approved questions, find out why before generating more content. Usually the guide is too long, too formal, or not accessible from where the prep conversation happens.

Where we talk about this

On AI with Michal sessions, AI-generated interview questions come up in the AI in recruiting track as part of the full intake-to-debrief workflow. We build question sets live from real scorecards and debrief which prompts produced more useful output. Start at the workshops page and bring a role where you know the debrief quality has been inconsistent.

Around the web (opinions and rabbit holes)

Third-party creators move fast. Treat these as starting points, not endorsements, and double-check anything before using it with candidates.

YouTube

Reddit

Quora

AI-generated versus manually crafted questions

FactorAI-generatedManually crafted
SpeedMinutesHours
ConsistencyHigh if prompt is specificVariable
Legal review neededYes, alwaysYes, but often skipped
Signal qualityDepends on prompt calibrationDepends on interviewer expertise
ScalabilityHighLow without templates

Related on this site

Frequently asked questions

What makes an AI-generated interview question legally safe?
Safety comes from what the model is asked to produce, not from the model itself. Input the job description, the competency being assessed, and explicit instructions to avoid protected characteristics (age, family status, religion, disability, national origin). Review every generated question against your jurisdiction's employment law before use. In the EU, the AI Act classifies hiring AI as high-risk; human review is not optional. In the US, EEOC guidance requires questions to be job-related and consistent across candidates. Add the generated questions to a review queue with a named HR or legal sign-off before they go to an interviewer. See explainable AI hiring for the audit trail approach.
How do you calibrate AI-generated questions to the actual role?
Start with a specific input: the job description, two or three "this hire would succeed at" examples from the hiring manager, and the competency your scorecard names for this interview stage. Vague prompts produce generic questions. A prompt like "generate five behavioral questions for a senior sourcer, focusing on how they handle high-volume outreach and ATS data hygiene" produces more useful output than "generate interview questions for a recruiter." After the first generation, test the questions in a debrief review to see which produced useful signal. Calibrate the prompt, not just the individual question.
Can AI generate follow-up probes, not just opening questions?
Yes, and this is where the format becomes most useful. Prompt the model to produce the opening behavioral question, two or three probing follow-ups (digging into what the candidate did versus what the team did, what went wrong, what they would do differently), and one hypothetical to stress-test the answer. Package these as an interview guide card rather than a flat list. Interviewers rarely remember to probe; a structured card makes follow-up automatic. Teams using this format report that answers become more specific and comparisons across candidates become more defensible when the panel debriefs. See panel debrief alignment for the debrief workflow.
What are the main failure modes of AI-generated interview question banks?
Three common problems: generic questions that any candidate can answer with a scripted story, legally risky phrasing that survived because no reviewer checked the output, and questions that drift from the competency being assessed because the model optimizes for question sound rather than signal quality. The fix is a three-step check: confirm each question maps to a named competency in your scorecard, ask HR to flag any phrase that touches protected characteristics, and pilot the questions in a real debrief before adding them to the library. Log which questions produced the strongest signal; retire the ones that do not.
Where should the generated question set live once approved?
Store approved questions in a shared tool your interviewers can access from the interview invite or the ATS: a Notion page, a Confluence doc, or an agent knowledge base linked from your ATS record. Organize by role family and competency, not by interview round, so questions can be reused across roles that share a competency. Version-control the library so you know when a question was added, by whom, and when it was last reviewed. Connect it to your calibration session workflow so the question set feeds the pre-brief conversation rather than landing cold in an interviewer's calendar invite.
Where can teams practice AI question generation safely?
The AI in recruiting workshop at AI with Michal includes a live exercise where attendees prompt an AI assistant to build a structured interview guide for a role they own, then debrief as a group on which questions would produce signal versus noise. The Starting with AI: the foundations in recruiting course covers prompt construction for interview tasks. Bring your actual scorecard to the session; questions calibrated against a real scorecard produce usable output in the first round. Practice with peers means the mistakes land in a workshop, not in a candidate conversation. Join membership for office hours where you can get feedback on a question set you built.

← Back to AI glossary in practice