Senior Program Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate: Application Deadline, Department, Employment Type, Location maybe? Those are metadata; we can fold minor metadata into a short

or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short

with Application Deadline, Department, Employment Type, Location maybe. But we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the description text etc. We need to parse the posting. Let's extract sections: - Description: includes imaginative description about Napier AI. That's prose. - The Role: Senior Program Manager (but we shouldn't repeat job title as heading). Under that there is a description of role responsibilities etc. - Then "Your day to day: Senior Programme Manager" with subheadings: Program Leadership, Client and Executive Stakeholder Management, Commercial Governance, Delivery Excellence and Risk Management, Third-Party Regulatory Instruments, Customer Outcomes and Transition. - Then "Do you have what it takes: Essential" list of requirements. - Then "Highly Desirable" list. - Then "About You" prose. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. "About the role": could be the description paragraph about Napier AI and the role overview. "Responsibilities": could be the bullet list under "Your day to day" sections (Program Leadership etc). Those are responsibilities. "Requirements": essential requirements list. "Qualifications": maybe the highly desirable? Or we could treat essential as Requirements, highly desirable as Qualifications. Or we could combine. "Skills": maybe the skills like commercial and contractual instincts, etc. But we can also put under Skills. "Benefits", "Pay", "Schedule": not present in posting. So we should NOT include those sections. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to use

for each section heading. Use

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

  for prose. We must not repeat job title as heading. So we won't have a heading for Senior Program Manager. We need to preserve all substantive information: include description paragraphs, role overview, responsibilities bullet points, essential requirements, highly desirable, About You. We need to format lists appropriately. Let's extract prose for About the role: The initial "Description" paragraph(s) plus maybe the "The Role: Senior Program Manager" paragraph before the day-to-day. That is about the role. Let's capture: Description: "Imagine catching criminals before they strike - that’s exactly what Napier’s AI-powered platform does! By analysing transactions and customers in real time, Napier AI’s technology empowers financial institutions to spot suspicious activity, like money laundering, and stops it in its tracks. Napier AI’s technology works like a digital detective, combining AI with smart analytics to outthink criminals and protect people’s money from becoming criminal proceeds. It’s not just about stopping crime - it’s about making the financial world safer and more trustworthy for everyone. Collaboration, innovation and wonderful people are just some of the reasons to bring your career to Napier. Our culture is shaped by our core values that promote equality, creativity, and opportunity in everything we do." Then "The Role: Senior Program Manager You will lead Napier AI's most complex and highest-value enterprise delivery programs including Tier 1 bank implementations. From there you will take portfolio leadership of Napier's strategic Tier 1 accounts as we scale that tier of the business. These programs operate under regulatory and contractual hard deadlines, multi-party governance (bank, Napier, hyperscaler, third-party integrators), and executive-level scrutiny on both sides. You will be brought in at critical phases, expected to establish authority quickly, restore delivery confidence where needed, hold the commercial line, and land go-live cleanly. This is a senior, customer-facing role that carries programs accountability end to end. You will be the single senior Napier delivery point of contact with the client's program director and executive sponsor. You will be trusted internally to hold Product, Engineering, Platform, and Professional Services to their commitments to ensure customers realise value from their investment in Napier's platform." That is about the role. Now Responsibilities: The bullet points under "Your day to day: Senior Programme Manager" with subheadings. We could treat each subheading as a responsibility category, but we need to output a list of duties. Could flatten into a single

  with each responsibility as
  • . However we need to preserve the subheadings maybe as part of the li text. Could do:
  • Program Leadership: ...
  . That preserves detail. Let's extract each: Program Leadership: - Own end-to-end delivery of Napier's largest enterprise programs, including Tier 1 National and European bank engagements - Establish and run program governance: steering committees, executive status reviews, RAID discipline, decision logs - Define and defend the acceptance criteria for go-live and any regulatory or contractual milestone - Coordinate delivery across Napier's Professional Services, Product, Engineering, Platform, Support, and Customer Success functions Client and Executive Stakeholder Management: - Act as the single senior Napier delivery contact with the client's program director, delivery leads, and executive sponsors - Chair steering committees and executive status forums with authority and credibility - Prevent client escalations bypassing program governance - Represent Napier at client executive escalations, industry regulator interactions where relevant, and third-party (hyperscaler, SI) governance Commercial Governance: - Own program P&L, forecast, and margin - Run formal change control against every scope movement, defect classification, and delivery obligation - Defend Napier against uncapped commitments, one-sided release triggers, and unbounded acceptance criteria - Hold the defect versus change request line: no product commitment leaves Napier without your sign-off - Escalate commercial and contractual risk to the CCO before it becomes a client-facing position Delivery Excellence and Risk Management: - Maintain the end-to-end program plan, dependency map, and critical path - Own the risk register and drive mitigations with named accountable owners - Establish and maintain go/no-go readiness assessment against agreed criteria - Drive continuous improvement in Napier's delivery methodology from evidence in the field Third-Party Regulatory Instruments: - Manage the operational side of any escrow, source-code deposit, or equivalent regulatory instrument on your programs, working with Napier Legal, Engineering, and the third-party agent - Manage client expectations on trigger events, deposit content, and verification cycles Customer Outcomes and Transition: - Ensure customers achieve successful implementation, adoption, and business value realisation - Manage a clean transition from delivery into Customer Success and Support with complete documentation and no orphaned commitments Now Requirements (Essential): List: - 12+ years leading large-scale enterprise software delivery programs, with at least 5 years at senior program director or equivalent level - Direct financial crime compliance domain experience: AML, KYC, Transaction Monitoring, Sanctions Screening, or Case Management platforms. Not adjacent, not learned on the job during a stint - deep and current - Delivered at least one enterprise implementation into a Tier 1 or systemic bank in the UK, EU, or US, chairing steering committees at C-1 level - Proven turnaround experience: taken over a live enterprise program mid-flight, restored client confidence, re-baselined credibly, and landed a successful outcome - Cloud-based enterprise SaaS platform delivery experience, ideally including hyperscaler-hosted environments (Azure, AWS, or GCP) - Multi-vendor program experience across client, primary vendor, hyperscaler, and system integrator - Strong commercial and contractual instincts: has run defensive change control, held scope, defended margin, and defeated attempts to reclassify enhancements as defects - Experience of programs with regulatory or contractual hard deadlines (go/no-go gates, DORA, PRA/FCA supervisory dates, or equivalent) - Presence and credibility at C-1 and C-suite client levels Now Qualifications (Highly Desirable): - Experience of escrow, source-code deposit, or equivalent third-party regulatory instruments in a live client engagement - Experience across multiple geographic regions (EMEA, Americas, APAC) - Program management certifications (MSP, PgMP, PMP, Prince2) - useful, but not a substitute for the experience above - Experience in Private Equity-backed software companies operating to a defined value creation plan Now Skills: Could be derived from "About You" paragraph: calm authority, structured judgement, comfortable in technical defect triage, commercial change control meeting, bank executive steering committee, knows when to push and when to protect, willing to hold uncomfortable positions internally to protect commercial and delivery outcome, does not need consensus to act, needs clarity of accountability, direct access to executive decision-making, trust to run program. We could treat that as Skills section. Now we need to output HTML fragment only. We should also include a short

  for metadata like Application Deadline, Department, Employment Type, Location? The instruction says fold minor metadata into a short

  or drop it. We could include a

  with that info: "Application Deadline: 13 November 2026 | Department: Professional Services | Employment Type: Permanent - Full Time | Location: USA". That preserves info. But we need to ensure we don't create headings for those. So we can put that

  before sections. Now we need to ensure we don't include any boilerplate like cookie/navigation/legal/EEO etc. There's none. Now output. Structure:

  Application Deadline: 13 November 2026 | Department: Professional Services | Employment Type: Permanent - Full Time | Location: USA

  About the role

  ... (combined description paragraphs)

  Responsibilities

  • Program Leadership: Own end-to-end delivery of Napier's largest enterprise programs, including Tier 1 National and European bank engagements; Establish and run program governance: steering committees, executive status reviews, RAID discipline, decision logs; Define and defend the acceptance criteria for go-live and any regulatory or contractual milestone; Coordinate delivery across Napier's Professional Services, Product, Engineering, Platform, Support, and Customer Success functions
  ... etc. But we need to keep each bullet as separate
  • maybe with sub-bullets? The instruction: Use
    • for any list of duties/requirements/benefits. So we can have each duty as a
    • . Could break each line into separate
    • . That would be many
    • but okay. We need to preserve all detail. So we can split each bullet line. Thus for Responsibilities we will have many
    • items, each representing a bullet. Similarly for Requirements and Qualifications. Now for Skills we can have

      with the About You paragraph. Let's craft. First, combine About the role paragraphs: Paragraph1: Description (the imaginative part). Paragraph2: The Role: Senior Program Manager ... (the role overview). We'll combine into one

      maybe two

      s? The instruction: use

      for prose. Could have multiple

      elements. We'll output two

      s. Now Responsibilities: We'll list each bullet as

    • . We'll need to keep the subheadings maybe as part of the li text. Let's list them: Program Leadership: - Own end-to-end delivery of Napier's largest enterprise programs, including Tier 1 National and European bank engagements - Establish and run program governance: steering committees, executive status reviews, RAID discipline, decision logs - Define and defend the acceptance criteria for go-live and any regulatory