Principal Product Manager- Conversational AI
for section headings. The job title is not to be repeated as heading. So we start with About the role
then content.
We need to include sections only when posting has real specific content. We have: About the role (the description). Then "What Would Your Day-to-day Look Like" - that could be a subsection? Could be part of responsibilities. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these standard headings. We need to decide which sections are present.
We have content about role, responsibilities, qualifications, skills, benefits, maybe schedule? Not explicit schedule. Pay? Not explicit salary numbers, but they mention competitive salary and pre-IPO equity packages. That's pay info. So we can include a Pay section with that content.
Benefits: they list many perks: unlimited PTO, Carrot Cash travel stipend, co-working space, work-from-home stipend, parental leave, entrepreneurial culture, open communication, small teams, 100% employer paid medical/dental/vision, disability/life insurance, HRA, DCA/FSA, 401k. So we can include Benefits section.
Requirements/Qualifications/Skills: The "An ideal candidate has..." paragraph lists qualifications. Could be split into Requirements and Skills. We'll create a Requirements section with the bullet list of qualifications. Also maybe Skills section for design fluency, coding ability, front-end experience, partner-facing, data-driven, LLM familiarity. But we can combine.
We must not repeat job title as heading. No Job ID etc.
We must remove boilerplate: the automated decision-making notice at end is boilerplate? It's about rights; likely considered legal/EEO boilerplate, should be removed. Also the "About Hopper" section is company description; could be considered not required? It's substantive about company but not role-specific. The instruction: 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. The "About Hopper" is not boilerplate; it's company overview. Should we keep? It's substantive about the company, but not directly about the role. The instruction says preserve ALL substantive information; does not restrict to role-only. So we should keep it. However we need to format into sections. Could add a section "About Hopper" but not in the list of allowed headings. The allowed headings are listed as examples; we can use other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive? It says use for section headings (e.g. ...). Likely we should stick to those headings; we can map company info under "About the role" or maybe a separate "About Hopper" but that's not in list. Safer to incorporate company description into "About the role" section or maybe a separate section "About the company" but not allowed. I'd include it as part of "About the role" or maybe a separate About Hopper
but risk being considered not following instruction. I'd keep within About the role.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to avoid filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we can list bullet points from "What Would Your day-to-day Look Like". For requirements we can list bullet points from ideal candidate paragraph. For skills maybe separate list.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each bullet point as is, not condense.
Let's extract bullets:
From "What Would Your Day-to-day Look Like":
- 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
That's 8 bullets.
From "An ideal candidate has..." paragraph:
- 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
- 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
That's 7 bullets.
Benefits list:
- 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
- Please ask us about our 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
Also maybe "competitive salary and the upsides of pre-IPO equity packages" could be under Pay.
Pay section: competitive salary and pre-IPO equity packages.
We need to avoid duplication: The first bullet of benefits includes competitive salary and equity; we could move that to Pay and keep benefits without that.
Thus Benefits list without that bullet.
Now About the role section: we need to include the initial paragraph about role: "About The Role HTS Assist is Hopper's agentic AI assistant for travel, resolving real customer issues like flight changes, cancellations, refunds, and bookings over chat and voice for some of the largest travel brands and enterprises in the world. As Principal Product Manager, you will own the customer-facing agent end to end: the conversations, the interface, and the experience our partners put in front of millions of travelers. This is a deliberately design-leaning role, and you will be the day-to-day design decision-maker, shaping flows and interfaces directly in close partnership with partner design teams and our in-house designer."
Also maybe include the "About Hopper" description? Could be part of About the role or separate. I'd add a short paragraph after the role description: "About Hopper ..." but that is lengthy. Might be better to include as a separate section "About the company" but not allowed. However we can include it as part of About the role, but that may be odd. The instruction: preserve ALL substantive information. So we must include it somewhere. I'll add a subsection under About the role maybe as a paragraph.
Thus About the role will have two paragraphs: first about the role, second about Hopper.
Now we need to output HTML fragment only, no /. Use
for each section heading. Use
for prose. Use
- for lists.
We must not include any markdown code fences.
Let's craft:
About the role
HTS Assist is Hopper's agentic AI assistant for travel, resolving real customer issues like flight changes, cancellations, refunds, and bookings over chat and voice for some of the largest travel brands and enterprises in the world. As Principal Product Manager, you will own the customer-facing agent end to end: the conversations, the interface, and the experience our partners put in front of millions of travelers. This is a deliberately design-leaning role, and you will be the day-to-day design decision-maker, shaping flows and interfaces directly in close partnership with partner design teams and our in-house designer.
About Hopper: 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 global travel agency that powers some of the world's largest brands. Through HTS, our B2B division, the company supercharges its partners' direct channels by integrating our fintech products on their sites or powering end-to-end travel portals. Today, our partners include leading travel brands like Capital One, Nubank, Air Canada, and many more. Here are just a few stats that demonstrate the company's recent growth: billions of dollars worth of travel and travel fintech are sold through Hopper and HTS's channels every year. Our fintech products, including Cancel for Any Reason and Flight Disruption Assistance, have exceptionally strong CSAT because the terms are always clear and customers receive instant, no-questions-asked resolutions. Almost 30% of our app customers purchase at least one fintech product when making a booking, and consumers are 1.6x more likely to repurchase if they add fintech to their booking versus booking travel alone. Given the success of its fintech products, Hopper launched a B2B initiative, HTS (Hopper Technology Solutions), which represents more than 75% of the business. Through HTS, any travel provider, including airlines, hotels, banks, and travel agencies, can integrate and seamlessly distribute Hopper's fintech or travel inventory on their direct channels. As its first HTS partnership, the company partnered with Capital One to co-develop Capital One Travel, a travel portal designed specifically for cardholders. Other HTS partners include Air Canada, Uber, CommBank, Nubank, Flair Airlines and many more. Hopper has been named the #1 most innovative company in travel by Fast Company
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive? It says use for section headings (e.g. ...). Likely we should stick to those headings; we can map company info under "About the role" or maybe a separate "About Hopper" but that's not in list. Safer to incorporate company description into "About the role" section or maybe a separate section "About the company" but not allowed. I'd include it as part of "About the role" or maybe a separate About Hopper
but risk being considered not following instruction. I'd keep within About the role.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to avoid filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So for responsibilities we can list bullet points from "What Would Your day-to-day Look Like". For requirements we can list bullet points from ideal candidate paragraph. For skills maybe separate list.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each bullet point as is, not condense.
Let's extract bullets:
From "What Would Your Day-to-day Look Like":
- 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
That's 8 bullets.
From "An ideal candidate has..." paragraph:
- 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
- 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
That's 7 bullets.
Benefits list:
- 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
- Please ask us about our 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
Also maybe "competitive salary and the upsides of pre-IPO equity packages" could be under Pay.
Pay section: competitive salary and pre-IPO equity packages.
We need to avoid duplication: The first bullet of benefits includes competitive salary and equity; we could move that to Pay and keep benefits without that.
Thus Benefits list without that bullet.
Now About the role section: we need to include the initial paragraph about role: "About The Role HTS Assist is Hopper's agentic AI assistant for travel, resolving real customer issues like flight changes, cancellations, refunds, and bookings over chat and voice for some of the largest travel brands and enterprises in the world. As Principal Product Manager, you will own the customer-facing agent end to end: the conversations, the interface, and the experience our partners put in front of millions of travelers. This is a deliberately design-leaning role, and you will be the day-to-day design decision-maker, shaping flows and interfaces directly in close partnership with partner design teams and our in-house designer."
Also maybe include the "About Hopper" description? Could be part of About the role or separate. I'd add a short paragraph after the role description: "About Hopper ..." but that is lengthy. Might be better to include as a separate section "About the company" but not allowed. However we can include it as part of About the role, but that may be odd. The instruction: preserve ALL substantive information. So we must include it somewhere. I'll add a subsection under About the role maybe as a paragraph.
Thus About the role will have two paragraphs: first about the role, second about Hopper.
Now we need to output HTML fragment only, no /. Use
for each section heading. Use
for prose. Use
- for lists.
We must not include any markdown code fences.
Let's craft:
About the role
HTS Assist is Hopper's agentic AI assistant for travel, resolving real customer issues like flight changes, cancellations, refunds, and bookings over chat and voice for some of the largest travel brands and enterprises in the world. As Principal Product Manager, you will own the customer-facing agent end to end: the conversations, the interface, and the experience our partners put in front of millions of travelers. This is a deliberately design-leaning role, and you will be the day-to-day design decision-maker, shaping flows and interfaces directly in close partnership with partner design teams and our in-house designer.
About Hopper: 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 global travel agency that powers some of the world's largest brands. Through HTS, our B2B division, the company supercharges its partners' direct channels by integrating our fintech products on their sites or powering end-to-end travel portals. Today, our partners include leading travel brands like Capital One, Nubank, Air Canada, and many more. Here are just a few stats that demonstrate the company's recent growth: billions of dollars worth of travel and travel fintech are sold through Hopper and HTS's channels every year. Our fintech products, including Cancel for Any Reason and Flight Disruption Assistance, have exceptionally strong CSAT because the terms are always clear and customers receive instant, no-questions-asked resolutions. Almost 30% of our app customers purchase at least one fintech product when making a booking, and consumers are 1.6x more likely to repurchase if they add fintech to their booking versus booking travel alone. Given the success of its fintech products, Hopper launched a B2B initiative, HTS (Hopper Technology Solutions), which represents more than 75% of the business. Through HTS, any travel provider, including airlines, hotels, banks, and travel agencies, can integrate and seamlessly distribute Hopper's fintech or travel inventory on their direct channels. As its first HTS partnership, the company partnered with Capital One to co-develop Capital One Travel, a travel portal designed specifically for cardholders. Other HTS partners include Air Canada, Uber, CommBank, Nubank, Flair Airlines and many more. Hopper has been named the #1 most innovative company in travel by Fast Company
About Hopper
but risk being considered not following instruction. I'd keep within About the role. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to avoid filler like "commensurate with experience". Not present. We need to use- for any list of duties/requirements/benefits. So for responsibilities we can list bullet points from "What Would Your day-to-day Look Like". For requirements we can list bullet points from ideal candidate paragraph. For skills maybe separate list.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each bullet point as is, not condense.
Let's extract bullets:
From "What Would Your Day-to-day Look Like":
- 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
That's 8 bullets.
From "An ideal candidate has..." paragraph:
- 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
- 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
That's 7 bullets.
Benefits list:
- 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
- Please ask us about our 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
Also maybe "competitive salary and the upsides of pre-IPO equity packages" could be under Pay.
Pay section: competitive salary and pre-IPO equity packages.
We need to avoid duplication: The first bullet of benefits includes competitive salary and equity; we could move that to Pay and keep benefits without that.
Thus Benefits list without that bullet.
Now About the role section: we need to include the initial paragraph about role: "About The Role HTS Assist is Hopper's agentic AI assistant for travel, resolving real customer issues like flight changes, cancellations, refunds, and bookings over chat and voice for some of the largest travel brands and enterprises in the world. As Principal Product Manager, you will own the customer-facing agent end to end: the conversations, the interface, and the experience our partners put in front of millions of travelers. This is a deliberately design-leaning role, and you will be the day-to-day design decision-maker, shaping flows and interfaces directly in close partnership with partner design teams and our in-house designer."
Also maybe include the "About Hopper" description? Could be part of About the role or separate. I'd add a short paragraph after the role description: "About Hopper ..." but that is lengthy. Might be better to include as a separate section "About the company" but not allowed. However we can include it as part of About the role, but that may be odd. The instruction: preserve ALL substantive information. So we must include it somewhere. I'll add a subsection under About the role maybe as a paragraph.
Thus About the role will have two paragraphs: first about the role, second about Hopper.
Now we need to output HTML fragment only, no /. Use
for each section heading. Use
for prose. Use
- for lists.
We must not include any markdown code fences.
Let's craft:
About the role
HTS Assist is Hopper's agentic AI assistant for travel, resolving real customer issues like flight changes, cancellations, refunds, and bookings over chat and voice for some of the largest travel brands and enterprises in the world. As Principal Product Manager, you will own the customer-facing agent end to end: the conversations, the interface, and the experience our partners put in front of millions of travelers. This is a deliberately design-leaning role, and you will be the day-to-day design decision-maker, shaping flows and interfaces directly in close partnership with partner design teams and our in-house designer.
About Hopper: 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 global travel agency that powers some of the world's largest brands. Through HTS, our B2B division, the company supercharges its partners' direct channels by integrating our fintech products on their sites or powering end-to-end travel portals. Today, our partners include leading travel brands like Capital One, Nubank, Air Canada, and many more. Here are just a few stats that demonstrate the company's recent growth: billions of dollars worth of travel and travel fintech are sold through Hopper and HTS's channels every year. Our fintech products, including Cancel for Any Reason and Flight Disruption Assistance, have exceptionally strong CSAT because the terms are always clear and customers receive instant, no-questions-asked resolutions. Almost 30% of our app customers purchase at least one fintech product when making a booking, and consumers are 1.6x more likely to repurchase if they add fintech to their booking versus booking travel alone. Given the success of its fintech products, Hopper launched a B2B initiative, HTS (Hopper Technology Solutions), which represents more than 75% of the business. Through HTS, any travel provider, including airlines, hotels, banks, and travel agencies, can integrate and seamlessly distribute Hopper's fintech or travel inventory on their direct channels. As its first HTS partnership, the company partnered with Capital One to co-develop Capital One Travel, a travel portal designed specifically for cardholders. Other HTS partners include Air Canada, Uber, CommBank, Nubank, Flair Airlines and many more. Hopper has been named the #1 most innovative company in travel by Fast Company
- for lists.
We must not include any markdown code fences.
Let's craft: