boxxkiteBuild the sandbox agents run in.
boxxkite is a self-hostable, Kubernetes-native sandbox for AI agent code execution — one isolated pod per session, network access denied by default. We run arbitrary, agent-generated code for a living, which makes this a team with an unusually sharp definition of “done”.
Everything you'd be joining is already readable: the source, the security posture, and the docs. Read them before you apply — it's the fastest way to work out whether you want this.
Open roles
3 positions
Engineering
Founding Full-Stack Engineer
Own a whole product surface top to bottom, with no specialist at any layer to hand it off to.
Remote (India)Full-time · Founding team
Founding AI/Agent Infrastructure Engineer
Be our first real customer: build agents on boxxkite all day, then tell us exactly where it falls short.
Remote (India)Full-time · Founding team
How we hire
Four steps, about two weeks end to end, and you'll know where you stand after each one.
- 01
A 30-minute call
What you've built, what broke, what you'd do differently. No trivia, no whiteboard.
- 02
A take-home, 4–5 hours
Unpaid, and hard-capped at 4–5 hours precisely because it is. You'll do it against the real product — hosted signup or a self-hosted clone — not a toy repo. Five calendar days, and ask for more if you need it.
- 03
A walkthrough, 60 minutes
You drive. Two-thirds on what you built, one third on what you deliberately left out — the omissions are usually the interesting part.
- 04
A conversation with the founder
Comp, equity, what the first 90 days actually look like, and your questions.
What you should know before applying
It's small, and you'd feel it
boxxkite is an indie-run project with a hosted beta and an Apache-2.0 core. There's no platform team, no on-call rotation to inherit, and no process to hide behind. What that buys you is that your name is on the decision.
The work is public
Most of what you'd write ships to a public repo under a permissive license, where anyone can read it, fork it, or file an issue about it. Some people find that energising and some find it exposing — worth knowing which one you are.
You have to use the thing
Every one of these roles involves running boxxkite yourself and having opinions about it. That starts at the take-home, which you'll do against the real product, and it doesn't stop after you join.
Remote, and actually remote
India-remote, working directly with the founder. Expect written decisions over meetings, and expect to be trusted with a surface rather than assigned tickets on it.
Nothing here fits?
Write to us anyway. If you've built something in this space — agent tooling, container isolation, developer experience for people who run untrusted code — tell us what you'd want to own and why it should exist here.