Credit Operations Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We need to include sections only when posting has real specific content. We must not create Pay/Schedule/Benefits unless posting actually states them. Pay and benefits are present, so we can have a Pay section (maybe also Benefits). The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the team, What you'll do, Responsibilities, Who you are, Minimum Requirements, Preferred Qualifications, Working remotely, Pay and benefits. However they want specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can adapt: Use those headings only if content matches. For example "About the role" could be "What you'll do". "Responsibilities" is present. "Requirements" could be Minimum Requirements. "Qualifications" could be Preferred Qualifications. "Skills" maybe not explicit separate; we could embed within Requirements/Qualifications. "Benefits" and "Pay" are present. "Schedule" not present (no schedule details). So we should not create Schedule section.
We must not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Remove duplicated lines. Also remove "Who we are About Stripe" maybe we can combine into About the role? Actually "Who we are About Stripe" is company overview; could be part of About the role? But we have heading About the role (maybe we put company overview there). However they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can have a short paragraph for company overview. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the content but can reformat into HTML. We need to use
- for any list of duties/requirements/benefits, and
for prose. Thus we need to parse the posting and create sections. Let's extract content: Company overview: "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." Team description: "About The Team The Risk team helps maintain a healthy financial ecosystem for businesses around the world. Credit Operations conducts credit risk assessments, underwrites small and mid-sized users, and develops mitigation strategies that enable Stripe to take smart risks while supporting growth. The globally distributed team partners with stakeholders across regions to support new and existing users and products." What you'll do: "As a Credit Operations Manager, you will lead and develop a team of credit operations analysts while setting a strategic vision for scalable, high-quality operations. You will help enable new and existing Stripe products by translating product strategies into operational capabilities and appropriate credit controls. In partnership with Credit Strategy, Product, Engineering, and Data Science, you will launch new programs and advance AI-enabled automation across Credit Operations." Responsibilities: list bullet points (they are currently sentences separated by no bullet but we can treat each as list item). Let's extract each: - Lead, motivate, and develop a high-performing Credit Operations team by setting clear goals, providing regular coaching and feedback, and supporting professional growth - Assess the team’s current and future capability needs and partner on hiring, workforce planning, and development strategies to close material gaps - Set priorities for the team in alignment with Credit’s broader strategy and translate them into clear goals, work plans, and operating mechanisms - Evolve Credit Operations’ systems, processes, and operating model to improve decision quality, mitigate emerging risks, and scale efficiently - Support new and existing Stripe products by assessing credit and operational impacts, defining requirements and controls, and preparing Credit Operations for launch and ongoing support - Partner with Risk leadership and cross-functional stakeholders to prioritize investments in risk mitigation, operational efficiency, and user experience - Use AI-enabled tools and partner with technical and operational stakeholders to test and implement automation, with appropriate quality controls and change management - Define and manage operating metrics and service-level agreements, using performance insights and root-cause analysis to drive improvements - Oversee credit-related vendor performance and ensure work meets applicable quality and compliance standards 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 numbered but we can convert to bullet list. - 10-15 years of work experience in commercial credit underwriting - 3-5 years of experience leading credit risk or underwriting teams in a fast-paced, high-growth environment - Experience in financial risk modeling or cash-flow forecasting - Proven track record of building, leading, and developing high-performing teams, including setting goals, managing performance, and coaching team members - Strong strategic thinking and problem-solving skills with the ability to translate complex challenges into actionable solutions - Excellent communication and stakeholder-management skills, with the ability to influence across functions - Demonstrated experience designing, launching, and scaling programs, products, or operational capabilities from planning through implementation and measurement - Experience using AI-enabled tools and partnering with technical and operational stakeholders to implement automation, including quality controls, change management, and team adoption - Commitment to delivering a user-centered experience while effectively managing risk Preferred Qualifications: bullet list. - Experience supporting credit-related product launches or translating product capabilities into operational requirements, workflows, controls, and launch-readiness plans - Strong knowledge of accounting principles and experience evaluating financial statements and business models across industries - Experience analyzing data and creating dashboards using SQL - Experience partnering with engineering teams to develop or improve investigative and decisioning tools - Bachelor’s degree in a relevant field; advanced degree or certification is a plus Working remotely at Stripe: paragraph. "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: paragraph. "The annual US base salary range for this role is $157,800 - $236,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 there is more boilerplate: "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 remove boilerplate like application instructions, EEO, etc. The last paragraph includes encouragement to apply, etc. That's arguably boilerplate/application instructions. According to rules: remove application instructions. So we should drop that final paragraph (starting with "We look forward to hearing from you.") as it's generic encouragement and application window details. Also drop "Please find our California applicant personal information notice here." etc. Thus we keep only substantive sections: company overview, team description, what you'll do, responsibilities, who you are (maybe brief), minimum requirements, preferred qualifications, working remotely, pay and benefits. We need headings: About the role (maybe combine company overview + team description? But we have separate headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can also add additional headings like About the team, What you'll do if they have content. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those specific headings when appropriate. But we can also use other headings if needed? The examples are just examples; they didn't say we cannot use other headings. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use
for any section heading we create. We can choose headings that match content: About the role, About the team, What you'll do, Responsibilities, Who you are, Minimum Requirements, Preferred Qualifications, Working remotely, Pay and benefits. That seems fine. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and benefits, so we can have a Pay section and a Benefits section? The posting mentions both pay and benefits together. Could combine into one section "Pay and benefits". But the instruction list includes Benefits and Pay as separate possible headings. We could make two sections: Pay and Benefits. However the posting includes both; we could split: Pay: salary range; Benefits: equity, bonus, 401k, medical, dental, vision, wellness stipends. That would be more specific and follow the instruction to prefer a few substantive sections over many thin ones? Actually they say "Prefer a few substantive sections over many thin ones." So maybe combine into one Pay and benefits section is better. But they also list Benefits and Pay as possible headings; we could still combine but heading would be "Pay and benefits". That's not exactly one of the examples but still a heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd combine into one section "Pay and benefits". That seems substantive. We also need to avoid creating Schedule section (no schedule info). So we omit. Now we need to output only