How to Conduct a Job Interview: A Step-by-Step Guide for Hiring Managers

This guide walks you through every stage of conducting a job interview: preparation, opening, questioning, closing, evaluation, and legal compliance. Whether you are interviewing for the first time or want to raise the standard across your entire hiring team, what follows is the practical framework you need.

Why Most Interviews Fail

Research consistently shows that unstructured interviews - where each interviewer asks whatever comes to mind - have very low predictive validity for job performance. The classic "gut feel" approach produces results barely better than chance. The reasons are well-documented: interviewers tend to make snap judgments in the first few minutes, spend the rest of the interview confirming that judgment (confirmation bias), and rate candidates higher who share their background or communication style (affinity bias).

Structured interviews, by contrast, use the same predetermined questions for every candidate, score responses against defined criteria, and aggregate ratings from multiple evaluators. Studies show structured interviews are roughly twice as predictive of job performance compared to unstructured ones. That difference translates directly into better hires, lower turnover, and stronger teams.

Step 1: Prepare Before the Interview

Define What You Are Actually Hiring For

Before you write a single question, get clear on what success looks like in the role. Pull the job description, talk to the outgoing person if relevant, and ask the hiring manager what the top three things are that someone needs to do well in the first six months. This clarity prevents you from interviewing for a generic version of the job title rather than the specific role you need to fill.

From that clarity, derive the three to five core competencies you will evaluate. For a senior software engineer, that might be: technical problem-solving, code review judgment, cross-functional communication, self-direction, and mentorship ability. Every question you write should tie back to one of these competencies.

Review the Resume Before, Not During

Read the candidate's resume and any work samples at least 24 hours before the interview. Note the specifics you want to explore: gaps in employment, transitions between industries, projects that look relevant, and anything that seems inconsistent. Coming into an interview without having read the resume is disrespectful to the candidate and makes you look unprepared - it also wastes the limited time you have together.

Prepare Your Question Set

Write out your questions in advance. For a structured interview, every candidate for the same role gets the same core questions in the same order. You can add follow-up probes based on their answers, but the foundation stays consistent. A typical 45-minute interview can cover five to seven substantive questions comfortably, with time for the candidate to ask their own questions at the end.

Step 2: Structure Your Questions Effectively

Behavioral Questions

Behavioral questions ask candidates to describe real situations from their past. The premise is simple: past behavior is the best predictor of future behavior. The STAR format (Situation, Task, Action, Result) gives you a framework for both asking and evaluating these questions.

Strong behavioral question examples:

• "Tell me about a time you had to deliver difficult feedback to a colleague. What was the situation, what did you do, and what happened?"
• "Describe a project that did not go as planned. How did you identify the problem, and what did you do about it?"
• "Tell me about a time you had to influence a decision without direct authority over the outcome."

When a candidate gives a vague answer, follow up with: "Can you give me a specific example?" or "What exactly did you do personally in that situation?" These probes separate candidates who have done the thing from candidates who know what the right thing to do is.

Situational Questions

Situational questions present a hypothetical scenario and ask what the candidate would do. They are useful for roles where the candidate may not have prior experience in a specific situation, or when you want to test judgment and reasoning. Example: "If you joined our team and within the first month discovered that our deployment process was creating recurring production incidents, how would you approach the problem?"

Technical or Skills-Based Questions

For roles requiring specific technical skills, include a component that tests those skills directly. This might be a brief coding exercise, a case study analysis, a writing sample, or a role-play scenario. Keep these focused - a 20-minute practical exercise tells you far more than an hour of talking about experience.

Questions to Avoid

Certain questions create legal exposure and have no legitimate relationship to job performance. Never ask about:

• Age, date of birth, or year of graduation (in age-discrimination contexts)
• Marital status, number of children, or family planning
• Country of origin, nationality, or immigration status (beyond right-to-work verification where required)
• Religion, political affiliation, or disability status
• Arrest records (as opposed to convictions, which may be relevant for specific roles)

If a candidate volunteers information you should not have, do not record it and steer the conversation back to job-relevant topics. In the US, EEOC guidelines govern much of this; in the EU, GDPR principles apply to how you collect and store candidate information.

Step 3: Set Up the Interview Environment

For In-Person Interviews

Book a quiet room without interruptions. Silence your phone. Have water available. Start on time - making a candidate wait in the lobby while you finish a meeting sends a message about how you treat people. Introduce everyone in the room clearly, including their role and why they are part of the interview.

For Video Interviews

Test your audio and camera 10 minutes before the call. Use a professional background or a clean, uncluttered space. Make sure your internet connection is stable. Log in early so you are ready when the candidate joins. If you are using an interview scheduling tool, confirm the candidate has the correct link and instructions in advance.

Step 4: Open the Interview Well

The first few minutes set the tone. A nervous candidate will not perform at their best, and you want to see their actual capability, not their anxiety. Start with a genuine, brief welcome. Explain the structure: "We have about 45 minutes today. I'll spend the first 30 asking you some questions about your experience, and then I want to leave the last 15 for your questions. Sound good?"

This small act of transparency - telling the candidate how the interview will work - reduces their anxiety dramatically and makes for better, more revealing answers.

