Principal Product Manager, Borrow — Remitly Financial Services

Here's a thinking process: 1. **Analyze User Input:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules are provided: use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use `

• ` for lists. Use `

  ` for prose. - Do NOT repeat job title as heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Identify the Job Posting Content:** The user provided a job description for "Principal Product Manager for Borrow" at Remitly. I need to extract relevant sections and structure them according to the rules. Let me parse the content: - "About The Role" section: Present. I'll use `

  ` for "About the Role" or similar. Wait, rules say: use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so those are examples. I should use relevant headings from the posting. - The posting has sections like: "About The Role", "You Will:", "You Have:", "Compensation Details.", "Our Benefits:", "Our Connected Work Culture:", and then EEO statements at the end. - I need to remove EEO, equal opportunity, scam warning, navigation, cookie, legal boilerplate at the end. - I need to keep substantive content. - I should not create sections like "Pay" or "Schedule" unless they are actually stated. The posting has "Compensation Details." with salary range, and benefits listed. It also has work culture expectations. I need to map these to the allowed headings carefully. Let's list what the posting actually has that's substantive: - About the role (paragraphs about Remitly expanding, Principal Product Manager for Borrow, etc.) - You Will: (list of responsibilities) - You Have: (list of requirements/qualifications) - Compensation Details: salary range $176,000-$220,000, equity, benefits overview - Our Benefits: list of benefits (flexible PTO, health/dental/vision, 401k, parental leave, mental health, ESPP, education/travel benefits) - Our Connected Work Culture: in-office expectation 50% time, etc. - Then EEO statements duplicated twice, which I must remove. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to map the content to these or similar, but only include sections that have real content. I should not create "Pay" if it's just "Compensation Details" with salary, but the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state pay/salary and benefits. I can use "Pay" for salary, "Benefits" for benefits list, "Schedule" if there's work schedule info (there is: in-office 50% time, 3 days a week). But I need to be careful: the rule says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I can have Pay, Benefits, Schedule if they have specific content. Let's map: - "About the role" -> the first paragraph(s) about the role. - "Responsibilities" -> "You Will:" section. I'll use `

  • ` for each bullet. - "Requirements" or "Qualifications" -> "You Have:" section. I'll map to "Requirements" or "Qualifications". The rules list both as examples. I'll pick one or use "Qualifications" since "You Have:" covers qualifications. I'll use `

    Qualifications

    ` or "Requirements". Let's see the exact list: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I can use a subset. I'll use "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I need to only include those that have content. The posting has "You Have:" which includes skills, experience, education. I can split into "Qualifications" and "Skills" or combine. Rules say "Prefer a few substantive sections over many thin ones." So I'll combine related ones. Let's decide on sections: 1. About the role (has content) 2. Responsibilities (has "You Will:") 3. Qualifications (has "You Have:" - I'll extract the core requirements/skills) 4. Benefits (has "Our Benefits:" list) 5. Pay (has salary range) 6. Schedule (has work culture/in-office expectation) But I need to check if "Skills" is distinct. "You Have:" has "8+ years of product management experience", "track record", "familiarity with lending", "cross-product engagement", "AI-first mindset", "quantitative skills", "working with Risk/Compliance/Legal", "product sense/design", "leadership", "comfort with ambiguity", "communication skills", "Bachelor's degree". I can maybe put some under "Qualifications" and some under "Skills", but to keep it few and substantive, I might combine into "Qualifications" or just have one section. The rules list "Qualifications, Skills" as separate examples, but I don't have to use all. I'll use "Qualifications" to cover the "You Have:" part, or maybe "Requirements". I'll read carefully: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Requirements" is an example. I can use "Requirements" for "You Have:". I'll use "Requirements" since it's listed. But "Qualifications" is also listed. I'll pick one. Let's use "Qualifications" as the heading for "You Have:". Or I could use "Requirements". I think "Qualifications" fits well. I'll use "Qualifications". Actually, looking at the posting, "You Have:" is a mix of requirements, skills, experience. I'll structure it as a list under "Qualifications". Now, let's extract content precisely, removing fluff and boilerplate. Content breakdown: "About The Role" section text: "Remitly is expanding beyond cross-border remittances to build a full suite of financial products that help consumers get paid, save, spend, and borrow — all built on the trust and reliability millions of customers already place in Remitly. As Principal Product Manager for Borrow, you will own one of the most consequential pillars of this vision: giving Remitly customers access to responsible, accessible credit and borrowing solutions that meet them where they are. This is a senior, high-ownership role. You will define the strategy and roadmap for Remitly's borrowing products — after a customer is onboarded through long-term retention and healthy repayment outcomes — while working with a cross-functional team of engineers, designers, analysts, and internal partners. You will balance product growth with responsible lending principles, building financial tools that genuinely improve customers' lives. Critically, you understand that a healthy borrowing portfolio is inseparable from overall product engagement — and you will drive usage across the full Remitly Card plan, knowing that customers who find broad value in the plan stay longer, borrow more responsibly, and represent lower risk. This position reports to the General Manager of the Borrow team." "You Will:" section (I'll list each bullet as

    ): - Own the end-to-end product strategy and roadmap for Remitly's suite of borrowing solutions, spanning early feature activation post-onboarding, ongoing engagement, proactive and reactive retention, and repayment experience. - Own the full product lifecycle — from discovery, requirements, and design collaboration through development, testing, launch, and ongoing optimization — ensuring consistent quality and velocity at every stage. - Drive early feature activation for newly onboarded members — designing the experiences and triggers that convert onboarded customers into active users (sending, saving, spending and borrowing), ensuring they quickly realize the value of Remitly Card features. - Drive engagement across the full Remitly Card plan — identifying opportunities to deepen usage of card features beyond borrowing, partnering with adjacent product teams to connect customers to relevant value, and using cross-feature engagement as a lever for retention and portfolio health. - Build proactive and reactive retention strategies — designing the triggers, interventions, and experiences that keep members engaged and in good standing, and that recover at-risk members before they lapse or default. - Develop a clear point of view on repayment UX and outcomes, treating repayment not as a back-office function but as a core product surface that builds trust, drives repeat borrowing, and protects the health of the portfolio. - Champion an AI-first way of working across the product lifecycle — using AI to accelerate research synthesis, experiment design, and spec writing, while identifying where AI can create differentiated product experiences within borrowing (e.g., dynamic credit offers, personalized repayment nudges, intelligent risk signals). - Define success metrics and instrumentation from day one — draw rates, repayment rates, retention cohorts, and cross-feature engagement — and build the experimentation and analytics framework to make fast, confident decisions. - Develop a strong competitive point of view on how borrowing products are evolving for immigrant and underserved consumer segments, and translate that into product bets that differentiate Remitly. - Represent the voice of the customer — conducting direct user research, synthesizing qualitative and quantitative signals, and building a roadmap that the full cross-functional team can rally around. - Communicate roadmap, trade-offs, and portfolio health clearly to cross-functional stakeholders and executive leadership, building alignment and momentum across Remitly's broader financial services strategy. "You Have:" section (I'll list relevant bullets, but need to be careful not to list everything if it makes the section too thin; but the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include all substantive details from "You Have:", but format as list items. However, "Prefer a few substantive sections over many thin ones." I'll include the key parts, but all are substantive. I'll list them as

    items. Let's extract "You Have:" bullets: - 8+ years of product management experience, with significant time in consumer fintech or financial services products — including demonstrated ownership of a full customer lifecycle. - A track record of scaling a financial product from early-stage through high-volume usage, with measurable impact on retention and repayment or portfolio health outcomes. - Deep familiarity with lending and credit product dynamics — underwriting, draw behavior, repayment mechanics, delinquency management — and a strong instinct for where product decisions drive portfolio outcomes. - Experience driving cross-product or platform engagement, with an understanding of how feature breadth and usage depth connect to retention and customer lifetime value. - An AI-first mindset