Software Engineer Intern (Backend / AI)

Supero; San Francisco (CA); Hybrid; USD 22,000 - 45,000; Full time

Benefits offered by this job

Paid internship

Potential full-time offer

Job summary

Supero in San Francisco is offering a three-month, full-time internship where you will own a real production feature rather than a sandbox. You will pick a track: Platform (Python services, connectors, access control), AI (generation pipeline, prompts, evals), or Applications (build real apps and break them on purpose).

Ship to production in your first three weeks. You will write a design note before code and the RCA after the incident; you will be part of reviews and learn MCP while building

Qualifications

• Real code in Python, JavaScript/TypeScript or Go.
• You have built something and shown it to someone.
• Curiosity about AI systems and practical experience with AI tooling.

Responsibilities

• What you’ll do: pick a track (Platform, AI, or Applications) and ship a production feature.
• Deliver a small, fully real project within three weeks.
• Write a design note before coding, and a root-cause analysis after incidents.
• Participate in code reviews and defend your changes.

Skills

Python

JavaScript/TypeScript

Go

Job description

Most internships hand you a sandbox. We do not have one to hand you — the parts of the platform that are missing are genuinely missing, and one of them would be yours.

Why this role exists

Most internships hand you a sandbox. We do not have one to hand you — the platform is the product, and the parts of it that are missing are genuinely missing.

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 will not be shadowing. You will own something small, real, and in production.

Your work is the application

We read what you have built before anything else. You do not need a recognisable logo on your CV, and you do not need to have interned anywhere before — send us something you made and tell us what fought back.

Three months, full-time, paid, and convertible to a full-time offer. We will give you the stipend figure on the first call — before you spend any time on an application, not after.

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 will be told 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 does not scare you.
• You have 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 have used LLMs to build, and you have at least one strong opinion about where they fall over. You do not need to know what MCP is — you will learn it here.
• You ask “how do I know that’s true?” about your own work.

Something you built is the first round

Route 2 is fully equal here, and it is the fastest one. Send something you have already built — any stack, any age, any domain — plus one page on the data model and the decision you would now reverse. It is scored exactly the same way as a fresh build. We know an unpaid evening is not equally available to everyone, and we would rather see what you have already made than watch you rebuild it for us.

If you would rather build on Supero: three entities, two roles, one live URL and a paragraph on what fought back. Aim for 90 minutes.