Engineering Intern
Two seats per cohort, two cohorts a year — that is the whole program. You get one scoped project that ships to production with your name on the changelog, a mentor who reviews your work daily, and an explicit answer at the midpoint about whether you are tracking toward an offer. This is the entry door, not a coffee run.
What you will do
Own one scoped project end to end — spec, build, ship, and the written postmortem of your own work.
Ship to production within the twelve weeks; the changelog entry is the deliverable, not the demo.
Sit in the same threads, reviews, and gate discussions as everyone else — no intern-tier visibility.
Write: a weekly update that holds up without your tone of voice, and a final write-up of what you built and why.
What we need
You are a student or within a year of graduating, and you can commit twelve full-time weeks.
You have built something real — a project, a tool, a contribution strangers used — and can explain why it is built the way it is.
Working fluency in at least one of TypeScript, Go, Rust, or Python.
You write clearly enough to work async; we will read something you wrote before your CV.
Nice to have
Open-source contributions, however small, that show how you take review.
Interest in runtimes, permissions systems, or evaluation — the things this company actually builds.
You have shipped under a deadline you set yourself.
Apply — we reply to everyone