Principal Product Manager- Conversational AI

We need to output HTML fragment with sections: About the role (already present), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse the posting. First, "About The Role" heading is given; we should use

About the role

and then prose. Then responsibilities: bullet list from "What Would Your Day-to-day Look Like" items. Those are responsibilities. Requirements: maybe "An ideal candidate has 8+ years..." etc. That's qualifications/requirements. Skills: design fluency, ability to write code, front-end experience, partner-facing experience, data-driven approach, familiarity with LLM-based products. Benefits: "Perks And Benefits Of Working With Us" list: Well-funded startup, competitive salary, pre-IPO equity, unlimited PTO, Carrot Cash travel stipend, access to co-working space via FlexDesk, work-from-home stipend, generous parental leave, entrepreneurial culture, open communication, small dynamic teams, 100% employer paid medical/dental/vision, disability and life insurance, HRA, DCA/FSA, access to 401k. Pay: Not explicitly stated; only "competitive salary". That's vague; we should not create Pay section unless posting actually states them. It says "competitive salary" but no numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specifics; we can include Benefits. Pay: "competitive salary" is not a specific number; might be considered not specific enough? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive salary". That's a statement about pay, albeit vague. Might be okay to include Pay section with that statement? However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include Pay with that sentence. But they also said prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But they want separate sections if content exists. I'd include Pay with the competitive salary line. Schedule: Not mentioned; no schedule info. So omit Schedule. Now we need to remove boilerplate: cookie/navigation/legal/EEO etc. At end there is a paragraph about AI-driven tools reviewing applications; that's boilerplate? It's about application process; maybe considered application instructions? It says "At Hopper, we leverage AI-driven tools..." That's not exactly application instructions but could be considered boilerplate. Probably remove. Also remove duplicated lines. Now craft HTML. Structure:

About the role

...

Responsibilities

• Own the roadmap for the customer-facing conversational agent across chat and voice, from intent coverage and conversation design to the interfaces partners embed in their apps and websites
• Engage enterprise partners through discovery, requirement shaping, and launch decisions, translating partner asks into product choices that keep one product serving many partners
• Partner with Partner Solutions on implementation and onboarding
• Drive design daily, working hands-on in Figma to produce flows and wireframes, and partner with design on high-fidelity and production assets
• Build working prototypes using AI coding tools where they beat a written spec, to test conversation flows and interface ideas
• Define and defend quality bars with the evaluation team, covering resolution rate, containment, escalation correctness, and conversation quality
• Specify agent behavior in detail, including resolution, tone, escalation policy, guardrails, and edge cases, and iterate from production conversation data
• Stay close to GTM, Partner Solutions, and Success teams, feeding what the field learns back into the roadmap

Requirements

An ideal candidate has 8+ years of product management experience, including principal or lead-level ownership of a customer-facing product, with conversational AI, customer experience automation, or an adjacent space strongly preferred.

Skills

• Design fluency, comfortable manipulating design files and producing flows and basic mocks solo in Figma, having operated as a de facto design lead on a lean team
• The ability to write enough code to get a prototype working without waiting on an engineer, treating AI tools as a normal part of how they build
• Hands-on front-end experience, having built or shipped web front ends and able to engage engineers credibly
• Deep partner-facing experience with enterprise clients, ideally in regulated industries, shaping requirements and launch decisions at the product level
• A data-driven approach grounded in customer service and automation metrics, including resolution, containment, CSAT, and escalation quality
• Working familiarity with LLM-based products, including prompt and behavior design, AI quality practices, and their failure modes

Benefits

• Well-funded and proven startup with large ambitions, competitive salary and the upsides of pre-IPO equity packages
• Unlimited PTO
• Carrot Cash travel stipend
• Access to co-working space on demand through FlexDesk and a work-from-home stipend
• Very generous parental leave, much above industry standards
• Entrepreneurial culture where pushing limits and taking risks is everyday business
• Open communication with management and company leadership
• Small, dynamic teams with massive impact
• 100% employer paid Medical, Dental and Vision coverage for employees
• Access to Disability and Life insurance
• Health Reimbursement Account (HRA)
• DCA/FSA and access to a 401k plan

Pay

Competitive salary (with pre-IPO equity upside)

