How to Interview Candidates: A Hiring Manager's Guide

Your first round of interviews as a hiring manager is coming up, and you have realized nobody actually trained you how to do this. You have sat across the table as a candidate a dozen times. Sitting on the other side is a different skill, and a bad interview process costs you a bad hire, which costs far more than the hours you spend fixing your questions now.

The good news is that interviewing well is learnable, and it does not require charisma or a gut instinct for “culture fit,” which is usually a euphemism for bias dressed up as intuition. It requires a structure you use consistently and a small set of questions that actually predict how someone will perform.

The core of how to interview candidates well is structure: ask every candidate for a role the same core questions in the same order, score them against written criteria right after each interview, and separate the evaluation of what someone did from how comfortable you felt talking to them. That consistency is what makes hiring decisions fair and defensible.

What is a structured interview, and why does it beat a “good conversation”?

Most untrained interviewers run what feels like a good conversation: some rapport, a few questions that occur to them in the moment, a gut check at the end. It feels natural, and it is a poor predictor of performance, because you are comparing five different unstructured conversations against each other instead of the same measurement applied five times.

A structured interview fixes that. Before you meet anyone, decide:

• The exact questions you will ask, tied to the skills the role actually requires
• The order you will ask them in
• What a strong, adequate, and weak answer looks like for each one, written down in advance

Then you run the same interview, in the same order, for every candidate. It feels rigid the first time you try it. It is the reason a structured process consistently outperforms free-form conversation at predicting who will actually do the job well, because you have removed the noise of five unrelated conversations and replaced it with one comparable measurement, asked five times.

How to conduct an interview: a repeatable structure

Here is a repeatable shape for a 45-minute interview. Adjust timing to your slot length, but keep the order.

1. Open (5 minutes). Put the candidate at ease. Briefly explain the format: “I’ll ask a few questions about your experience, and we’ll leave time at the end for yours.” This alone reduces nervous, guarded answers.
2. Role-specific behavioral questions (25 minutes). Three to four questions tied to the skills the role needs most. Ask a follow-up on each: “What did you specifically do,” “What was the outcome,” “What would you do differently now.”
3. One judgment question (5 minutes). A realistic scenario from the actual job, not a brain teaser. “A stakeholder wants a change two days before launch that you think is risky. Walk me through how you’d handle it.”
4. Candidate questions (10 minutes). Their questions tell you almost as much as your own. A candidate asking about the team’s biggest current challenge is thinking differently than one asking only about vacation policy.

Write your notes during the interview, not after. Memory reconstructs conversations to fit whatever impression you formed, which is exactly the bias structure is meant to prevent.

Interview questions to ask candidates that actually predict performance

Skip hypothetical brain teasers and generic questions like “where do you see yourself in five years,” which tell you little about job performance. Behavioral questions about real past situations are far more useful, because you are asking for evidence, not speculation.

Good categories to draw from:

• Handling pressure: “Tell me about a time you had to deliver something under a tight deadline with limited resources. What did you do?”
• Conflict and disagreement: “Describe a disagreement with a teammate or manager and how you handled it.”
• Ownership and initiative: “Tell me about something you improved that nobody asked you to fix.”
• Failure and learning: “Tell me about a time something you owned did not go well. What changed afterward?”
• Collaboration: “Tell me about a project where you depended on someone outside your team, and how you kept it on track.”

For each answer, listen for what the candidate specifically did, not what “we” did as a team. A candidate who cannot separate their own contribution from the group’s is either being modest or was not the driver, and you need to know which with a direct follow-up: “What was your specific part in that?”

How do I evaluate candidates fairly? Scoring without bias creeping in

Bias does not usually show up as an obvious prejudice. It shows up as small things: liking a candidate because they went to your school, penalizing someone for being nervous when nerves are not part of the job, or letting one strong or weak answer color your read of everything else that follows.

A few habits reduce it substantially:

• Score immediately after each interview, before discussing candidates with anyone. Write specific evidence for each score, not just a number.
• Use the same written criteria for every candidate, decided before you saw anyone, so you are not inventing standards on the fly that happen to favor whoever you liked.
• If you are on a panel, collect scores independently first. One confident opinion stated early in a debrief can anchor everyone else’s judgment before they have said what they actually thought.
• Separate “I’d enjoy grabbing coffee with this person” from “this person will do the job well.” They are different questions, and only one of them belongs in a hiring decision.

Approach	What it measures	Risk
Unstructured conversation	Rapport, comfort	High bias, hard to compare candidates
Structured behavioral interview	Past evidence of relevant skills	Requires prep, feels rigid at first
Brain teasers and puzzles	Comfort with puzzles	Weak link to actual job performance

Common mistakes new hiring managers make

• Talking too much. If you are speaking more than a third of the time, you are not learning enough about the candidate. Ask a question, then stay quiet through the pause.
• Asking leading questions. “You’d be comfortable with tight deadlines, right?” invites the answer you want to hear instead of the truth.
• Skipping the follow-up. A first answer is often the rehearsed version. “What specifically did you do” and “what happened next” get you past the polish.
• Deciding too early. The first five minutes create a strong first impression that colors everything after it unless you deliberately hold your judgment until the interview is complete.
• Selling instead of assessing. It is fine to represent the role and team well, but if you spend the interview convincing rather than evaluating, you learn little about the person across the table.

This is a practical, good-hiring guide, not a legal one. Employment law around interview questions varies by location and role, and a specialist in employment law is the right call for anything about what you can legally ask or how to document a rejection.

Interviewing well is a skill you build like any other

The first few interviews you run will feel awkward, and that is normal. The structure gets easier with repetition, and the payoff compounds: better hires, fewer costly mistakes, and a process you trust enough to hand to other managers as your team grows. Reading about how to prepare candidates for interviews is useful background here too, since it shows you what a well-prepared candidate on the other side of the table looks like: see our guide to common interview questions and answers.

If interviewing well is one piece of a bigger step up into managing and leading a team, executive coaching works through the harder parts of the new-manager transition with someone who has done it before, not a textbook.

Take the two-minute quiz and get matched with a coach who can help you build the confidence and the process to run interviews you trust. The first session is fully refundable within 48 hours.