HR Manager
Role
The person who runs human resources end to end — hiring, employment contracts, payroll, leave, and the operation of review and pay cycles.
Why it exists
At ten people this work is not attached to anyone. The founder runs the interviews, the employment contract is a template someone found online and edited, and payroll is a calculation the founder does once a month before sending transfers. Time off is a message in a group chat saying "out tomorrow."
What breaks it is not headcount but variety. Someone asks about parental leave. Someone's probation period is ending. Someone wants to reopen the conversation about their salary. Each of those touches employment law, internal policy, and fairness across everyone else at the same time, and nobody has been named to answer them.
Pagedeck ran into this around thirty people. An employee two months in asked how many vacation days they had, and neither Grace nor any of the team leads knew. Leave accrues month by month for people in their first year, and nobody was tracking it and nothing was written down. Three days later the same question got a different answer.
An HR manager is the seat those scattered pieces get collected into. The reason to collect them is consistency more than efficiency. The same question has to produce the same answer, and the standard applied to one person last month has to apply to the next person this month, before how the company treats people becomes something anyone can predict.
A day in the job
Everything from hiring to the last day of employment — every step a person passes through from joining to leaving — belongs to this seat. It breaks into five blocks.
- Running recruitment. A team says it needs a seat filled; the HR manager sharpens and posts the job description, organizes applications for the team, schedules interviews, and issues the offer that states the terms of joining. With no dedicated recruiter in the company, finding and contacting candidates directly lands here too.
- Processing arrivals and departures. Contracts, statutory registrations, equipment and accounts make up employee onboarding at the front end, while handover, access removal, and final settlement make up offboarding at the back. Both are run from checklists, because a missed step turns into a legal or security problem immediately.
- Clearing the work that returns on a fixed date every month. Calculating and paying salaries, reconciling statutory contributions, year-end tax filing, tracking leave as it accrues and expires. At around forty-five people a payroll run takes about two days, and longer in a month with mid-cycle joiners and leavers.
- Operating policy and writing it down. Work rules, leave policy, and the work arrangement that fixes where and when people work get documented and updated whenever they change. An undocumented policy gives a different answer to each person who asks, and that difference turns into a fairness complaint.
- Running the review and compensation cycles. Announcing the schedule, distributing the forms, collecting results, reflecting salary changes in contracts. What gets evaluated is decided by leadership and team leads; making it happen on time and to one standard is what this seat contributes.
Blocks 1 and 3 take the most hours. Blocks 4 and 5 are what people remember. Nobody mentions that payroll arrived on time; a policy applied differently to two people is still being discussed a year later.
Who they work with
Almost every seat in the company crosses this one, but in four distinct ways.
- Leadership — headcount plans, total salary cost, and reorganizations, all of which put money and structure on the table. At Pagedeck the HR manager and Grace settle the quarter's hiring numbers together: HR builds the proposal, leadership makes the call.
- The team that asked for the hire — that team knows what kind of person it needs; translating that into a posting and an interview process is HR's part. When the two drift apart, you get months of applicants arriving and every one of them failing the interview.
- Individual employees — the front door for leave, pay, contracts, and complaints. What gets said here stays here by default, with the exception of matters the company is obliged to act on, such as harassment or safety. Saying where that line falls before listening is part of the job.
- Outside specialists — employment lawyers, accountants, recruiting agencies. When the law changes or a dispute starts, the company does not decide internally; it hands the question over.
As a company grows, the block splits apart. A recruiter who does nothing but hiring goes first, then an HR business partner (HRBP) attached to a single division, then people operations taking on policy design. A chief human resources officer (CHRO) sits above all of it.
How it sounds at work
"Let me check with HR and come back to you — this isn't something I can decide on my own."
The question touches employment terms or policy, so there is a fixed standard to check against.
"HR will handle the posting and scheduling for this one; we'll take the interviews."
A split between running the process and making the judgment.
"We don't have an HR manager yet — the founder still covers it."
Often also a statement that none of the company's people policies are written down.
Pagedeck hired its first HR manager at thirty-two people. What that person did for three months was not build new policy but gather what already existed. Three different contract templates became one, leave balances that had been calculated differently for different people were recomputed from each person's start date, and time-off records scattered through chat moved into a single table.
Three months in, "who do I even ask about this?" had disappeared as a question, and the time team leads spent answering HR questions dropped with it. Not one visible new policy came out of that quarter, and it was still the clearest demonstration of what the seat is worth.
What people get wrong
The most common assumption is that an HR manager is the person who hires. Since an interview is where most people first meet the role, it sticks easily. In practice hiring is one of five blocks, and payroll, contracts, and policy operation fill the rest. Hire for recruitment alone and two months later nobody owns payroll or statutory filings, and that work goes back to the founder.
The other one is that HR works for the company, so raising anything with them puts you at a disadvantage. The role is employed by the company and enforces its policies, so the reading is understandable. What the work actually consists of is not picking a side but making one standard apply to everyone. That said, it is not a role that can promise total confidentiality either. Matters the company must act on do go up, and the distrust appears precisely when nobody said so beforehand.
Easily confused with
| Term | What they own | How it differs |
|---|---|---|
| HRBP | Solves people problems alongside one specific organization | The scope is one division rather than the whole company. Not a seat that writes policy but one that applies it to that organization's situation |
| People operations | Designs the employee experience and the policies behind it | Works on the process rather than the case. Not the person receiving a leave request but the one redesigning how leave works |
| CHRO | Leads the entire people organization | An executive seat deciding total salary cost and org structure, not one running day-to-day operations |
Where to go next
- People
see the full map of the work this seat is responsible for
- People operations
the same territory viewed from policy design, and where this role splits as a company grows
Last updated 2026-09-16