Principal Product Manager

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

for each section heading. Only include sections that have real specific content. Remove boilerplate etc. We need to parse the posting. Content: - Who We Are: description of X-LAB, XDS, etc. This could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We have: - Who We Are (company overview) -> maybe "About the role"? But "About the role" is about the job, not company. However we can still use "About the role" heading for company overview? Might be okay. But better to use "About the role" for description of the role? The posting includes "XDS is seeking a Principal Product Manager...". That's about the role. So we could have "About the role" covering that paragraph. - Responsibilities: bullet list under "What You’ll Do". That's responsibilities. - Requirements/Qualifications/Skills: bullet list under "You’re a Great Fit With:" includes experience, track record, familiarity, etc. Could be Requirements and Qualifications and Skills. We need to decide which sections to include. We can combine into Requirements (or Qualifications) and Skills. But we need to avoid thin sections. Perhaps we can have one "Requirements" section covering all bullet points. Or we could split into Requirements and Skills if distinct. The bullet list includes: 6+ years experience..., Proven track record..., Strong familiarity..., Experience working..., Willingness..., Ability... These are qualifications/skills. Could be under "Requirements". We'll include a single

Requirements

with

• items. - Benefits: bullet list under "Our Compensation And Benefits": Competitive salary ($160-$180k base + $10-20k bonus), Demo bike fleet, Generous time off policy, Comprehensive medical, dental, and vision coverage, Office space in beautiful Santa Monica, California. Also Compensation Range: $145K - $195K (maybe duplicate). We need to include Pay and Benefits sections only if posting actually states them. It does state compensation and benefits. So we need a Pay section (maybe separate) and Benefits section. The instruction: Prefer a few substantive sections over many thin ones. But we have both Pay and Benefits with concrete info. Could combine into "Compensation and Benefits" but headings list includes Benefits and Pay separate. We could create a Benefits section and include Pay inside? But they said include a section ONLY when posting has real, specific content for it. So we need both Pay and Benefits if we have specifics. We have salary range and bonus, that's Pay. Benefits: demo bike fleet, time off, medical/dental/vision, office space. So we can have two sections:

  Pay

  with

  or

  ? Pay is not a list but we can use

  . Benefits as

  . - Schedule: not mentioned (full time onsite). Could be Schedule: full time, onsite. That's specific: "This position is full time and onsite in our Santa Monica HQ." That's schedule info. So we can include Schedule section. - About the role: we need a section for role overview. Could be "About the role". We'll include a paragraph summarizing the role: XDS seeking Principal Product Manager, own and develop multiple categories, etc. - Responsibilities: we have bullet list under "What You’ll Do". We'll output as
  • . - Requirements: bullet list under "You’re a Great Fit With:". We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like "Equal Opportunity", "Learn more at ...", "See an insider’s look..." etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the company overview? The "Who We Are" paragraph is substantive about company. Should we include it? Possibly under "About the role" or maybe we could add a section "About the company"? Not in allowed headings list. But we could incorporate into About the role? The instruction says use headings e.g. About the role, Responsibilities, etc. It doesn't forbid other headings? It 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. Likely we should only use those headings. So we need to map content to those headings. The "Who We Are" could go under About the role? But About the role is about the job, not company. However we could treat it as "About the role" includes company context. Might be acceptable. Alternatively we could omit company overview if not fitting any heading. But we must preserve ALL substantive information. So we need to include it somewhere. Perhaps we can include it as a

    before any headings? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra paragraphs outside headings. But they said use

    for section headings (e.g. About the role, Responsibilities...). It didn't say we cannot have other elements. But to be safe, we can include a brief intro paragraph before headings, but that might be considered not following the rule. However the rule says "use

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

    for prose. So we can have a

    for company overview, then headings for sections. Thus structure:

    Who We Are X-LAB is the in-house performance bicycle line by XDS, which has quietly become the world’s largest and most vertically integrated bicycle manufacturer and the largest maker of carbon fiber frames, supplying many of the top brands in cycling and mobility. Today, XDS is quiet no more. XDS launched X-LAB in April 2026 as the global consumer brand to take the industry by storm. Three decades of experience building exceptional bicycles have culminated into a unique line of road, gravel, electric, city, hybrid, and soon mountain bikes that riders and shops can’t stop talking about. X-LAB is the new inflection point for the category. We launched in April 2026 with a full lineup across road, gravel, city, fitness, e-bike, and soon mountain categories, with validation from the highest and most demanding levels of the sport through the XDS Astana Team and a rapidly growing network of dealers. Our ambition is not simply to sell more bikes. It is to make great bikes more integrated, more accessible, and better supported through the independent shops and communities that grow cycling and bring in new riders. That is what makes this moment exciting. Joining X-LAB means shaping a company with unmatched production scale, real engineering R&D depth, and the confidence to earn trust… one rider, one dealer, one product, and one market at a time. Are you ready to ride ahead of the pack? Learn more at https://xlabbikes.com See an insider’s look of our factory: Youtube Video

    But we need to remove boilerplate like "Learn more at ...", "See an insider’s look...". Those are likely considered navigation/boilerplate? They are not legal/EEO but maybe still considered promotional. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more at ..." and "See an insider’s look..." could be considered navigation/promotional but not explicitly listed. Might be okay to keep? Safer to remove them as they are like links/promotional. We'll remove those sentences. Thus company overview paragraph without those lines. Now responsibilities: bullet list under "What You’ll Do". We'll extract each line: - Own and manage X-LAB product lines end-to-end, leading the full product lifecycle from concept through launch, delivery, and iteration - Lead the definition, development, and launch of products that deliver world-class rider experience and strengthen X-LAB’s position as a leading performance brand - Collect feedback from riders, dealers, and service teams, and work closely with engineering and design teams to drive continuous product improvements - Partner closely with Marketing to translate product features, technologies, and engineering advantages into compelling stories and launch assets - Develop product go-to-market materials, including product training content, user manuals, assembly guides, technical documentation, and FAQs - Build alignment and buy-in for product vision across internal teams, suppliers, dealers, and key external partners We'll put each as

    . Requirements: bullet list under "You’re a Great Fit With:": - 6+ years of experience in product development, consumer hardware, automotive, micromobility, cycling, or related industries - Proven track record of successfully bringing high-volume consumer products to market, ideally at 100,000+ unit scale - Strong familiarity with the full product development lifecycle, including ideation, prototyping, vendor management, engineering, tooling, quality assurance, certification, mass production, deployment, and product iteration - Experience working closely with suppliers, OEM/ODM partners, and manufacturing teams - Willingness and enthusiasm for domestic and international travel (approximately 25%) - Ability to work cross-functionally and thrive in a fast-paced environment We'll put as

    . Pay: we have "Competitive salary ($160-$180k base + $10-20k bonus )" and also "Compensation Range: $145K - $195K". There's some overlap; we need to preserve all substantive info, not invent or summarize away detail. So we should include both statements? They are somewhat overlapping but both are present. We'll include both as separate sentences in a

    . Benefits: bullet list: - Demo bike fleet - Generous time off policy - Comprehensive medical, dental, and vision coverage - Office space in beautiful Santa Monica, California Schedule: "This position is full time and onsite in our Santa Monica HQ." We'll put as

    . Now ensure we don't repeat job title as heading. We didn't. We must not include any markdown code fences. Just raw HTML. Let's craft. We'll start with a

    for company overview (Who We Are). Then

    About the role

    maybe with a paragraph describing the role: "XDS is seeking a Principal Product Manager to join us as we establish XDS in the North American market. You'll own and develop multiple categories, managing product vision from concept to market and beyond. You’ll work closely with engineering, design, marketing, and distribution partners to create more bikes that riders love. You’ll balance near-term and long-term vision and drive the US product line while staying fully connected to real world cycling. This role is cross functional at its core - this PM will work closely with teams across XDS to bring products to market, develop and grow product lines, and enhance our existing products and features. The ideal candidate is obsessed with bikes or vehicles in general, highly analytical, resourceful, customer focused, and thrives under time constraints to meet deadlines. This position is full time and onsite in our Santa Monica HQ." Wait schedule info already in Schedule section; we might duplicate. Better to keep schedule separate. So About the role paragraph can exclude schedule line. We'll keep schedule separate. Thus About the role paragraph: "XDS is seeking a Principal Product Manager to join us as we establish XDS in the North American market. You'll own and develop multiple categories, managing product vision from concept to market and beyond. You’ll work closely with engineering, design, marketing