Hiring manager vs. recruiter: who actually owns the decision

Ask a hiring manager and a recruiter to describe who owns a hiring decision and you will usually get two different answers delivered with equal confidence. The hiring manager says they make the final call because they will manage the person. The recruiter says they drive the process because they run the funnel, screen the candidates, and keep the req moving. Both answers are partly true, and the gap between them is exactly where good candidates slip through the cracks.

This is not a trivial org chart question. The cost of a bad hire runs into tens of thousands of dollars, and a meaningful share of bad hires trace back to a process where nobody was clearly accountable for a specific decision at a specific stage. A strong candidate who sits in limbo for a week while a recruiter waits on a hiring manager who thinks the recruiter is still vetting is not a hypothetical. It happens on nearly every req where the two roles were never explicitly divided.

The confusion is understandable because the two roles genuinely overlap, and they are supposed to. The problem is not overlap. It is unspoken overlap, where both people believe they hold a piece of authority the other person also believes they hold, and nobody finds out until a deadline is missed or an offer goes out with the wrong terms attached.

What a recruiter is actually on the hook for

A recruiter owns the machinery of the search: writing or refining the job posting, building the sourcing strategy, running outreach to passive candidates, screening inbound applicants, and keeping the pipeline moving so a req does not quietly stall. How to recruit passive candidates and how to reduce time to hire both live squarely inside this part of the job, and a good recruiter is judged on whether qualified people are entering the funnel and moving through it at a reasonable pace.

A recruiter also owns the candidate experience end to end, which is a bigger job than it sounds. That includes setting expectations about timeline, following up promptly, coordinating interview logistics, and closing the loop with candidates who do not advance. None of this requires deep subject-matter expertise in the role being filled. It requires process discipline, which is a different skill than the one the hiring manager brings to the table.

What a recruiter does not own, or should not, is the final call on who gets the offer. A good recruiter builds a shortlist of qualified people, surfaces a recommendation based on what they have seen across the funnel, and pushes back when a hiring manager's instincts conflict with what the data in the process actually shows. But the recruiter is not the person who has to manage this hire's output for the next two years, and pretending otherwise sets up a recruiter to make a call they are not positioned to own.

What a hiring manager is actually on the hook for

A hiring manager owns the definition of the role and the final decision on who fills it. That starts earlier than most hiring managers treat it: a vague, rushed job description handed to a recruiter without real input is the first failure point in a surprising number of bad searches, because a job description that does not clearly reflect what the role actually requires sends the recruiter chasing the wrong profile from day one.

The hiring manager also owns the interview itself, not just the yes-or-no at the end of it. That means showing up prepared, asking questions that actually test for the skills the role requires, and giving the recruiter real feedback after every interview rather than a vague thumbs up or thumbs down. A structured interview process only works if the hiring manager treats their part of it with the same discipline they expect from the recruiter's part.

Most importantly, the hiring manager owns the speed of their own decisions. A recruiter can build a perfect pipeline and still lose a strong candidate to a competing offer because the hiring manager sat on interview feedback for a week. The decision authority that comes with being the hiring manager is not free. It comes with an obligation to actually use it promptly, and a hiring manager who treats the recruiter as responsible for chasing them down for feedback has quietly shifted blame for a failure that was theirs to prevent.

Where the split breaks down in practice

The theoretical division of labor above sounds clean. In practice it breaks down at a handful of predictable moments, and almost every one of them comes from an assumption nobody said out loud. The first is scope creep on the job description: the recruiter builds a search plan around what was written down, the hiring manager starts rejecting candidates for criteria that were never in that document, and both people believe the other one is the problem.

The second is feedback timing. The recruiter assumes silence means the hiring manager is still deciding. The hiring manager assumes silence means the recruiter is still screening more candidates. Days pass, the candidate accepts another offer, and the postmortem reveals that both sides were simply waiting on the other.

The third, and the most damaging, is disagreement about final authority after an interview panel is split. If a recruiter and a hiring manager have never explicitly agreed on who breaks a tie when interviewers disagree, that disagreement gets litigated for the first time in the moment it matters most, under time pressure, with a candidate waiting on an answer. Recruiting metrics that actually matter will show you a slow time-to-decision number months later, but by then the damage to that specific search has already been done.

