Careers
Building the operator platform.
Founding roles across engineering, design, and operations. If you want to build the platform your operators live in — its tools, its MCP, its Cradle — reach out.
Two founding-engineer roles open now.
- Founding Backend Engineer
Build the platform, its MCP, the Operational Graph, and the engine that turns operational signal into safe, reviewed action. Python + TypeScript, graph modeling, real data pipelines. Remote (EU hours). Read the full role at /careers/founding-backend-engineer.
- Founding Frontend Engineer
Help build the surfaces that make Operations Intelligence legible. Next.js, typography-forward design, real-time state. Remote (EU hours). Read the full role at /careers/founding-frontend-engineer.
Where founding hires slot in.
- Founding engineer · substrate
Own the Data + Identity + Departments band. Postgres + typed schema + row-level client isolation from day one.
- Founding engineer · intelligence
Own the Memory + Reasoning + Detectors band. Knowledge graph + multi-provider router + preference-pair capture.
- Founding engineer · action
Own the Pearl + Shell + Approval + Orchestrator band. Per-domain entity + human approval graph + action queue.
- Founding designer · brand + product
Own the marketing site + design system + Pearl UI. Editorial register · brand palette · concept-family imagery.
- Founding operator · GTM + enterprise
Land the enterprise cohort. Structure the pilot. Turn clients into references.
Signals we hire on.
You’ve run something at real scale before — a team, a product, an operation
You reach for a Postgres query before you reach for a library
You think in institutions, not features
You care about the audit trail as much as the automation
You can write. Every founding hire ships product AND writes about it