Software Engineer Intern (Backend / AI)

Supero is an agent-native application development platform. You describe a system; the platform generates the schema, APIs, access control and a deployed multi-tenant app. We’re small, the product is the platform itself, and the parts of it that are missing are genuinely missing.

Most internships hand you a sandbox. We don’t have one to hand you. In the last six months, intern-scoped work here has included a connector cost guard, a field-level access test suite, and the tooling that catches when a generated app silently ships without seed data. You won’t be shadowing. You’ll own something small, real, and in production.

What you’ll do

• Pick a track: Platform (Python services, connectors, access control), AI (generation pipeline, prompts, evals, MCP tools), or Applications (build real apps on Supero and break them on purpose).
• Ship to production in your first three weeks — something small, entirely yours.
• Write the design note before the code, and the RCA after the incident. You’ll be taught how; nobody expects you to arrive knowing.
• Sit in the reviews where we argue about whether a claim is actually true.

What we look for

• Real code in Python, JavaScript/TypeScript or Go — enough that a 400-line pull request doesn’t scare you.
• You’ve built something and put it in front of someone. A side project, a college system people actually used, a tool for your lab. What it is matters less than that it left your laptop.
• Curiosity about AI systems. You’ve used LLMs to build and have at least one strong opinion about where they fall over. You do not need to know what MCP is — you’ll learn it here.
• You ask “how do I know that’s true?” about your own work.

You don’t need a recognisable logo on your CV, and you don’t need to have interned before.

How you apply: something you built is the first round

For interns and new graduates this replaces our screening call and our take-home entirely. Two routes, scored identically:

• Build a small system on Supero — ideally driven over our MCP server from Claude Code, Cursor or Copilot. Three to five entities, two roles, one thing that can go wrong. Send a screenshot of the landing page, the live URL, and a few paragraphs: what you were modelling, one decision you’d reverse, and two things about Supero itself — what you liked most and what you’d improve. Aim for 90 minutes; four hours is a hard cap. Free account, no credit card.
• Send something you already built — any stack, any age, any domain — plus one page on the data model and the decision you’d now reverse. Nothing about this route is a lesser option. We know an unpaid evening isn’t equally available to everyone.

What we score: not visual polish. Whether the data model survives a second tenant, whether you handled the state with no happy path, and whether you noticed something wrong with our platform and said so. A three-entity app with a defensible model and a sharp bug report beats a twenty-screen app that only works if you click in the right order.

Don’t submit anything that isn’t yours to submit — no employer’s proprietary code, no real personal data. Invent your test data. You keep full IP in what you build; we get a limited licence to review it, and we delete our copy within 90 days of a final decision.

Pay: From $30.00 per hour

Expected hours: 40.0 per week

Work Location: Remote