Engineering Intern

What you'll own in your first weeks

• Ship a scoped feature or fix to production in your first couple of weeks, with tests.
• Own one small area end to end, such as a part of this marketplace, an internal tool, or an evaluation script for an LLM feature, and keep it working.
• Read the code you touch until you understand it, and leave it clearer than you found it.

What you must already be able to do

All of these. This is the bar, not a wish list.

• You have shipped real projects that other people use: an app, a library, a tool, a bot. Coursework alone does not count.
• You write clean code in TypeScript or Python, and can pick up the other quickly.
• You have strong fundamentals: data structures, how the web works, SQL, Git, and debugging code you didn't write.
• You get yourself unstuck by reading the documentation and the source before asking.

You'll stand out if

• You have contributed to open source and a maintainer merged your change.
• You have built something on an LLM API and can explain exactly where it failed.
• You have shipped to a deadline for real users, such as a hackathon project people kept using afterwards.

Don't apply if

• You want the certificate more than the work.
• You can't show us anything you've built yet. Build one thing people use, then apply.
• You need step-by-step instructions for every task.

How we hire

1. 01Apply with proof of work. Links to things you built or grew tell us more than a CV, so there is no CV upload.
2. 02We read every application. If your work clears the bar for the role, we email you.
3. 03A practical exercise. A practical exercise relevant to the role, close to the work you would actually do.
4. 04A conversation with the founder. About what you've built, how you think, and the work ahead.