Staff Engineer - Growth - Verifications

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 https://www.kraken.com/culture 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.

The Pro Verifications team decides whether a business signing up on the Pro side is who it says it is, and whether we're allowed to onboard it. That means figuring out who actually owns the business, running it against sanctions and watchlists, and doing all of it fast enough that a real customer doesn't lose patience and leave. Every Pro customer hits these systems, so slow or wrong is very visible — and the team is early, which means whoever joins gets to decide how a lot of it works instead of inheriting it.

How We Work

• We deploy constantly, almost always behind a flag, in pieces small enough to pull back fast.

• Security and compliance show up at design time, not as a gate at the end.

• Every story is tied to a metric it's meant to move — if work isn't on the board, it doesn't get staffed.

• At this level, you're expected to shape these standards, not just work inside them.

THE OPPORTUNITY

As a Staff Engineer on Pro Verifications, you'll own the technical direction for how verification is built here — the architecture, the patterns other engineers work inside, and the calls about what we own versus what we lean on a vendor for. You'll be hands-on across the stack, drive out entire classes of recurring failure rather than patching them one at a time, and design the fail-closed and audit behavior that keeps regulators satisfied.

This is a high-impact, hands-on technical leadership role for engineers who've built where being wrong has real consequences, and who want to shape a system that stays fast, safe, and defensible as it grows.

• Set the shape of the verification services and their contracts across the KYC/KYB flow.

• Decide how we abstract KYC and KYB vendors so a bad provider day doesn't turn into an outage.

• Design fail-closed behavior and audit trails that hold up under regulatory scrutiny.

• Identify the classes of failure that keep recurring and remove them for good.

• Write and drive architecture decisions (ADRs), and hold the line on security and compliance at design time, not as a late gate.

• Mentor and raise the bar for senior engineers through design reviews, code, and direct feedback.

• Be measured on whether verification gets faster, more of it decides itself, fewer decisions are wrong, and the systems stay up — and on whether the team got stronger for you being on it.

WHAT YOU BRING

• Around eight years building and running production systems, with a track record of owning a domain's technical direction, not just delivering inside one.

• Deep, fluent expertise in Rust, with the versatility to work across TypeScript and React where verification meets the customer.

• You've set architecture other people build on, and it held up — you can point to specific classes of failure you designed out, not just incidents you fixed.

• You've made teams faster through patterns, tooling, or mentoring — engineers around you got better and shipped more because of calls you made.

• You've built where being wrong had real consequences: compliance, payments, security, or anywhere a bad call costs more than a rough user experience.

• Strong on distributed systems, service contracts, and secure design — yo