Learning & Development Specialist - Fraud / Disputes

<h3>About the Team</h3> <p>Transaction Risk Enablement is the shared services function supporting Mercury's Fraud, Disputes, and Risk UX programs. We build the knowledge base articles, SOPs, and eLearning that frontline teams rely on to do their jobs accurately and consistently — and that hold up to regulatory scrutiny in a financial services environment. This is a small, high-output team doing work that directly shapes how well-documented and audit-ready Mercury's risk operations are.</p> <h3>Role Summary</h3> <p>We're looking for a L&amp;D Specialist to join a growing team supporting Fraud, Disputes, and Risk UX. You'll write and maintain formal SOPs, Guru knowledge base articles, and Articulate-built eLearning — translating operational processes and regulatory requirements into content that's clear, accurate, and usable by the teams who rely on it every day. You'll work primarily within one or two of these domains, going deep on the processes and regulatory context that matter most there, while collaborating with Specialists and SMEs across the broader team.</p> <p>This is an experienced-contributor role: you'll own content projects from scoping through publication with minimal oversight, exercise sound judgment in ambiguous or incomplete-information situations, and be looked to as a source of regulatory and process knowledge others build on. You're not just executing a content backlog — you're expected to spot where standards or resources need to improve and drive those improvements yourself.</p> <p>This is a strong fit for someone who enjoys both the craft of instructional design and the discipline of regulatory-grade technical writing — and who wants ownership over content that has real operational weight, not just training that gets built once and forgotten.</p> <p><em>*Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC.</em></p> <h3>What You'll Do</h3> <ul> <li>Own SOP, knowledge base, and eLearning projects end to end — from initial scoping and SME discovery through drafting, review, sign-off, and publishing — with minimal day-to-day direction</li> <li>Author and maintain formal SOPs following Mercury's standard template — version control, regulatory citations, sign-off workflow, and publishing to PDF</li> <li>Write and update Guru knowledge base articles as operational job aids for frontline teams</li> <li>Design and build eLearning modules in Articulate 360 (Rise) that train analysts on new and updated procedures</li> <li>Partner directly with process owners, ops managers, and subject matter experts to extract and structure knowledge that often exists only informally — in SME notes, verbal walkthroughs, or partially maintained knowledge base articles</li> <li>Translate relevant regulatory source material (e.g., OCC guidance, Reg E, Reg Z) into procedures that are clear to frontline staff and defensible under review</li> <li>Keep existing content current as processes, tools, and regulatory requirements evolve, and proactively flag where team standards or templates need to improve</li> <li>Manage your own authoring pipeline, prioritizing based on business risk and team dependencies, and navigate ambiguity when priorities or source material are incomplete</li> <li>Participate in and often lead review and sign-off cycles, incorporating SME and compliance feedback into clean, versioned final documents</li> <li>Contribute to shared team resources and standards — templates, style guides, review processes — and mentor other Specialists on regulatory writing and instructional design practices</li> </ul> <h3>What You'll Bring</h3> <ul> <li>1–3 years writing SOPs and eLearning in a regulated financial services environment — banking*, fintech, payments, or compliance preferred</li> <li>Hands-on proficiency with Articulate 360 (Rise) or an equivalent eLearning authoring tool; familiarity with Guru, or other knowledge base system.</li> <li>Strong technical writing skills — you can take a complex, multi-step operational process and turn it into a procedure that's clear, unambiguous, and audit-ready</li> <li>Comfort working from regulatory source material (e.g., OCC handbooks, Reg E, Reg Z)</li> <li>Ability to work from incomplete or informal inputs — SME notes, existing knowledge base content, verbal walkthroughs — rather than requiring fully structured source material</li> <li>Experience in one or more of the following disciplines: fraud operations (account or card), disputes/chargeback processing, or risk review</li> <li>Self-directed