Head of Engineering, Foundations

About the Role:

$200B+ in assets and $90B in money movement run on infrastructure that about 50 engineers and a growing number of agents build on top of. We're hiring a Head of Engineering, Foundations to lead the team that owns it. This role reports directly to the CEO and has company-level scope.

Part of what this team owns is new. Agents are becoming first-class users of our own systems, and nobody has a settled answer for what a platform owes a non-human user: sandboxing, audit trails, rollback, all against systems that move real money. You'd be deciding how that works here.

As a Head of Engineering here, you'd be expected to personally ship, not just direct.

Responsibilities:

• Hire, coach, and grow a small team of high-performing engineers, and develop the staff and principal engineers who carry technical standards into other teams.
• Build the platform the whole engineering org runs on: developer platforms, deployment pipelines, observability, and developer tooling.
• Automate infrastructure as code on Kubernetes and AWS, using Pulumi, cdk8s, and ArgoCD.
• Build the harnesses agents execute inside, including sandboxing, audit trails, and rollback against systems that move real money.
• Set the engineering standards for reliability, operability, and architectural coherence, and sequence the quality work that keeps teams shipping quickly over time.

What we’re looking for:

• 12+ years in engineering, including 5+ leading teams.
• A builder who leads. You write clean, well-tested code and have designed and shipped systems end to end, and you want to keep doing that while growing a team.
• Leverage through senior engineers. You've developed staff and principal ICs who make other teams better.
• Systems judgment. You've operated consequential infrastructure before. Kubernetes, AWS, and infrastructure-as-code experience helps, but judgment matters more than familiarity with our exact stack.
• Developer experience as a product. You design infrastructure for the engineers using it rather than just operating it.
• You author the standard. You have a clear point of view on what good infrastructure looks like and set it rather than inheriting it.