Teams and organisation
Six teams. One registry. One rulebook.
- Teams
- 6
- Target headcount · v1
- ~45
- Executive team size
- 5
- Ratio · IC : Manager
- ~8 : 1
Team map
How the company is divided
- 01
Engineering
Four product modules on a shared registry. TypeScript at the edge, Rust where latency matters, Go for the Trillian registry, and Python for AI and risk models. Security, platform, and SDK subteams. - 02
Clearing operations
Runs the live clearing function — margin, default, member services, and the rulebook. Cross-functional with regulatory and engineering. Owns the settlement state machine and the default waterfall. - 03
Regulatory affairs
Parallel programs for FinCEN, SEC, CFTC, SEF/DCM, FCC, and ITU. Runs external counsel relationships. Writes filings, responds to staff letters, and tracks rule-making proceedings that touch the platform. - 04
Legal
Corporate, commercial, IP, and disputes. Drafts the rulebook, member agreements, connectivity agreements with ground stations, and the licensing around did:orbit and the protocol spec. - 05
Business development
Splits into Operators (LEO/MEO/GEO clearing members) and Ground Stations (attestation partners). Writes deal memos, runs the design-partner cohort, and owns the member-pipeline CRM. - 06
Finance and operations
Corporate finance, FP&A, treasury, and general operations. Owns the segregated settlement-account architecture on the MSB side, and the Series A preparatory work.
Who reports to whom
Executive team · v1
- Founder · CEO
- Mitchell McLennan
Runs engineering and product through Series A. Chair of the rulebook committee.
- CTO
- Hiring
Owns the four-module platform technical strategy. Reports to CEO.
- Head of Clearing
- Hiring
Runs live clearing operations. Reports to CEO. Peer of the GC.
- General Counsel
- Hiring
Corporate, commercial, rulebook, IP. Reports to CEO.
- Head of Regulatory
- Hiring
Four-track filing programs. Reports to GC during v1, CEO thereafter.
- Head of BD
- Hiring
Operators + ground stations. Reports to CEO.
- Finance
- Fractional CFO · 2026
Fractional through Series A close, then full-time CFO search.
How work flows
Coordination model
- 01
Sprint cadence
Two-week sprints across engineering, with a Monday plan and a Friday demo. Regulatory and legal run on a four-week cadence. BD and member services run on a weekly cadence. - 02
Writing-first
Every sprint begins with a Dispatch document. Every meeting that needs a decision is preceded by a one-page memo. Async over synchronous whenever possible. - 03
ADRs for every irreversible call
Architecture Decision Records live in /docs/decisions, numbered, dated, and signed off. If a decision is hard to reverse, it gets an ADR before it ships. - 04
All-hands
Monthly, 60 minutes, one hour across every time zone. Metrics review, one demo from each team, and open Q&A. Recorded and written up for async attendees.
Where we are
Hubs and time zones
- Hubs
- 3
- Coordinated window
- 09:00 – 17:00 UTC
- In-person cadence
- Quarterly
- Time-zone policy
- No forced relocation
New York, London, Singapore. Optional co-working stipend in each.
Overlap with NYC, LON, and Singapore inside an eight-hour window.
Whole-team offsite every quarter, rotating between hubs.
We hire where the person is; we do not require moves to a hub.
Team-specific questions
Talk to the person who runs the team.
If you are weighing a role and want a conversation with the actual manager before applying — we arrange that directly. Email the careers desk and name the team you want to talk to.