Head of People Operations

You don't process the transactions anymore. You design the systems through which an AI-native organization hires, onboards, develops, evaluates, and grows its people — humans whose jobs are themselves being transformed. People Operations becomes a design function.

Elevationprimary Emergencesecondary Convergencepartial

Family

Operations & People

Equivalent legacy role

Head of People Operations, VP People, Head of HR, Director of People Operations

Reports to

CEO, COO, or Chief People Officer

Works alongside

Workflow Architect · Governance Specialist

The work

You own the people side of an organization undergoing structural transformation. Hiring, onboarding, performance, learning, compensation, organizational design — and the strategic question of what an AI-native workforce should look like and how to get there. The agent handles transactional work; you handle the design.

Day-to-day, you:

Design hiring profiles for AI-native roles. What to interview for at T2 vs T3, which skills matter at each tier, what signals to weight. The hiring profile spec is the load-bearing artifact.
Run workforce planning for the AI-native operating model. Which roles grow, which contract, which emerge, which compress. Headcount and capability planning at the strategic level.
Specify L&D programming. What people need to learn at each tier of each role, in what order, by what method. The catalog maps to a curriculum; you design the curriculum.
Lead the transformation as a change-management practitioner. Most employees are anxious. The framework gives them a destination, but you handle the lived experience of getting there. Communications, coaching, manager enablement.
Design compensation bands for shifting roles. What an AI-fluent senior engineer is worth versus a legacy senior engineer. Which roles compress and which expand. The comp bands evolve with the operating model.
Run performance evaluation at the new metrics. With activity metrics losing meaning, performance review needs different instruments. You design the rubric.
Partner with function heads on team design. Which teams need a Workflow Architect, which need an Agent Supervisor, which roles should converge. The framework gives the patterns; you and the function head apply them.
Maintain ethical and legal standards. Compliance with employment law, ethics around AI in performance evaluation, fairness in workforce transformation decisions. Some of this work is genuinely new because the situation is genuinely new.

What success looks like

Concrete outputs at this tier:

Hiring quality. New hires perform at expected tier within their probationary period. Bad-hire rate is low.
Internal transformation rate. A meaningful percentage of the existing workforce successfully transitions to the AI-native version of their role each quarter.
Retention of high-performers. Top talent stays through the transformation; voluntary attrition is selective, not broad.
Manager capability. Managers across the org can articulate the operating model, run transition conversations, and evaluate at the new metrics.
L&D effectiveness. People who complete L&D programming demonstrate the skills the program targeted. The curriculum is working.
Workforce design coherence. Org structure matches the operating model. Teams have the roles they need; redundancies and gaps are being actively addressed.

What does not count as success: programs launched, training hours delivered, satisfaction survey scores in isolation from capability.

What makes this work interesting

The interesting part is not the policies and procedures. It is the strategic question of how to design an organization that has never existed before.

The role becomes designerly. Workforce planning, comp band design, L&D programming, organizational structure — all are design problems with strategic stakes. The work rewards systems thinking.

You sit at the center of the transformation. Engineering, sales, customer success, marketing — they're all transforming, and they all need your help to do it well. Few roles see the whole picture this way.

You're inventing the playbook. There's no established curriculum for how a People Operations function supports an AI-native transformation. You write it.

You materially shape who succeeds. The hiring profiles you design determine who joins. The L&D programs you build determine who grows. The performance instruments you specify determine who is recognized. The leverage is real.

Cross-function work deepens. With transactional HR work absorbed, you have time to engage substantively with function heads, with executives, with senior individual contributors. The role becomes a partner-level seat.

The strategic questions are genuinely hard. How do we evaluate performance when activity metrics no longer mean what they meant? How do we compensate roles whose scope has changed? How do we develop leaders who lead transformed teams? The problems are new; the answers will define the org for years.

Mission alignment compounds. People Operations done well is what makes the rest of the transformation possible. The work rewards people who care about the people in the system, not just the system itself.

What may not appeal. If your craft was in the transactional, operational, compliance-heavy side of HR — building processes, managing forms, running open enrollment — that work absorbs into agents and tooling. Your role becomes more strategic and abstract. Some HR practitioners find this richer; others find it uncomfortably ambiguous. You also lose some of the concrete, completable work of legacy HR — the new role's projects tend to be longer-running and harder to mark "done". Be honest with yourself about which kind of People work you wanted to do.

Who thrives in this role

The aptitudes that matter most at T3 are systems-thinking, strategic, and change-management aptitudes — different from operational HR strengths.

