Staff Site Reliability Engineer - Dev Platform

About the role

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.

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 engineers build a lot of software. Developer Platform AI builds the AI systems they use to do it: agents that write and review code, simple access to the best models in the tools they already use, and the infrastructure that connects AI to our internal systems.

This is a small team with a lot of reach. The tools you ship will change how engineers across Kraken work every day, and you'll see that happen directly. The work spans agent platforms, code review, LLM routing and cost controls, MCP integrations with tools like Slack, Jira and GitLab, and the security and observability that make all of it safe to run.

If you want to work on applied AI with real users from day one, this is that job.

THE OPPORTUNITY

- LLM traffic doesn't behave like normal API traffic. Requests are long-running, streaming and expensive. One prompt can cost a few cents or a few dollars. One team's burst can burn another team's budget. Providers change their rate limits, failure modes and pricing without warning. Running this well is a problem few companies have solved, and it's the job. - Own the reliability of the platform engineers depend on: the AI Gateway, the agent runtime and the connections to internal tools. Set the SLOs, own the error budgets and decide what happens when they're spent. - Design resilience across model providers: routing, failover, retries, rate limiting and graceful degradation when a provider is slow, throttling or down. - Make LLM traffic legible. Build observability that shows latency, errors, token usage and cost by team, model and use case, so engineers can see what their workloads cost and where they're spending their time waiting. - Treat capacity and cost as one problem. Routing decisions affect both latency and spend, and you'll own the tradeoff directly. - Work with Security, Finance and AI governance to put access controls, budgets, audit logging and data handling into the platform, not into a spreadsheet next to it. - Lead incident response and blameless post-incident reviews. Turn what breaks into fixes that stay fixed. - Automate operations with infrastructure as code, safe deployments and progressive rollouts, so the platform gets more reliable as it grows rather than more fragile. - Mentor engineers and raise the operating standard across the team. This is a Staff role. You'll set the technical direction for how the platform runs, not just keep it running. The platform is small enough that your decisions shape it directly, and used broadly enough that they affect every engineering team at Kraken.