Engineering Manager, Machine Learning - Credit Risk
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. So we need to map content to headings.
We have sections: About the role? Could be "About the team" or "What you’ll do". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should use those exact headings where applicable.
We have content:
- About Stripe (company description) maybe not needed as heading? Could be part of About the role? But we could put under About the role
with description of role and company? However they said do NOT repeat job title as heading; we can still have About the role heading.
- About The Team: could be part of About the role or separate? Probably we can include under About the role.
- What you’ll do: that's Responsibilities.
- Responsibilities: we have a list.
- Who you are: Minimum Requirements and Preferred Qualifications.
- Minimum Requirements: could be Requirements.
- Preferred Qualifications: could be Qualifications.
- Hybrid work at Stripe: could be Schedule? Actually schedule is about work location/hybrid. Could be Schedule heading.
- Pay and benefits: Pay and Benefits.
We need to output only HTML fragment, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's some boilerplate at end: "Please find our California applicant personal information notice here. The application window will remain open for 100 days..." That's application instructions, should be removed. Also "We look forward to hearing from you..." maybe not boilerplate but it's generic; but it's part of the posting; we might keep? It's not a list; it's prose. It's not boilerplate like EEO. It's okay to keep.
We need to ensure we don't include sections with placeholder text. All sections have content.
Let's extract content:
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 Credit Risk team develops intelligent systems that help Stripe identify high-risk accounts, minimize credit losses, and improve profitability. Credit risk is a complex machine learning problem that requires us to distinguish emerging risk from healthy business activity while giving legitimate users a clear and reliable experience. Our team consists of machine learning engineers who build models and systems used across Stripe’s credit-risk products. We work closely with partners in Product, Data Science, Credit Strategy, Operations, and other engineering teams. Together, we help stakeholders make informed decisions and support sustainable growth wherever credit risk affects Stripe’s products."
What you’ll do (Responsibilities): bullet list:
- Set and execute the strategy for detecting and mitigating credit risk through machine learning
- Own outcomes related to credit losses, profitability, detection quality, and the user experience
- Lead the design and delivery of reliable machine learning models, services, and decision systems
- Translate advances in machine learning into practical capabilities that support the team’s business goals
- Partner with Product, Data Science, Credit Strategy, Operations, and engineering teams to define priorities and deliver cross-functional programs
- Recruit, hire, and develop machine learning engineers while building an inclusive and effective team
- Contribute to broader engineering and machine learning initiatives as a member of Stripe’s engineering management team
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 (list):
- 3+ years of experience managing engineers who build and operate production machine learning systems
- Experience applying machine learning to complex, real-world problems and leading the technical delivery of models and supporting systems
- Experience setting strategy and working across engineering, product, data science, operations, and business teams to deliver measurable outcomes
- Experience recruiting, managing, and developing engineers in a fast-moving environment with significant autonomy
Preferred Qualifications (list):
- Experience with credit risk, fraud detection, financial risk, trust and safety, or another domain involving decisions under uncertainty
- Experience balancing risk reduction with customer or user experience
- Experience building machine learning systems that support high-stakes, time-sensitive decisions at scale
- Experience setting a multi-year technical direction while delivering progress through quarterly plans
- Experience managing geographically distributed teams
Hybrid work at Stripe: paragraphs:
"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: paragraphs:
"The annual US base salary range for this role is $258,600 - $387,800. 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."
Then final paragraph: "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."
We should keep that as prose under maybe a section? Could be part of About the role or separate? There's no specific heading for that; we could just include it as a
after Pay and benefits, maybe under a generic section? But instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could add a heading like "About the role" and put the initial descriptive paragraphs (About Stripe, About The Team, What you’ll do?) Actually "What you’ll do" is responsibilities. So maybe we have sections: About the role (containing About Stripe and About The Team), Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. But we need to separate Pay and Benefits? The instruction list includes Benefits, Pay, Schedule as separate possible headings. We could combine Pay and Benefits under one heading "Pay and benefits" as they appear together. Or we could have separate Pay and Benefits headings. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can choose to use Pay and Benefits as separate or combined. Since the posting includes both pay and benefits together, we could make a heading "Pay and benefits". That matches the example "Pay, Benefits". But they gave separate headings; we can still use "Pay and benefits" as a heading? It's not exactly in the list but it's close. Safer to follow exactly: we could have
Pay
and Benefits
separate. But the posting lumps them; we could split: Pay paragraph about salary range; Benefits paragraph about additional benefits. That would be accurate.
Schedule: hybrid work info.
Thus sections:
- About the role (contains About Stripe and About The Team)
- Responsibilities (What you’ll do)
- Requirements (Minimum Requirements)
- Qualifications (Preferred Qualifications)
- Pay (salary range)
- Benefits (additional benefits)
- Schedule (Hybrid work at Stripe)
We might also include a short paragraph about "Who you are" intro before Requirements? Could be included under About the role or as a separate intro. But we can incorporate that intro into About the role or as a before Requirements. The instruction: preserve all substantive information. So we need to include that intro sentence: "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." This is substantive. Where to place? Could be a
under About the role or before Requirements. I'd put it as a
under About the role after the team description maybe.
Now we need to output only HTML fragment. Use
for each heading. Use - for lists. Use
for prose.
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 Credit Risk team develops intelligent systems that help Stripe identify high-risk accounts, minimize credit losses, and improve profitability. Credit risk is a complex machine learning problem that requires us to distinguish emerging risk from healthy business activity while giving legitimate users a clear and reliable experience. Our team consists of machine learning engineers who build models and systems used across Stripe’s credit-risk products. We work closely with partners in Product, Data Science, Credit Strategy, Operations, and other engineering teams. Together, we help stakeholders make informed decisions and support sustainable growth wherever credit risk affects Stripe’s products.
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.
Responsibilities
- Set and execute the strategy for detecting and mitigating credit risk through machine learning
- Own outcomes related to credit losses, profitability, detection quality, and the user experience
- Lead the design
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's some boilerplate at end: "Please find our California applicant personal information notice here. The application window will remain open for 100 days..." That's application instructions, should be removed. Also "We look forward to hearing from you..." maybe not boilerplate but it's generic; but it's part of the posting; we might keep? It's not a list; it's prose. It's not boilerplate like EEO. It's okay to keep. We need to ensure we don't include sections with placeholder text. All sections have content. Let's extract content: 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 Credit Risk team develops intelligent systems that help Stripe identify high-risk accounts, minimize credit losses, and improve profitability. Credit risk is a complex machine learning problem that requires us to distinguish emerging risk from healthy business activity while giving legitimate users a clear and reliable experience. Our team consists of machine learning engineers who build models and systems used across Stripe’s credit-risk products. We work closely with partners in Product, Data Science, Credit Strategy, Operations, and other engineering teams. Together, we help stakeholders make informed decisions and support sustainable growth wherever credit risk affects Stripe’s products." What you’ll do (Responsibilities): bullet list: - Set and execute the strategy for detecting and mitigating credit risk through machine learning - Own outcomes related to credit losses, profitability, detection quality, and the user experience - Lead the design and delivery of reliable machine learning models, services, and decision systems - Translate advances in machine learning into practical capabilities that support the team’s business goals - Partner with Product, Data Science, Credit Strategy, Operations, and engineering teams to define priorities and deliver cross-functional programs - Recruit, hire, and develop machine learning engineers while building an inclusive and effective team - Contribute to broader engineering and machine learning initiatives as a member of Stripe’s engineering management team 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 (list): - 3+ years of experience managing engineers who build and operate production machine learning systems - Experience applying machine learning to complex, real-world problems and leading the technical delivery of models and supporting systems - Experience setting strategy and working across engineering, product, data science, operations, and business teams to deliver measurable outcomes - Experience recruiting, managing, and developing engineers in a fast-moving environment with significant autonomy Preferred Qualifications (list): - Experience with credit risk, fraud detection, financial risk, trust and safety, or another domain involving decisions under uncertainty - Experience balancing risk reduction with customer or user experience - Experience building machine learning systems that support high-stakes, time-sensitive decisions at scale - Experience setting a multi-year technical direction while delivering progress through quarterly plans - Experience managing geographically distributed teams Hybrid work at Stripe: paragraphs: "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: paragraphs: "The annual US base salary range for this role is $258,600 - $387,800. 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." Then final paragraph: "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." We should keep that as prose under maybe a section? Could be part of About the role or separate? There's no specific heading for that; we could just include it as a
after Pay and benefits, maybe under a generic section? But instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could add a heading like "About the role" and put the initial descriptive paragraphs (About Stripe, About The Team, What you’ll do?) Actually "What you’ll do" is responsibilities. So maybe we have sections: About the role (containing About Stripe and About The Team), Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. But we need to separate Pay and Benefits? The instruction list includes Benefits, Pay, Schedule as separate possible headings. We could combine Pay and Benefits under one heading "Pay and benefits" as they appear together. Or we could have separate Pay and Benefits headings. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can choose to use Pay and Benefits as separate or combined. Since the posting includes both pay and benefits together, we could make a heading "Pay and benefits". That matches the example "Pay, Benefits". But they gave separate headings; we can still use "Pay and benefits" as a heading? It's not exactly in the list but it's close. Safer to follow exactly: we could have
Pay
andBenefits
separate. But the posting lumps them; we could split: Pay paragraph about salary range; Benefits paragraph about additional benefits. That would be accurate. Schedule: hybrid work info. Thus sections: - About the role (contains About Stripe and About The Team) - Responsibilities (What you’ll do) - Requirements (Minimum Requirements) - Qualifications (Preferred Qualifications) - Pay (salary range) - Benefits (additional benefits) - Schedule (Hybrid work at Stripe) We might also include a short paragraph about "Who you are" intro before Requirements? Could be included under About the role or as a separate intro. But we can incorporate that intro into About the role or as abefore Requirements. The instruction: preserve all substantive information. So we need to include that intro sentence: "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." This is substantive. Where to place? Could be a
under About the role or before Requirements. I'd put it as a
under About the role after the team description maybe. Now we need to output only HTML fragment. Use
for each heading. Use
- for lists. Use
for prose. 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 Credit Risk team develops intelligent systems that help Stripe identify high-risk accounts, minimize credit losses, and improve profitability. Credit risk is a complex machine learning problem that requires us to distinguish emerging risk from healthy business activity while giving legitimate users a clear and reliable experience. Our team consists of machine learning engineers who build models and systems used across Stripe’s credit-risk products. We work closely with partners in Product, Data Science, Credit Strategy, Operations, and other engineering teams. Together, we help stakeholders make informed decisions and support sustainable growth wherever credit risk affects Stripe’s products.
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.
Responsibilities
- Set and execute the strategy for detecting and mitigating credit risk through machine learning
- Own outcomes related to credit losses, profitability, detection quality, and the user experience
- Lead the design
- for lists. Use