You think in systems and structures. Organizations are systems; workforces are systems; transformations are systems. People who naturally see structure produce better design.

You hold contradictions without flattening them. Speed vs. people-first. Standardization vs. personalization. Performance vs. inclusion. People Operations leaders who collapse these into "just pick one" produce worse outcomes than ones who navigate them.

You write clearly. Hiring profiles, performance rubrics, L&D specifications, change-management communications — clear writing is core. Function heads need to understand what you've designed.

You're comfortable with strategic ambiguity. The right answer to "what should our org structure look like in 18 months?" is not in a textbook. People Operations leaders who can sit with that question and produce good answers over time thrive.

You care about people without losing strategic clarity. Soft on people, hard on systems. People Operations leaders who care too much about being liked produce worse outcomes for the people they care about.

You partner well with executives. Workforce strategy is executive work. People Operations leaders who can hold their ground with the CEO and the function heads produce better workforce design than ones who defer.

You can navigate hard conversations. Transformations include role changes, comp adjustments, and sometimes people who don't successfully transition. People Operations leaders who avoid hard conversations make the transformation worse, not better.

Less essential than before: depth in HRIS configuration, knowledge of specific HR vendor stacks, the ability to personally run open enrollment. The agent absorbs operational HR work. Your value is in design and judgment.

Skills to develop to get there

The aptitudes describe disposition. The skills below are what you actively build.

Hiring profile specification. Writing what to interview for at each tier of each role, with clear signals and disqualifiers. How to practice: take one role you've hired for recently. Rewrite the hiring profile from scratch using the framework's tier definitions. Have a function head review.

Workforce planning at the operating-model level. Translating org strategy into team composition, role distribution, and capability roadmap. How to practice: sketch your workforce 18 months from now. Identify the roles that grow, contract, emerge. Defend each call.

Compensation band design. Designing comp structures for roles whose scope is changing. How to practice: take one role family. Map current comp to current scope. Map scope at T3. Adjust comp; defend the changes.

Performance instrument design. Writing performance rubrics that measure what matters at the new metrics. How to practice: for one role, draft a tier-specific performance rubric. Have a manager apply it; refine.

L&D programming specification. Writing what people need to learn, in what order, by what method, with what success criteria. How to practice: for one role's tier transition (e.g., Senior Engineer L2 → L3), specify the curriculum.

Change-management communication. Speaking and writing about transformation in ways that land with anxious employees. How to practice: draft a transformation communication. Test with three employees at different tiers; adjust based on how they hear it.

Cross-function partnership. Working substantively with function heads on team design. How to practice: commit to one substantive workforce-design engagement per function per quarter.

Hard conversation craft. Holding role-change, performance, and transition conversations with care. How to practice: after each hard conversation, write a one-paragraph post-mortem. What worked? What would you do differently? The pattern is your training.

Pick the skill that maps to your most recent strategic miss in workforce design. Practice it for a month.

How this differs from the legacy Head of People Operations role

Legacy Head of People Ops (pre-AI)	Head of People Operations (AI-native)
Manages HR transactions and operations	Designs the operating model and the workforce it requires
Hiring profiles based on resume and credentials	Hiring profiles based on tier-appropriate skills and judgment
Performance review centered on activity and goal completion	Performance review centered on system contribution and judgment quality
L&D programs purchased from vendors	L&D programs specified for the org's specific operating model
Workforce planning is annual headcount budgeting	Workforce planning is continuous operating-model evolution
Change management is event-based (acquisitions, restructures)	Change management is ongoing (the transformation is the work)
Best practitioners are the most operationally rigorous	Best practitioners are the most strategically clear
Career path: VP People → CHRO of similar-stage company	Career path: same, plus lateral to COO, transformation leadership

The role is not a more strategic version of legacy HR. It is structurally different — operational HR has been absorbed; strategic and design work has expanded.

Which role evolution patterns are in play

Elevation (primary). The role's center of gravity rises from transactional operations to strategic workforce design. Value migrates from operational rigor to design judgment.
Emergence (secondary). Workforce planning for AI-native operations, comp band design for transforming roles, and L&D programming for tier-specific skill development are genuinely new responsibilities.
Convergence (partial). Boundaries with COO, Governance Specialist, Workflow Architect blur as Operations & People work increasingly intersects with operating-model design.

Specialization and Absorption do not meaningfully apply to the role itself; they apply to subordinate roles (HR generalists, HR coordinators) within the People function.