Product Manager - Servicing

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Our Company", "About Our Workplace", "About The Role" maybe we keep content but headings should be standardized? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting includes "About Our Company", "About Our Workplace", "About The Role", "What Youll Do At Splash", "What Youll Bring To Splash", "Compensation", "Splashers Enjoy". Also "Employment at Splash is based on individual merit..." is EEO boilerplate, remove. Also scam notice remove. Also "Originally posted on Himalayas" remove. We need to decide which sections to include: About the role (maybe combine About The Role and About Our Company/Workplace? The instruction says 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 an

About the role

containing description of role and maybe company overview? But "About the role" likely should contain the role description and maybe company context. The posting has "About Our Company", "About Our Workplace", "About The Role". We could combine company and workplace into a brief paragraph under About the role? However we must preserve ALL substantive information; we cannot drop company description unless we fold it into a short

. The instruction: fold minor metadata into a short

or drop it. Company description may be considered substantive? It's about mission, history, remote-first, values. That seems substantive. We could put it under About the role as a

after heading. Or we could create a separate section like "About the company" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit everything into those headings. Likely we put company overview under About the role (maybe as a brief intro). Then Responsibilities: "What Youll Do At Splash". Requirements/Qualifications/Skills: we need to split "What Youll Bring To Splash" into those categories. The posting lists required experience and nice-to-have. We can treat required as Requirements/Qualifications, and nice-to-have as Skills? Or we can have Requirements (must-have), Qualifications (maybe same), Skills (nice-to-have). But we should not create thin sections. We need to decide. We have Compensation section: base salary range, bonus component. That's Pay. Also benefits: list under "Splashers Enjoy". That's Benefits. Schedule: remote-first, mention flexible PTO? Not explicit schedule. Could infer remote work freedom, flexible PTO. But we should only include Schedule if posting actually states them. It mentions "Fully remote work freedom (for most roles)" and "Flexible PTO + 9 company holidays". That's schedule/benefits. Could put under Benefits or Schedule. Since we have a Benefits section already, we can put remote work and PTO there. Schedule maybe not needed if not explicit hours. We'll omit Schedule. We need to avoid filler like "commensurate with experience". Not present. We must not include EEO or scam notice. We need to output only HTML fragment. Let's craft:

About the role

[company overview + workplace + role description?] Might be long. Could split: About the role heading then a paragraph summarizing company and role. Then separate headings for Responsibilities etc. But we must not duplicate content. Let's extract substantive pieces: Company overview: - Founded 2013 after seeing friends/family struggle with student loans. - Mission: help people with debt, expanded to credit card refinancing. - Refinanced $6+ Billion loans via network of Splash-powered credit union and bank partners. - Raised over $135 million from investors (list). - Core: little company from Cleveland with big dream: make people more powerful than their debt. - Remote-first, collections team works in-person at Arizona location. - Days spent simplifying financial products, building financial tech that transforms lending. - Operates like a startup: fast-paced, nimble, full of heart. - Values: Own It, Raise the Bar, Say the Hard Thing, Elevate Each Other. - Slack channels #kids-and-pets, #food. Role description (About The Role): - Product Manager to own borrower servicing experience. - Report to Senior PM for Servicing. - Focus on building great customer experiences impacting thousands of borrowers manage, repay, interact with loans. - Improve operational processes and partner onboarding behind experiences. - Own domain end to end: discovery, writing requirements, partnering with engineering, design, business stakeholders, using data. - Not a support role. What Youll Do At Splash (Responsibilities): - Own discovery and delivery of borrower-facing servicing features, intuitive experiences for borrowers to manage, repay, stay on track. - Partner with lender implementation teams to translate partner servicing requirements into product requirements and support go-live delivery across credit union and bank partners. - Help maintain and evolve servicing platform configuration, including loan settings, borrower communications, platform-level changes. - Drive initiatives that reduce delinquency and improve payment behavior, including self-service improvements, payment plan optimization, enrollment experiences. - Use AI tools to accelerate workflow: drafting documents, synthesizing research, analyzing data, automating repetitive tasks. - Develop working knowledge of loan sales, collections, disbursements workflows, with growing ownership over time. What Youll Bring To Splash (Requirements/Qualifications/Skills): Required: - 2-5 years product management experience in fast-paced environment with real ownership/accountability. - Demonstrated product craft: identify/frame problems, translate to executable requirements, drive delivery within agile PDLC. - Good eye for UX: articulate what makes experience intuitive/broken, partner effectively with design. - Comfort using data to inform decisions and measure outcomes: ask right questions, find answers, act. - Clear, structured communication: translate between technical and non-technical audiences, keep stakeholders informed proactively. - Experience working with third-party platforms or vendors to ship product changes. - Proficiency with AI-powered productivity tools (e.g., Claude, ChatGPT, Copilot, Cursor) to accelerate research, analysis, documentation. Nice-to-have: - Experience in fintech, consumer lending, or regulated environment. - Familiarity with loan servicing, payments, collections, or capital markets. - Experience working with bank, credit union, or platform partners to deliver product changes. - Experience running A/B tests or product experiments to improve conversion, engagement, user behavior. - Familiarity with data and BI tools and product analytics tools; SQL proficiency is a plus. Compensation/Pay: - Base salary range $100,000 to $150,000 annually, based on market data and internal compensation practices. - Role may also be eligible for a bonus component tied to individual and company performance. - Final compensation determined by location, experience, skill level. Benefits: - Fully remote work freedom (for most roles) - Competitive salary packages - Flexible PTO + 9 company holidays - Equity: Share in our start-up success - Comprehensive and affordable insurance benefits - Paid parental leave for both caregivers - Essential modern equipment to get the job done - Fully paid Claude subscription to supercharge your work - 401(k) for your future savings - Quarterly meet-ups: In person & virtual fun - Awesome Splash swag to flaunt your team spirit We should not include "Employment at Splash is based on individual merit..." etc. Now produce HTML with headings