Do not start with "Tell me about yourself." It is over-used and produces generic rehearsed summaries. Instead, pick a specific thread from their background: "I noticed you moved from agency-side to in-house fairly early in your career. What drove that decision?"

Step 5: Ask Questions and Listen Actively

Your job during the interview is mostly to listen. Ask a question, then stay quiet. Resist the urge to fill silence. Some candidates need a moment to think, and the best answers often come after a brief pause. Maintain eye contact and take brief notes - candidates understand you are noting important points.

When you probe, use open-ended follow-ups. "Can you tell me more about that?" is almost always a useful prompt. "What was your specific contribution, as opposed to the team's?" separates individual contribution from collective outcomes. "What would you do differently?" reveals self-awareness and growth mindset.

Watch for vague, generic answers that could apply to any situation. A candidate who answers every behavioral question with "we" rather than "I," who describes what should have been done without describing what was done, or who cannot provide specific details when probed is raising a yellow flag about the authenticity of their experience.

Step 6: Sell the Role (Without Overselling It)

The interview is also a sales conversation. Strong candidates are evaluating you just as much as you are evaluating them. Be honest about the challenges of the role. Talk about what makes your team good to work with. Describe what growth looks like. Vague promises like "tons of opportunities" or "we're like a family" raise red flags for sophisticated candidates who have heard those phrases before and found them hollow.

Specific, honest descriptions of the role attract candidates who are the right fit and help self-select out those who are not - which saves everyone time.

Step 7: Close the Interview Professionally

Always leave adequate time for the candidate's questions. Candidates who ask thoughtful questions about the role, team dynamics, success metrics, or company direction are showing genuine engagement. Candidates with no questions sometimes indicate low interest - though occasionally it means you covered everything thoroughly.

Before ending, tell the candidate what happens next: "We are interviewing through next week and will be in touch by [specific date] to let you know our decision." Then follow through on that timeline. Ghosting candidates is one of the most damaging things you can do to your employer brand.

Step 8: Score and Debrief Immediately

Score each candidate on each competency immediately after the interview, before discussing with other interviewers. Debrief discussions are valuable but can be dominated by whoever speaks first or most confidently. Independent scoring first preserves the integrity of diverse perspectives.

In the debrief, go around the room and share scores before anyone discusses. Then explore disagreements - they often reveal the most important information. One person rating communication a 2 and another rating it a 4 is a signal worth investigating, not averaging away.

A Simple Scoring Rubric

Use a 1-4 scale for each competency rather than a 1-10 scale. The middle (2-3) forces more discrimination:

• 4 - Strong yes: Candidate demonstrated this clearly with specific examples and impact
• 3 - Lean yes: Candidate showed evidence but with some gaps or limited depth
• 2 - Lean no: Evidence was weak, vague, or concerning in some way
• 1 - Strong no: Candidate showed clear deficiency or red flags in this area

Step 9: Make and Communicate Your Decision

Once you have completed your debrief and reached a decision, move quickly. Top candidates are typically interviewing with multiple companies simultaneously. The average time from application to offer across US companies is about 23 days - moving faster than that is itself a competitive advantage.

When you reject candidates, communicate clearly and promptly. You do not need to explain every reason in detail, but a clear "We have decided to move forward with another candidate" sent within 48 hours of your decision is far better than leaving people in silence. Rejected candidates who were treated well become brand ambassadors; ghosted candidates often do not.

Common Interview Mistakes to Avoid

• Talking too much: The candidate should be speaking 70-80% of the time. If you find yourself explaining the company for 20 minutes, refocus.
• Asking leading questions: "You're comfortable with Salesforce, right?" is not a question - it is an invitation to agree. Ask "Walk me through your experience with CRM tools" instead.
• Ignoring the notes you took: If you do not review and score your notes immediately after the interview, they lose value rapidly. Your memory degrades fast.
• Over-indexing on likability: Likable people who cannot do the job are worse hires than difficult people who can. Evaluate performance evidence, not charm.
• Comparing candidates to each other rather than the role: A candidate who is better than everyone else you have seen is still not a good hire if they are not good enough for the role.

Panel vs. One-on-One Interviews

Panel interviews, where two or more interviewers are present simultaneously, offer several advantages: they reduce individual bias, allow different perspectives to be tested in one session, and are more efficient for the candidate. The disadvantage is that some candidates find panels more stressful, which can suppress authentic responses.

A common hybrid approach is to use separate one-on-one interviews with different evaluators, each covering different competencies. A recruiter might assess motivation and culture fit; a technical lead assesses domain skills; a potential peer assesses collaboration style. This spreads the evaluation burden and reduces any single interviewer's outsized influence.

Legal Compliance Quick Reference

Across most jurisdictions, the legal test for any interview question is straightforward: is this directly relevant to the candidate's ability to perform the job? If yes, you can ask it. If no, you cannot. Keep records of your interview notes and scoring rubrics for at least one year after the hire decision. In the EU, candidates have the right to access data you hold about them under GDPR, so your notes should be professional and factual, not personal.

Conclusion

Conducting a good job interview is a learnable skill. It requires preparation, a structured question set, active listening, disciplined scoring, and respectful communication. The organizations that invest in these practices hire better people, build stronger teams, and suffer less from the costly cycle of bad hires and early turnover. Start with one change - write your questions before the interview rather than improvising - and add structure from there.