She got the offer because of one line in her cover note: "I used your product to manage my student org's budget last semester. The CSV export is broken on Firefox — here's a screenshot."

That's the entire game. But let me back up and start with what the data actually looks like.

The landscape

We're tracking 2,166 open internship positions across the startups in our database. That's about 2% of all listings — a small slice, but a meaningful number of real opportunities.

The distribution is uneven in ways that matter:

Engineering internships dominate, accounting for roughly 40% of the total. This tracks with what you'd expect — startups need code written, and interns who can ship code are immediately useful.

But the second-largest category is operations and business, at about 25%. These are the roles that most intern-seekers overlook entirely. Marketing and data internships each account for roughly 10-12%. Design and product round out the rest.

The geographic split is also worth noting. About 55% of startup internships are in the US, with California and New York leading. But a surprising 20% are remote or remote-eligible, which means you don't necessarily need to relocate for a summer position.

What startups actually want from interns (it's not what universities tell you)

University career centers prepare students for internships at large companies. They teach you to optimize your resume for ATS systems, practice behavioral interview questions, and write cover letters that begin with "I am writing to express my interest in..."

This advice is actively counterproductive for startup internships. Here's why:

Startups don't use ATS for intern hiring. A company with 30 employees doesn't have a recruiting team or an applicant tracking system. Your resume goes to a founder's inbox, or a Notion board, or a shared Google Sheet. The person reading it is probably the same person who will manage you. They're not scanning for keywords — they're scanning for signal.

The signal they're looking for is evidence of initiative. Not leadership (a word that means nothing on a student resume). Not teamwork (everyone claims this). Initiative — meaning you did something that nobody asked you to do, and it worked.

This could be a side project. A contribution to an open-source tool. A blog post about something you built. A bug report for a product you actually use. The bar is not high. It just has to be real.

They care about fit more than credentials. At a large company, an intern is one of 200. At a startup, an intern is one of two or three. You'll be sitting in the same room (or Slack channel) as the founders. Cultural fit isn't a nice-to-have — it's a hard requirement. This means your application needs to show that you understand what the company does and why you specifically want to be there.

The application mistakes that get you rejected in seconds

I've talked to enough startup founders about intern hiring to identify the patterns. These are the instant-rejection triggers:

The mass-apply template. "Dear Hiring Manager, I am excited to apply for the Software Engineering Intern position at [Company Name]." If the founder can tell you sent the same email to 50 companies, you're done. It doesn't matter how qualified you are.

The resume that lists coursework but no projects. "Relevant coursework: Data Structures, Algorithms, Operating Systems." Every CS student has taken these classes. This tells the founder nothing about what you can actually do. Replace coursework with a project section — even if the projects are small.

No evidence of using the product. This is the single biggest differentiator. If you apply to a startup and you haven't tried their product, you're at a massive disadvantage compared to someone who has. Founders notice. They always notice.

Applying only to the "big name" startups. Everyone applies to Stripe, Figma, and Anthropic. The acceptance rate at these companies for internships is lower than most Ivy League schools. Meanwhile, a Series A company with 40 employees that just raised $15M is desperate for a summer intern and getting five applications. The opportunity cost of ignoring smaller startups is enormous.

How to actually stand out

The intern who got hired — the one with the Firefox bug report — did three things right:

First, she used the product before applying. This took maybe 20 minutes. It gave her something specific to say, which immediately separated her from the 139 other applications that were generic.

Second, she found a real problem and documented it. She didn't just say "I love your product." She said "here's something broken, and here's proof." This demonstrated exactly the kind of initiative that startups value.

Third, she kept it short. Her entire application was four sentences. No cover letter template. No "I am passionate about..." preamble. Just: who she was, what she'd noticed, what she could do, and when she was available.

The math is in your favor

Here's the thing about startup internships that most candidates don't realize: the competition is dramatically lower than at large companies. A FAANG internship might get 10,000 applications. A startup internship at a Series B company might get 30.

With 2,166 positions open and most candidates focusing exclusively on brand-name companies, the actual odds of landing a startup internship are surprisingly good — if you're willing to apply to companies you haven't heard of, and if you put in the 20 minutes of effort to make each application specific.

The intern who used the product, found the bug, and wrote four sentences? She's now a full-time engineer at that company. She skipped the entire entry-level job search because she'd already proven she could do the work.

That's the real value of a startup internship. It's not the line on your resume. It's the shortcut past the line.