LEVERAGE COMPUTER / CAREERS / FOUNDING INFRASTRUCTURE ENGINEER
WHAT WE'RE BUILDING
Leverage is the multiplayer computer for AI-native teams. Communication, work, memory, files, tools, permissions, and execution live in one system, so humans and agents work from the same context.
Teams use Leverage for shared agent sessions, bug sweeps, product planning, customer research, PRs, docs, scheduled automations, and any workflow where private AI chats are the wrong shape.
Multiplayer. Governed. Compounding. Always-on. Any model, any tool.
→ read the full thesisWHAT YOU'LL OWN
You'll own the infrastructure that lets agents do real work for teams: VM lifecycle, sandbox boundaries, filesystem persistence, runtime orchestration, process supervision, tunnel reliability, and governed access to external tools.
You'll make long-running agent sessions reliable and inspectable.
You'll work close to the product. The infra is not hidden plumbing here; it defines what agents are allowed to do, how fast they feel, how much they cost, and how much teams trust them.
WHO YOU ARE
You are a systems engineer who likes owning production surfaces end-to-end. You can debug across TypeScript, Go, Linux, networking, queues, databases, and runtime boundaries without needing the problem pre-sliced.
You care about reliability and speed in the same breath. You think in p95s, recovery paths, cost per run, isolation boundaries, and the operational shape of a system before it is fully mature.
Experience with VMs, containers, sandboxing, schedulers, observability, distributed systems, infra for developer tools, or agent runtimes is directly relevant. Taste for simple systems is required.
COMPENSATION
We offer a top-tier salary based on your level, plus meaningful equity.
THE TEAM
We are a small team, deliberately talent-dense and moving fast.
The founding team has built and scaled AI-native products, shipped enterprise AI systems, and taken companies from zero to meaningful revenue.
We use Leverage to build Leverage. That means you will be building the compute layer from inside the workflow it is meant to unlock.
or email founders@leverage.computer