Hiring manager satisfaction survey

A hiring manager satisfaction survey measures how a hiring manager experienced the recruiting process on a specific search — communication, candidate quality, speed, how well their requirements were understood — not how the person who was eventually hired is performing on the job. Confusing the two produces a number that cannot tell a slow, frustrating process that happened to end in a good hire apart from a smooth process that ended in a mediocre one.

For the survey that measures the hire's actual performance, see the quality of hire survey template. For the commitments this survey often ends up checking, see the recruiting SLA with hiring managers.

What this survey measures, and what it does not

This survey is about the recruiting service: did the recruiter understand the role, did candidates match what was asked for, was the manager kept informed, did the process move at a reasonable pace. It says nothing about whether the eventual hire turns out to be good at the job, which depends on factors well outside the recruiter's control. Keep this survey's results and the quality-of-hire data in separate tracking, even though both eventually inform how well recruiting is working, because a manager can be delighted with the process and unhappy with the hire, or the reverse, and both combinations are useful to see clearly rather than blended into one score.

The per-requisition survey

Hiring manager satisfaction survey — [requisition title/ID]
Recruiter: [name]      Closed: [date]      For: [hiring manager name]

Rate each 1 (strongly disagree) to 5 (strongly agree).

1. The recruiter understood what I actually needed for this role.
   [1] [2] [3] [4] [5]
2. The candidates submitted matched what I was looking for.
   [1] [2] [3] [4] [5]
3. I was kept informed of progress without having to chase for updates.
   [1] [2] [3] [4] [5]
4. The process moved at a reasonable pace given the role.
   [1] [2] [3] [4] [5]
5. I would want to work with this recruiter again on a future search.
   [1] [2] [3] [4] [5]

6. What was the single best part of working with recruiting on this search?
7. What is the one thing that would have made this search go better?

The quarterly relationship survey

Hiring manager satisfaction survey — quarterly
For: [hiring manager name]      Quarter: [Q_ 20__]      Recruiting team/recruiter(s): [names]

1. Across the searches this quarter, recruiting understood my team's needs.
   [1] [2] [3] [4] [5]
2. I trust recruiting's read on a candidate's fit for my team.
   [1] [2] [3] [4] [5]
3. Recruiting sets realistic expectations about timeline and candidate availability.
   [1] [2] [3] [4] [5]

4. What should recruiting keep doing?
5. What should recruiting change?

Scoring and aggregating across recruiters

Convert each 1-5 answer to a 0-100 scale and average the numeric questions for a per-requisition score. Track this by recruiter over a rolling quarter rather than reacting to any single response, since one difficult manager or one unusually hard search can pull a single score down without reflecting the recruiter's typical work. Watch the trend and the pattern of short answers more than any individual number: a recruiter whose scores dip specifically on searches for one department, or specifically on the "kept informed" question, has a narrower, more fixable problem than a recruiter whose scores are randomly scattered across every question.

A filled example

Using the results without it becoming a scorecard nobody trusts

Share aggregated, trended results with each recruiter privately first, before any team-wide reporting, so the conversation starts as coaching rather than public ranking. Where a pattern points to something structural — a chronically understaffed desk, a role type that always runs behind because of an internal approval bottleneck outside the recruiter's control — say so explicitly rather than letting a low score sit on an individual recruiter's record for a problem that was never theirs to fix. This is also where the results connect naturally to a recruiting SLA: a consistent "not kept informed" pattern across several recruiters points to a process gap worth fixing with an actual commitment, not just individual coaching.

Timing and response rates

Send the per-requisition version within a few days of the role closing, while the search is still fresh in the manager's mind, and keep it short enough to finish in under two minutes. Send the quarterly version on a fixed calendar date rather than triggering it from an event, so managers get used to the rhythm. If response rates are low, ask a few managers directly what would make it worth their time to respond rather than assuming the survey itself is unnecessary; a five-question form sent at the wrong moment gets ignored for reasons that have nothing to do with its content.

Reading a low score fairly across different req types

Segment scores by role difficulty before drawing conclusions about a recruiter's performance. Averaging a recruiter's easy and hard searches together hides the fact that a recruiter handling the team's hardest reqs will structurally show lower satisfaction scores than one handling routine, high-volume roles, even if both are doing equally strong work.

How this differs from other feedback loops

Recruiting teams sometimes already collect informal feedback through exit interviews, ad hoc Slack messages, or a manager mentioning something in a hallway conversation. None of that replaces a structured survey, because informal feedback is unevenly distributed: managers who are frustrated are more likely to say something unprompted than managers who are satisfied, which skews what leadership hears toward complaints. A structured survey sent to every manager after every closed requisition captures the quiet majority who would never otherwise volunteer an opinion, and it is the only version of this feedback that can be tracked as a trend over time rather than a scattered set of anecdotes.

Common mistakes

The most common mistake is only surveying managers whose searches went well, because the recruiter sends the survey themselves and quietly skips the ones that were rocky. Automate the send so it goes out for every closed requisition regardless of how it went, or have someone outside the recruiting team trigger it. A second mistake is treating a single low score as a performance issue before checking whether the search itself was unusually hard — a role with a narrow, hard-to-find skill set or an unrealistic budget will produce lower satisfaction scores than an easy req almost regardless of the recruiter's skill, and comparing those two scores directly is not a fair comparison. A third is never closing the loop: collecting the "what would have made this better" answers and never changing anything visible in response teaches managers that the survey is a formality, and response rates decline accordingly.

A fourth mistake is running this survey through a general employee engagement platform's generic template instead of the specific questions above. Generic satisfaction questions ("how happy are you with HR services") produce a vague number that cannot be traced back to a specific recruiter, a specific requisition, or a specific fixable behavior. The value of this survey comes entirely from being tied to a real search a manager just went through, answered close enough to the event that the details are still fresh and specific rather than a general impression built up over a year of scattered interactions.

Reporting results without turning it into a leaderboard

Share trends with the recruiting team as coaching input, not as a ranked list posted for everyone to see. A public leaderboard built from this data creates an incentive to chase the score itself — for example, only sending the survey after searches that clearly went well — which defeats the purpose of measuring the real, full range of experiences managers are having. Keep the reporting private between a recruiter and their manager, and reserve any team-wide sharing for aggregated, anonymized trends that cannot be traced back to an individual recruiter's number.