Partner Development Manager, Strategic Partnerships

We need to output HTML fragment with headings

for sections: About the role? Actually the posting includes sections: Who we are, About Stripe, About The Team, What you’ll do (Responsibilities), Who you are (Minimum Requirements, Preferred Requirements), Pay and benefits, Hybrid work at Stripe (maybe schedule?), etc. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Apply now", "Please find our California applicant personal information notice here." etc. We need to preserve all substantive information. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include based on content. We have: - About Stripe (description) - About The Team (description) - What you’ll do (Responsibilities) list bullet points. - Who you are (Minimum Requirements) list bullet points. - Preferred Requirements (list bullet points) - Pay and benefits (salary range, additional benefits) - Hybrid work at Stripe (work location expectations) - could be Schedule? Actually it's about remote/in-office expectations. Could be considered Schedule or Work arrangement. The instruction says use headings like Pay, Schedule, Benefits. So we could have a section "Schedule" for hybrid work expectations. Or "Work Location". But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: maybe combine About Stripe + About The Team? Or we could have separate sections: About the role (maybe not needed). But we need to include sections only when posting has real specific content. We have content about Stripe and the team. Could make an "About the role" section summarizing? But we must not invent or summarize away detail. We could keep "About Stripe" and "About The Team" as separate sections with

  headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if appropriate. Could also use other headings if needed? Probably better to stick to those examples. So we need to map content to those headings. We have: - About the role: could be a brief description of the role (maybe from "Who we are About Stripe" and "About The Team"? Actually "About the role" could be a summary of what the role entails. But we have explicit "What you’ll do Responsibilities". So maybe "About the role" could be a short paragraph describing the role's purpose. The posting includes: "We're looking for a senior member to join our team to develop new partnerships with our largest users and strategic partners, and drive critical initiatives that will be foundational for Stripe." That's under About The Team? Actually that's in About The Team paragraph. Could be considered About the role. We'll include that as About the role. - Responsibilities: we have bullet list. - Requirements: Minimum Requirements. - Qualifications: maybe Preferred Requirements? Or we could treat Preferred Requirements as Qualifications. - Skills: maybe not separate; we could embed skills within Requirements. - Benefits: Additional benefits list. - Pay: salary range. - Schedule: Hybrid work at Stripe (remote/in-office expectations). We must not create sections with filler like "commensurate with experience". We have actual content. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  The annual US base salary range for this role is $163,400 - $245,200. ...

  Schedule

  Hybrid work at Stripe ...

  We need to preserve all substantive information. Let's extract details. About the role: The posting includes: - "Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone's reach while doing the most important work of your career." - "About The Team The Strategic Partnerships team develops and manages relationships with large partners that enable Stripe's product strategy and deliver new capabilities to Stripe users. Our team executes on high-impact, cross-functional initiatives across new products, geographic expansion, user advocacy, and policy. These partnerships have a significant impact on Stripe and the products used by millions of our users. We're looking for a senior member to join our team to develop new partnerships with our largest users and strategic partners, and drive critical initiatives that will be foundational for Stripe. A successful candidate will have significant experience delivering complex deal work, creating and driving strategy, working with cross-functional teams to launch new initiatives, and initiating first-of-a-kind partnerships. We're looking for someone who exhibits a strong sense of ownership, performs at a senior level, drives to have an impact, and has an entrepreneurial spirit." We could combine these into About the role paragraph(s). We'll keep as two paragraphs maybe. Responsibilities bullet points: - Evaluate and develop the business case to support Stripe’s product and engineering investment in new strategic partnerships across verticals (e.g. AI, Platforms, Payment Methods) - Manage strategic planning, negotiation and new partnership development - Ensure highly structured, methodical deal management rooted in milestones, KPIs, and alignment with partners on opportunities of mutual interest - Navigate the largest partners, in partnership with product, operations, marketing and sales, to execute deals supporting Stripe’s strategy - Develop and grow Stripe’s relationships with partners, including their senior executives and leadership - Partner with cross-functional teams (Product, Engineering, Go-to-Market Partnerships, Product Marketing, Operations) to design and implement strategies and processes that will enable us to scale our partnerships and increase our velocity as a team Minimum Requirements bullet points: - 8+ years of partnerships experience with 3+ years of business development experience, establishing partnerships with financial institutions, fintech, payment method, or equivalent strategic, complex partners - Strong agency, can handle ambiguity in a fast-moving organization, and thrives on a high level of autonomy and responsibility - Strong communication skills, in both verbal and written form, and ability to influence internal and external stakeholders across a wide variety of functions - Technical acumen, an ability to understand Stripe’s product portfolio and strategy and use this understanding to define requirements with partners and evaluate new partnership opportunities - 3+ years experience defining and executing partnership strategies to build innovative product experiences - 3+ years experience negotiating commercial deals with top financial and technology institutions, including scaling such deals across multiple partners - Interest in and intellectual curiosity about payments, economic infrastructure, and Stripe’s partners Preferred Requirements bullet points: - Payments experience - Hybrid work at Stripe (actually that's under Hybrid work section; but Preferred Requirements list includes "Payments experience" and "Hybrid work at Stripe"? Wait reading: after Minimum Requirements, there is "Preferred Requirements Payments experience Hybrid work at Stripe". Actually the text: "Preferred Requirements Payments experience Hybrid work at Stripe This role is available either in an office or a remote location (35+ miles or 56+ km from a Stripe office)." It seems the Preferred Requirements are just "Payments experience" and maybe "Hybrid work at Stripe" is not a preference but a description of work arrangement. However the formatting is ambiguous. Let's parse: Original snippet: Preferred Requirements Payments experience Hybrid work at Stripe This role is available either in an office or a remote location (35+ miles or 56+ km from a Stripe office). In-office expectations Office-assigned Stripes spend at least 50% of the time in a given month in their local office or with users. This hits a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility about how to do this in a way that makes sense for individuals and their teams. Working remotely at Stripe A remote location is defined as being 35 miles (56 kilometers) or more from one of our offices. While you would be welcome to come into the office for team/business meetings, on-sites, meet-ups, and events, our expectation is you would regularly work from home rather than a Stripe office. Stripe does not cover the cost of relocating to a remote location. We encourage you to apply for roles that match the location where you currently live or plan to live. Thus "Preferred Requirements" includes "Payments experience" and maybe "Hybrid work at Stripe" is not a requirement but a description of work arrangement. Actually "Hybrid work at Stripe" appears as a heading? The text "Hybrid work at Stripe" appears before the description. So likely "Preferred Requirements" is just "Payments experience". Then there is a section "Hybrid work at Stripe" describing schedule. Thus we will treat: - Preferred Requirements: Payments experience (single bullet) - Schedule: Hybrid work at Stripe (description) Now Benefits: "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." Pay: "The annual US base salary range for this role is $163,400 - $245,200. 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 need to keep all that. Now we need to strip boilerplate: lines like "At Stripe, we're looking for people with passion, grit, and integrity. You're encouraged to apply even if your experience doesn't precisely match the job description. Your skills and passion will stand out—and set you apart—especially if your career has taken some extraordinary twists and turns. At Stripe, we welcome diverse perspectives and people who think rigorously and aren't afraid to challenge assumptions. Join us. Apply now Please find our California applicant personal information notice here. The application window will remain open for 100 days after the Job Post is published. However, this opportunity will remain open based on the needs of the business, which may cause the application window to close before or after the 100-day mark." We must remove that. Also remove duplicated lines? Not seeing duplicates. Now produce HTML. We'll need to ensure proper nesting:
  • ...
  . For multiple items, we can have
  • item1
  • item2
  ...
  . We'll output as a single fragment. Let's craft. About the role: combine the two paragraphs into maybe two

  elements. Responsibilities: list. Requirements: list