Building the Future of Open Finance

Payward - the parent company behind Kraken, NinjaTrader, Breakout, xStocks, Payward Services and CF Benchmarks - has spent the last 15 years building one of the most modern and globally accessible financial infrastructure platforms in the industry, built to advance an open, global financial system.

Before you apply, we encourage you to explore our culture page to understand what drives us and how we work.

The team

Founded in 2011, Kraken is one of the world's longest-standing crypto platforms, trusted by over 10 million individuals and institutions across the globe. It offers spot trading, margin, futures, staking, and OTC services, with products built for both individual investors and institutional clients.

Kraken's Compliance Operations teams, including the Financial Intelligence Unit (FIU), investigations and enhanced due diligence, are the front line of how Kraken detects and responds to financial crime. The systems they run on sit within Core Services Product, alongside the engineering teams who build them. That covers alert ingestion, case management, investigator tooling and a growing set of automation and AI tools.

This role owns the product for that investigation platform. That means how an alert is created, enriched, grouped and suppressed. How it becomes a case. How an investigator reaches and documents a decision. And how every step is evidenced to a regulator or auditor. You'll start with the FIU, where the workflows are most complex and the audit bar is highest, then extend the platform across Compliance Operations.

The opportunity

• 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. Write phased deliverables and acceptance criteria that Compliance signs off, and hold the line when scope moves.
• Get requirements in before engineering starts. Build 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. Reconcile 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. That means 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.