TALENT ACQUISITION · MAY 2026
Let me be direct about something that many in our profession have been dancing around for years.
Recruiting and human resources are not the same discipline. They are not naturally aligned. They do not always share the same goals, the same metrics, the same timelines, or the same definition of success. And the organizational assumption that recruiting belongs inside HR — as a subset of it, reporting through it, governed by it — is one that deserves far more scrutiny than it typically receives.
I hold GPHR and SPHR certifications. I have spent over 25 years embedded in organizations where both functions lived side by side, sometimes collaboratively, sometimes in outright conflict. I have led recruiting at DocuSign, Amazon, AIFUND, Costco, and dozens of other organizations. I have watched exceptional recruiting teams get slow-walked into mediocrity by HR governance structures that optimized for compliance at the expense of velocity. And I have also watched standalone recruiting functions create legal and cultural disasters because nobody was asking the right questions about equity, ethics, and organizational health.
But I want to be equally clear about something that distinguishes this argument from a simple recruiting-versus-HR polemic: I have lived deeply on both sides of this line. I have built HR functions from the ground up for early-stage companies where no people infrastructure existed at all — designing policy frameworks, compensation architecture, and employee relations processes before a single HR professional was on staff. I have served simultaneously as the HR leader and the head of recruiting — wearing both hats at once, understanding in real time how the two functions pull against each other and where they genuinely need each other. And I have partnered closely and successfully with human resources organizations on a global scale — across multiple continents, in regulated and unregulated industries, in hypergrowth environments and mature enterprises — building the kind of functional trust that makes both teams better.
I am not making this argument from the outside. I am making it from deep inside both disciplines. And that is precisely why I believe the relationship between them deserves an honest conversation rather than a comfortable assumption.
My honest assessment: recruiting and human resources are step-siblings. Close. Sometimes close enough to feel like the same family. But not the same DNA. And the organizations that treat them as identical — that fold recruiting into HR as though the relationship were natural and inevitable — are often paying a price they cannot easily trace back to this structural decision.
This is the debate our industry needs to have more openly.
What Each Function Actually Does
Before we can debate where recruiting should sit, we have to be precise about what each function is actually doing — and where their interests diverge.
Human Resources is, at its core, a compliance and employee relations function. Its primary constituencies are the existing workforce and the organization itself. It is responsible for policy, procedure, legal compliance, benefits administration, performance management, compensation structure, labor relations, and culture stewardship. It is fundamentally oriented toward the internal organization — the people already inside the building.
Recruiting is a sales and market intelligence function. Its primary constituency is the external talent market. It is responsible for identifying, attracting, evaluating, and closing candidates who do not yet work for the organization. It operates in a competitive market with real-time pricing, volatile supply and demand, and outcomes measured in weeks and quarters. It is fundamentally oriented toward the outside world.
These are different orientations. Different time horizons. Different risk tolerances. Different definitions of urgency.
An HR function optimized for policy consistency and legal defensibility will, if unchecked, apply those values to the recruiting process — and the recruiting process will slow down, formalize, and begin to select for compliance over capability. An unchecked recruiting function, freed from HR governance entirely, can trample employee relations, create compensation inequity, and generate legal exposure that the organization will pay for years down the road.
The question is not which function is right. The question is which relationship between them produces the best outcomes — and under what conditions.
The Case for Recruiting as a Stand-Alone Function
High-Growth Environments
In hypergrowth technology companies, the ability to hire fast and hire well is often the single most important operational capability the organization has. Every week a critical engineering role goes unfilled is a week of product delay, competitive disadvantage, and compounding technical debt. The stakes are existential, and the timelines are unforgiving.
In these environments, recruiting organized under HR almost always underperforms. Not because the HR leaders are incompetent — but because the HR governance structure is not built for the speed and market-responsiveness that hypergrowth demands. Approval chains that work perfectly well for policy updates become catastrophic bottlenecks when you are trying to extend an offer to a candidate who has three competing bids expiring in 48 hours.
The most successful high-growth companies — Amazon in its early expansion phase, Meta during its rapid scaling years, Stripe as it built out its global engineering organization — have all, at various points, structured recruiting as a function with direct access to executive leadership, separate reporting lines from HR, and authority to move at market speed.
Amazon's Bar Raiser program is instructive here. It lived conceptually in recruiting, not HR. The hiring bar was set and enforced by recruiting leaders with organizational authority that ran parallel to — not through — the traditional HR function. That structural decision was not accidental. It reflected a belief that the recruiting function, when properly empowered, could be the organization's most important quality control mechanism.
Organizations Where Talent Is the Primary Product
In professional services firms, management consulting practices, and executive search firms — where the people are the product — recruiting is a revenue-generating function, not an overhead function. Organizing it under HR in these contexts makes roughly as much sense as putting your sales team under your compliance department.
I have worked with professional services organizations that made this structural mistake and spent years unwinding it. The recruiting function had been calibrated to HR's operational rhythm — annual planning cycles, committee-based approvals, standardized process for every hire regardless of seniority or criticality — when what it needed to be was agile, market-facing, and empowered to close.
Venture-Backed Startups and Founder-Led Companies
In early-stage companies, the HR function may not yet fully exist. The first recruiting hires are often the first people operations hires of any kind. In this context, the question of whether recruiting reports into HR is moot — but the implications of the organizational design choice made in those early months will echo through the company's culture for years.
The founders who get this right tend to build recruiting as a strategic function with direct CEO access, treating each hire as a board-level decision in the early stages. The founders who get this wrong tend to layer HR over recruiting prematurely, importing compliance structures and governance overhead that the company is not yet large enough to need — and inadvertently signaling to their recruiting team that their function is administrative rather than strategic.
Having built HR functions from scratch at several early-stage companies myself, I can tell you: the sequence matters enormously. Bringing in recruiting authority before HR infrastructure exists is manageable — and often necessary. Bringing in HR governance before your recruiting function has found its footing can institutionalize slowness at exactly the moment when speed is survival.
The Case for HR Oversight of Recruiting
I believe strongly in the arguments above. I also believe that recruiting operating without any HR guardrails is a recipe for problems that are real, costly, and sometimes catastrophic.
Regulated Industries and Compliance-Heavy Environments
In financial services, healthcare, government contracting, and defense — where hiring decisions carry significant legal exposure and regulatory scrutiny — the absence of HR governance over recruiting is not a structural preference, it is a risk. These are environments where a poorly documented interview process, an inadvertent accommodation failure, or an offer letter that does not include the legally required language can generate litigation that costs far more than the hire it was attached to.
I have seen what happens when aggressive recruiting functions in regulated industries operate without adequate HR oversight. The hires happen faster. The legal bills arrive later. The math does not favor the speed.
In these environments, HR oversight of recruiting is not bureaucratic friction — it is institutional protection. The compliance function that HR provides is a genuine service to the recruiting process, even when it does not feel like one.
Large Enterprise Environments With Complex Compensation Structures
In large organizations with formal job architecture, leveling frameworks, and compensation bands, recruiting decisions cannot be made in isolation from the HR systems that govern those structures. A recruiter who promises a candidate a compensation package that does not fit within the established band — or who inadvertently creates internal equity problems by negotiating aggressively for one hire while ignoring comparable roles — creates problems that reverberate through the organization long after the hire is made.
HR oversight in these environments is not about slowing recruiting down. It is about ensuring that individual recruiting decisions fit within the organizational system they are feeding. When it works well, HR and recruiting in large enterprises function as checks and balances — each preventing the excesses that the other, left unchecked, would produce.
Unionized and Labor-Represented Workforces
In unionized environments, the collective bargaining agreement governs significant aspects of how hiring is conducted, how offers are structured, and what role seniority plays in candidate selection. A recruiting function operating without HR integration in this context would routinely violate contractual obligations it did not know existed.
This is an environment where the step-sibling relationship between recruiting and HR needs to be close — not identical, but close enough to share a dinner table without conflict.
The Culture Stewardship Argument
There is a less structural but equally important argument for HR's involvement in recruiting: culture stewardship. HR is often the function most responsible for defining and protecting organizational culture — the values, norms, and behavioral expectations that distinguish one workplace from another.
When recruiting operates entirely outside HR's orbit, it can begin to hire for skill in ways that are disconnected from cultural fit — not the toxic "culture fit" that functions as a bias shield, but the legitimate question of whether a candidate's working style, communication preferences, and professional values are compatible with the environment they are entering. HR, at its best, provides that cultural reference point for recruiting decisions.
Having partnered with HR organizations across multiple continents and industries, I have seen this dynamic at its best: HR and recruiting operating as genuinely complementary functions, each making the other more effective. The HR partner who understands the talent market helps the recruiting team make smarter decisions about how to position roles. The recruiter who respects HR's cultural mandate helps the HR team avoid the blind spots that come from looking only inward. When both functions operate with mutual respect and clearly defined roles, the combined output is better than either could produce alone.
Step-Siblings: The Most Honest Metaphor I Know
Here is the framework I have arrived at after 25 years of watching this relationship work and fail in organizations of every size and type.
Recruiting and human resources are step-siblings. They share a household. They have overlapping interests and genuine areas of mutual dependency. But they have different parents — different origin stories, different core competencies, different natural orientations. And when organizations pretend they are identical twins — when they force them into the same reporting line, the same metrics, the same governance philosophy, the same definition of success — both functions typically suffer.
The step-sibling relationship works best when:
-
There are clear boundaries. Recruiting owns the external talent market and the process of attracting and evaluating candidates. HR owns policy, compliance, employee relations, and compensation architecture. Each respects the other's domain without colonizing it.
-
There are defined handoffs. The moment a candidate accepts an offer, they transition from recruiting's responsibility to HR's. That handoff should be explicit, deliberate, and well-designed — not a fuzzy gray zone where both functions are simultaneously accountable and neither is truly responsible.
-
Both functions report with appropriate proximity to leadership. In organizations where talent is a strategic priority — which should be most organizations — both recruiting and HR deserve a seat close enough to the executive table to exercise genuine influence. A recruiting function buried four levels deep in an HR org chart is a recruiting function whose strategic input has already been discounted.
-
Conflict is acknowledged rather than suppressed. The interests of recruiting and HR will sometimes be in tension. A recruiting team pushing to close a candidate faster than HR's offer process allows. An HR function insisting on documentation standards that a recruiter views as bureaucratic delay. These tensions are not failures — they are features of a healthy relationship between two distinct functions. Organizations that suppress the conflict by assuming the functions are aligned produce the worst outcomes, because the tension goes underground rather than getting resolved.
What the Research and Practice Suggest
The organizational design literature on this question is thinner than the practitioner debate would suggest — partly because most organizations treat the reporting line of recruiting as an administrative decision rather than a strategic one. But the evidence that does exist is instructive.
A 2023 Deloitte Global Human Capital Trends report found that organizations with recruiting functions that had direct executive access — regardless of whether they formally reported through HR — demonstrated significantly higher hiring velocity and quality-of-hire scores than those where recruiting was embedded multiple layers deep in the HR structure.
McKinsey's talent analytics research has consistently shown that the companies with the strongest talent outcomes treat recruiting as a business function with P&L-adjacent accountability, not as an HR service delivery operation. The reporting line varies — sometimes through HR, sometimes through the COO, sometimes directly to the CEO in early-stage companies — but the common factor is strategic access and business accountability.
On the other side, SHRM data on EEOC charge rates and employment litigation consistently shows higher exposure in organizations where recruiting operates without HR compliance involvement — suggesting that the guardrail function HR provides has measurable value even when it is experienced as friction.
My Recommendation: Structural Clarity Over Structural Dogma
I do not believe there is a single correct answer to whether recruiting should report through HR or operate as a stand-alone function. The right structure depends on the organization's size, industry, growth stage, regulatory environment, and leadership philosophy.
What I do believe is this:
Treating the question as already settled — because "that's how it's always been organized" — is one of the most expensive non-decisions an organization can make.
If your recruiting function is underperforming and you have not examined whether its position within the organizational structure is part of the problem, you are missing a variable that may matter more than any tool, technology, or talent investment you are considering.
If your recruiting function is operating without HR oversight and you have not examined what you are trading away in compliance, equity, and culture stewardship, you are accumulating risk that will eventually present itself on your legal docket.
The step-siblings can thrive in the same house. They can also make each other miserable. The determining factor is almost never the relationship itself — it is the clarity, respect, and honesty with which the household rules are defined.
Organizations that get this right — that define the boundaries clearly, build the handoffs deliberately, and give both functions the access and authority they need to succeed — tend to win the talent war. Not because they found the perfect org chart. Because they had the honest conversation that most organizations avoid.
Scott R. Baillie, GPHR SPHR · CEO, Esarbi Executive Partners, LLC | Transglobal Recruiting Services, LLC
Scott has 25+ years of embedded experience inside the recruiting and talent functions of Amazon, Microsoft, DocuSign, AIFUND, Costco, and dozens of other organizations globally. He has built HR functions from scratch for early-stage companies, served simultaneously as HR leader and recruiting head, and partnered with human resources organizations on a global scale across multiple continents and industries. He holds GPHR, SPHR, and multiple AI certifications, and advises organizations on talent strategy, recruiting function design, and AI-era workforce transformation.
