Group Product Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if content exists. No job title heading. No Job ID etc. Remove boilerplate. Keep substantive info. We need to parse the posting. Content: - Intro about Gigs: description. Could be "About the role"? Actually "About Gigs" is company description. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have sections in posting: - "About Gigs At Gigs, we're building..." That's company overview. Could go under "About the role"? Usually "About the role" is description of role, but we have "The Role" later. So we could put company overview under "About the role"? Might be okay. But we could also treat "About Gigs" as "About the role"? Not ideal but we need to use headings only when we have content. We have content for "About the role" maybe from "The Role" paragraph: "As a Group Product Manager at Gigs, you'll lead a team..." That's role description. So we can put that under

About the role

. Then "What You Will Do" list -> Responsibilities. Then "What We Are Looking For" -> Requirements/Qualifications/Skills. Could split: Requirements (years experience), Qualifications (track record, judgment, etc.), Skills (communication, AI tools). But we can combine if needed. The instruction: prefer few substantive sections over many thin ones. So we could have Requirements covering experience, qualifications, skills. But we have separate headings possible. Let's see content: "What We Are Looking For" bullet list: - 7+ years in product management, including 3+ years leading and coaching other product managers - A strong track record shipping in complex domains, ideally platforms, APIs, or backend-heavy systems - Sound judgment and the ability to make calls with imperfect information while keeping teams aligned - A customer-oriented mindset, with experience working directly with customers, engineers, and cross-functional partners - Clear, concise communication (especially written) and an owner mindset that creates momentum - Hands-on use of modern AI tools, with a view on where they make product teams better, not just faster Then "Nice to Have" list: - Experience in telecom or other operationally intensive industries (payments, marketplaces, neobanks, infrastructure) - Experience building 0→1 products or scaling products through rapid growth - A strong technical background (former engineer, CS degree or similar) - Experience building or growing a product team from an early stage We could treat "What We Are Looking For" as Requirements (must-have) and "Nice to Have" as Qualifications or Skills. But we have separate headings for Qualifications and Skills. Could map: - Requirements: the must-have list (7+ years etc.) - Qualifications: maybe the nice-to-have? Or we could treat Qualifications as the nice-to-have list. - Skills: maybe the specific skills like communication, AI tools, judgment etc. But those are already in must-have. Given instruction to prefer few sections, we could combine Requirements and Qualifications into one section, but we have headings for each; we should only emit heading if we have content. Could emit Requirements with must-have, Qualifications with nice-to-have, Skills maybe omitted or combine. But we also have "What We Offer" -> Benefits. Also "Work At Gigs" -> maybe Schedule? Not exactly. There's mention of in-person collaboration, flexibility, regular time in hubs, occasional travel. That's about work arrangement, could be Schedule? Not exactly schedule but could be considered Work arrangement. However we only emit Schedule if posting actually states schedule details (like full-time, hours). It does not. So we should not create Schedule section. Pay: Not mentioned explicitly (competitive compensation and stock options). That's compensation info. Could be Pay section? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive compensation and stock options". That's compensation info, so we can create Pay section with that. Benefits section: they list stipends, budget for learning, free phone and international data plan. So Benefits section. Thus we will have sections: - About the role (role description) - Responsibilities (What You Will Do) - Requirements (must-have) - Qualifications (nice-to-have) - Skills (maybe we could omit or combine with Requirements? But we have communication, AI tools etc. Could put under Skills. However those are already in must-have. To avoid duplication, maybe we put Skills as communication, AI tools, judgment etc. But we already have them in Requirements. Could decide to not have Skills section and instead put those under Requirements. But we have separate headings; we can omit Skills if we don't have distinct content beyond what's already covered. The instruction: prefer few substantive sections over many thin ones. So we could omit Skills and just have Requirements covering all must-have and nice-to-have? But we have nice-to-have separate; we could put them under Qualifications. So we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six sections. Check if any content for "About the role" beyond role description: we have "The Role As a Group Product Manager at Gigs, you'll lead a team..." That's good. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive information. Let's extract each piece. About the role: The paragraph starting "The Role As a Group Product Manager at Gigs, you'll lead a team of product managers building the platform that lets any company offer its own mobile service. That covers our APIs, network integrations, and the experiences our customers put in front of their users. You'll set direction across multiple product areas, stay close to the hardest problems yourself, and raise the bar on product craft across the team. If you're an exceptional product leader, we'd like to meet you now, even if the exact scope is something we shape together." We'll put that in

