People Operations Partner GTM - US Remote

We need to output HTML fragment with sections: About the role? Actually the posting includes intro about Jeranne etc. We need to reformat job posting into clean semantic HTML. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, 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 parse the posting. Key sections: - Intro: "Hi! 👋 I'm Jeranne, based in Amsterdam 🇳🇱, and I lead the People team at WeTravel. We help travel businesses grow by giving them the platform and support to run and scale exceptional trips. We're growing our People team, and looking for a People Partner who understands what it takes to grow and scale a company." - Core responsibility: "Your core responsibility: own the full people partnership for our GTM org — Commercial, CX and Finance/Ops — across the US, LATAM, and APAC, roughly 10 (senior) leaders and 250 WeTravellers. You'll help leaders make sharper people decisions, build high-performing teams, and spot the talent and organizational moves that unlock the business's next stage of growth. This is a high-visibility, cross-functional role: you'll partner directly with that leadership to build the programs and policies that let WeTravel scale sustainably, owning org design for your own group and shaping compensation, performance and talent decisions company-wide. We need someone equally comfortable with strategy and delivery: challenging a leader on org design one day, navigating a complex ER case the next, supporting integration work as we bring on new teams, or figuring out how to make performance management actually work for sales. One of our people pillars is Grow Talent: managers who multiply; talent that grows and stays - clear growth paths, a working performance and development cycle, succession for critical roles. You'll help lead that work, including the performance management redesign and co-designing and owning the manager enablement program. It's a hands-on partnership, built for someone who wants the pace of a hyper-growth company." - How We Work: "We aim to run People like a product team, not a policy function: our employees and managers are the users, and we build, ship and iterate based on what actually lands to improve the experience. We're a small, global team, you will be partnering closely with our (EMEA based) People Partner, People Operations and Talent Acquisition and report to the VP People (based in EMEA)." - What You'll Do: list of bullet points. - Why You Should or Shouldn't Apply: bullet points for Should Apply If and You Might Not Be The Right Fit If. - Benefits: list of benefits. - Please Note: restrictions (states not accepted, legal right to work, no visa sponsorship, update date). This is maybe metadata but not boilerplate? It's important info. Should we include? It's not EEO/legal boilerplate? It's specific restrictions. Probably we should keep as a short paragraph under maybe "Eligibility" or similar. But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map content accordingly. We need to decide which sections to include. We have substantive content for: - About the role (intro + core responsibility + How We Work). Could be "About the role". - Responsibilities (What You'll Do). That's a list. - Requirements/Qualifications (Why You Should Apply). Could be "Requirements" or "Qualifications". We have both Should Apply If and Might Not Be The Right Fit If. Could combine into Requirements. - Benefits: list. - Pay: not mentioned explicitly (no salary). So we should NOT create Pay section. - Schedule: not mentioned explicitly (no schedule). So we should NOT create Schedule. We also have eligibility note (states not accepted, legal right to work, no visa sponsorship, update date). This is not exactly a standard heading but could be placed under "About the role" as a short paragraph or maybe under "Requirements". But we need to preserve all substantive information. We could add a short

  after the Benefits section maybe titled "Eligibility" but we don't have that heading allowed. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot add other headings, but to be safe we can incorporate eligibility note into a paragraph under "About the role" or "Requirements". Probably better to put under "About the role" as a short note. We must not include boilerplate like EEO, equal-opportunity, scam-warning. The posting includes "Equal Opportunities WeTravel is an equal opportunity employer..." That's boilerplate; we should remove. Also "Please Note" includes restrictions; we keep. Also "You will receive an update on your application after 14th of September 2026." That's application instruction? It's a timeline; maybe we should keep as it's substantive? It's about application process; but instruction says remove application instructions. This is an update timeline; could be considered application instruction. Safer to remove. Also "If you're excited about this opportunity and believe you're a good fit, we encourage you to apply and join us..." that's application instruction; remove. Now we need to produce HTML. Structure:

  About the role

  ... intro + core responsibility + How We Work + eligibility note?

  Then

  Responsibilities

  • ... each bullet from What You'll Do
  Then

  Requirements

  • ... Should Apply If bullets
  Maybe also include "You Might Not Be The Right Fit If" as a separate list? Could be under Requirements as well but maybe as a separate section "Qualifications"? But we have both Requirements and Qualifications allowed. Could put Should Apply If under Requirements, and Might Not Be The Right Fit If under Qualifications. Or combine. Better: Requirements = Should Apply If. Qualifications = Might Not Be The Right Fit If (i.e., disqualifiers). But the instruction says "prefer a few substantive sections over many thin ones." Could combine into one Requirements section with both positive and negative? Might be okay. But we have separate headings allowed: Requirements, Qualifications. We could use both. Let's assign:

  Requirements

  You Should Apply If You Have ...

  • ... each bullet

  Qualifications

  You Might Not Be The Right Fit If You ...

  • ... each bullet