Company Strategy & Operations

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

for each heading only if there is real content. We must not repeat job title. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions like "Apply now", "Please find our California applicant personal information notice here." Also remove duplicated lines. We need to parse the posting. Content: - Who we are About Stripe: description of Stripe. Could be "About the role"? Actually "About the role" heading maybe for description of role and team. The posting includes "About The Team & Role". So we can put that under

About the role

with paragraphs. - Responsibilities: bullet list under "What you’ll do". So we need

• items. - Requirements: Minimum Requirements list. - Qualifications: Preferred Qualifications list. - Skills: maybe not explicit separate; but we could combine some skills in Requirements? The instruction says use sections only when posting has real specific content. There's no explicit "Skills" heading; but we could infer skills from requirements? Probably better not to create a Skills section if not explicitly present. The posting mentions "Technical proficiency in AI tools", "Experience applying automation-thinking", etc. Those are part of requirements. So we may not need separate Skills. - Benefits: The posting mentions "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." Also earlier: "Pay and benefits" section includes salary range and benefits. So we can have Benefits section with that list. - Pay: The posting includes salary range: "The annual US base salary range for this role is $174,100 - $261,100." Also note about OTE etc. So we need Pay section. - Schedule: Hybrid work info: "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 ... Working remotely at Stripe ..." So we can put Schedule section with that info. We must not include headings with filler like "commensurate with experience". Not present. We must not include Job ID/requisition numbers. We must not include application instructions like "Apply now", "Please find our California applicant personal information notice here." Also "The application window will remain open for 100 days..." etc. Remove. We must preserve all substantive information. So we need to keep the description of Stripe, about team & role, responsibilities, minimum requirements, preferred qualifications, hybrid work details, pay and benefits. We need to format as HTML fragment: use

  for each section heading, then content: either

  for prose,

  • for lists. We need to decide grouping. Potential sections:

    About the role

    (contains Stripe description and team/role description). Could split into two paragraphs: one about Stripe, one about team & role.

    Responsibilities

    (list of what you’ll do)

    Minimum Requirements

    (list)

    Preferred Qualifications

    (list)

    Benefits

    (list of benefits)

    Pay

    (salary range paragraph)

    Schedule

    (hybrid work details) We must not include Skills section. Check if any content duplicated: The "Who we are About Stripe" appears at start; we include that. Now ensure we don't include boilerplate 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...." That's near the end before "Apply now". That is somewhat generic but still substantive? It's about culture; maybe we should keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That paragraph is not exactly boilerplate; it's a motivational statement. Might be considered part of the posting but not a specific section. Could be placed under About the role? Might be okay to keep as a paragraph after About the role. However it's somewhat generic; but not explicitly prohibited. I'd keep it as part of About the role maybe. Also "Join us. Apply now" is application instruction; remove. Also "Please find our California applicant personal information notice here." remove. Also "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." That's application instruction; remove. Now let's extract content. Original text: 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 & Role Stripe is looking for a senior operator and systems thinker to join the Central Strategy and Operations (S&O) team. This is a senior individual contributor role for someone who is obsessed with how organizations actually work and who builds the infrastructure that makes Stripe faster, clearer, and more coordinated as it scales. Central S&O sits at the center of how Stripe runs as a company. This role specifically owns the machinery of company operations—the planning processes, operating rhythms, information architecture, and cross-functional systems that let the leadership team at Stripe make better decisions, faster. If you're the kind of person who looks at a broken process and immediately starts designing the system that replaces it—and who reaches for automation before asking for headcount—this role is for you. You'll work across the most senior leaders at Stripe and partner teams to design, run, and continuously improve the operational systems that connect strategy to execution. This is not a coordination or program management role. It's a build role. You'll own outcomes end-to-end and raise the operational ceiling of the company. What you’ll do Run planning for Stripe. You'll own and execute how Stripe does annual planning including multiple offshoot workstreams, and the frameworks leadership uses to make decisions. Continuous improvement of existing processes, automating manual workflows and helping us redesign lighter ways to do the work in the future.Build, automate, and scale central operations infrastructure. You'll identify where manual, repetitive, or fragmented processes are creating drag and replace them with scalable systems—whether that's working with others on structured data pipelines, AI-augmented workflows, or new tooling. Your first instinct is to build, not to coordinate.Translate strategy into operational reality. Help teams drive strategic discussions in leadership forums with your thinking and architecture. Prepare and run leadership-level operating forums, bring your own point of view into the room, and own the follow-through.Drive continuous operational improvement. You'll have direct working relationships with the most senior leaders at Stripe and challenge assumptions, not just execute against them. You'll maintain a running view of where the operational systems of the company are breaking down—where decisions are slow, handoffs are unclear, or accountability is diffuse—and work across teams to address root causes. Who you are We're looking for someone who meets the minimum requirements to be considered for the role. If you meet these requirements, you are encouraged to apply. The preferred qualifications are a bonus, not a requirement. Minimum Requirements 10+ years of work experience, with a significant portion in operational roles at high-growth tech companies—product operations, strategy and operations, business operations, or company or corporate planningA track record of building and owning operational systems. You have measurably improved how a company or large team operates, not just managed existing processes.Deep experience either with company or functional planning—annual planning, OKR and SOKR-style goal-setting, resource allocation, and operating cadence designA systems thinker who is automation-first—you instinctively reach for tools, data pipelines, and AI-augmented workflows to reduce manual overhead and increase leverageStrong analytical rigor—you're comfortable owning data and metrics directly, running your own analyses, and pressure-testing assumptions without relying on a dedicated analytics partnerExperience working directly with and presenting to C-suite and senior executive stakeholders. You're comfortable owning the room and bringing a sharp, independent perspective.High comfort with ambiguity—you take an undefined operational problem, scope it, design a solution, and drive it to completion with minimal oversightTechnical proficiency in AI tools in order to automate workflows as neededExperience applying automation-thinking and scaled approaches to operational workflows—from analysis and synthesis to systems and decision supportPrior experience at a technology company is required. Preferred Qualifications Background in fintech, management consulting, or investment banking is a plus, but not required.Experience with the product and infrastructure ecosystem at Stripe or similar complex platform businessesFamiliarity with modern planning tools, workflow automation platforms, and operational data infrastructure 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. Pay and benefits The annual US base salary range for this role is $174,100 - $261,100. 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. 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 look forward to hearing from you. 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 need to strip out the application instructions and boilerplate at the end: "We look forward to hearing from you." maybe keep? It's not boilerplate but it's a closing line. Might be okay