We need to ensure we didn't repeat job title. No Job ID. We should not include the "About Hopper" section? That's company description; not a required heading. Could be omitted as not part of required headings. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we must include company description. So we can omit. We must preserve ALL substantive information; we omitted some like "About Hopper" details. That is substantive but not under those headings. Should we include it? The instruction says use those headings for sections; but we could include a generic section like "About the company" but not in list. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples; we could add other headings if needed. But they also said "Prefer a few substantive sections over many thin ones." The company description is substantive; maybe we should include it as a section like "About Hopper". However they didn't forbid other headings. But to be safe, we could include it as a section with

About Hopper

. It's not in the examples but seems reasonable. But the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. I'd include About Hopper as a section. Also we have "About The Role" already; we used that. Now check for any duplicated lines: we have "competitive salary" appears both in Benefits and Pay; but Benefits bullet includes "competitive salary and the upsides of pre-IPO equity packages". Pay section repeats competitive salary; maybe we should avoid duplication. Could combine: Pay section could just mention "competitive salary with pre-IPO equity upside". Benefits bullet could then not mention competitive salary? But we must preserve ALL substantive information; removing competitive salary from Benefits would lose that info. However we could keep both; duplication is okay? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines should be removed. So we should avoid duplicating the same sentence. The phrase "competitive salary" appears in both; we could keep it only in Benefits and mention Pay as "See Benefits for compensation details" but that would be summarizing. Better to keep Pay section with just "competitive salary" and remove it from Benefits bullet? But then we lose the mention of competitive salary in Benefits bullet; but we could keep Benefits bullet without that phrase, but we still need to convey the benefit of competitive salary. The benefit is compensation; we could keep Pay section and remove the phrase from Benefits bullet, but then we lose the mention of pre-IPO equity upside? Actually Benefits bullet includes "competitive salary and the upsides of pre-IPO equity packages". If we move competitive salary to Pay, we could keep Benefits bullet as "the upsides of pre-IPO equity packages". But that loses the explicit mention of competitive salary in Benefits. However the Pay section covers it. The instruction: preserve ALL substantive information; we are not losing it, just moving it. That's okay. Thus adjust Benefits bullet: remove "competitive salary and". Keep "the upsides of pre-IPO equity packages". Also we have "Well-funded and proven startup with large ambitions" remains. Now Benefits list: - Well-funded and proven startup with large ambitions - the upsides of pre-IPO equity packages - Unlimited PTO - Carrot Cash travel stipend - Access to co-working space on demand through FlexDesk and a work-from-home stipend - Very generous parental leave, much above industry standards - Entrepreneurial culture where pushing limits and taking risks is everyday business - Open communication with management and company leadership - Small, dynamic teams with massive impact - 100% employer paid Medical, Dental and Vision coverage for employees - Access to Disability and Life insurance - Health Reimbursement Account (HRA) - DCA/FSA and access to a 401k plan Now Pay section:

Competitive salary

Now About Hopper section: we need to include the company description paragraphs. Let's extract the substantive content from "About Hopper" paragraph(s). It starts after "Perks And Benefits Of Working With Us" and continues until the AI tools paragraph. We'll include that as About Hopper. We need to ensure we don't include the AI tools paragraph (application instructions). That is: "At Hopper, we leverage AI-driven tools to assist our team in efficiently reviewing applications. These tools help us assess qualifications fairly and objectively. By submitting your application, you acknowledge the use of these automated screening technologies." That's boilerplate/application instructions; remove. Thus About Hopper content: "At Hopper, we are on a mission to become the leading travel platform globally, powering Hopper's mobile app, website and our B2B business, HTS (Hopper Technology Solutions). By leveraging massive amounts of data and advanced machine learning algorithms, Hopper combines its world-class travel agency offering with proprietary fintech products to bring transparency, flexibility and savings to travelers globally. We have developed several unique fintech solutions that address everything from pricing volatility to trip disruptions, helping people travel better and save more on their trips. The Hopper platform serves hundreds of millions of travelers globally and continues to capture market share around the world. The Hopper app has been downloaded over 120 million times and has become largely popular among younger travelers, with 70% of its users being Gen Z and millennials. While many know us as the Gen Z and Millennial travel app, Hopper has evolved to become much more than that. In recent years, we've grown into a travel fintech provider, commerce platform, and