How Many Questions to Ask Candidates in 30 Minute Interviews
How many questions are asked in a 30 minute interview? Five or six substantive ones from the interviewer, each with a follow-up or two, and two to four from the candidate in the last five to eight minutes. A 20 minute screen fits three or four core questions and a 45 minute interview eight or nine. This page has 40 questions for both sides of the table: a screening script for hiring managers and recruiters, in the order the call runs, then a ranked list for candidates to ask back.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Interviewer: opening
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.
Interviewer: evidence
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 a 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.
Interviewer: fit and close
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. Rules on asking about salary history differ by country and state, so check what applies where you hire. Do this in the first screen: a mismatch on pay found at the offer stage wastes every round before it.
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.
Candidate: ask first
What would the person in this role need to have done in their first six months for you to be pleased?
Why ask it
The one question to ask if you only get one, because it forces a concrete answer about the actual work rather than the job description. A hiring manager who cannot name anything specific either has not defined the role or is filling a gap they have not diagnosed.
What problem are you hoping this hire solves?
Why ask it
You are listening for whether the problem is capacity, capability or a mess someone left behind, since each means a different first year. If the answer is that they are simply growing, ask which team's work is currently late because this seat is empty.
Why is the role open?
Why ask it
Short, and it costs you almost nothing in a tight slot. A backfill invites the obvious follow-up about what happened to the last person, and a vague answer about restructuring is worth remembering when you compare this with other offers.
Who would I report to, and how often would we actually talk?
Why ask it
Ask this even if you think you know, because the person interviewing you is frequently not the manager. Weekly one-to-ones that are protected, versus a manager with fourteen reports who catches up monthly, is the difference between two very different jobs.
What happened with the last person who held this role?
Why ask it
Promoted internally, left the industry, or fired at four months are three answers you cannot get any other way. Watch for a shift into careful language here, which usually means the story is more complicated than the answer you are being given.
Which part of this job do people underestimate?
Why ask it
Interviewers enjoy this one and tend to answer it honestly, because it lets them be candid without criticizing anyone. The answer is usually the least appealing part of the role, which is exactly the part you cannot find on the posting.
What would make you conclude, six months in, that this hire had not worked?
Why ask it
The inverse of the six-month question, and it draws out different material: the specific behavior that irritates this manager, the deadline that cannot slip. If they say they cannot imagine it, ask what happened the last time a hire on this team did not work out.
Candidate: if time
What does a normal week look like, and how much of it is meetings?
Why ask it
Cheap to ask and hard to spin. An answer of thirty hours of meetings for a role sold as hands-on work tells you the job title and the calendar do not match, which is worth knowing before you negotiate anything.
Who else would I be working with day to day?
Why ask it
Names and functions, not an org chart. This surfaces the dependency nobody mentioned, such as a role that only succeeds with cooperation from a team in another country or a stakeholder everyone speaks carefully about.
What is the team's biggest constraint right now: people, budget, a dependency, or a decision that has not been made?
Why ask it
Offering the options makes it easy to answer in a hurry and hard to answer in platitudes. A pending decision above their head is the most useful answer, because it means the role's scope may change after you accept it.
How is performance measured here, and when is the first formal review?
Why ask it
Ask for the mechanism and the date. Vagueness on both, in a company large enough to have a process, usually means reviews happen when someone remembers, which also tends to be how raises and promotions happen.
What has changed about the team in the last year?
Why ask it
Reorganizations, departures, a new leader, a shifted mandate. Recent churn is not automatically a reason to walk away, but it changes what your first six months would involve and it is much harder to find out after you start.
How do decisions get made here when people disagree?
Why ask it
Everyone claims to be collaborative, so listen for the actual mechanism: a named decision-maker, a document, a meeting, or a quiet escalation to whoever is loudest. If they cannot describe a recent example, the honest answer is usually that nothing gets decided.
What happened to the last two people who were promoted out of this team?
Why ask it
Much sharper than asking about growth opportunities, which invites a brochure answer. Two real names with dates is a good sign. A long pause suggests the path exists on a slide rather than in practice.
What is the honest expectation on hours, travel and being reachable outside them?
Why ask it
Say honest and then wait. The useful detail is usually in the qualification that follows the first answer: quarter end, a launch, a client in another time zone. Interviewers rarely lie about this if you ask plainly, but they seldom volunteer it.
Where does the team stand on office and remote days, and is that written down or informal?
Why ask it
The written policy and the team's actual habit often differ, and the second one is what you will be judged against. If the answer is that it is flexible, ask how many days the person interviewing you came in last week.
Candidate: closing
Is the range on the posting the range you are working with, and where in it would someone with my experience land?
Why ask it
Ask this in a first round if compensation could rule the job out, and ask it in this two-part form so a yes cannot be a non-answer. If there is no posted range, ask what the range is rather than offering a number first.
What are the remaining steps, who is involved, and what is your timeline?
Why ask it
Practical, so save it for last if time is short, and get names or job titles rather than just a number of rounds. If nobody can give you a timeline, ask whether the role has final approval yet.
Is there anything in my background that gives you pause?
Why ask it
The highest-risk and highest-value question a candidate can ask in a short interview, because it invites an objection you can answer while you are still in the room. Ask it only if you can take the answer without becoming defensive, and keep your reply to two sentences.
What should I have asked you that I did not?
Why ask it
A good closer when you have thirty seconds left and no time for anything substantial. It occasionally produces the most candid thing said in the whole interview, and it never costs you anything unless it is your only question.
How many questions fit in a 30 minute interview
Practical guidance for the conversation itself
How many questions are asked in a 30 minute interview
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.
In a 20 minute or a 45 minute interview
The same arithmetic scales. Twenty minutes leaves about twelve for your questions once you have opened, kept five for theirs and closed, which is three or four core questions: keep one project taken apart properly, the gap in their experience and the logistics, and drop the rest. Forty-five minutes leaves about thirty, which is eight or nine. Spend the extra time on a second example in depth, not on more topics.
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 when you are the interviewer
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.
If you are the candidate: how many to expect and how many to ask
Expect to be asked five or six, not fifteen
A well-run 30 minute interview puts five or six main questions to you, each followed by one or two requests for detail. Prepare two or three examples you can tell in two minutes and then take apart when asked, because the follow-ups are where the time goes. If you get a dozen quick questions instead, keep each answer short and save your detail for the one closest to the job.
Expect to ask two to four, prepare six
A 30 minute interview typically runs as five minutes of introductions, fifteen to twenty on you, and five to eight for your questions. That is two to four questions once follow-ups are counted. Prepare six ranked in order so you are never choosing under pressure, and accept that you will not reach the bottom of the list.
Rank them by what could change your decision
Put anything that could rule the job out at the top: the range, the manager, the hours, what happened to the last person. Questions about culture and growth are worth asking in a later round when there is time for a real answer.
Ask one mid-conversation, not all at the end
Asking one question in the middle, when they mention a project or a reorganization, makes the exchange a conversation rather than a queue. It also protects you if the interviewer runs out of time at the end, which happens often.
Do not stockpile questions to look interested
Interest is shown by following up on what they actually said, not by volume. Six shallow questions read worse than two that clearly came out of listening, and in a 30 minute slot they will also make you the reason the interview overran.
Managing the clock as a candidate
- Keep each question to one sentence. Multi-part questions get one part answered, usually the easiest one.
- One follow-up per question. That is where the specifics live, and a second follow-up starts to feel like an interrogation.
- At around the 25 minute mark, ask directly: "We have a few minutes left, can I ask two things?" Interviewers appreciate being told the plan.
- If they offer one question only, use the six-month success question or the one about their reservations, depending on how the interview has gone.
- If time runs out entirely, say you have three questions and ask whether to send them by email. It is a reasonable request, and a legitimate reason to be in their inbox.
What goes wrong for candidates in a short interview
Asking what is already on the website
In a 30 minute slot this is expensive, because it consumes one of your two or three questions and signals you did not prepare. Read the posting, the last year of company announcements and the interviewer's own background first.
Leaving compensation for later every time
If the range could make the whole process moot, ask in round one. A candidate who waits until the final round to find the range is well below what they need has sat through hours of interviews to learn something one sentence would have told them.
Reading questions off a list
It is obvious on video calls and it stops you noticing that they already answered question three. Keep the list where you can glance at it, and cross off what has been covered as they talk.
Asking nothing
No questions reads as no interest or no preparation, and it can count against an otherwise strong candidate. Two is enough. Zero is a problem.
Interviewing the wrong person
A recruiter screen cannot answer how decisions get made on the team, and a hiring manager may not know the benefits detail. Match the question to the person in front of you and save the rest for the round where someone can answer it.
After the call, as the candidate
- Write down the answers within ten minutes, particularly on scope, manager and process, while the wording is still fresh.
- Send any unasked questions in a short follow-up email, three at most, and keep it to the ones with factual answers.
- Note anything the interviewer was careful about. Careful language in a first round is usually the thing you will hear more about in the second.
- Compare what you were told about the role against the posting. Where they differ, ask in the next round which version is current.