and content using

for prose,

• for lists. We need to decide where to put lists. For responsibilities, we can use
  . For requirements/qualifications/skills we can split. We have three possible sections: Responsibilities, Requirements, Qualifications, Skills. We could combine Requirements and Qualifications as one (since similar). But we need to follow instruction: use heading only when posting has real specific content. We have content for Responsibilities, Requirements (must-have), Qualifications (maybe same as requirements), Skills (nice-to-have). To avoid thin sections, we could make Requirements (must-have) and Skills (nice-to-have) and omit Qualifications if redundant. Or we could make Requirements (must-have) and Qualifications (nice-to-have). But the instruction list includes both Requirements and Qualifications as separate possible headings. We can decide to include both if we have distinct content. We have must-have and nice-to-have. So we can put must-have under Requirements, nice-to-have under Skills. Qualifications maybe we can omit or combine with Requirements. Let's omit Qualifications to avoid thin section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't create empty headings. Now craft HTML. Start with

  About the role

  Then a

  containing company overview and role description? Might be long but okay. Better: split: After About the role heading, we can have a short paragraph summarizing company and role, then maybe another paragraph for role specifics? But we can keep as one paragraph. Let's write:

  Founded in 2013 after seeing friends and family struggle with student loans, Splash Financial helps people manage debt, including credit‑card refinancing, and has refinanced over $6 billion in loans through its network of credit‑union and bank partners. The company has raised more than $135 million from investors such as DST Global, Citi Ventures, TruStage Ventures, Northwestern Mutual Future Ventures, and Detroit Venture Partners. Splash is remote‑first (with the collections team based in Arizona), operates like a fast‑paced startup, and is guided by the values Own It, Raise the Bar, Say the Hard Thing, and Elevate Each Other. In this role you will own the borrower servicing experience, reporting to the Senior PM for Servicing, and work end‑to‑end on discovery, requirements, engineering/design collaboration, and data‑driven decision making to improve how thousands of borrowers manage, repay, and interact with their loans.

  Then Responsibilities heading.

  Responsibilities

  • Own the discovery and delivery of borrower‑facing servicing features, focusing on intuitive experiences that make it easy for borrowers to manage, repay, and stay on track with their loans.
  • Partner with lender implementation teams to translate partner servicing requirements into product requirements and support go‑live delivery across credit‑union and bank partners.
  • Help maintain and evolve the servicing platform configuration, including loan settings, borrower communications, and platform‑level changes.
  • Drive initiatives that reduce delinquency and improve payment behavior, including self‑service improvements, payment plan optimization, and enrollment experiences.
  • Use AI tools to accelerate your workflow — drafting documents, synthesizing research, analyzing data, and automating repetitive tasks.
  • Develop working knowledge of loan sales, collections, and disbursements workflows, with growing ownership over time.
  Then Requirements heading (must‑have).

  Requirements

  • 2‑5 years of product management experience in a fast‑paced