How to Prepare for an Interview When You Don't Know the Questions
11 min read
You can't know the exact questions, but you can forecast most of the territory. The Forecast → Story Bank → Recovery method, with a line-by-line JD decode.
You cannot know the exact interview questions in advance, but you can predict most of the territory they will come from, because interviewers build questions from three inputs you already have: the job description, your resume, and their own role. The Forecast → Story Bank → Recovery method from Interview Drills turns those inputs into a question forecast, six to eight reusable stories that cover it, and practiced recovery moves for whatever is left.
Is there any way to prepare when you have no idea what they'll ask?
Yes — because interview questions feel unpredictable, but they are not random: interviewers construct them from the job description, your resume, and their own role in the process, which makes the large majority of the question territory forecastable even though the exact wording is not.
Most advice for this situation splits into two unhelpful halves. One half is the generic prep checklist — research the company, rehearse common questions, print your resume — which never engages with the actual worry: I can't know what they'll ask. The other half is damage control — what to say once you're already stumped. Neither teaches the thing that actually solves the problem: prediction.
The reframe that changes your prep: stop preparing answers to questions, and start preparing the territories that generate questions. An interviewer asking "tell me about a time you missed a deadline" and one asking "describe a project that went sideways" are drawing from the same territory — how you handle failure — and one prepared story covers both. Interviewers ask unexpected questions to watch you think, not to hear a memorized right answer, so preparing territories plus a retrieval habit beats preparing scripts every time.
Territories also shift as hiring shifts, and the newest one blindsides more candidates than any other right now: how you use AI in your work, asked conversationally in roles that have nothing to do with AI. It's forecastable the same way — one prepared 90-second story covers every version of it — and it has its own preparation guide.
The method in this guide has three steps, in order:
- Forecast — decode the job description, your resume, and the interviewer lineup into likely question territories.
- Story Bank — build six to eight stories that cover those territories many-to-one.
- Recovery — script and rehearse five moves for the minority of questions your forecast misses.
How do interviewers decide what questions to ask?
Nearly every interview question traces to one of three sources — the job description, your resume, or the interviewer's own role — and that is the entire basis of the Three-Input Forecast.
Input 1: the job description
Competency and situational questions come from requirement lines. "Manage competing priorities" becomes a too-much-to-do question. A named tool becomes "walk me through how you've used it." Most interviewers do not write questions from scratch; they skim the posting shortly before the call and turn its strongest lines into prompts. Whether or not your interviewer prepares a formal question document, the job description is the document they prepare from — which means you can prepare from it too. (The hiring-manager behavior described here is a practitioner-level generalization, not survey data; treat it as a working model, and notice how well it predicts the questions you actually get.)
Input 2: your resume
Walk-me-through and defend-this questions come from your own claims. Every bullet you wrote is a question invitation ("you say you cut onboarding time — how?"), and every anomaly — a gap, a five-month stint, a pivot between industries — is a near-certain question. If a line on your resume makes you slightly nervous, forecast it.
Input 3: the interviewer's role
The same job produces different questions depending on who is asking. A recruiter screens for basics, logistics, and salary alignment. A hiring manager probes whether you can do the specific job on the posting. A panel divides competencies among its members. This input is powerful enough that it gets its own section below.
How do you turn a job description into a question forecast?
Read the job description line by line and translate each requirement into the question category it predictably generates — this JD Decode is the single highest-leverage hour of interview prep, because it converts "I have no idea what they'll ask" into a short written forecast.
Here is a full decode of a composite job-description excerpt. This is an illustrative example — a composite JD, not a real posting — but every decode pattern in it transfers directly.
| JD line (illustrative composite) | Question territory | Example question it spawns | Story that covers it |
|---|---|---|---|
| "Manage competing priorities across multiple concurrent projects" | Prioritization under pressure | "Tell me about a time you had too much to do and not enough time." | The two-deadline week |
| "Partner with cross-functional stakeholders in engineering, marketing, and finance" | Conflict and alignment | "Describe a time you disagreed with someone from another team." | The stakeholder who said no |
| "Comfortable in a fast-paced environment where priorities shift" | Ambiguity and adaptability | "Tell me about a time the goal changed halfway through." | The relaunched launch |
| "3+ years with reporting tools such as Tableau" | Skill verification | "Walk me through how you've actually used Tableau." | Direct experience — not a story, a demo |
| "Strong written and verbal communication skills" | Communication and influence | "Tell me about explaining something complex to a non-expert." | The report nobody read — plus every answer you give is itself the test |
| "Reports to the VP of Operations in a newly created role" | Self-direction in ambiguity | "There's no playbook for this role — how would you structure your first 90 days?" | The process I built from nothing |
The last line is the kind of decode most candidates miss: "newly created role" is not filler — it predicts questions about defining your own success criteria without a template, because the hiring manager is worried about exactly that.
Then run the same decode on your resume's three riskiest lines. This is the defend-this forecast:
| Resume line (illustrative) | Question it predictably generates | The prepared frame |
|---|---|---|
| A ten-month employment gap | "What were you doing between March and January?" | One calm sentence of fact, one sentence of what you did with the time, then forward — never an apology spiral |
| A five-month stint | "Why did you leave so quickly?" | The honest structural reason (reorg, role-as-described mismatch) stated without blame, plus what you verified about this role to avoid a repeat |
| A pivot between industries | "Why the change — and why should we bet on it?" | The through-line skill that transfers, with one concrete result from each side of the pivot |
This decode is the manual version of something Interview Drills automates: on its Interview Accelerator and Interview Pro plans, you save target roles and get a match analysis per role — strengths, gaps, and talking points — which is the Forecast step run against your actual resume and posting.
How many stories do I need? "I can't prep 100 answers"
Six to eight well-chosen stories, each mapped against the core competencies interviewers probe — leadership, conflict, failure, ambiguity, results, initiative — cover the large majority of behavioral questions, because interviewers ask about competencies, not scripts, and one strong story answers many differently worded questions.
This is the Story Matrix: your stories as rows, the six competencies as columns, and a mark wherever a story can credibly carry that territory. Here is what a filled-in matrix looks like — story titles are illustrative placeholders; yours come from your own work history:
| Story | Leadership | Conflict | Failure | Ambiguity | Results | Initiative |
|---|---|---|---|---|---|---|
| The relaunched launch | ✓ | ✓ | ✓ | ✓ | ||
| The stakeholder who said no | ✓ | ✓ | ✓ | |||
| The two-deadline week | ✓ | ✓ | ||||
| The process I built from nothing | ✓ | ✓ | ✓ | |||
| The mistake in the report | ✓ | ✓ | ||||
| The teammate I unblocked | ✓ | ✓ | ✓ |
Read it horizontally and you see why this beats question-by-question prep: "The relaunched launch" alone covers a leadership question, a failure question, an ambiguity question, and a results question — four territories, one story. Read it vertically and the gaps jump out: if no row covers Conflict, that is your prep priority, not another rehearsal of your strengths answer.
Build each story as bullet-point beats, never a memorized script. Upvoted Reddit advice on this is blunt: memorized answers make you sound like "a stilted robot," and a 210-upvote advice post on r/interviews — the highest-scoring advice post in our research pass — recommends the lighter CAR structure over full STAR precisely because "when your brain scrambles, your mouth rambles." (How long the spoken version should run is its own question — see our guide to how long interview answers should be.) Here is one matrix row worked in CAR — beats first, spoken version beside it (illustrative):
Beats (what you actually memorize):
- Context: Q3 launch, two weeks out, main integration partner pulled support
- Action: killed two features, renegotiated scope with sales myself, daily 15-minute standup
- Result: shipped 9 days late instead of a quarter late; partner signed for v2
Spoken version (what the beats become out loud):
"Two weeks before a Q3 launch, our main integration partner pulled their support, which broke about a third of the release. Instead of slipping a quarter, I cut the two features that depended on them, renegotiated the scope directly with our sales lead, and ran a daily 15-minute standup until we shipped. We landed nine days late instead of ninety, and the partner came back and signed on for the next version."
The connective tissue is improvised fresh each time — that is what keeps it conversational. Only the beats are fixed. If you want scaffolding for drafting the beats, the free STAR Method Builder on this site structures a story in a few minutes.
Choosing which six to eight stories, and mining a thin-feeling work history for them, is its own method — a full story-bank guide is planned for this site as a dedicated deep dive.
Does prep change depending on who's interviewing you?
Yes — the same job description produces different questions at each stage, so forecast per interviewer: recruiter screens forecast to logistics, motivation, and salary; hiring-manager rounds forecast to the JD's top requirement lines plus your resume's riskiest line; panels forecast to collaboration, conflict, and values questions divided among the interviewers.
| Stage | What this interviewer owns | Likely territories | Which stories to load |
|---|---|---|---|
| Recruiter screen | Basic fit, logistics, not wasting the manager's time | Tell me about yourself, why this role, timeline, salary expectations | None — this round runs on your intro narrative and clean logistics answers |
| Hiring manager | "Can this person do this job?" | The JD's top three requirement lines, plus your riskiest resume line | Your 2–3 strongest results and ambiguity stories, mapped to those exact JD lines |
| Panel | Collaboration and team fit, split among members | Conflict, communication, values, working style — often one competency per panelist | Conflict and teammate stories; expect the same territory probed twice in different words |
| Skip-level / executive | Judgment, trajectory, self-awareness | Why this company, biggest failure, where you're heading | Your failure story with the sharpest lesson, plus a genuinely curious question back |
One certainty worth stating plainly: "tell me about yourself" appears at nearly every stage, which makes it the single most forecastable question in any interview. It deserves rehearsed-out-loud treatment, not just notes — you can run a free scored practice rep of it on this site's Tell Me About Yourself drill.
What do you do when you can't answer an interview question?
When a question lands outside your forecast, you have five recovery moves — buy time, think aloud, clarify, bridge to an adjacent strength, or honestly defer — and each one has a specific failure mode, which is the part most advice leaves out.
| Move | Script (say it in your own words) | When it works | When it backfires |
|---|---|---|---|
| Buy time | "That's worth a real answer — give me a second to pick the right example." | Any question, once or twice per interview; the pause reads as thoughtfulness | Used on every question, it stops reading as thoughtfulness and starts reading as unprepared |
| Think aloud | "Let me reason through this out loud. The first thing I'd want to know is..." | Judgment and how-would-you questions — the reasoning is the answer | Knowledge questions. Narrating your way toward a fact you don't have just extends the miss in public |
| Clarify | "When you say 'difficult stakeholder,' do you mean resistant to the work, or a communication mismatch?" | Broad or genuinely ambiguous questions; it also buys structured thinking time | When the question was already specific — then it reads as a stall, and you still owe the answer |
| Bridge | "I haven't faced that exact situation. The closest I've come is X — here's what I did and what transfers." | Experience questions just outside your history | If you skip the acknowledgment and jump straight to X, it reads as evasive — name the gap first, then bridge |
| Honest deferral | "I don't know that one. Here's how I'd find out, and here's the nearest thing I do know." | Factual and technical questions outside your forecast — honesty plus a bridge keeps credibility intact, where a bluff invites follow-ups you can't survive | Anything the job description explicitly lists. "I don't know" on a listed requirement signals you didn't prepare — those lines are exactly what the JD Decode exists to catch |
Insight
Notice the loop: the deferral move's failure case — getting caught unprepared on a listed requirement — is only reachable if you skipped the Forecast step. The three parts of the method cover for each other: forecasting shrinks how often you need recovery, and recovery covers the forecast's misses.
"I have a ton of examples, but my mind blanks" — why prepared people still freeze
Most interview failures are retrieval failures, not knowledge failures: candidates who have plenty of examples still blank under live pressure because they practiced recognizing good answers — reading notes, watching videos, thinking through stories silently — instead of producing them out loud under time pressure.
The pattern is all over Reddit's job-hunting subreddits, in posters' own words. From r/interviews: "I have a ton of examples I could provide, but my mind blanks and I stammer like an idiot." From r/recruitinghell: "No matter how many hours I dig into the company, drill interview question banks, run mock sessions... or binge YouTube tutorials on 'perfect answers'" — and then, the poster goes on, it all falls apart the moment the interview starts. (The Reddit quotes in this article come from a research pass of roughly 25 archived posts across r/interviews, r/recruitinghell, and related job-hunting subreddits.) These are not under-prepared people. They are people whose preparation never included the actual skill being tested: retrieving a story and speaking it, on a clock, while being evaluated. (If blanking despite solid prep is your main problem, that failure mode gets a full guide of its own: why your mind goes blank in interviews.)
That is why the third pillar of this method is training retrieval, not accumulating more material. Concretely: take your forecast, and for each territory, answer one question out loud, timed, and get honest feedback on it — then repeat until retrieval is boring. A friend can do this for you if they'll genuinely score you rather than nod politely (Reddit is littered with mock interviews that "felt fake" and ended in tears).
Disclosure: Interview Drills, whose site you are reading, is our product, and it is built to be exactly this practice loop. Interview Drills is an AI-powered interview training platform designed for people who have a real interview coming up. It diagnoses interview weaknesses with a free 3-minute quiz, prescribes a 14-day training track of practice drills, scores spoken answers on six dimensions in under 60 seconds, and personalizes scoring and feedback to the candidate's resume and target job. In terms of this article's method: the match analysis is the Forecast step, the scored drills are retrieval training, and the score report tells you whether your CAR story actually landed with Structure and Conciseness intact — feedback a mirror can't give you.
You can run the loop without paying anything: the 3-minute diagnostic quiz requires no account, this site's drill pages give you 1 free scored drill per day with no account (3 per day with a free account), and you can start with the question your forecast guarantees — Tell Me About Yourself.
Two honest routing notes, because this method is not for every situation. If your interview is tomorrow, you do not have time for a full forecast-and-bank cycle — compress it: decode only the JD's top three lines, bank three stories, rehearse each once out loud. Our free guide to preparing for an interview in 24 hours walks that compression hour by hour. (If you want it automated, the 24-Hour Interview Crash Course, included with every Interview Drills paid plan, runs the same compression from a pasted posting: up to 8 questions generated from the posting plus 3 from the question library, and it banks your 3 core stories.) And if your real problem is panic — racing heart, spiraling thoughts, freezing despite knowing your material — question forecasting won't fix that by itself; start with our guide to interview anxiety.
You cannot control what they ask. You can control how much of it you saw coming — and how well you've trained for the part you didn't.
Frequently asked questions
- What should I do when I can't answer an interview question?
- Buy a few seconds first — say something like "That's worth a real answer, give me a moment to pick the right example." Then either think aloud through your reasoning or ask a clarifying question. For knowledge questions you genuinely don't know, an honest "I haven't worked with that, but here's the closest thing I have done" beats bluffing, because a bluffed answer invites follow-up questions you can't survive.
- Is it OK to say "I don't know" in an interview?
- Yes, for factual or technical questions — an honest deferral with a bridge to adjacent experience keeps you credible, while a bluff invites probing follow-ups that expose the gap and cost you trust on everything else you said. The exception: saying "I don't know" about something the job description explicitly lists reads as unprepared. Those lines are exactly what a job-description decode tells you to prepare in advance.
- How many stories do I need to prepare for a behavioral interview?
- Six to eight, chosen so that together they cover the core competencies interviewers probe: leadership, conflict, failure, ambiguity, results, and initiative. Interviewers ask about competencies rather than specific scenarios, so one strong story answers many differently worded questions — you don't need an answer per question, you need a story per territory.
- How do interviewers decide what questions to ask?
- Interviewers build questions from three inputs: the job description's requirement lines, your resume's claims and gaps, and their own role in the hiring process. A recruiter screens for basics and logistics, a hiring manager probes how you'd do the actual job, and a panel divides competencies among its members. That is why the question territory is predictable even when the exact wording is not.
- What if my mind goes blank even though I prepared?
- Going blank is a retrieval failure, not a preparation failure — reading your notes silently trains recognition, but an interview demands producing answers out loud under time pressure, which is a different skill. Practice speaking your stories against a clock with honest feedback. If freezing and anxiety are your main problem rather than prep, that deserves its own dedicated approach beyond question forecasting.
- How do I prepare if I'm bad at making things up on the spot?
- Design your prep so you rarely have to improvise. Forecasting likely question territories from the job description and your resume, then banking six to eight stories that cover them, front-loads the thinking so the large majority of questions land on material you've already prepared. For the rest, recovery moves — buy time, clarify, think aloud, bridge — are learnable structure, not improvisational talent.