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.

Enterprise Transformation owns Kraken's internal AI platform. AI tooling is deployed at scale across the org. Tiered spend controls are live, a governed integration gateway is in production, and a system inventory is being built against real regulatory obligations. The next constraint is not access. It's capability. The frontier moves every few weeks, and most of what arrives is a protocol, API, or primitive that someone has to turn into something the rest of the company can safely use.

 

The opportunity

• Design and build the technical layer of the AI platform, from integration surface to production runbook. Identify capability gaps between what's possible and what the organization can safely use, then close them by evaluating vendors or building internally.

• Own the governed integration gateway as an engineering surface. You'll handle connector onboarding, authentication flows including OAuth and federated identity, reliability, and vendor escalation when things break.

• Build internal tooling that extends the platform. Think agent scaffolding, reusable skills and prompt assets, evaluation harnesses for model changes, provisioning automation, and integrations between AI tooling and your systems of record.

• Configure and operate tiered spend controls across the AI estate. Set caps by role and tier, build alerting rules, manage exception queues, run monthly reconciliation against vendor commitments, and eliminate the current single author risk in cap automation.

• Implement the technical controls behind policy on data handling, retention, and model eligibility. This means identity integration, SSO and SCIM, entitlement by role and tier, and workspace configuration where retention terms differ by model class.

• Work directly with teams to unblock them. Sit with them, understand the workflow, build or configure the thing that enables them to get real leverage from the tools.