Knowledge Management & Training Lead

Mercury•San Francisco, NY

19h

About The Position

Mercury's Vendor Strategy team is hiring a Knowledge & Enablement Lead to own the frameworks and governance for how Mercury's risk operations — and the BPO partners who deliver them — document, learn, and prove what they do, as we scale toward bank readiness. This is one role spanning two disciplines: knowledge management (the single source of truth for how work gets done) and training (how internal and vendor teams learn to do it). It is a system design and framework role with real execution target behind it. You will set the requirements, standards, and review cadence that risk operations documents and trains against, you will directly manage a BPO-based team of content writers who produce against those standards, and you will drive adoption through enablement practitioners embedded on other teams. If you need positional authority to make change happen, this is the wrong role. If you can set a knowledge and enablement standard so clearly that people adopt it because it's obviously better, it's the right one.

Requirements

7–10+ years of experience in knowledge management, enablement/L&D, operational training, or related functions, including experience building or substantially scaling a knowledge-management and/or enablement function.
Experience operating in a regulated industry or similarly complex, control-oriented environment.
A hybrid skill set spanning knowledge management and enablement/L&D — able to design both the systems that govern how operational knowledge is created and maintained and how teams are trained and certified against it.
Experience designing knowledge, training, and certification programs for BPO or outsourced operations teams, with an understanding of how to make complex information clear, accessible, and actionable for a BPO audience.
Experience leading a team, pod, or vendor-delivered group — setting priorities and performance expectations, providing direct feedback, maintaining a high quality bar, and developing capability.
Track record of setting standards that teams outside your reporting line actually adopted, demonstrating strong cross-functional influence without authority.
Strong systems thinking and writing skills, with the ability to build practical operating models and cadence in ambiguous or evolving environments.
Experience defining and reporting metrics that demonstrate the effectiveness of knowledge and enablement programs, including their impact on operational performance.
A thoughtful perspective on how AI can improve knowledge management and enablement, including how AI-powered tools can help teams find and apply accurate information in real time.

Nice To Haves

Experience in financial services, banking, fintech, payments, or a related financial-services environment.
Familiarity with regulated operations such as KYC/KYB, AML, fraud, or disputes, and with what an examiner or internal auditor expects documentation to look like.
Familiarity with knowledge-management and enablement platforms ideally Guru, WorkRamp, or similar tools.
Experience operating as the central standard-setter across a federated or decentralized organization.
Startup or high-growth experience; comfort building from a blank page.

Responsibilities

Own the knowledge framework. Define the architecture for the canonical library of risk-operations procedures — the ownership model, versioning, last-published and next-review dates, deprecation rules, and a live annual review cycle. Design for how knowledge is increasingly accessed and applied through AI-powered tools, not only how it is documented and stored. This is a systems problem before it is a writing problem.
Set policy, procedure, and documentation standards. Own the standards, templates, and structural conventions that govern how policy and procedure get written across risk operations — structured so business risk can build RCSAs and controls directly from them, and so compliance can approve regulatory content against a consistent format rather than a bespoke one each time.
Govern adoption and quality. Run the governance layer that keeps standards live: review cadence, compliance against the standard, exception handling, and escalation when programs drift. Own the audit and examination readiness of the documentation estate.
Manage the BPO content-writing team. Directly manage a vendor-based team of technical content writers — set priorities and performance expectations, give regular feedback, run the quality bar, participate in selection and composition of the pod, and develop the writers' capability against Mercury's frameworks.
Define requirements for teams you don't manage. Set the enablement and documentation requirements that enablement practitioners embedded across risk programs execute against, and make those requirements clear, useful, and adoptable without a reporting line to enforce them.
Architect training and certification. Design a training and certification system built for vendor delivery — translating complex operational content for BPO audiences through milestone-based curricula, topic-level certifications, and routing by certification — distinct from an internal-only L&D lens.
Instrument the function. Define and report the metrics that show the programs improving over time: time-to-productivity, certification coverage, procedure freshness and review compliance, and the link between quality-failure patterns and training interventions.
Enable cross-skilling. Build the documentation and certification pathways that let staffing flex across risk programs (onboarding, ODD/EDD, AML/sanctions, fraud, disputes) as demand moves