← All open roles

H01 Β· Technical leadership

CTO and Chief Systems Architect

Help a person own a computer they can trust with their working life. You will make the hardware, operating system, private data, agent and remote execution behave as one dependable product.

First teamOffice-first9 cities

About the role

You make the hardware, the operating system, the private data, the agent and remote execution behave as one dependable product rather than five that were introduced to each other late. You set architecture and engineering priorities with the founder, establish one authoritative agent identity and policy domain per person, and own the tradeoffs nobody else can make. This is the technical spine of a claim we make publicly: that a person can own a computer they trust with their working life.

The work

Set the architecture and engineering priorities with the founder. Establish one authoritative agent identity and policy domain per person, review tradeoffs in public within the team, and build alongside the engineers. Define which components we create, adopt or develop with partners.

What good looks like

In your first 90 days, deliver a working reference system, a threat model and a funded delivery plan with named owners and measurable release criteria.

Evidence we look for

Bring deep systems judgment and evidence that you have shipped complex products across organizational boundaries. Explain a major failure, the evidence that changed your view and the people you helped develop.

What we need to see

  • Deep systems judgement across hardware and software, not depth in one and vocabulary in the other
  • You have shipped a complex product across organisational boundaries, where the hard part was the seams
  • You can walk through a major failure you owned: the evidence that changed your view and what you did next
  • A record of developing engineers who went on to do better work than they could before

Nice to have

  • Operating-system, silicon, or secure-enclave work specifically
  • You have set an architecture that survived several years of the product changing under it
  • Experience in a regulated or safety-critical domain

The exercise

Walk through a system you built, then design recovery after the user's primary computer is lost.

Where and how we work

In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.