Hiring is the highest-leverage decision a manager makes, and the interview is where most of us get it wrong. We ask whatever comes to mind, warm to the person who interviews smoothly, and discover months later that "interviews well" and "does the job well" are not the same skill. The good news: you don't need to be a trained interviewer to hire better. You need a short list of questions that reveal how someone actually works — and a plan for what to listen for.
Here's the takeaway up front: the best interview questions ask about real past behavior, not hypotheticals, and your job in the room is to listen for specifics, not polish. Below is a practical set of interview questions to ask candidates, grouped by what each one tests, plus what strong and weak answers sound like — and the mistakes that quietly sink good hiring decisions.
Start with what you're actually hiring for
Before you write a single question, write down what this role needs to do in its first six months — three or four concrete outcomes, not a wish-list of traits. "Runs the monthly close without hand-holding" is something you can probe for. "Detail-oriented team player" is not: everyone claims it and no question tests it. Your questions should ladder up to those outcomes.
Then ask every candidate the same core set. A structured interview — same core questions, same order — is more reliable than a free-flowing chat for one simple reason: when everyone answers the same questions, you're comparing candidates against each other, not against whoever happened to charm you that day. The trade-off is that it feels a little less like a natural conversation. Worth it — consistency is what makes the comparison fair.
The interview questions that actually tell you something
Questions about how they really work
This is the most useful category by far, because past behavior is the best available guide to future behavior. Ask people to walk you through things they've actually done, not things they might do.
- "Tell me about a time you [did the thing this role requires]. What was the situation, what did you do, and how did it turn out?" The workhorse question. Swap in the real task: rescued a slipping project, handled an angry customer, cut a budget without drama.
- "Walk me through a recent piece of work you're proud of. What was your specific part in it?" Tests genuine contribution. Listen for "I," not a warm fog of "we."
- "Tell me about something you were responsible for that went wrong. What happened, and what did you do next?" Tests ownership and honesty. You're not looking for a flawless record — you're looking for someone who can name a real failure without blaming everyone around them.
Strong answers give you specific situations, their own actions, and what they'd do differently. Weak answers stay vague, hide behind "we always...," or offer a rehearsed "weakness" that's secretly a brag.
Questions that test how they think
- "How would you approach [a real problem this role faces] in your first month?" A light hypothetical is fair here, because you're testing method, not a single right answer. The strong candidate asks clarifying questions and lays out a sensible sequence; the weak one blurts a confident answer to a problem they don't understand yet.
- "What would you need to learn to be effective here, and how would you go about it?" Tests self-awareness and how someone ramps. Nobody arrives fully formed — the good ones know it and have a way to close the gap.
Questions about working with other people
- "Tell me about a disagreement with a colleague or manager. How did you handle it?" Tests how they handle conflict, not whether they have it — everyone does. Listen for respect for the other person's view and a route to resolution, not a story where they were simply right and everyone else was an idiot.
- "How do you like to receive feedback?" Quietly one of the most revealing questions you can ask. It tells you how to manage this person, and whether they've thought about their own growth at all.
Questions about motivation and fit
- "Why this role, and why now?" Tests whether they've actually thought about it or are firing off applications by the dozen. You want real reasons over flattery.
- "What does a good manager do, for you?" Tells you whether you can offer what they need. If they want daily direction and you run a hands-off team, it's far better to learn that today than in month three.
One caution on "fit": it means can do the work and work well with the team — never is like us. Hiring for sameness is how teams get narrow and how bias creeps in unnoticed. Screen for what the role needs, not for who feels familiar.
A quick guide to reading the answers
| What you ask | Strong answer sounds like | Red flag |
|---|---|---|
| Tell me about a time… | A specific situation, their actions, a clear outcome | "We generally…", no personal role, no detail |
| A piece of work you're proud of | "I" statements, real trade-offs they made | Credit for a team effort with no specifics |
| Something that went wrong | Owns it, names the lesson, changed since | Blames others, or claims nothing has gone wrong |
| A disagreement you handled | Respects the other view, finds a resolution | They were right, everyone else was wrong |
| Why this role, why now | Concrete reasons tied to the work | Generic flattery, or "I just need a job" |
How to listen: separate polish from substance
The questions only work if you listen well. A few habits do most of the work:
- Follow up relentlessly. The first answer is often rehearsed; the truth is in the follow-up. "What was your specific part?" "What would you do differently?" "What did the other person think?"
- Hunt for specifics. Names, numbers, sequences, trade-offs. Specifics are hard to fake — polish is easy.
- Talk less. Aim to listen roughly 80% of the time. If you spend twenty minutes selling the role, you've learned nothing about the person.
- Take notes against your outcomes, during the interview or right after. Memory blurs candidates together and quietly favors the last one and the most charming one.
- Beware the mirror. We instinctively rate people who remind us of ourselves higher. Notice the pull, and score the answer, not the rapport.
Interview questions to avoid
- Anything about protected characteristics — age, marital or family status, health, religion, or where someone is "originally" from. Beyond being unfair, in many places it's illegal. Keep every question about the work.
- Pure hypotheticals as your main event. "How would you handle an angry customer?" invites a textbook answer. "Tell me about an angry customer you actually handled" gets you the truth.
- Brainteasers and puzzles ("how many golf balls fit in a bus?"). They test composure under a party trick, not the job.
- Leading questions. "We move fast here — you're good with that?" only ever gets a yes. Ask it neutrally: "Tell me about the pace of your last role and how it suited you."
A simple interview scorecard you can use this week
You don't need software or a hiring committee. You need a page and a little discipline.
Before: Write the three or four outcomes the role must deliver. Pick five or six core questions that map to them. If others are interviewing too, split the questions so you're not all asking the same thing.
During: Ask every candidate the same core questions. Follow up for specifics. Listen far more than you talk.
After: Within an hour, rate each outcome on a simple scale — say 1 to 4 — with one line of evidence for each score. Do this before the group discusses, so a strong voice in the room doesn't anchor everyone to the same opinion.
And remember the interview is only half the job. The offer is where a good hire is won or lost, and the first weeks are where they decide whether they made the right choice. Once you've picked someone, set them up to succeed from day one — a strong hire onboarded badly still walks.
FAQ
What are the best interview questions to ask candidates? The ones about real past behavior: "Tell me about a time you…" mapped to what the role actually requires. They beat hypotheticals because past behavior predicts future behavior far better than a candidate's guess at what they'd do.
How many questions should I ask in an interview? Five or six core questions, asked of every candidate, with room to follow up. Depth beats breadth — a handful of questions you probe hard tells you more than twenty you rush through. Keeping the core set consistent is also what lets you compare people fairly.
What are good behavioral interview questions? Ones that ask for a specific past example: a project that went wrong, a disagreement they handled, work they're proud of and their exact part in it. Listen for the situation, their own actions, and the result — and be wary of answers that never leave "we."
What questions should you not ask in an interview? Anything about protected characteristics (age, family status, health, religion, national origin), brainteasers, and leading questions that telegraph the answer you want. They're unfair, legally risky, or simply uninformative. Keep every question tied to the work.
How do I tell if an answer is a red flag? Watch for vagueness, no personal ownership ("we" with no "I"), blaming others for everything that went wrong, and textbook answers to real-experience questions. A confident non-answer is still a non-answer.
How can I interview candidates fairly? Ask everyone the same core questions, score answers against the role's outcomes rather than your gut, take notes in the moment, and decide your rating before the group talks. Structure is what keeps charm, familiarity, and first impressions from doing the deciding for you.
Great hiring isn't a talent you're born with — it's a short list of the right questions and the discipline to listen for specifics. Get that right and you spend far less time later fixing a hire that never fit. For more do-it-Monday advice on hiring and leading a team, visit YouManageIt.
