Skip to content

How to prepare a hiring manager for a second interview

Round two should test what remains unresolved, not ask the candidate to repeat the first conversation.

· 11 min read

An open folder of briefing documents for a hiring manager.

Preparing a hiring manager for a second interview means showing them what the first round already established and what still needs to be tested.

Give the manager a clear purpose for round two. Summarise the candidate’s relevant evidence, name the important questions still open and link to the original answers. That prevents the next interview from becoming another “talk me through your background” conversation.

What should a second interview cover?

Ask the manager: “What do you still need to know before deciding?” Translate “another opinion” into the skill, decision or expectation they will examine.

For this customer-success role, suppose the agreed requirement is to investigate an adoption problem and choose a response, not simply arrange training. That distinction determines the follow-up questions.

Start with this sample first-round answer:

A customer's team was barely using our software. I spoke with them and arranged a training session, which they attended.

You know that the candidate spoke to the customer and organised training. You do not yet know why the software went unused, who chose training or whether it helped.

Use those gaps to plan the next interview:

What you already know What to ask next
The customer was barely using the software. “Why weren't they using it?” Then: “How did you find out?”
The candidate arranged training. “Who decided training was the answer?”
Training took place. “What changed afterwards?”

These questions reveal different things. The first explores how the candidate investigated the problem. The second clarifies whether they chose the response or organised someone else's plan. The third checks whether they followed up.

Use any answer already collected in the first round. Ask only about the gaps that still matter; the three questions are not a script to repeat regardless of the earlier conversation.

What should a hiring manager's second-interview brief include?

Include the role, the relevant first-round answer, what remains unclear and a link to the source. The manager needs enough context to ask a useful next question, not another copy of the CV.

The brief could say:

Role and requirement: Customer success; investigates low adoption and chooses an appropriate response.

Already covered: The candidate spoke to the customer and arranged training. The team attended.

Focus for this interview: Establish the cause, the candidate’s part in choosing training and how they checked the result.

Do not assume: Attendance proves the original problem was solved.

Source: [Application link, interview date and relevant answer].

Decision afterwards: Record whether the evidence meets this requirement, with any essential question still open.

Check that the manager can open the linked answer using their own account. Identify the job and interview date, especially when the person has more than one application.

Keep “arranged training” distinct from “diagnosed the problem”. The brief should preserve the question round two needs to answer, not resolve it through an enthusiastic summary.

Screened interviews provide a transcript, topic summaries and an assessment. Use the candidate's words to check an important claim before passing it to the manager. A summary is useful preparation, not independent proof that the past event happened.

Should you share the first interviewer's rating?

Give the next interviewer the information they need without automatically giving them your conclusion. “Ask how they checked the cause” helps them prepare. “Excellent judgement; likely a hire” tells them what to think.

GitLab's interviewing guidance allows specific notes for later interviewers while restricting fuller feedback according to the person's role. It is a useful example of separating preparation from earlier verdicts.

Use your own agreed interview process. Where ratings should be withheld, check the notes, profile fields and report links the interviewer can see. Removing a rating from the brief does not hide it elsewhere.

Follow the answer, rather than repeating the first interview

The manager could begin:

You mentioned arranging training for a customer. I'd like to understand what led to that. Why weren't they using the software?

Listen to the answer, then ask:

How did you find that out?

Follow the responsibility the person describes. Someone who organised a colleague's training plan can explain how they made it work. Someone who investigated the problem can explain what they found. Those are different contributions to assess against your vacancy.

Compare two possible replies:

“Usage was low, so I booked training.” You still do not know why the team was not using the software. Ask what made them think training would help.

“I asked three team members to show me how they used it. They could sign in, but none knew how to produce the weekly report they needed.” This describes a check and a specific obstacle. Ask what the candidate did next and whether the team could produce the report afterwards.

Continue the second answer with “What did you do next?” The candidate replies:

I recommended a session on producing that report. Afterwards I asked each person to prepare one. Two could do it; the third was missing access to a field, so I asked the administrator to correct the permission. I had not checked again before moving accounts.

The manager now has evidence of investigation, a targeted response and a check that revealed an unresolved access problem. Training attendance alone supplied none of that. The record should preserve the remaining uncertainty, not claim the whole customer problem was solved.

Ask one question at a time. “What happened afterwards?” allows an incomplete result; “How did your training solve it?” assumes success.

Is it ever useful to repeat a first-round question?

Yes, when the repetition has a purpose. A specialist may need to examine the method in more detail. A genuine contradiction may need clarification. Your interview design may call for a separate example.

Explain that purpose:

I read your account of arranging the training. I'd like to focus on what happened afterwards. How did you check whether it helped?

That builds on the earlier answer. It does not require the candidate to repeat their career history.

Use the same job requirements for everyone, but follow what each person has already explained. One candidate may still need to describe their decision; another may need to explain the result.

