How Many Questions to Ask in a 30 Minute Interview
If you are running a 30 minute interview, plan five or six substantive questions and nothing more: at roughly three minutes each with follow-ups you have used twenty minutes, which leaves time to open properly and to answer the candidate's questions. This page gives twenty questions for a short screen with a suggested time budget, ordered as the call itself runs. Written for hiring managers and recruiters.
The questions
Open any question for the note
Before we start: is 30 minutes still workable for you, and is there anything you want to make sure we cover?
Why ask it
Costs twenty seconds and buys two things: permission to interrupt later, and the candidate's own priority, which is often compensation or logistics. Better to know at minute one than to have them raise it as you are trying to close the call.
Give me the two-minute version of what you do now and where you think this role fits.
Why ask it
Naming the length is the point. Candidates asked to walk through their background will happily use twelve minutes, and cutting them off later costs you rapport. How well they hold to two minutes is also the first evidence you get about how they communicate.
What made you start looking?
Why ask it
You are listening for whether they are running from something or toward something, and whether the thing they are escaping exists here too. A candidate who cannot name any reason usually has not decided to leave and will be difficult to close.
Pick something from the last year you are proud of and walk me through your part in it.
Why ask it
Letting them choose gets you their best material and shows what they consider good work. The instruction about their part matters, since the difference between a strong and a weak candidate here is often just how specific they can be about what they personally did.
Which parts of that were yours, and which were someone else's?
Why ask it
The single most useful follow-up in a short screen. Persistent use of we, with no answer when you press for the boundary, is the most common sign of a borrowed accomplishment. Strong candidates are usually quick to credit others precisely.
What was the hardest part, and what did you do when it went wrong?
Why ask it
Every real project has a bad week, so an answer with no difficulty in it means you are being told a summary rather than a story. Listen for what they changed rather than how it ended, since a good outcome can be luck and a good response cannot.
Tell me about a time you disagreed with a decision and lost. What did you do afterwards?
Why ask it
The afterwards is the question. Committing to a decision they argued against, without relitigating it for six months, is a strong signal. An answer where they were retrospectively proved right and everyone admitted it is usually a rehearsed story rather than an example.
Looking at the job description, which part looks least like work you have done?
Why ask it
Invites the candidate to volunteer their own gap, which most will do honestly if the question is framed as ordinary rather than as a trap. Someone who claims every element is squarely in their experience is either overqualified or not reading carefully.
Which of the tools listed have you used yourself in the last year, and how deeply?
Why ask it
Ask for personal use and recency rather than familiarity. A candidate who has configured something is different from one who has worked alongside it, and in a 30 minute screen this one question can replace a whole technical section.
If your first project were the one I described, how would you spend the first two weeks?
Why ask it
The nearest thing to a work sample that fits in three minutes. You are looking for whether they ask questions before answering, and whether they plan to talk to anyone before shipping something. A confident plan built on no information is a warning.
What do you want more of, and less of, than you have now?
Why ask it
More useful than asking about career goals, because it produces an answer you can check against this job. If the thing they want less of is the bulk of the role, say so in the call rather than declining them silently afterwards.
What kind of manager gets your best work?
Why ask it
Answers tend to describe either autonomy or structure, and both are fine as long as they match the manager who is actually available. A candidate wanting weekly coaching from a manager with fifteen reports will struggle regardless of skill.
What is a piece of feedback you have had that you disagreed with?
Why ask it
Harder to rehearse than the standard weakness question and much more informative. Look for whether they can state the feedback fairly before disagreeing with it, and whether anything at all changed as a result.
What are the constraints on your side: notice period, hours, travel, where you work from?
Why ask it
Cheap to ask and expensive to discover in week four. Group these together so none of them feels like a probe, and note anything that will need an accommodation or an exception so you can check it now rather than promise it later.
Are you in process anywhere else, and how far along?
Why ask it
Sets your own timeline. A candidate with a final round elsewhere next week means your four-stage process needs compressing or you will lose them. Reluctance to answer is reasonable and not a mark against them.
The range for this role is what was posted. Does that work for what you are looking for?
Why ask it
Stating the range and asking for a yes or no is faster and fairer than asking for their expectations, and in many places asking for salary history is unlawful. Do this in the first screen: it is the most common reason a late-stage process collapses.
Is there anything on your resume you would expect me to ask about that I have not?
Why ask it
Gives a candidate a clean way to explain a gap, a short tenure or a career change without you having to interrogate it. Most people use it for exactly that, and the answer is usually duller and more human than the version you had assumed.
What questions do you have for me?
Why ask it
Reserve five to eight minutes for this and treat it as evidence rather than as the wind-down. What they ask about first, the work, the team, the process or the money, tells you what they will be weighing when they decide, and their questions often reveal more preparation than their answers did.
Based on this conversation, is this a job you would want? What would you need to know to be sure?
Why ask it
Asked plainly, this gets an honest read on interest at a point where you can still act on it. Hesitation here is not a rejection: it usually names the exact thing to address in the next round, whether that is scope, the manager, or the hours.
Anything you want to add before we finish?
Why ask it
Thirty seconds, and occasionally produces the detail that changes your decision, particularly from nervous candidates who are only now settling. It also ends the call on their terms, which matters for a candidate you may want to approach again in a year.
Designing a 30 minute interview
Practical guidance for the conversation itself
How many questions to plan
Five or six core questions, with follow-ups
A substantive question and its follow-ups takes three to four minutes if you let the candidate actually answer. Five or six fills twenty minutes. Anything beyond that is either being rushed or is squeezing out their questions, and both cost you information.
A workable 30 minute budget
Two minutes to open and set the shape of the call, eighteen to twenty on your questions, five to eight for theirs, one to close with clear next steps and a date. Write the times next to your questions and keep the clock where you can see it.
Fifteen rapid questions is a worse screen, not a fuller one
Short answers to many questions produce rehearsed material and no evidence. One project taken apart properly tells you more about how someone works than a dozen topics touched for ninety seconds each.
Ask every candidate the same core set
Same questions, same order, same follow-ups where possible. Comparability is the whole point of a structured screen, and it is also your defense if a hiring decision is ever challenged.
Running the call
- Say the plan out loud at the start, including that you will interrupt to keep to time. Interruptions then read as timekeeping rather than as rudeness.
- Ask one question at a time. A two-part question in a short screen gets the easier half answered and you will not notice the other half went missing.
- Use silence. Four seconds after an answer often produces the specific detail the first pass left out.
- Interrupt long answers with a redirect rather than a stop: "That is useful, and what was your part in the decision?"
- Take notes on what they said, not on your impression. Impressions are what you will still have tomorrow anyway, quotes are not.
Common mistakes
Talking for the first ten minutes
A long description of the company and the role eats a third of the call and teaches the candidate exactly what to say back to you. Keep the pitch to ninety seconds and save the detail for their questions at the end.
Leaving compensation to a later round
In a 30 minute screen this is the single highest-value fact to establish. Skipping it is how processes reach the offer stage and then fail on a number that was knowable in week one.
Letting the last five minutes disappear
When your questions overrun, the candidate's questions get cut, and that is the part of the call that persuades them to take the job. Guard the time as firmly as you would guard your own agenda.
Asking questions you cannot score
Riddles, favorite animals and where they see themselves in five years generate conversation and no comparable evidence. If you would not know what a good answer looked like in advance, cut the question.
Deciding in the first three minutes
Everything after that becomes confirmation. Writing evidence against each question as you go, rather than a running verdict, is the practical defense against it.
Immediately afterwards
- Spend five minutes writing up before the next call. Notes written at the end of the day blur into each other and favour whoever you saw last.
- Record a decision and the reason in the candidate's own words, so the next interviewer can probe what you could not cover in 30 minutes.
- Pass on what they told you about timelines and constraints, and act on it: a candidate in a final round elsewhere needs a compressed process or a fast no.
- Tell them what happens next and by when, then meet that date. In a short screen, this is most of what they will remember about your organization.