Topic 2 — Recruiter vs. HR vs. People Ops

Goal: Distinguish recruiting from related people roles, and in-house from agency.

Lesson 2.1 — Recruiting vs. HR

Two weeks into her first tech-recruiting role at Northwind Robotics, Yara gets pulled into a Slack thread by mistake. An engineer's paycheck came through short, and someone tagged "the recruiting team" to fix it. Yara types the most useful sentence of her early career: "That's a People Ops question — I'll loop in Pri." That paycheck was never hers to touch.

Here's the line she'd just learned. Recruiting — also called Talent Acquisition, or TA — is the work of finding and hiring new people. Getting them in the door. Yara's whole job lives before someone's first day: sourcing, screening, walking candidates through interviews, closing the offer.

HR (Human Resources) is the broader function that takes over after the hire. Payroll, benefits, policies, employee relations, compliance, the awkward conversations and the annual reviews. The short paycheck belonged to HR, not to Yara.

Recruiting brings people in. HR takes care of them once they're here.

Yara, who spent three years as a sales SDR before this, finds the comparison clicks instantly. Recruiting is like sales: chasing, persuading, closing, always working a fresh pipeline of people who aren't here yet. HR is account management: the customer already signed, and now the job is keeping them happy, paid, and out of legal trouble. Same company, two very different clocks.

Lesson 2.2 — What "People Ops" actually means

On her first day, Yara noticed Pri's title wasn't "Head of HR." It was Head of People Ops. She assumed it was a fancier word for the same thing and almost didn't ask.

She wasn't far off. People Operations ("People Ops") is a tech-popularized term for an employee-experience-and-culture-centric take on HR. It came out of Google around 2006, when Laszlo Bock retitled the function to back away from the dusty, paperwork-and-policy reputation "HR" had picked up. The idea: people aren't resources to be processed, they're the reason the company wins or loses, so the team supporting them should be strategic and proactive, not reactive paperwork.

In practice, at most companies People Ops and HR mean roughly the same thing. The label mostly signals a more strategic, employee-centric flavor — more focus on culture, growth, and the day-one-onward experience. Pri owns onboarding, comp bands, and compliance at Northwind; at an old-line manufacturer the person doing that identical job would just be called HR.

One more thing: recruiting can sit inside either an HR org or a People Ops org. At Northwind, Yara's TA team and Pri's People Ops team are siblings under the same People umbrella. So don't let "People Operations Coordinator" or "HR Generalist" confuse you about whether a role is recruiting. Read what the work actually is.

Lesson 2.3 — In-house vs. agency: where recruiters work

There's a second split that matters even more for your job search, and it's not about what recruiters do. It's about who they work for.

Yara is an in-house (internal) recruiter. She works for one company — Northwind — and hires only for Northwind's own roles. That shapes everything. She cares about long-term fit and culture, because she'll still be here when the engineer she hires is up for promotion in two years. And she partners with the same hiring managers over and over. Marcus, the VP of Engineering, owns most of her open roles; the better she learns how Marcus thinks, the better she does her job. It's a relationship that compounds.

Her mentor Imani spent four years at a staffing agency before going in-house, and she describes the other world like this.

"Agency, you're hired by the recruiting firm, not the company you're filling roles for. You juggle ten roles across six clients, and you move fast or you don't eat."

An agency (external) recruiter works for a recruiting firm that client companies pay to find candidates. They run many roles at once across multiple clients, the pace is faster, and the work is more sales-like. Imani didn't pick a candidate hoping they'd flourish for five years; she picked the one most likely to get hired now, because that's what the client paid for and how she got paid.

Both are real, respectable recruiting jobs. They just feel completely different day to day, and a lot of why comes down to how the money works — the next lesson.

Lesson 2.4 — The agency commission model

Why does agency recruiting move so fast? Follow the money.

When Imani placed a candidate at a client company, her firm sent that client an invoice. The most common arrangement is called a contingency fee, and it works like a bet: the agency only gets paid if and when a candidate they sourced actually gets hired. No placement, no payment. The fee is typically a percentage of the new hire's first-year salary — commonly around 15–25%, often higher for senior or hard-to-fill roles.