A different retelling is not automatically a contradiction. Check a specific difference that matters rather than expecting the person to repeat the same words.

Add a short exercise only for a skill you still need to see

Suppose the earlier conversation did not show how the applicant tells a customer that the product cannot do what they need. A brief exercise can cover that question.

Agree the task, time allowance, permitted tools and adjustment arrangements before using it. Give every applicant the same starting facts. Use a sample customer case for the interview exercise:

A customer has finished training but still finds the software difficult to use. Their team has to type the same details into two systems because those systems do not share information.

Your company has not agreed to fix this. The customer's contract renews next month. You can promise an update by Thursday, but not a fix.

What would you tell the customer today?

One reasonable reply is:

I understand that your team is still entering the same information twice. More training will not remove that extra work.

Could you show me the steps involved? I'll ask our product team whether there is another way to do it and update you by Thursday. I cannot promise a fix at this stage.

Ask what work would happen between that message and Thursday's update. The answer should connect the promised response with a specific product-team check and someone responsible for replying.

Follow-up: no fix is available

Next, tell the applicant that the product team has confirmed there is no available feature that removes the duplicate entry. Ask for the promised customer update. The renewal decision depends on hearing that limit clearly.

A suitable reply could be:

I've checked with our product team. We don't currently have a feature that removes the double entry, and no fix has been agreed. I want you to have that answer before making your renewal decision. We can talk through how much work remains, but I can't promise it will disappear.

Compare the response with the brief, not with the sample's phrasing. The applicant needs to state the limitation, acknowledge the work it leaves for the customer and avoid promises they cannot authorise.

The next task is preparing an honest renewal discussion. Ask what the applicant would learn about the customer's priorities and which colleague they would involve. A discount may need separate approval; it would not remove the extra data entry. Listen for a plan that addresses the customer's actual difficulty rather than changing the subject to a sales concession.

Optional alternative: a workaround still leaves daily work

Instead of the no-fix follow-up, say an export reduces typing but the customer must upload a file every day. Ask the applicant to explain the remaining work and what they would check before recommending it.

Use this variation when evaluating partial solutions is relevant to the job. Do not add every variation to the same short interview. Record any help given beside the answer.

Leave time for the candidate's questions

The candidate also needs to know whether your team can support them. A reasonable question is: “What would your company do when a customer needs a feature you cannot provide?”

Explain who makes product decisions, who handles difficult renewals and what help the person would get. Bring in a colleague when you cannot answer.

Do not treat questions about workload or support as a lack of enthusiasm. They are part of deciding whether the job is a good match.

A 30-minute agenda the manager can use

Allow two minutes to explain the focus, ten to explore the earlier example, ten for one short exercise and eight for the candidate’s questions and next steps.

Choose the exercise and at most one necessary follow-up in advance. The agenda is not long enough for every possible variation. Skip the exercise when existing evidence already covers the skill, or book longer when the task needs it.

For one interviewer, five minutes of preparation and five for feedback make 40 minutes of staff time around the 30-minute call. Reserve those minutes too.

What if the manager has not read the first-round notes?

Give the manager the short brief and check access to the original notes. Be honest about missing information rather than making the candidate restart without explanation:

I have the summary of your first interview, but I couldn't open the full notes. I'd like to continue with your customer example. Please correct anything I've misunderstood.

Continue only with questions the available information supports, and ask the coordinator to recover the missing notes. If an essential part remains unassessed, record that limitation and arrange the focused follow-up needed. The candidate should not receive a lower rating because your team could not open its own notes.

When notes are available but the manager has not read them, address preparation before the candidate joins. Use the recovery wording only for a genuine access problem, not as an excuse to say a link failed.

For the next interview, fix the actual cause: access or time to prepare. A longer brief will not resolve either by itself.

Write down what this interview added

A useful note describes the answer, not just the interviewer's confidence. For the exercise, it could say:

The candidate asked to see the repeated work and said they would check with the product team. Their reply promised a Thursday update without promising a fix. We did not assess price negotiation.

Compare that with “I agree they are strong.” The first tells the team what was assessed and what remains open. The second does not.

Have interviewers record ratings and reasons before the debrief. For the worked history example, the added finding is specific: the applicant checked the users’ difficulty, recommended targeted training and tested whether they could produce the report. One person still needed an access fix, and its outcome was unknown.

Compare that with the round-one note, which established only a conversation and attendance. Round two has added evidence of the agreed work, not merely another interviewer’s favourable impression.

Compare both rounds' notes before arranging another interview. What did the second round establish, and what important question is still open? Reuse an existing work sample or arrange a focused check where needed. Do not book a third broad conversation simply because nobody has made the decision.

Ask candidates separately which parts they had to repeat. Use that feedback to improve preparation and handovers, not to assess suitability.

A useful second interview moves both decisions forward: whether you should hire the person, and whether they want to join the team.