First-time hiring manager interview guide: before, during and after

A first-time hiring manager's interview job is narrower than it feels: decide what the role needs before meeting anyone, ask every candidate the same core questions, write down what they actually said, and score it before a general feeling takes over. You do not need recruiting training to do that well. You need a plan for the week before, the hour itself, and the hour after.

This guide walks through each, including the questions you must not ask. It assumes you interview a few times a month and work with a recruiter or HR partner, though most of it applies if you do not.

What changes when you are the one hiring

As an interviewer for someone else's team, a weak read costs little. As the hiring manager, you will manage the result every week, and the mistakes first-time managers make are predictable. The US Office of Personnel Management's structured interview guide lists the common ones, and three matter most for new hiring managers:

• Deciding in the first few minutes. The guide calls this relying on first impressions, and advises holding judgment until you have enough information. A confident handshake and a good opening story are not the job.
• Favoring people like you. The "similar to me" error: higher ratings for candidates who share your background, your school or your way of talking.
• Pressure to hire. When the team is stretched, you decide on too few candidates or too little evidence. An empty seat for another month is often easier to recover from than the wrong person for a year.

The fix for all three is the same: structure. The same questions, a written scale, and notes that record what was said.

Before the interview: the week-before checklist

Agree what the role needs

Sit down with your recruiter for an intake meeting before any interviews are booked. Leave with four to six competencies, which is the range OPM's guide gives for a typical structured interview, and for each one a sentence describing what strong looks like six months into the job. Split them into must-haves and nice-to-haves. Our list of intake meeting questions covers what to settle.

Read the resume with three questions

1. What did they own, and what did they contribute to? "Led", "managed" and "drove" cover everything from deciding to attending. Mark the claims your must-haves depend on.
2. Where is the evidence for each must-have? Note what you will ask to confirm it.
3. What is unclear? Scope, team size, what the company did. Write it down as a question, not a conclusion.

Do not score the resume. Its job is to tell you what to ask.

Write your questions and what a good answer sounds like

Most of your questions should ask about something the candidate actually did ("tell me about a time"), with one or two scenarios about the job ("what would you do if"). Write them down, and ask every candidate the same ones. Use this kit for a one-hour interview:

INTERVIEW KIT: [role], [date]
Must-haves: [C1], [C2]        Nice-to-haves: [C3], [C4]
Already covered by the recruiter: [compensation, notice, location, authorization]

OPENING (5 min)
  Introduce yourself and the role in two minutes.
  Explain the format: "I'll ask about five areas, I'll take notes,
  and we'll keep the last ten minutes for your questions."

QUESTIONS (35-40 min)
  Q1 [C1] Tell me about a time you [situation the job involves].
      Probes: What was the situation? What did you do, personally?
              What happened? What would you do differently?
      Strong answer includes: [2-3 observable things]
  Q2 [C1] [question]
      Probes / strong answer: [...]
  Q3 [C2] [question]
  Q4 [C2] [question]
  Q5 [C3] What would you do if [realistic scenario from the job]?
  Q6 [C4] [question, if time allows]

CANDIDATE QUESTIONS (10 min)
  Answer honestly, including what is hard about the role.

CLOSE (2 min)
  "You'll hear from [recruiter] by [day]." No hints about the outcome.

AFTER (15 min, blocked in your calendar)
  Score each competency from your notes before talking to anyone.

The probes follow OPM's guide, which organizes follow-ups around the situation, the action and the outcome. The rating scale belongs on the scorecard; the interview scorecard template has a 1–4 scale with anchors.

Book the logistics

• Block 15 minutes after each interview for scoring. Without the block, the scorecard gets written at the end of the week.
• Ask the recruiter to check whether the candidate needs any accommodation for the interview. The EEOC's guidance on pre-offer questions says employers may explain what the process involves and ask whether an applicant will need a reasonable accommodation for it.
• For video interviews, test your camera and have the candidate's phone number in case the link fails.

What you cannot ask, and what to ask instead

