AI Principal Product Manager
About the role
then paragraphs. - Responsibilities: bullet list. - Successful Candidates Have: that's qualifications/requirements. We'll treat as Requirements or Qualifications. Provide list. - Benefits: mention "We also offer benefits to eligible employees including medical, dental, retirement, and generous leave policies." Also later: "We provide meaningful, high-impact benefits designed to support the holistic well-being..." So we have benefits content. - Pay: "Annual salary range: $159,141 USD - $272,813 USD". Also earlier: "Starting pay is determined based on a combination of factors..." So we have pay info. - Schedule: "WORK MODEL: This role is fully remote and not tied to any specific office location. While there are no regular in-office requirements, we encourage our remote team members to gather intentionally for key company and team events to stay connected and engaged." That's schedule/work model. Thus we will include sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, privacy notices, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "AI FLUENCY", "WHAT WE LOVE ABOUT YOU", etc? Those are not required sections but they contain substantive content? They are about culture/values. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The sections we have sections like "WHAT WE LOVE ABOUT YOU" etc. Those are not in the prescribed list of headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not create extra headings beyond those. So we should ignore those sections unless they map to Benefits etc. The "WHAT WE LOVE ABOUT YOU" is more about culture, not required. We can omit. Similarly "TOGETHER@TKWW: OUR APPROCH TO HYBRID WORK" is about work model; we already have schedule/work model. Could incorporate some of that into Schedule section but we already have schedule content. We can maybe add more detail from that paragraph into Schedule section, but we must not invent. The schedule section currently has the WORK MODEL paragraph. The TOGETHER@TKWW paragraph adds more detail about hybrid work approach. That is also schedule/work model content. We can include it in the Schedule section as additional prose. It's not boilerplate; it's specific. So we should include that. Thus Schedule section will contain both paragraphs. Now we need to format: Use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail.
Let's extract content.
About the Role: The paragraph after "About the Role" heading:
"Nearly every couple takes on one of the most complex, emotional, high-stakes projects of their lives largely on their own: hundreds of decisions, dozens of vendors, and more than a year of sustained work. AI finally makes it possible to make this process easier, so couples can focus on the joy of planning a wedding.We are seeking a Principal Product Manager to define and build a brand new AI product in the wedding space from zero to one. Operating with startup-like autonomy inside the industry's dominant brand, you will have total craft ownership to define what an intelligent experience in this space should be.In this role, you will leverage assets that took decades to create and that no competitor can replicate, including the industry's deepest vendor graph, decades of behavioral data, and the trust of a brand couples already rely on for the biggest day of their lives. You aren't just adding AI to an existing workflow; you are building a category defining product from the ground up at startup speed."
We need to keep that as prose, maybe split into paragraphs for readability but not required. We'll output as
...
.
Responsibilities: The list after "Responsibilities" heading:
"Own from strategy to shipped product: rapid prototypes, early user cohorts, iteration loops, and launch. You define the roadmap and are accountable for the outcomes.
Own the market case, not just the product. Define who this is for, what it is called, where couples encounter it, why it wins, and over time how it becomes a durable business. You will build the positioning and category narrative together with Product Marketing and carry it into the roadmap rather than receiving it after the fact.
Define what a trustworthy AI is. When it guides, when it asks, when it acts, and how couples stay in control at every step. Your point of view here shapes the product's foundation.
Run a rapid build-measure-learn loop. Prototype weekly, put work in front of users and experts early, and kill ideas fast when the evidence says to.
Own the measurement and the unit economics. Define what success means for a product with no internal precedent, instrument it, and know what each engaged couple costs to serve. Usage-based cost is a product constraint here, not a finance problem to inherit.
Turn our proprietary assets into product advantage: shape how the vendor graph, couple graph, reviews, and planning workflows power experiences no general-purpose AI can match.
Help shape company-level AI direction. Act as a senior thought partner to product, engineering, design, marketing, and data science leadership on how AI changes what couples expect and what we build."
We need each as - . Ensure we preserve the content exactly.
Successful Candidates Have: list after that heading:
"Successful Candidates Have
8+ years of product management experience in consumer products at scale, including recent, hands-on experience shipping LLM-powered products (assistants, agents, or copilots) to real users.
A zero-to-one track record: at least one product taken from an ambiguous concept to a launched, measured reality, ideally inside a larger organization.
Working fluency with the modern AI stack: prompting, evaluation frameworks, agentic patterns, memory and tool use. You can hold your own in technical design conversations with ML/AI engineers.
Fluency in what it costs to run AI in production. You understand what drives cost per user, you have made model, context, and caching tradeoffs against a real budget, and you treat cost to serve as a product metric rather than someone else's line item.
Commercial and category instincts. You have launched something the market had no existing name for, and you can argue from evidence about positioning, distribution, and willingness to pay.
A strong, articulable point of view on AI autonomy: when an assistant should guide, when it should ask, when it should act, and how to keep users in control. We will ask you for it.
Founder instincts. You prototype as you write documents, you treat ambiguity as room to move, and you ship to learn rather than plan to certainty.
Executive-grade communication. You turn complex, novel problem spaces into narratives that align leaders and teams.
Rigor about measurement. You design success metrics for products that have no benchmark yet, and you let the data overrule your instincts."
We'll put each as
- under Requirements (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We can choose Requirements. We'll output
Requirements
then - ... etc.
Benefits: Content: "We also offer benefits to eligible employees including medical, dental, retirement, and generous leave policies." Also later: "We provide meaningful, high-impact benefits designed to support the holistic well-being of our diverse workforce and help our people thrive both professionally and personally. From physical and mental wellness to flexible time off our programs are built around the moments that matter most."
We need to preserve all. We'll combine into
maybe two paragraphs.
Pay: Content: "Starting pay is determined based on a combination of factors which may include location/market, education, experience, skills, and other qualifications of the successful candidate. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, commissions, equity or sales incentives, if applicable." Then "Annual salary range: $159,141 USD - $272,813 USD". We'll keep as prose.
Schedule: Content: "WORK MODEL: This role is fully remote and not tied to any specific office location. While there are no regular in-office requirements, we encourage our remote team members to gather intentionally for key company and team events to stay connected and engaged." plus the TOGETHER@TKWW paragraph: "Together@TKWW is designed to support how we work best: combining the flexibility we value with meaningful opportunities to connect in person. Whether a role is Together@TKWW-eligible or not, we believe in purposeful moments to come together, build strong relationships, and drive bold ideas forward.For Together@TKWW-eligible roles, this includes regular in-office time to foster collaboration and connection.For roles not eligible for in-office expectations, we support connection through virtual collaboration and intentional gatherings.To facilitate in-person collaboration, we have office spaces in Barcelona, Spain; Delhi, India; Galway, Ireland; London, England and New York, NY."
We'll combine into Schedule section.
Now ensure we don't include any boilerplate like EEO, privacy notice, etc. Also remove duplicated lines. The posting had duplicated privacy notice lines; we will omit.
Now produce HTML fragment.
We must not include or . Just the fragment.
Let's craft.
We'll need to escape any HTML special characters? The content includes ampersand (&) in "and". That's fine. Also includes bullet points with colons. No need to escape.
We'll output:
About the role
Nearly every couple takes on one of the most complex, emotional, high-stakes projects of their lives largely on their own: hundreds of decisions, dozens of vendors, and more than a year of sustained work. AI finally makes it possible to make this process easier, so couples can focus on the joy of planning a wedding. We are seeking a Principal Product Manager to define and build a brand new AI product in the wedding space from zero to one. Operating with startup-like autonomy inside the industry's dominant brand, you will have total craft ownership to define what an intelligent experience in this space should be. In this role, you will leverage assets that took decades to create and that no competitor can replicate, including the industry's deepest vendor graph, decades of behavioral data, and the trust of a brand couples already rely on for the biggest day of their lives. You aren't just adding AI to an existing workflow; you are building a category defining product from the ground up at startup speed.
Responsibilities
- Own from strategy to shipped product: rapid prototypes, early user cohorts, iteration loops, and launch. You define the roadmap and are accountable for the outcomes.
- Own the market case, not just the product. Define who this is for, what it is called, where couples encounter it, why it wins, and over time how it becomes a durable business. You will build the positioning and category narrative together with Product Marketing and carry it into the roadmap rather than receiving it after the fact.
- Define what a trustworthy AI is. When it guides, when it asks, when it acts, and how couples stay in control at every step. Your point of view here shapes the product's foundation.
- Run a rapid build-measure-learn loop. Prototype weekly, put work in front of users and experts early, and kill ideas fast when the evidence says to.
- Own the measurement and the unit economics. Define what success means for a product with no internal precedent, instrument it, and know what each engaged couple costs to serve. Usage-based cost is a product constraint
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Let's extract content. About the Role: The paragraph after "About the Role" heading: "Nearly every couple takes on one of the most complex, emotional, high-stakes projects of their lives largely on their own: hundreds of decisions, dozens of vendors, and more than a year of sustained work. AI finally makes it possible to make this process easier, so couples can focus on the joy of planning a wedding.We are seeking a Principal Product Manager to define and build a brand new AI product in the wedding space from zero to one. Operating with startup-like autonomy inside the industry's dominant brand, you will have total craft ownership to define what an intelligent experience in this space should be.In this role, you will leverage assets that took decades to create and that no competitor can replicate, including the industry's deepest vendor graph, decades of behavioral data, and the trust of a brand couples already rely on for the biggest day of their lives. You aren't just adding AI to an existing workflow; you are building a category defining product from the ground up at startup speed." We need to keep that as prose, maybe split into paragraphs for readability but not required. We'll output as
...
. Responsibilities: The list after "Responsibilities" heading: "Own from strategy to shipped product: rapid prototypes, early user cohorts, iteration loops, and launch. You define the roadmap and are accountable for the outcomes. Own the market case, not just the product. Define who this is for, what it is called, where couples encounter it, why it wins, and over time how it becomes a durable business. You will build the positioning and category narrative together with Product Marketing and carry it into the roadmap rather than receiving it after the fact. Define what a trustworthy AI is. When it guides, when it asks, when it acts, and how couples stay in control at every step. Your point of view here shapes the product's foundation. Run a rapid build-measure-learn loop. Prototype weekly, put work in front of users and experts early, and kill ideas fast when the evidence says to. Own the measurement and the unit economics. Define what success means for a product with no internal precedent, instrument it, and know what each engaged couple costs to serve. Usage-based cost is a product constraint here, not a finance problem to inherit. Turn our proprietary assets into product advantage: shape how the vendor graph, couple graph, reviews, and planning workflows power experiences no general-purpose AI can match. Help shape company-level AI direction. Act as a senior thought partner to product, engineering, design, marketing, and data science leadership on how AI changes what couples expect and what we build." We need each asRequirements
then- ... etc.
Benefits: Content: "We also offer benefits to eligible employees including medical, dental, retirement, and generous leave policies." Also later: "We provide meaningful, high-impact benefits designed to support the holistic well-being of our diverse workforce and help our people thrive both professionally and personally. From physical and mental wellness to flexible time off our programs are built around the moments that matter most."
We need to preserve all. We'll combine into
maybe two paragraphs. Pay: Content: "Starting pay is determined based on a combination of factors which may include location/market, education, experience, skills, and other qualifications of the successful candidate. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, commissions, equity or sales incentives, if applicable." Then "Annual salary range: $159,141 USD - $272,813 USD". We'll keep as prose. Schedule: Content: "WORK MODEL: This role is fully remote and not tied to any specific office location. While there are no regular in-office requirements, we encourage our remote team members to gather intentionally for key company and team events to stay connected and engaged." plus the TOGETHER@TKWW paragraph: "Together@TKWW is designed to support how we work best: combining the flexibility we value with meaningful opportunities to connect in person. Whether a role is Together@TKWW-eligible or not, we believe in purposeful moments to come together, build strong relationships, and drive bold ideas forward.For Together@TKWW-eligible roles, this includes regular in-office time to foster collaboration and connection.For roles not eligible for in-office expectations, we support connection through virtual collaboration and intentional gatherings.To facilitate in-person collaboration, we have office spaces in Barcelona, Spain; Delhi, India; Galway, Ireland; London, England and New York, NY." We'll combine into Schedule section. Now ensure we don't include any boilerplate like EEO, privacy notice, etc. Also remove duplicated lines. The posting had duplicated privacy notice lines; we will omit. Now produce HTML fragment. We must not include or . Just the fragment. Let's craft. We'll need to escape any HTML special characters? The content includes ampersand (&) in "and". That's fine. Also includes bullet points with colons. No need to escape. We'll output:
About the role
Nearly every couple takes on one of the most complex, emotional, high-stakes projects of their lives largely on their own: hundreds of decisions, dozens of vendors, and more than a year of sustained work. AI finally makes it possible to make this process easier, so couples can focus on the joy of planning a wedding. We are seeking a Principal Product Manager to define and build a brand new AI product in the wedding space from zero to one. Operating with startup-like autonomy inside the industry's dominant brand, you will have total craft ownership to define what an intelligent experience in this space should be. In this role, you will leverage assets that took decades to create and that no competitor can replicate, including the industry's deepest vendor graph, decades of behavioral data, and the trust of a brand couples already rely on for the biggest day of their lives. You aren't just adding AI to an existing workflow; you are building a category defining product from the ground up at startup speed.
Responsibilities
- Own from strategy to shipped product: rapid prototypes, early user cohorts, iteration loops, and launch. You define the roadmap and are accountable for the outcomes.
- Own the market case, not just the product. Define who this is for, what it is called, where couples encounter it, why it wins, and over time how it becomes a durable business. You will build the positioning and category narrative together with Product Marketing and carry it into the roadmap rather than receiving it after the fact.
- Define what a trustworthy AI is. When it guides, when it asks, when it acts, and how couples stay in control at every step. Your point of view here shapes the product's foundation.
- Run a rapid build-measure-learn loop. Prototype weekly, put work in front of users and experts early, and kill ideas fast when the evidence says to.
- Own the measurement and the unit economics. Define what success means for a product with no internal precedent, instrument it, and know what each engaged couple costs to serve. Usage-based cost is a product constraint