. Responsibilities: The list under "What You Will Do". Each bullet as

. The text: - Lead and coach a team of product managers to deliver consistently against committed KPIs, building clear ownership, strong product craft, and predictable execution. - Own strategy and roadmap across multiple product areas, balancing customer value, business impact, and long-term platform foundations - Stay hands-on by owning key problems end-to-end, from discovery and specs to build vs. buy decisions and launch - Partner with Engineering and Design leadership to turn vision into execution, align priorities, and make trade-offs across teams - Work directly with customers, network partners, and internal teams to understand problems, validate solutions, and drive measurable outcomes - Shape how the product org works, including where AI and automation change how we discover, build, and ship We'll put in

• . Requirements: Must-have list from "What We Are Looking For". Bullets: - 7+ years in product management, including 3+ years leading and coaching other product managers - A strong track record shipping in complex domains, ideally platforms, APIs, or backend-heavy systems - Sound judgment and the ability to make calls with imperfect information while keeping teams aligned - A customer-oriented mindset, with experience working directly with customers, engineers, and cross-functional partners - Clear, concise communication (especially written) and an owner mindset that creates momentum - Hands-on use of modern AI tools, with a view on where they make product teams better, not just faster Qualifications: Nice-to-have list: - Experience in telecom or other operationally intensive industries (payments, marketplaces, neobanks, infrastructure) - Experience building 0→1 products or scaling products through rapid growth - A strong technical background (former engineer, CS degree or similar) - Experience building or growing a product team from an early stage Benefits: From "What We Offer": "We offer competitive compensation and stock options because we see you as a true partner in our growth. We also provide stipends for your home office or work setup, a budget for learning and development to fuel your career, and of course, a free phone and international data plan". Actually compensation part is Pay; benefits part is stipends, learning budget, free phone and data plan. So we split. Pay: "competitive compensation and stock options". Could phrase as "competitive compensation and stock options". We'll put in

  . Benefits: stipends for home office or work setup, budget for learning and development, free phone and international data plan. Also maybe mention "We believe in rewarding excellence." but that's fluff; we can keep as part of Benefits intro. We need to ensure we don't include boilerplate like "Want to learn more about our benefits, hubs, and what it’s like to work at Gigs? Check out our Careers page." That's navigation/instruction; remove. Also remove "At Gigs, we value in-person collaboration..." That's work arrangement; could be considered Schedule? Not exactly schedule; but we could treat as part of Benefits? Not really. It's about work environment. Could be omitted as not matching headings. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Work At Gigs" paragraph is not boilerplate but describes work arrangement. Could be considered under "Schedule"? Not exactly schedule; but we have no heading for work environment. Could we put under "Benefits"? Not appropriate. Could we create a section "Work Arrangement"? Not allowed headings list. So we should omit it because we only allowed those headings. 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 we should stick to those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we could create a section for "Work At Gigs" only if we map to one of allowed headings. It doesn't fit any. So we should omit it. Similarly "Our offices are designed to feel like home-inspired workspaces..." also omit. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any content for Skills: we could omit. Now produce HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  ...

  Make sure no extra whitespace? It's fine. Now write content precisely. About the role paragraph: copy exactly as in posting but ensure no extra fluff. Let's copy: "The Role As a Group Product Manager at Gigs, you'll lead a team of product managers building the platform that lets any company offer its own mobile service. That covers our APIs, network integrations, and the experiences our customers put in front of their users. You'll set direction across multiple product areas, stay close to the hardest problems yourself, and raise the bar on product craft across the team. If you're an exceptional product leader, we'd like to meet you now, even if the exact scope is something we shape together." We need to ensure we don't repeat "The Role" as heading; we have heading About the role, so paragraph starts after that. Should we keep the phrase "The Role"? It's part of the sentence; we can keep it as is. Now Responsibilities bullets: copy each. Check punctuation. Now Requirements bullets. Now Qual