The EEOC's page on prohibited employment policies and practices says information requested during hiring should be limited to what is essential for deciding whether a person is qualified. The practical test: if the answer should not affect your decision, do not ask the question. The table below covers the questions that most often slip out.

On age: the federal regulation says asking for date of birth is not automatically a violation, but such requests are closely scrutinized. The federal age law protects people aged 40 and over. There is no good reason for a hiring manager to raise age in an interview. On pay, leave compensation to your recruiter; some states and cities ban asking about pay history, covered in salary expectation questions.

The small-talk trap

Most off-limits questions from new hiring managers are not asked on purpose. They come out of friendly conversation: "Oh, where's that accent from?", "Do you have kids? Mine are five and seven." Keep the small talk to the commute, the weather, the office. If a candidate volunteers something personal, acknowledge it, do not follow up, and leave it out of your notes. See what not to write in interview notes.

Running the hour

Follow the kit. The structure is what lets you compare candidates next week, when you no longer remember who said what.

Ask follow-ups until you hear what they did

First answers are rehearsed and usually about the team. The evidence is in the follow-ups:

• "What did you do, specifically?" when you hear "we". Ask it more than once if needed.
• "What happened next?" and "How did you know it worked?" when the story stops before the result.
• "Walk me through the first day." when an answer stays abstract.
• "What would you do differently?" Candidates who can answer this have usually thought about the work, not only rehearsed the story.

Redirect without being rude

If a candidate drifts, wait for a pause and say: "That's helpful. I want to make sure we get to everything, so let me take us to the next area." You are responsible for covering the kit; the candidate is not.

Take notes of what was said

Write short fragments in the candidate's words, next to the question number: "rebuilt the onboarding checklist after two new hires quit in month one". Do not write verdicts like "great energy". Tell the candidate at the start that you will take notes, then look up whenever they are mid-answer.

Sell the role honestly, at the end

Spend the last ten minutes on their questions. Answer the hard ones straight, including what is difficult about the team or the role. A candidate who joins on an honest picture is more likely to stay than one who joins on a pitch.

After: score within the hour

1. Before talking to anyone, including other interviewers, rate each competency from your notes on the agreed scale.
2. Write the evidence under each rating: what the candidate said or did, not your conclusion. Evidence-based interview feedback explains the method.
3. Mark anything you did not cover as "not assessed". Do not fill the gap with a guess.
4. Write your recommendation and the one thing you would still need to know. That line becomes the next interviewer's question or a reference check topic.

If typing notes while listening is the part you find hardest, Interview Signal captures the conversation on your own computer, with no bot joining the call, and builds a structured scorecard where each score carries the candidate's own words, checked against the transcript.

Working with your recruiter

A good recruiter makes a first-time hiring manager look experienced. Make it easy for them.

• Give feedback the same day. Candidates in other processes do not wait, and the recruiter cannot hold them without a signal from you.
• Send reasons, not a verdict. "No" does not help the next search. "No: could not give a first-hand example of running a budget, after two follow-ups" does.
• Pass on what the candidate asked. Questions you could not answer, concerns about the role, anything about timing.
• Ask the recruiter what they know: competing offers, compensation fit, how the candidate described the interview afterwards.
• Let the recruiter deliver the news, good or bad. It keeps the message consistent.
• Say early if the brief was wrong. If three strong candidates all miss the same must-have, the must-have may be the problem. Change it openly, for every candidate, not quietly for one.

When the interviews are done and you have two or three finalists, move on to how to compare candidates after interviews.

Your first-interview checklist

• Four to six competencies agreed with the recruiter, must-haves marked.
• Resume read with the claims to test marked.
• Same written questions for every candidate, each with probes and a strong-answer line.
• Accommodation checked; video link and phone number ready.
• No questions about family, health, religion, origin, age or anything else on the list above, including in small talk.
• Notes taken as the candidate's words, tagged by question.
• Last ten minutes for their questions, answered honestly.
• Close with the next step and a date, no hints.
• Scorecard written within the hour, before talking to anyone.
• Feedback with reasons sent to the recruiter the same day.