About The Position

This role owns the product for the investigation platform within Kraken's Compliance Operations. This includes how alerts are created, enriched, grouped, and suppressed, how they become cases, how investigators reach and document decisions, and how every step is evidenced to regulators or auditors. The role will initially focus on the Financial Intelligence Unit (FIU), where workflows are most complex and the audit bar is highest, and will then extend the platform across Compliance Operations.

Requirements

  • 4+ years of product management, including 2+ years on financial-crime systems such as transaction monitoring, investigations, case management, KYC/EDD or sanctions screening.
  • Working knowledge of how an AML programme is examined, including the questions regulators, internal audit and model validation ask about monitoring, filing and control systems.
  • The technical fluency to go deep on data flows and system design with engineers, and to spot when a design won't meet the requirement.
  • A track record of shipping internal tools or operational platforms that measurably changed how an operations team works.
  • Clear, concise writing, from PRDs and phase plans to audit walkthroughs and executive updates.
  • The judgement to tell a senior stakeholder a timeline isn't realistic because the requirements aren't written yet, and to keep the relationship intact.

Nice To Haves

  • Direct FIU experience, such as alert disposition, SAR/STR filing or leading investigators.
  • Crypto or digital-asset experience, such as blockchain analytics, wallet-level transaction analysis or focal vs counterparty logic.
  • Experience shipping AI or ML into a regulated investigative workflow, including the control design.
  • Build-vs-buy and vendor evaluation for monitoring or case-management tooling.
  • Experience with programmes that span jurisdictions (UK, EU/MiCA, US).

Responsibilities

  • Own the investigation-platform roadmap end to end, sequence it and defend it, and re-sequence it when a regulator or the RCO raises a P0.
  • Define "done" before build starts, writing phased deliverables and acceptance criteria that Compliance signs off, and holding the line when scope moves.
  • Get requirements in before engineering starts, building the intake between Compliance policy, monitoring rules, and case management so that changes don't reach investigators before their workflows are ready.
  • Understand the process before building, reconciling policy and SOPs against what investigators actually do and what the system actually does. Know the difference between a process fix and a technical one, and say which requests are in scope for engineering.
  • Understand the pipeline well enough to challenge it: ingestion, profile and transaction resolution, suppression and grouping logic, and reconciliation between vendor output and case management. Be able to walk an auditor through it with live examples.
  • Make auditability a first-class requirement: audit trail, data lineage, evidence retention, reviewer attribution, change-management controls, and validation of filtering and suppression logic.
  • Ship automation and AI into regulated workflows with controls that hold up in Compliance, IT, and privacy audits, meaning human-in-the-loop design, explainability, and ongoing monitoring.
  • Run the operating rhythm: a shared forum with engineering and adjacent product managers, a regular stakeholder update, and one delivery status that everyone reads the same way.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service