Senior Technical Program Manager - Credit & Lending

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, etc. Also remove application instructions. The posting includes sections: description of role, what you'll do (program ownership, governance, communication, execution). What we're looking for (experience, etc). How you work (product-first, AI-native, etc). What you bring (technical fluency, communication, commercial instincts, emotional intelligence). Total Rewards includes salary ranges. We need to map these to sections: About the role (maybe intro paragraph). Responsibilities (what you'll do). Requirements (experience). Qualifications (maybe "What we're looking for" includes experience and qualifications). Skills (maybe "How you work" and "What you bring"). Benefits (maybe "Total Rewards" includes benefits but not detailed; only mentions base salary, equity, benefits. No specifics of benefits. So we should not create Benefits section unless specific content. The posting says "Total Rewards The total rewards package at Mercury includes base salary, equity (stock options/RSUs), and benefits." No detail of benefits. So we should not create Benefits section because no specific benefit details. Pay section: we have salary ranges. So include Pay. Schedule: not mentioned, so omit. We need to include sections only when posting has real specific content. So we will have: About the role (intro paragraph). Responsibilities (what you'll do). Requirements (experience). Qualifications (maybe combine with Requirements? But we need separate if content. Could treat "What we're looking for" as Requirements. "How you work" and "What you bring" as Skills. Could also have Qualifications separate if we want to list education? Not present. Might skip Qualifications if no specific content. But we need to decide. We have: "What you'll do:" -> Responsibilities. "What we're looking for:" -> Requirements (experience). Could also be Qualifications. "How you work" and "What you bring" -> Skills. "Total Rewards" -> Pay (salary ranges). Could also include equity mention but that's part of Pay. Thus sections: About the role (intro paragraph before "What you'll do:"), Responsibilities, Requirements, Skills, Pay. We must not include Benefits or Schedule. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit details. So we need to include all bullet points from the posting. Let's extract content. Intro paragraph: "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." We need to keep that as About the role paragraph. Now Responsibilities: Under "What you'll do:" there are bullet-like paragraphs but not bullet list. We need to convert to

  • for any list of duties/requirements/benefits. The content includes several bullet-like items separated by line breaks. We'll treat each as a list item. List items: - 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. We need to keep these as list items. Could group under subheadings? Not allowed; only headings are h3 sections. Within section we can have paragraphs and lists. We could keep the headings like "Program ownership" as bold? Not required. We'll just list each as
  • . Might be long but okay. Now Requirements: Under "What we're looking for:" we have bullet-like items: - Experience 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 need to keep as list items. Now Skills: Combine "How you work" and "What you bring". Let's list each bullet. How you work: - 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. What you bring: - 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. We'll make a combined list under Skills. Now Pay: Under "Total Rewards" we have salary ranges: - US employees in New York City, Los Angeles, Seattle, or the San Francisco Bay Area: $180,200—$225,200 USD - US employees outside of New York City, Los Angeles, Seattle, or the San Francisco Bay Area: $162,200—$202,700 USD - Canadian employees (any location): $170,300—$212,800 CAD Also mention base salary, equity (stock options/RSUs), and benefits. But we should not invent benefits details. We can include mention of equity as part of Pay? The instruction: include Pay section only when posting actually states them. It does state salary ranges. So we can include those. Also we could mention equity and benefits briefly as prose? The Pay section could include a paragraph about total rewards includes base salary, equity, benefits. Then list ranges. That preserves info. We must not include Benefits section separately. Now we need to output HTML fragment only, no markdown fences. Let's craft. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    ...

    Skills

    ...

    Pay

    ...

    ...
    Make sure to preserve all details, no omission. Check for any boilerplate to remove: The EEO paragraph, the accommodation statement, the "Mercury values diversity & belonging..." etc. Remove those. Also remove the line "*Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC." This is substantive? It's a note about banking services. It's part of the intro; we should keep it as it's substantive info about the company. It's not boilerplate; it's a clarification. Keep. Now ensure we didn't miss any details: The intro also includes "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." Keep. Now check responsibilities list: Ensure we captured all bullet points. From posting: "What you'll do: 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