Recruiting OperationsWhat RecOps owns, and how to build it

Definition

What recruiting operations actually is

Recruiting operations is the infrastructure layer of hiring. It covers how the pipeline is designed, which system holds the truth, what the numbers mean, and what everyone involved is expected to do and by when. Sales figured this out fifteen years ago and called it RevOps. Recruiting has been slower to get there, mostly because hiring teams get judged on roles closed this quarter rather than on whether the machine will still work next year.

The dividing line I use is simple. Recruiting is the work that only exists because a specific role is open: sourcing for it, screening for it, closing the person. RecOps is the work that would still need doing if every role closed tomorrow. Nobody sources candidates for a job that does not exist. Somebody still has to keep the ATS clean, keep the scorecards current, and keep the reporting honest.

That test settles most turf arguments. Building an interview loop for the new sales role is recruiting. Deciding that every loop in the company has a named owner per stage is RecOps.

Pillar 1

Process: one pipeline, written down

Most companies do not have one hiring process. They have as many processes as they have hiring managers, all wearing the same job titles on the org chart. Engineering runs five rounds. Sales runs two and a reference call. Marketing invented a take-home assignment last spring and nobody remembers approving it.

The RecOps job is not to make every role identical. It is to make the skeleton identical and the muscle role-specific. Same stage names across every requisition, so conversion data is comparable. Same rule that every interviewer submits a scorecard before the debrief. Same service levels for how fast applications get reviewed and feedback gets filed.

Google's hiring research made the case for consistency years ago. Their re:Work guide to structured interviewing found that asking every candidate the same questions and scoring against the same rubric predicts performance better than freeform conversation. Consistency also happens to be what the EEOC expects from selection procedures. You get better decisions and a cleaner defensibility story from the same piece of work.

Start with a written pipeline and one interview scorecard per role family. If a hiring manager wants to change the loop, fine, but the change goes through RecOps and gets applied to the template so the next team inherits it.

Pillar 3

Systems: fewer tools, better configured

Ask a mid-size talent team what they use and you will often hear seven names: an ATS, a sourcing tool, a scheduling tool, an assessment platform, a background check vendor, a video interview product, and a spreadsheet holding it all together with tape. Every integration between them is a place data goes stale, and somebody has to own each one.

My honest view: most teams under 500 employees are running two or three tools more than they need. Scheduling, scorecards, and reporting are table stakes for a modern ATS. If you are paying separately for those, you are paying twice, once in license fees and once in the operations time it takes to keep the pieces talking.

RecOps owns the consolidation decision and the configuration that follows: pipeline stages, permission levels, email templates, automated status updates, and the rules for what gets automated versus what stays human. The screening layer is where teams see the fastest return, because application review is the largest admin block in that 17.7 hour number. Tools like AI screening handle the triage so a human reviews a ranked shortlist rather than 300 raw resumes.

One warning before you consolidate. Migrating systems is its own project and it goes badly when it is improvised. Work through an ATS migration checklist before you sign anything, and pull historical data out in a usable format while you still have access.

Pillar 4

Enablement: the part everyone skips

You can design a perfect process and still watch it collapse, because the people executing it were never taught how. Most hiring managers have had zero hours of formal training on interviewing. They were promoted, handed a requisition, and told to go find someone good.

Enablement fixes that with unglamorous, repeatable work. A 60-minute session on how to run a structured interview. A written intake template so kickoff meetings produce a real brief instead of “someone like Sarah but cheaper.” Question banks so interviewers are not improvising at 9am. A short certification before anyone joins a loop for the first time.

Then hold the line on service levels. Applications reviewed within 24 hours. Interview feedback filed within 24 hours. Debrief within 48 hours of the final round. Publish compliance by team. I have watched feedback times drop by half within a month of the first report going out, purely because senior people do not enjoy being the red row on a shared dashboard.

Our guide to interview training for hiring managers covers the curriculum in more detail.

Month one is diagnosis. Do not change anything yet. Pull every open requisition, record how long candidates have been sitting in each stage, and write down the process as it genuinely runs rather than as the handbook claims. A structured hiring process audit gives you the baseline you will be judged against later, and the ugly numbers are your negotiating position.

Month two is agreement. One stage set. One scorecard per role family. Published service levels. Expect resistance here, and expect it from your most senior hiring managers, who have the most invested in doing it their own way. Bring the month-one data to those conversations. “Your last three roles averaged 61 days and 40 of them were spent waiting on feedback” is a much better argument than a slide about best practice.

Month three is payback. Now that the process is stable, automate the parts that never needed a human: scheduling, status updates, screening triage, reminder nudges for late feedback. Our guide to recruitment automation covers what to automate first and what should stay manual.