A decision rights model beats a job description

The fix is not a better job description for the recruiter role or the hiring manager role. It is an explicit decision rights model, agreed before the req opens, that names who has final say at each stage rather than leaving it to be inferred from title. Harvard Business Review's research on decision rights in organizations is built on a simple insight that applies directly here: when more than one person has a plausible claim to a decision and nobody has formally resolved whose claim wins, the decision takes longer and the outcome is worse, regardless of how capable either person is individually.

In practice this means writing down, for every req, who decides whether a candidate advances past the phone screen, who decides whether to extend an offer, who decides on compensation within a pre-approved band, and who has the tiebreaker if the hiring manager and recruiter disagree on a borderline candidate. This takes fifteen minutes at kickoff and eliminates the single most common source of friction in the recruiter-hiring manager relationship.

The specific split does not need to look identical across every company. What matters is that it is explicit and that both people have actually agreed to it rather than silently assumed their own version of it. A recruiter and a hiring manager who have never had this conversation are not in alignment just because neither one has complained yet.

Why the confusion gets worse on lean teams

This problem is often worse, not better, at smaller companies, which is counterintuitive given how much more informal communication is possible on a small team. When to hire your first in-house recruiter covers the specific moment many growing companies face: a hiring manager has been doing their own recruiting out of necessity, and the moment a dedicated recruiter joins, nobody has actually renegotiated who owns what. The hiring manager keeps acting like the recruiter is a scheduler. The recruiter, trying to prove value fast, starts making calls that were never explicitly theirs to make.

At companies without a dedicated recruiter at all, the same confusion shows up between a founder and whoever else is involved in hiring, whether that is a co-founder, an early employee sitting in on interviews, or an outside agency. How to hire when you are a team of one is really a guide to wearing both roles consciously rather than letting one half of the job quietly disappear because nobody was assigned to own it.

The instinct on a lean team is to assume informality is more efficient than a documented process. For most things, it is. For decision rights on hiring, informality is exactly what produces the ambiguity this article is describing. A five-minute conversation at the start of a search costs almost nothing. A week of a strong candidate sitting in limbo because nobody knew who owed them an answer costs a great deal more.

The weekly cadence that keeps both sides honest

A decision rights model solves the structural problem, but it does not solve the day-to-day drift that happens over the life of a search. The practical fix for that is a short, recurring check-in, ideally weekly, where the recruiter reports exactly where every active candidate sits and the hiring manager commits to a specific date for any decision that is theirs to make. This is not a status meeting for its own sake. It exists specifically to prevent the silence that both sides otherwise interpret as the other person's job to break.

LinkedIn Talent Solutions research on recruiter and hiring manager alignment consistently finds that the single biggest driver of hiring manager satisfaction with their recruiting partner is not sourcing quality. It is communication frequency and clarity about where things stand. Hiring managers tolerate a smaller pipeline far better than they tolerate not knowing what is happening with the pipeline they have.

The same research cuts the other way too. Recruiters report their biggest frustration is hiring managers who go quiet on feedback, and a standing weekly touchpoint is one of the few process fixes that measurably reduces that specific complaint, because it creates a forcing function for feedback that would otherwise be put off indefinitely.

Fixing it when the relationship is already strained

If a recruiter and hiring manager are already a few bad searches into a strained relationship, the fix is not a new tool or a new process document. It is a direct conversation about where things actually broke down, with both people willing to admit their own half of it. The recruiter who has been quietly resentful about slow feedback and the hiring manager who has been quietly resentful about a thin pipeline are usually both partially right, and neither grievance gets resolved by avoiding the other person.

SHRM's guidance on talent acquisition partnerships treats the recruiter-hiring manager relationship as a genuine internal client relationship, not an administrative handoff, and that framing is useful here. A strained client relationship gets fixed with an honest conversation about expectations, not with the client quietly working around the vendor or the vendor quietly lowering their effort. The same applies internally.

The companies that get this right are not the ones with the most sophisticated recruiting technology. They are the ones where a recruiter and a hiring manager can name, specifically, who owns what, without hesitating or contradicting each other. That clarity does not happen by accident, and it does not happen once and stay fixed. It is a conversation worth having explicitly at the start of every search that matters, not just the ones where it has already gone wrong.