Senior Technical Program Manager - Credit & Lending

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - Intro paragraph: "Back to jobs New Senior Technical Program Manager - Credit & Lending San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States Mercury is building Mercury Bank, N.A., a proposed nationally chartered bank focused on serving ambitious businesses. Credit and lending are central to that mission, and as we migrate our charge card and term loan products to the Bank's own balance sheet and build the next generation of lending infrastructure, we need someone who can hold the full program together. The Senior Technical Program Manager for Credit and Lending will own end-to-end delivery of the technology programs that power Mercury's charge card, term loan, and adjacent credit products. You will be the connective tissue between Engineering, Product, Risk, Compliance, Treasury, and Operations: setting strategy for how these programs run, surfacing tradeoffs that unblock leaders, sequencing the critical path, and ensuring that what ships is audit-ready from day one. We are looking for someone who has operated at this level before, in a regulated environment, at scale, with real accountability for outcomes. Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC." That's about the role. Then "What You'll Do" with bullet points (actually paragraphs). We need to extract responsibilities. List: - Program ownership: Own the integrated program plan across all active credit and lending workstreams, covering milestones, dependencies, and critical paths across Engineering, Product, Risk, Compliance, Treasury, and Operations. - Proactively manage sequencing, resourcing tradeoffs, and escalations. When initiatives are off-track, you identify it first and bring a recommended path forward. - Ensure Compliance, Treasury, and Operations readiness lands alongside product and regulatory milestones. - Drive incident learnings back into design, test coverage, and runbooks so each issue improves the underlying system, not just fixes the symptom. - Contribute to the overall (proposed) Mercury Bank, NA technical program, collaborating with other TPMs to build a holistic view of progress and risks. - Governance and decision-making: Keep a single source of truth for status, decisions, risks, and owners. Maintain a living RAID log with clear owners and impact assessments. Facilitate structured decision-making by surfacing options and tradeoffs to leaders before problems escalate. Build and improve the operating systems that drive credit and lending product decisions: planning cycles, reviews, decision frameworks, launch readiness. - Communication and influence: Produce concise, predictable updates calibrated to the audience. Synthesize complex cross-functional information into recommendations that help executives decide and move. Produce documentation of program objectives, architecture decisions, and operational impacts that onboards new team members without requiring a meeting to explain it. Function as a trusted thought partner to engineering leads, product managers, and senior leadership. - Execution and improvement: Identify inefficiencies and eliminate them through automation, AI tooling, or process redesign. Lead technical retrospectives and post-mortems, ensuring learnings are systematized rather than forgotten. Then "Experience" section: "What we're looking for:" with bullet points. List: - 10+ years of program management or technical program management in a high-growth or regulated environment. - Direct experience in financial services, fintech, or credit infrastructure. Compliance, audit, reporting and risk management obligations are familiar territory. - Track record of operating at the department or business level, owning programs with multiple concurrent workstreams and cross-functional accountability. - Proven ability to communicate with and influence executive stakeholders, in writing and in high-stakes meetings, without a senior manager to translate. - Bonus: Familiarity with the lending tooling ecosystem such as loan origination, credit risk management and lending management systems. Then "How you work" bullet points (maybe skills/qualities). Could be under Skills or Qualities. List: - Product-first. You evaluate everything through: what is the user problem, what is the fastest path to learning, what actually moves the needle. - AI-native. You use AI tools to do your actual work. You have built workflows or tooling that changed how your team operates. When you see a repetitive process, you automate it. - Comfortable in ambiguity. You build structure where there is none. - Systems thinker. You see dependencies, second-order effects, and points of failure before they surface, and you build programs that account for them. - Energized by building and operating. You do your best work designing the system and running it well once it is built. Then "What You Bring" bullet points (skills/qualifications): - Technical fluency. You can understand and challenge engineering decisions, identify technical risks early, and translate complexity for non-technical stakeholders. - Exceptional written and verbal communication. You write documentation that clarifies hard decisions and build frameworks teams actually adopt. - Commercial instincts. You understand the financial dynamics of a lending business well enough to evaluate tradeoffs with authority. - High emotional intelligence. You build trust quickly across engineering, product, risk, and executive stakeholders. You navigate complex interpersonal situations without losing credibility or momentum. Then "Total Rewards" section: includes base salary, equity, benefits. Provide salary ranges. We need to include Pay section if posting actually states them. Yes, they give salary ranges for US employees in certain cities, US employees outside those, Canadian employees. Thus we can create a Pay section with those ranges. Benefits: they mention total rewards package includes base salary, equity (stock options/RSUs), and benefits. But they don't detail specific benefits (health, 401k, etc). Since they didn't list specific benefits, we should not create a Benefits section unless they actually state them. The phrase "total rewards package at Mercury includes base salary, equity (stock options/RSUs), and benefits." is vague; no specifics. According to rule: never create Benefits section unless posting actually states them. Since they didn't list specific benefits, we should omit Benefits section. Schedule: not mentioned. So omit Schedule. Now we need sections: About the role (maybe as

About the role

), Responsibilities (

Responsibilities

), Requirements (

Requirements

), Qualifications (

Qualifications

)? The posting has Experience and What you bring and How you work. Could map to Requirements (experience), Qualifications (what you bring), Skills (how you work). But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. Thus: - About the role: intro paragraph(s) describing role and mission. - Responsibilities: the "What You'll Do" bullet points. - Requirements: the "Experience" bullet points (10+ years etc). Could also include "Bonus" as part of requirements. - Qualifications: maybe "What You Bring" bullet points (technical fluency, communication, commercial instincts, emotional intelligence). Or could be Qualifications. - Skills: "How you work" bullet points (product-first, AI-native, etc). - Pay: salary ranges. We must not include Benefits or Schedule. We must not repeat job title as heading. We must not include Job ID etc. We must output only HTML fragment. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus for each section we need to decide if content is prose or list. About the role: likely prose paragraphs. Could be multiple

  . Responsibilities: list of duties ->

  • . Requirements: list ->
    • . Qualifications: list ->
      • . Skills: list ->
        • . Pay: could be prose or list. Since it's salary ranges, could be

          with details. We must preserve all substantive information; do not invent or summarize away detail. Thus we need to include all bullet points exactly as given (or close). Must not omit any. Let's extract each bullet precisely. From "What You'll Do": We have headings within that section: Program ownership, Governance and decision-making, Communication and influence, Execution and improvement. But we can just list each bullet as separate

        • items, preserving the content. Let's list them: 1. Own the integrated program plan across all active credit and lending workstreams, covering milestones, dependencies, and critical paths across Engineering, Product, Risk, Compliance, Treasury, and Operations. 2. Proactively manage sequencing, resourcing tradeoffs, and escalations. When initiatives are off-track, you identify it first and bring a recommended path forward. 3. Ensure Compliance, Treasury, and Operations readiness lands alongside product and regulatory milestones. 4. Drive incident learnings back into design, test coverage, and runbooks so each issue improves the underlying system, not just fixes the symptom. 5. Contribute to the overall (proposed) Mercury Bank, NA technical program, collaborating with other TPMs to build a holistic view of progress and risks. 6. Keep a single source of truth for status, decisions, risks, and owners. Maintain a living RAID log with clear owners and impact assessments. 7. Facilitate structured decision-making by surfacing options and tradeoffs to leaders before problems escalate. 8. Build and improve the operating systems that drive credit and lending product decisions: planning cycles, reviews, decision frameworks, launch readiness. 9. Produce concise, predictable updates calibrated to the audience. Synthesize complex cross-functional information into recommendations that help executives decide and move. 10. Produce documentation of program objectives, architecture decisions, and operational impacts that onboards new team members without requiring a meeting to explain it. 11. Function as a trusted thought partner to engineering leads, product managers, and senior leadership. 12. Identify inefficiencies and eliminate them through automation, AI tooling, or process redesign. 13. Lead technical retrospectives and post-mortems, ensuring learnings are systematized rather than forgotten. Check if any missing: The bullet about "Drive incident learnings back into design, test coverage, and runbooks so each issue improves the underlying system, not just fixes the symptom." included. Now Requirements (Experience): List: - 10+ years of program management or technical program management in a high-growth or regulated environment. - Direct experience in financial services, fintech, or credit infrastructure. Compliance, audit, reporting and risk management obligations are familiar territory. - Track record of operating at the department or business level, owning programs with multiple concurrent workstreams and cross-functional accountability. - Proven ability to communicate with and influence executive stakeholders, in writing and in high-stakes meetings, without a senior manager to translate. - Bonus: Familiarity with the lending tooling ecosystem such as loan origination, credit risk management and lending management systems. We should keep the "Bonus:" as part of list item. Now Qualifications (What You Bring): List: - Technical fluency. You can understand and challenge engineering decisions, identify technical risks early, and translate complexity for non-technical stakeholders. - Exceptional written and verbal communication. You write documentation that clarifies hard decisions and build frameworks teams actually adopt. - Commercial instincts. You understand the financial dynamics of a lending business well enough to evaluate tradeoffs with authority. - High emotional intelligence. You build trust quickly across engineering, product, risk, and executive stakeholders. You navigate complex interpersonal situations without losing credibility or momentum. Now Skills (How you work): List: - Product-first. You evaluate everything through: what is the user problem, what is the fastest path to learning, what actually moves the needle. - AI-native. You use AI tools to do your actual work. You have built workflows or tooling that changed how your team operates. When you see a repetitive process, you automate