Product Lead, Data Products

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

for each heading. Use

• for any list of duties/requirements/benefits etc. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include only sections with real specific content. We need to parse the posting. We have sections: - About Stripe (company description) – maybe not needed? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should include only those headings if they have content. The posting includes "About The Role", "What You'll Do", "Who You Are", "Nice to Have", "Why This Role", "In-office expectations", "Pay and benefits", "Additional benefits". Also "About Stripe" and "About The Team". Those are not in the list but could be considered "About the role"? Actually "About The Role" is present. We'll treat that as heading "About the role". The content under "About The Role" is a paragraph describing the role. We'll put that in

  . Then "What You'll Do" is responsibilities. We'll make a

  Responsibilities

  with a
  • list of each bullet. Then "Who You Are" is requirements/qualifications. Could split into Requirements and Qualifications? The instruction says we can have both sections. We need to decide based on content. "Who You Are" includes bullet points: 10+ years experience, leading PM teams, deep expertise in data products, strong commercial intuition, technically fluent, exceptional written communicator, high ownership instincts, comfortable in complex stakeholder environment. Those are qualifications/requirements. Could put them under Requirements or Qualifications. Since they are both similar, we could put them under Requirements (or Qualifications). The instruction: prefer a few substantive sections over many thin ones. So maybe combine into one section, e.g., Requirements. But we have also "Nice to Have" which could be Skills or Qualifications? Nice to Have are additional desired experience. Could be under Skills or Qualifications. We'll decide: Requirements (mandatory) and Nice to Have as Skills? Or Qualifications? Let's treat "Who You Are" as Requirements (mandatory). Then "Nice to Have" as Skills (or Qualifications). The instruction says we can have Skills section. So we can put Nice to Have under Skills. Then "Why This Role" maybe not needed; could be omitted as not a standard heading. Could be part of About the role? But we already have About the role. Could incorporate as a paragraph under About the role? However we must preserve all substantive information. So we need to include that content somewhere. Could add a section "About the role" that includes both the description and why this role. Or we could add a separate section like "Impact" but not in allowed headings. Better to incorporate into About the role paragraph. Then "In-office expectations" is about Schedule? Actually schedule is about in-office expectations. Could be Schedule section. The posting says: "In-office expectations Office-assigned Stripes ...". That's about schedule expectations. So we can put that under Schedule. Then "Pay and benefits" includes Pay and benefits. We need separate Pay and Benefits sections if content exists. The posting includes Pay: annual US base salary range $268,000 - $402,000. Also mentions equity, bonus, 401(k), medical, dental, vision, wellness stipends. So we need Pay section with salary range. Benefits section with list of benefits. We also have "Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends." That's benefits. Thus we will have sections: - About the role (h3) containing paragraphs: description from About The Role plus Why This Role maybe. - Responsibilities (h3) with ul list from What You'll Do. - Requirements (h3) with ul list from Who You Are. - Skills (h3) with ul list from Nice to Have. - Pay (h3) with p containing salary range. - Benefits (h3) with ul list of benefits. - Schedule (h3) with p containing in-office expectations. We must not include empty sections. All have content. We must not include boilerplate like EEO etc. Not present. We must not include navigation etc. We must not repeat job title. We must not include markdown fences. We'll output only HTML. Now craft content. About the role paragraph: combine the description from "About The Role" and "Why This Role". Let's write: "The PM leading Data Products will own the product strategy and execution for Stripe's merchant-facing data portfolio — defining what it means for Stripe to be the best data platform for merchants and agents. You'll set the direction across Sigma, SDP, and other data products, lead a team of PMs, and work closely with engineering, design, sales, and Stripe customers to shape how businesses access, analyze, and act on their Stripe data. This is a high-stakes, high-visibility role. Data access is increasingly a core buying criterion for Stripe's largest customers, and the competitive landscape for data portability and embedded analytics is evolving fast. You'll need to think strategically about platform positioning, lead through ambiguity, and ship products that work flawlessly for a very sophisticated user base. Stripe's merchants run their businesses on Stripe data. When Stripe’s data products surface the right insight at the right moment — merchants make better decisions, and they stay on Stripe. This role is a direct lever on that outcome. You'll have meaningful scope, a strong team, and the opportunity to define what world-class data access looks like for the most important businesses in the world." That seems fine. Now Responsibilities list: each bullet from "What You'll Do". Let's extract: - Set and own the product strategy for Stripe’s data products, defining the multi-year vision and translating it into a coherent roadmap that balances enterprise growth, self-serve expansion, and platform quality - Lead and develop a PM team. Manage, mentor, and hire PMs; build a high-caliber team culture with strong product craft and clear ownership - Drive revenue and retention outcomes. Deeply understand the commercial role of data products in Stripe's sales and self serve motions and build accordingly - Define what "great" looks like for merchant data access — from schema design and query performance to delivery reliability, latency SLAs, and integrations with third-party warehouses (Snowflake, BigQuery, Redshift, Databricks) - Partner with enterprise customers. Engage directly with Stripe's largest users to understand how they use and rely on their Stripe data, and feed those insights back into the roadmap - Navigate deep technical complexity. Work fluently with data engineering and infrastructure teams on the underlying Reporting Data Warehouse and data pipeline architecture - Anticipate the AI shift. Identify how AI-native workflows (agentic data access, natural language querying, automated reporting) should reshape the product surface over the next 2–3 years - Communicate and influence broadly. Write crisp strategy docs, earn trust from senior stakeholders across Product, Sales, and Finance, and represent Data Products clearly at the leadership level We'll put each as
  • . Now Requirements list from "Who Are You": bullet points: - 10+ years in product management, including experience leading or managing PM teams of 5+ PMs - Deep expertise in data products. You have shipped at least one of: a BI/analytics tool, a data integration product, a warehouse connector, or a developer data API - Strong commercial intuition. You understand how data products drive enterprise deal velocity, expansion, and retention, and you've worked closely with Sales and CS on product strategy - Technically fluent. You can hold your own in discussions about data pipeline architecture, warehouse connectors, SQL query execution, and data delivery semantics; you don't need to write the code but you need to understand the tradeoffs - Exceptional written communicator. You write with the clarity and precision Stripe's culture demands, from a tight decision memo to a multi-year strategy narrative - High ownership instincts. You proactively identify what needs to happen, move fast without waiting for permission, and hold yourself accountable to outcomes - Comfortable in a complex stakeholder environment. Data products touch engineering, enterprise sales, customer success, finance, and legal; you can align them without losing pace We'll put each as
  • . Now Skills list from "Nice to Have": - Experience building products on top of or integrating with major cloud data warehouses (Snowflake, BigQuery, Redshift, Databricks) - Familiarity with Stripe's data model and the kinds of analytics questions merchants care about (payments, disputes, revenue recognition, reconciliation) - Background in fintech or payments — you understand the data complexity that comes with operating across hundreds of payment methods, currencies, and regulatory regimes We'll put each as
  • . Now Pay: "The annual US base salary range for this role is $268,000 - $402,000. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. This salary range may be inclusive of several career levels at Stripe and will be narrowed during the interview process based on a number of factors, including the candidate’s experience, qualifications, and location. Applicants interested in this role and who are not located in the US may request the annual salary range for their location during the interview process." We'll put that in a

    . Now Benefits: list from "Additional benefits for this role may include: equity, company bonus or sales commissions/bonuses; 401(k) plan; medical, dental, and vision benefits; and wellness stipends." We'll make

    • equity
    • company bonus or sales commissions/bonuses
    • 401(k) plan
    • medical, dental, and vision benefits
    • wellness stipends
    Now Schedule: In-office expectations paragraph: "Office-assigned Stripes in most of our locations are currently expected to spend at least 50% of the time in a given month in their local office or with users. This expectation may vary depending on role, team and location. For example, Stripes in Stripe Delivery Center roles in Mexico City, Mexico, Bengaluru, India, and Dublin, Ireland work 100% from the office. Also, some teams have greater in-office attendance requirements, to appropriately support our users and workflows, which the hiring manager will discuss. This approach helps strike a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility when possible." We'll put that in

    . Now ensure we don't include any extra sections like About Stripe or About The Team. We omitted them. That's okay because we preserved substantive information? The instruction says preserve ALL substantive information. If we omit About Stripe and About The Team, we lose some substantive info about company and team. However the instruction says we should include sections only when posting has real specific content for it — never emit a heading followed by filler/placeholder text. It didn't say we must include all content; we must preserve ALL substantive information. So we need to include that info somewhere. Could we incorporate it into About the role? Possibly we can add a brief paragraph about Stripe and the team within About the role section. The About the role section currently includes role description; we could prepend a brief description of Stripe and the team. That would preserve that info. Thus we can modify About the role paragraph to include: "Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world’s largest enterprises to the most ambitious startups