Engineering Manager, Product and Business
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We need to map content to these headings appropriately.
We have:
- About the role: could be "Who we are About Stripe" and "About The Team". That's description of company and team. Could be under "About the role" maybe.
- Responsibilities: list under "What you’ll do Responsibilities". That's a list.
- Requirements: Minimum Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe not explicit; we could combine with Requirements? But we should not create empty sections. If no specific skills list. The posting mentions technical proficiency, problem solving, etc. Those are in Minimum Requirements. Could treat as Skills? But we already have Requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with content. We have content for About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits (Pay and benefits includes benefits), Pay (salary range). Schedule: hybrid work details (remote/in-office expectations) could be considered Schedule. So we can include Schedule section.
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out things like "Please find our California applicant personal information notice here. The application window will remain open for 100 days..." etc. Also "We look forward to hearing from you." etc. Also "At Stripe, we're looking for people with passion, grit, and integrity." That's maybe boilerplate but could be considered part of culture; but it's generic. Might be considered boilerplate; but it's not explicitly listed as EEO etc. Safer to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statement may be okay but could be considered fluff. However it's not duplicated. I'd keep it as part of About the role maybe.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep details like salary range, benefits list, hybrid work expectations.
We need to format using for each section heading, then content:
for prose,
- for lists.
We must not include markdown fences.
Let's craft:
About the role
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.
The Product and Business Engineering organization manages Stripe's core financial products, develops tools for efficient payment acceptance and risk management, provides a consistent developer experience, and creates solutions that empower businesses to optimize their revenue operations. This includes:
- Payments and Risk: The Payments Engineering organization focuses on developing products and platforms that enable users to accept payments from customers efficiently. This includes building APIs for processing payments, enabling regional, non-card payment options, and extending Stripe's capabilities to make it easy for businesses to accept in-person payments. The Risk Engineering team develops products that minimize financial and regulatory risks while ensuring a seamless user experience, thereby safeguarding Stripe’s brand and financial stability.
- Link: Stripe’s consumer payments network, designed to make online checkout faster and more secure. It lets consumers save their payment details and use them across participating Stripe businesses, reducing friction at checkout while helping businesses improve conversion. The Link team builds experiences and infrastructure for consumers, merchants, and payment method partners, including support for local and lower-cost payment methods, smart authentication, and account protections. Over time, Link aims to give consumers more choice in how they pay while helping businesses grow revenue and manage payment costs.
- Developer Experience and Product Platform (DEeP): The Developer Experience & Product Platform (DEeP) team empowers all of Stripe’s products with a shared product platform that can help with rapidly delivering high quality, consistent cross-product experiences across our UI and API surfaces. It focuses on providing consistent and scalable developer experience that any developer can leverage to accelerate customers’ ability to create value from Stripe.
- Revenue and Financial Automation (RFA): The Revenue and Finance Automation (RFA) suite gives businesses power over the entire life cycle of their cash flow. By coordinating billing, tax, reporting, and data services in one modern stack, Stripe’s RFA suite eliminates the inefficiencies of legacy finance tools and supports revenue growth.
Responsibilities
As an Engineering Manager at Stripe, you will play a pivotal role in driving the success of your team and the broader organization. Your responsibilities will include:
- Leading engineering and design processes, coaching, mentoring, and supporting your team as they build innovative solutions.
- Collaborating with stakeholders across product, design, infrastructure, marketing, and operations to ensure alignment on projects and objectives and shaping the team’s strategy and roadmap.
- Owning problems from end-to-end by managing diverse systems, processes, and technologies, while continuously seeking opportunities to optimize efficiency and user experience.
- Upholding high engineering standards, ensuring consistency across codebases, and implementing best practices throughout your team.
- Recruiting top engineering talent in partnership with Stripe’s recruiting team to build a diverse and high-performing team.
- Supporting your team members' career growth by providing insights and development opportunities tailored to their goals.
Requirements
Minimum Requirements:
- 4+ years of engineering management experience, directly managing and growing teams of 5+ engineers focused on building and shipping products at scale
- 8+ years of full time software development experience
- Experience building extensible, leveraged software solutions that scale to different kinds of user needs, with the ability to empathize with users and advocate for exceptional user experiences
- Strong problem-solving skills, with a history of creatively tackling complex challenges
- Background in dealing with ambiguity and executing on multiple high-impact work streams simultaneously
- Commitment to fostering a supportive, feedback-driven, and challenging work environment
- Technical proficiency to engage thoughtfully with engineers about architecture and product design, offering valuable insights when necessary
- A mindset of autonomy and entrepreneurship, where you're excited to take responsibility and drive initiatives forward
Qualifications
Preferred Qualifications:
- You have a strong product and design sense, and enjoy finding elegant solutions to complex problems
- Experience thriving in cross-functional environments, demonstrating rigorous thinking, effective decision-making, and ability to build strong cross-team relationships
- You have experience building and leading a distributed team that works across multiple locations and time zones
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 $214,600 - $354,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.
Schedule
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.
We must ensure no duplicate content. Also we should not include "Who you are" section separate; we already covered Minimum Requirements and Preferred Qualifications. The "Who you are" paragraph: "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." That's somewhat redundant; we could incorporate into Requirements but it's basically saying if you meet min reqs, apply. Might be considered boilerplate; but it's not duplicated. Might keep as part of Requirements? But we already have Requirements list. Could add a p before list: "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." That's substantive? It's generic but maybe keep. However instruction: do not emit heading followed by filler/placeholder text. This is not filler; it's a statement. I'd include it as a p under Requirements before the list. Similarly "Who you are" heading not needed. We also have "Team Matching: exact team matching for one of the subteams will be determined throughout the interview process based on business priority, your experience, location, etc. Please note we may also consider you for different orgs outside of Product and Business Engineering depending on open roles." That's substantive about team assignment. Could be included under About the role maybe as a p. We should include that. Let's adjust About the role to include that after the team description. Add a p: "Team matching: exact team matching for one of the subteams will be determined throughout the interview process based on business priority, your experience, location, etc. Please note we may also consider you for different orgs outside of Product and Business Engineering depending on open roles." Now ensure no duplication. Now check for any boilerplate removed: We removed the paragraphs about "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.", "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