Interview Questions to Ask Candidates
Published
Hiring teams rarely lose good people for asking too few questions. They lose them because every interviewer asked something different, so nobody could compare the answers. Selectal builds AI recruiters that run first-round interviews — over a thousand structured conversations a week at one customer — so we see which questions produce comparable evidence and which produce polite noise. Below: the questions, what each tests, and the follow-up that exposes a rehearsed story.
Choosing interview questions to ask candidates is a design decision, not a warm-up ritual. A question earns its place only if two interviewers would score the same answer the same way, and if the answer tells you something the résumé already on your desk cannot. Everything here is grouped by what you are trying to learn, not by how the question sounds in the room.
Why interview questions to ask candidates decide the hire
An interview is a measuring instrument. If the questions change from candidate to candidate, you are not comparing people — you are comparing conversations. That is how a confident talker beats a stronger but quieter engineer, and how two interviewers leave the same room with opposite conclusions about the same person.
Structured interviews fix this by holding the questions constant and scoring answers against criteria fixed in advance. The evidence is old and unglamorous: structured formats predict job performance far more reliably than unstructured chats. Planning also buys time — you rarely have more than forty interview minutes, and a list built from what the role requires beats one built from what you were asked at your own last interview.
- Same questions, same order, every candidate
- Criteria written before the first interview
- One question per requirement, not per hunch
- Follow-ups planned, not improvised
How to build your list of interview questions to ask candidates
Start from the job, not from a template. Write down the three to five things a person must do well in this role during their first six months, then find one question per item that forces evidence rather than opinion. If you cannot say what a strong answer contains, the question is not ready to be asked. A workable set for a 45-minute conversation looks like this — six to ten questions in total, leaving room for the follow-ups that do the real work:
- 1 opening question for context
- 3–4 questions on core skills
- 2–3 behavioral questions on past work
- 1–2 situational questions on the role's typical dilemma
- 1 question on motivation and working conditions
- 5 minutes for the candidate's own questions
Keep the same list for every candidate on the same role. Change it between roles, never between people. If a follow-up occurs to you mid-interview, ask it — then write it down and ask it of everyone else, or it stays an impression rather than evidence you can defend later.
Opening interview questions to ask a candidate
The first two minutes exist to make the conversation possible, not to score points. A good opening question is easy to answer, gives you context, and lets you check the shape of the résumé without an interrogation. Point it at something concrete — the current role, the last project, the reason for looking — rather than at the person in general.
- Walk me through what you do day to day now
- What drew you to this role specifically?
- Which part of your current job would you keep?
- What does a good week look like in your work?
Avoid "tell me about yourself" as the literal opener: it is not wrong, but it invites a rehearsed two-minute monologue that tells you little. Listen instead for how the candidate frames the work — as tasks completed or as problems solved. That framing usually holds for the rest of the interview, and it is one of the few things you can read reliably in the first five minutes.
Interview questions to ask candidates about experience
Experience questions are where résumés get tested. The goal is not to confirm that a project existed, but to find out what the person actually did inside it — which decisions were theirs, which belonged to someone else, and what happened when the plan met reality.
- Which part of that project was yours?
- What did you decide, and what did someone else decide?
- What would you do differently now?
- Who disagreed with you, and how did that end?
- What broke, and how did you find out?
The strongest signal comes from the follow-up, not the question. When someone says "we improved the process", ask what they personally changed and on what day. Vague ownership survives one question and rarely survives three. Watch, too, for candidates who describe nothing but successes: a person who cannot name a failure has either not worked on anything hard or is managing you rather than answering.
Interview questions to ask candidates about skills
Skill questions should look like the job. If the role involves writing SQL, ask about a query that went wrong; if it involves calming angry customers, ask about the last one. Keep them open — a quiz with a right answer tests recall, while a question about approach tests thinking, and thinking is what you are hiring.
| What you want to learn | Question shape |
|---|---|
| Depth | Explain how you would approach X for someone junior |
| Judgment | When would you not use your favourite tool here? |
| Currency | What changed in your field in the last year? |
| Limits | What part of this job would you need help with? |
The last row matters more than it looks. Candidates who can name the edge of their own competence tend to be the ones who ask for help before a deadline burns, and that habit is worth more over a year than a slightly deeper answer to the first question.
Behavioral interview questions to ask candidates
Behavioral questions ask about the past on the theory that past behaviour predicts future behaviour better than stated intentions do. They usually start with "tell me about a time", and they live or die on specificity — a general answer means you have not asked the second question yet.
- Tell me about a time you missed a deadline
- Describe a conflict with a colleague and how it resolved
- Tell me about feedback that changed how you work
- Describe a decision you made with incomplete information
- Tell me about the hardest thing you shipped last year
Score them on the parts of the answer rather than on the story's charm: the situation, what the candidate personally did, and the result someone else could verify. If an answer jumps straight from problem to happy ending, the middle is exactly where you dig. One behavioral question asked properly, with two follow-ups, beats three asked shallowly.
Situational interview questions to ask candidates
Situational questions describe a scenario the person has not lived through and ask what they would do. They earn their place for roles where the hard part is judgment under pressure, and for candidates changing industries, whose past does not map neatly onto your job description.
- A customer demands a refund you cannot approve. What now?
- Two priorities from two managers, one afternoon. What ships?
- You spot a mistake in work that already went out
- Your teammate is quietly missing their part of a deadline
The trap is that these questions reward imagination as much as competence: a candidate can describe an ideal response they have never managed in real life. Balance each situational question with a behavioral one covering the same ground, then compare the two answers — the gap between what someone says they would do and what they actually did is often the most useful thing you learn all interview.
Interview questions to ask candidates about motivation and fit
Fit questions are the easiest to get wrong, because "fit" quietly turns into "someone like us" — and that is a hiring mistake before it is anything else. Ask about the working conditions a person needs rather than about their personality, and keep every question anchored to the work instead of to private life.
- What kind of manager gets the best work out of you?
- What made you leave your last role?
- Which parts of a job drain you?
- How do you prefer feedback — written, live, immediate?
The answers tell you whether the environment you actually have — not the one described on your careers page — will let this person do well. A brilliant hire in the wrong setup leaves within a year, and the interview is the cheapest place to see that coming. Hobbies, family plans and weekend habits predict nothing and are unsafe to ask about, so leave them out entirely.
Good interview questions to ask a candidate about pay and logistics
Money and logistics belong early, ideally in the first screen. Discovering a 40% gap in expectations after four rounds of interviews wastes a month for both sides, and it is the most common reason a process that looked strong all the way through ends with nothing to show for it.
- What salary range are you targeting?
- What is your notice period?
- Which days would you be on site?
- Do you need visa sponsorship for this role?
- What other processes are you in, and where?
Asking for salary history — as opposed to expectations — is restricted or banned in many US states and in other jurisdictions, so ask what someone wants to earn rather than what they used to. The last question on the list is not nosy either: knowing that a candidate has a final round elsewhere on Friday changes how fast your own process has to move this week.
Interview questions to ask candidates in a phone screen
A phone or video screen has exactly one job: decide whether a full interview is worth an hour of two people's time. Fifteen to twenty minutes, five questions, the same order every time — and no attempt to reach a hiring decision at this stage, because that is not what the format can support.
- What are you looking for in your next role?
- Which of these responsibilities have you done before?
- What salary range works for you?
- When could you start?
- What questions do you have about the role?
Everything else waits. Screens fail when they swell into mini-interviews: the interviewer runs out of time, the candidate repeats the same stories an hour later, and nobody ends up with a comparable record of who said what. This is also the stage where volume hurts most — most applicants never hear back at all, and that silence starts precisely here, in the round nobody has capacity for.
Interview questions to ask candidates: the ones that are off limits
Some questions are unlawful in many jurisdictions, and most of the rest are simply useless. In the US, anything touching protected characteristics — age, race, religion, national origin, disability, pregnancy or family status — exposes you to a discrimination claim regardless of how friendly the intent was.
- Age, birth year or graduation year
- Marital status, children or plans for them
- Religion, ethnicity or country of origin
- Health, disability or medical history
- Salary history, where it is prohibited
If the job has a genuine requirement — a shift pattern, a licence, physical work — ask about the requirement itself: can you work Saturdays, do you hold the certification. That is lawful, and more useful than the question you were tempted to ask. Brain teasers deserve their own line: puzzle questions mostly measure practice at puzzles, and the companies once famous for them abandoned the practice years ago.
Interview questions to ask candidates: how to score the answers
A question without a scoring rule produces an opinion. Before the first interview, write down what a weak, an adequate and a strong answer contains for each question, then score immediately after the conversation while the details are still fresh rather than at the end of the week.
| Score | What it means |
|---|---|
| 1 | No relevant evidence, or evidence contradicts the requirement |
| 2 | Some relevant experience, thin on ownership or outcome |
| 3 | Clear ownership, specific actions, plausible result |
| 4 | All of the above plus judgment the role will need later |
Two rules keep the scale honest. Score each question before discussing the candidate with anyone else, and never revise an earlier score after meeting a stronger applicant. Recalibrating retroactively is how an entire shortlist quietly reshuffles around whoever you happened to interview last, which is the bias structured interviewing was supposed to remove.
How AI interviews change the interview questions to ask candidates
AI interviewers now handle first-round screening at a scale humans cannot reach: at Kodland, Selectal's AI recruiters run 1,149 interviews a week, and Drinkit cut candidate processing from 30 minutes to five. When every applicant gets the same structured conversation, the question list splits into a repeatable part and a human part.
- Screening questions become fully standardised
- Follow-ups generated from the answer, not the script
- Human interview time moves to the shortlist
- Every answer arrives recorded and comparable
What does not change is your judgment about what the role requires. The system asks and records, while the criteria, the weighting and the hiring decision stay with your team — which is also what keeps the process defensible if a candidate asks why they were not moved forward. In practice, teams split the list by stage, and whichever stage a question sits in, the same three checks apply before it goes live:
| Stage | Questions that belong here |
|---|---|
| AI first round | Experience, logistics, availability, basic skills |
| Human round | Situational dilemmas, trade-offs, team-specific judgment |
- Tied to a requirement, not to habit
- Scoring rule written in advance
- Asked of every candidate on the role
Conclusion
Good interviewing is less about finding clever questions than about asking the same ones, in the same order, and scoring them the same way. Build the list from the job, keep it constant across candidates, follow up until you hear specifics, and stay away from questions that are unlawful or merely decorative. Structure is what makes answers comparable, and comparison is what makes the hire.
FAQ
How many questions should one interview have?
Six to ten for a 45-minute interview, plus five minutes for the candidate's own questions. Fewer than six leaves you with thin evidence on at least one requirement, while more than ten means rushed answers and no room for the follow-ups that actually reveal what a person did. A workable split:
- 1 opening, 3–4 skills, 2–3 behavioral
- 1–2 situational, 1 on motivation
What are the best interview questions to ask a candidate?
The ones tied to what the role genuinely requires. A question is good when two interviewers would score the same answer identically, and when the answer reveals something a résumé cannot — ownership of a decision, a trade-off made under pressure, the limits of someone's own competence.
Should every candidate get identical questions?
Yes, for the same role. Consistency is what makes answers comparable, and comparability is the whole point of interviewing several people. Ad-hoc follow-ups are fine, provided you ask them of everyone; a question asked of one candidate only is an impression, not evidence.
How do I tell a rehearsed answer from a real one?
Ask for the specifics underneath it: dates, the decision actually made, who disagreed, what broke and how it was found. Rehearsed stories thin out after the second follow-up, while real ones get more detailed — the person starts remembering things they did not plan to mention.
Can I ask a candidate about salary history?
Ask about expectations, not history. Salary history questions are restricted or banned in many US states and in other jurisdictions, and they anchor your offer to what a previous employer happened to pay rather than to the value of the role you are filling right now.
Do AI interviews replace hiring managers?
No. They handle repeatable first-round screening and record every answer in comparable form; the criteria, the weighting and the hiring decision stay with your team. What changes is where human interview time goes — to the shortlist rather than to the first call.