Run the numbers and the pace makes sense. Place a backend engineer at a $160,000 salary on a 20% contingency, and the firm bills the client about $32,000 for that one hire. Imani took home a cut of each fee on top of her base — so every filled role was money in her pocket, and every empty one was time spent for nothing. That's the engine. It's why agency recruiters are commission-driven and why they move fast.

That same intensity is why agency is such a common first recruiting job. High volume means fast learning: you'll screen more candidates and run more searches in one agency year than in three quiet in-house ones. Plenty of recruiters — Imani included — start at an agency to learn the craft, then move in-house once they want depth over speed.

Knowing this split sets your expectations before you apply. Agency: faster pace, commission upside, broad reps. In-house: steadier, salary-based, relationship- and culture-focused, deeper on one company. Neither is the "real" one. They're two doors into the same field.

Lesson 2.5 — The vocabulary that makes you fluent

In her first intake meeting, Marcus rattled off a sentence Yara only half understood: "I've got an approved req for a senior backend engineer, the pipeline's thin, and most of the people we want are passive — can your sourcer dig in?" She nodded, then looked up half of it afterward. By her third meeting she was speaking it back. Here's the starter vocabulary she built.

• Technical recruiter — a recruiter who specializes in hiring for tech roles, which means understanding those roles (Topic 3). Yara's job.
• Sourcer — someone who specializes in finding candidates, often a separate role from the people who interview them (Topic 5).
• Talent Acquisition (TA) — a broader, more strategic name for recruiting; common for in-house teams. Yara's team is "the TA team."
• Headhunter — informal term for a recruiter who pursues specific, often senior or passive, people. Less "post a job," more "go get that person."
• Candidate — anyone being considered for a role. Hiring manager — the person the new hire will report to, who makes the final call (your key partner; Topic 8). For Yara, that's Marcus.
• Requisition (a "req") — an approved open role, with sign-off and budget behind it. The green light to start hiring; an idea without one isn't real yet.
• Pipeline — the candidates currently moving through your process for a role. A "thin pipeline" means too few people in play.

The last pair matters most. Active candidates are job-hunting right now — applying, answering ads, updating profiles. Passive candidates are happily employed and not looking, but open to the right opportunity if it lands in front of them. The catch: passive candidates are often the strongest talent and the hardest to reach, precisely because they're not raising their hand. That gap is the entire reason proactive sourcing exists, and it's why Yara couldn't just post Marcus's job and wait. Topic 5 goes deep on reaching them.

Worked example — One open role, the whole cast

Marcus needs a senior backend engineer. Watch the field's vocabulary and roles light up around a single hire.

It starts with a requisition. Marcus can't just want an engineer — the role has to be approved and budgeted. Once that req is signed off, it lands in Yara's queue. She's the in-house technical recruiter, hiring for Northwind alone, with its culture and two-year fit in mind, partnering with the same hiring manager she'll work with on the next ten roles too.

The pipeline starts empty, and that's a problem, because the best backend engineers are passive — already employed, not answering job ads. So Yara leans on the team's sourcer to find people who aren't looking. One of them is Devon Asante, content at his current job but curious. Yara isn't posting and praying; she's effectively headhunting Devon, reaching out to a specific person about a specific opportunity. (Topic 5 covers how.)

Now the road not taken. With no in-house team, Marcus might instead pay an agency to fill this. That recruiter would run his req alongside nine others, move fast, and bill Northwind a contingency fee — roughly 15–25% of Devon's first-year salary, paid only if Devon actually started. On a $160K hire at 20%, about $32,000 for the one placement. Yara, salaried, costs Northwind the same whether this takes a week or two months — which is why she can optimize for the right hire instead of the fast one.

And when Devon signs? Yara's part ends and Pri's begins. Recruiting got him in the door; People Ops handles his onboarding, comp, benefits, and first ninety days. One role, and you've watched recruiting, sourcing, headhunting, agency-vs-in-house, and People Ops all play their distinct parts.