People Ops Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Gaia", "About The Role", "What you will do", "What we are looking for", "Nice to have", "What success looks like", "What we offer", "Compensation Range". Need to follow rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About Gaia (company description) - About The Role (role description) - What you will do (detailed responsibilities broken into subcategories: People strategy and leadership, Talent acquisition, Performance, growth, and engagement, Compensation and benefits, People operations and compliance) - What we are looking for (requirements) - Nice to have (preferred qualifications) - What success looks like (90 days and first year goals) - What we offer (benefits) - Compensation Range: $145K - $175K We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine sections: "About the role" could contain the "About Gaia" and "About The Role"? Actually "About the role" heading is for role description. We could put "About Gaia" maybe as a brief intro paragraph before heading? But we need to preserve all substantive info. Could include a

  about Gaia before the heading. We need to avoid repeating job title as heading (not needed). No Job ID. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to decide which sections to output. Likely sections: About the role (maybe includes role overview), Responsibilities (detailed duties), Requirements (must-have), Qualifications (nice-to-have?), Benefits, Pay. But we must not create sections with filler. Ensure each heading has real content. Let's map: - About the role: could contain the "About Gaia" and "About The Role" paragraphs (role overview). That's substantive. - Responsibilities: could contain the "What you will do" sections (People strategy and leadership, Talent acquisition, Performance, growth, and engagement, Compensation and benefits, People operations and compliance). Those are duties. - Requirements: could contain "What we are looking for" (must-have). That's a list. - Qualifications: could contain "Nice to have" (preferred). That's also a list. - Benefits: could contain "What we offer" (benefits list). That's a list. - Pay: could contain "Compensation Range: $145K - $175K". That's specific. We should not include Schedule because not mentioned. We need to ensure we don't create sections with placeholder text. All have content. Now format: For each section,

    Heading

    then content. Inside sections, we need to use
    • for any list of duties/requirements/benefits. For prose, use

      . Thus:

      About the role

      About Gaia Gaia is on a mission to make family building accessible and affordable. We offer fixed price fertility treatment plans through a national network of partner clinics, flexible financing for members, and a benefits offering for employers. We are a Series B company with teams in the US and London, backed by investors who share our belief that everyone deserves a fair shot at building a family.

      About The Role We are hiring a People Ops Manager to build the people function for our next stage of growth. You will own the full employee lifecycle across our US, UK and remote teams, from hiring and onboarding through performance, compensation, and culture. This is a hands on leadership role: you will set strategy and do much of the work yourself, partnering closely with the CFO, CEO, and leadership team. The right person is equal parts operator and culture builder. You care about getting payroll, compliance, and policy exactly right, and you also know how to help a mission driven team do the best work of their careers.

      But we might want to keep them as separate paragraphs. Then Responsibilities: we need to list duties. The "What you will do" includes bullet-like subheadings with paragraphs. We can turn each subheading into a
      • containing the description. Or we could keep subheadings as

        ?? The rule: Use

        • for any list of duties/requirements/benefits. So we should make a list. Thus:

          Responsibilities

          • People strategy and leadership: Build and own the people roadmap aligned to company goals, headcount plans, and budget; Serve as a trusted advisor to the leadership team on org design, team structure, and leadership development; Partner with Finance on workforce planning, headcount forecasting, and people cost modeling; Report on people metrics (retention, engagement, time to hire, compensation benchmarks) to leadership and the board.
          • Talent acquisition: Manage, coach, and develop our Recruiter, setting clear priorities and hiring goals; Own the hiring process end to end, including role scoping, sourcing strategy, interview design, and offer management; Build a consistent, inclusive, and efficient hiring experience that reflects the Gaia brand; Manage recruiting partners and tools, and build our employer brand.
          • Performance, growth, and engagement: Design and run performance review cycles, goal setting, and feedback practices; Build career frameworks, leveling, and development programs; Measure and act on employee engagement, and champion a culture of ownership, care, and accountability; Lead onboarding and offboarding so every transition is thoughtful and well run.
          • Compensation and benefits: Own compensation philosophy, salary bands, and equity guidelines in partnership with the CFO; Run annual compensation reviews and benchmarking; Manage benefits programs, broker relationships, and open enrollment, including our own family building benefits for employees.
          • People operations and compliance: Oversee HRIS, payroll inputs, and PEO relationships (Justworks in the US, and UK payroll providers); Ensure compliance with US federal and state employment law and UK employment law for our London team; Maintain employee handbooks, policies, and documentation for both entities; Handle employee relations matters with sound judgment, discretion, and fairness; Support audit, diligence, and fundraising processes with accurate people data.
          But we need to ensure we don't add extra formatting like unless needed. The rule didn't forbid using other tags, but we should keep simple. Could just put plain text. However using is okay but not required. Safer to avoid extra tags; just plain text. Thus each
        • contains the sentences. Now Requirements: "What we are looking for" list. We need to make a
          • list. Content: - 8+ years of experience in People or HR roles, with at least 3 years leading the function or a meaningful part of it at a venture backed startup (Series A to C) - Experience supporting teams across the US and UK, or across multiple US states and at least one international entity - Strong working knowledge of US employment law; familiarity with UK employment practices is a strong plus - Track record of building people programs from scratch (performance, compensation, leveling, onboarding) - Experience managing and developing direct reports, ideally including recruiters - Comfortable with data: you can build a headcount model, run a comp analysis, and present people metrics clearly - Excellent judgment and discretion with sensitive information - A builder mindset: you are energized by ambiguity and happy to roll up your sleeves - Genuine connection to our mission of making family building accessible We'll put each as
          • . Then Qualifications: "Nice to have" list. - Experience in healthcare, benefits, fintech, or another regulated industry - Experience with HRIS and ATS tools such as Justworks, Rippling, BambooHR, Greenhouse, or Ashby - SHRM, CIPD, or similar certification Now Benefits: "What we offer" list. - Competitive salary and meaningful equity - Comprehensive medical, dental, and vision coverage - Fertility and family building benefits through Gaia - The chance to build a people function at a mission driven company at a pivotal stage We could also include "Equal opportunity" but that's boilerplate; we should remove EEO boilerplate. The posting includes "Equal opportunity Gaia is an equal opportunity employer..." That's boilerplate; we should remove. Now Pay: "Compensation Range: $145K - $175K". That's specific. We'll put in a

            maybe. We should not include Schedule. Now ensure we don't repeat any content inadvertently. Also we need to preserve all substantive information. Did we miss anything? The "What success looks like" section includes 90 days and first year goals. That's substantive; we need to include it somewhere. Could be under Responsibilities? Or maybe a separate section like "Goals" but not in allowed headings. However we could incorporate into Responsibilities or maybe a separate section like "What success looks like" but not in allowed headings list. The instruction: "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but not exclusive? It says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section like "Success metrics" but not in the list; maybe better to incorporate into Responsibilities or maybe a separate section like "Goals" but not listed. Safer to incorporate into Responsibilities as part of duties? But it's about success metrics, not duties. Could create a section "What success looks like" but that's not in the allowed list; risk of being considered not following instruction. However the instruction says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add a section for success metrics. But we need to decide. The posting includes "What success looks like" with concrete 90-day and first-year goals. That's substantive. I'd include a section

            What success looks like