Hiring Manager
Role
The manager who defines why a role is needed and makes the final call on candidates, because the person hired will work on their team.
Why it exists
When hiring belonged entirely to the people team, companies kept running a full process and ending up with nobody hired. The people team posted the role and gathered the applicants, but the only person who actually knew what the role required was the manager who would hand out the work. With no written answer to where the decision sat, applications lingered on every desk equally.
The same scene repeated itself. A recruiter forwards ten applications; the manager, busy with something urgent, opens them three days later. After the interview the only feedback is "they seemed fine," which is not a yes or a no. Meanwhile the candidate takes an offer somewhere else, and two weeks later, when a decision finally arrives, there's nobody left to give it to. The people team says the manager never looks; the manager says the right people never show up. Neither of them is lying.
The hiring manager role fills that gap by naming someone. Every open role gets exactly one person who owns the outcome, and that person carries everything from writing the requirements to making the final call. One role, one name, written down where everyone involved can see it. Running the process and deciding what the team needs stay separate jobs — but the second one now has an owner.
A day in the job
Most of the day goes into reading candidates, meeting them, and reaching conclusions. From the day a role opens to a new hire's first morning, roughly six things land on this person.
- Define the requirements. What the role will own and what someone needs to be able to do goes into the job description (JD). The three lines written there become the three things interviewers check, so vagueness here blurs every judgment downstream.
- Read applications. Screening isn't about who is most impressive; it's about whether anything in the application overlaps with what the role asks for. Not letting a pile sit longer than a day is close to the baseline skill of this job, and the fastest way to build that habit is to read in short daily passes rather than saving them all for one long afternoon.
- Design the interviews and sit in them. Divide up who checks what in the technical interview so the candidate doesn't answer the same question three times.
- Run the debrief. Every interviewer puts their read on the table with the evidence behind it, and the pass-or-no decision gets made in that room. Push it to next week and memory turns into impression.
- Decide whether to extend an offer and where to land the terms. The salary band usually comes from the company; placing a candidate inside it is this person's judgment.
- Prepare the first three months once someone accepts. From here the work stops being hiring and becomes managing.
Between all six sits the job of keeping things moving. Half of what stretches time to hire isn't a shortage of candidates — it's decisions waiting on this desk. Strong candidates are almost always talking to several companies, and one reply sent three days late is enough to lose them.
Who they work with
The closest working relationship is with the recruiter. The recruiter finds candidates, schedules, and keeps the process moving; the hiring manager decides what to look for and judges the people who show up. The two sit down at least weekly to look at how many candidates are at which stage. When "good candidates aren't coming through" gets said in that meeting, what follows is either narrowing the requirements or changing the sourcing channels.
Then there are the colleagues who interview. They have their own jobs and are lending time, so handing each of them a clear slice is this role's responsibility. Send them in with "take a look and let me know what you think" and three people examine the same thing while nobody covers the rest.
To a candidate, this person is the company. From the quality of the questions and the wait for an answer, candidates infer how the team works. That's why sending rejections also belongs to this job rather than getting delegated away.
With leadership the conversation is about the role itself. Nothing opens until headcount is approved, and a seat still unfilled after six months gets pulled back into a conversation about whether it's still needed. At Pagedeck, Grace runs that review once a quarter.
How it sounds at work
"Who's the hiring manager on this one? I think we need to redo the requirements first."
Nothing can be discussed until the person who owns the decision is identified.
"Twelve applications, sitting three days. These need to be read today."
The reason candidates are being lost is right here, at this desk.
"The interviewers disagree, but the hiring manager makes the call."
A statement that a split panel won't be settled by vote.
When Pagedeck opened a sales role, Sofia took this job. The draft description came back with three required qualifications: three years of experience, sales background, strong communication. Sofia's view was that those three lines gave interviewers nothing to ask about, so she replaced them with having explained an early-stage product to a customer for the first time.
Changing one line changed everything after it. Screening now had a real filter and the pass rate halved. Interviews turned into one long question about a specific customer at a previous company and how that person had been convinced. Even with a smaller pool, the time to a signed acceptance came down by three weeks.
What people get wrong
The most common assumption is that the people team does the hiring and the manager just shows up to interviews. Since the people team posts, schedules, and corresponds, almost all the visible effort does come from there. But only one person knows what the role actually needs, and if that knowledge never reaches the job description or the interview questions, the people team is collecting candidates without a direction. Left alone, this ends with twenty interviews, no hire, and a quarter closed out blaming the market.
Reading the role as filtering people is only half of it too. Judging is one side; selling is the other. A finalist is usually in conversation with other companies, so explaining what they'd get to work on here and helping them decide belongs to the same person. Filter without selling and the share of offers that get declined climbs, and each declined offer costs another six weeks because the search restarts from an empty pipeline.
Easily confused with
| Term | What they own | How it differs |
|---|---|---|
| Recruiter | Finding candidates and running the process | Carries many roles at once and doesn't decide who passes. A hiring manager carries one role and makes the final call |
Where to go next
- Hiring
see the sequence of stages this role sits on top of
- Job description
look closely at the first thing this role produces
Last updated 2026-09-16