The Best Interview Questions to Ask Candidates
We've sat behind enough one-way mirrors, so to speak, to know the uncomfortable truth: most hiring managers ask interview questions that feel productive but predict almost nothing. "Where do you see yourself in five years?" tells you who prepared a stock answer, not who can do the job. Our guide to interviewing candidates covers the whole process end to end; this page is just the question bank — what to actually ask, and why each type earns its place in the interview.
The questions that predict performance share a pattern: they ask about real behavior, not hypotheticals about character. "Tell me about a time" beats "how would you handle" more often than most interviewers assume, because past behavior is evidence and hypothetical behavior is a guess dressed up as an answer.
Below is the breakdown by question type — behavioral, situational, and role-specific — what each one actually reveals, and a full set of behavioral questions with what a strong answer sounds like versus a rehearsed one.
The three question types, and what each one reveals
Every good interview question falls into one of three buckets. Mixing all three in a single interview, rather than leaning on just one, is what actually covers a candidate's real range.
| Question type | What it reveals | Example question |
|---|---|---|
| Behavioral | How the candidate has actually acted under real past conditions | "Tell me about a time you disagreed with a manager's decision. What did you do?" |
| Situational | How the candidate reasons through a problem they haven't necessarily faced yet | "If a client emailed asking for a deadline you know is unrealistic, what would you say?" |
| Role-specific / technical | Whether the candidate has the actual working knowledge the job requires | "Walk me through how you'd reconcile a discrepancy in a monthly report." |
| Motivational / fit | Why this role, why now, and whether that reason holds up under a follow-up | "What made you apply to this specific role, not just any similar one?" |
| Values / culture | Whether the candidate's working style matches how the team actually operates | "Describe the kind of feedback that's helped you improve most." |
Behavioral and situational questions get confused constantly, and the difference matters. Behavioral asks about something that happened. Situational asks about something that could happen. Both are useful; they're just not interchangeable, and a candidate's polish on one doesn't guarantee the other.
Behavioral interview questions (and what good answers look like)
This is the category worth spending the most interview time on, because it's the hardest to fake convincingly on the spot. A candidate can rehearse a values statement. It's much harder to rehearse a coherent, specific story about a real past event that holds up under a follow-up question.
- "Tell me about a time you missed a deadline. What happened, and what did you do next?" — A strong answer owns the miss specifically, explains the actual cause, and describes a concrete fix, not just "I worked harder." A weak answer blames a teammate or gets vague on what they personally did.
- "Describe a time you had to persuade someone who disagreed with you." — Strong answers describe the other person's actual objection and how they addressed it directly. Weak answers skip straight to "and they agreed with me," with nothing about how.
- "Tell me about a mistake you caught yourself, before anyone else noticed." — This one filters for self-awareness. Strong answers are specific and slightly uncomfortable to tell. If someone can't produce a real example, that's informative on its own.
- "Give me an example of a time you had to learn something new quickly to do your job." — Strong answers describe an actual process — what they read, who they asked, what they tried first. Weak answers stay abstract: "I'm a fast learner."
- "Tell me about a time you received critical feedback. What did you do with it?" — Listen for whether the change described actually followed from the feedback, or whether the story conveniently ends before any real behavior change would show up.
According to Harvard Business Review, structured interviews built around a consistent set of questions predict job performance meaningfully better than unstructured conversations driven by gut feel — which is the whole case for building a real question set instead of winging it based on the resume in front of you.
Let AI ranking do the first pass
Jobedly's AI agents score every applicant 0–100 against the role before you ever sit down for an interview, so your questions can focus on confirming fit, not re-screening from zero.
Find candidates with AISituational interview questions worth asking
Situational questions earn their spot when the role involves judgment calls that don't have a clean past-experience equivalent yet — a first-time manager, a role in a new industry for the candidate, or a scenario specific to your business that wouldn't show up anywhere else.
- "A customer is upset about something that genuinely wasn't your team's fault. What do you say to them?"
- "You're given a project with an unclear deadline and a manager who's hard to reach. How do you proceed?"
- "Two priorities collide and you can only finish one today. How do you decide?"
- "You notice a coworker is struggling but hasn't asked for help. What do you do, if anything?"
Good situational answers walk through actual reasoning — trade-offs considered, who they'd involve, what they'd do first. Weak answers jump straight to a tidy resolution with no visible thinking in between, which is usually a sign the answer is a script rather than genuine problem-solving.
Building role-specific questions that actually test the job
Role-specific questions matter more right now than in a slower labor market, simply because there's more competing supply on both sides. U.S. job openings sat at 7.594M in May 2026 according to BLS Job Openings and Labor Turnover Survey — a lot of open roles, and a lot of resumes that look similar on paper for each of them. A question that actually tests the work is what separates candidates who can do the job from candidates who can describe it convincingly.
Generic behavioral and situational questions travel across roles. Role-specific questions shouldn't — they need to test the actual work, not a proxy for it.
- Pull the three or four tasks that make up most of the role's actual day-to-day work, not the impressive-sounding responsibilities from the job posting.
- For each one, write a question that requires describing real process, not a definition. "What is a P&L" tests vocabulary. "Walk me through how you'd build a monthly P&L from raw transaction data" tests capability.
- Add one question that would trip up someone who's only ever done adjacent work, not the actual job — this is what separates a real match from a resume that looks close enough.
- Keep two or three of these consistent across every candidate for the role, so answers are actually comparable side by side.
This is also where a well-written job posting pays off twice — once for attracting the right applicants, and again here, because a specific posting gives you the raw material for specific questions instead of starting from a blank page.
Questions that feel useful but rarely are
A few other low-value staples worth retiring: "what's your greatest weakness" almost always produces a rehearsed non-weakness, and "why should we hire you" invites a sales pitch instead of evidence. Neither is harmful, exactly — they're just dead weight compared to a specific behavioral question in the same five minutes.
Putting your question set together
A solid interview for most roles runs five to seven questions total: two or three behavioral, one or two situational, two role-specific, and one motivational or values question to close. That's enough depth without running the conversation past the point where answers start getting shorter out of fatigue.
The same set, asked the same way, to every candidate for a given role, is what turns a collection of good questions into something you can actually compare across people — which is exactly the structure our guide to building an interview scorecard is built around. Questions and scoring work together; a great question set loses most of its value if there's no consistent way to score the answers afterward.
And a caution worth naming directly: a few common categories of questions aren't just low-value, they're legally risky regardless of intent. Our breakdown of illegal interview questions to avoid covers exactly which topics to stay off of and what to ask instead.
Post once. Let the AI agents do the sorting.
Post a job free on Jobedly and our AI agents surface and rank qualified candidates 0–100 so you spend time on the shortlist, not the pile.
Post a job freeFrequently asked questions
What are the best interview questions to ask a candidate?
Why are behavioral questions better than hypothetical ones?
How many questions should a job interview include?
Should every candidate for a role get the same questions?
What's the difference between behavioral and situational interview questions?
Are personality or novelty interview questions worth asking?
Glossary
- Behavioral question
- An interview question that asks about a specific past event, used because real past behavior predicts future behavior better than a hypothetical answer.
- Situational question
- An interview question that presents a hypothetical scenario to test judgment and reasoning, typically used when a role involves decisions with no clean past-experience equivalent.
- Structured interview
- An interview format that asks the same core set of questions to every candidate for a role, making answers directly comparable.
- Role-specific question
- A question built from the actual day-to-day tasks of a job, designed to test real working knowledge rather than general interview skill.
- Follow-up probe
- A clarifying question asked after an initial answer to test whether a candidate's story holds up under more specific detail.