How to Write an Internship Resume When You Have No Experience

There's a moment, somewhere around your second year, when you notice the trap. Every internship you'd actually want lists prior experience under requirements. And the only way to get prior experience is an internship. You read that sentence twice, close the tab, and go and do something else for a while, feeling slightly worse about yourself than you did an hour ago.

Almost everyone hits this wall. Almost everyone gets past it. And the way through isn't a hack or a better template — it's noticing that you have been answering the wrong question.

What are they actually asking?

You think the question is "where have you worked?" It isn't. Nobody hiring an intern believes you've worked anywhere. That's the entire premise of the word intern.

The question is: "if we give this person a desk and three months, will it have been worth it?" And that resolves into three sub-questions, all of which you can answer today, with no job history at all:

1. 1Can you be taught? Is there evidence you've learned something hard, on purpose, and stuck with it past the point where it stopped being fun?
2. 2Will you show up? Have you held a commitment — any commitment — over time, including on the days you didn't feel like it?
3. 3*Do you actually want this?* Or did you apply to 200 postings with the same document? They can tell. They can always tell.

Every line on your resume should be evidence for one of those three. That's the whole strategy. Nothing else earns its space.

What counts as evidence?

Far more than you're currently giving yourself credit for. Go through this list honestly and write down everything that applies — you'll find four or five things you'd written off:

Why does specificity matter so much?

Because generic lines are indistinguishable from lies, and specific ones are indistinguishable from truth. Compare:

• Relevant coursework: Databases, Algorithms, Software Engineering.
• Strong problem-solving skills and a passion for technology.
• Volunteered at a local charity.

• Built a query planner for the Databases module. Mine was the only one in
  the cohort that handled nested joins, because I'd misread the spec and
  built the harder version by accident, then couldn't bring myself to
  simplify it.
• Taught myself enough Rust over one summer to rewrite my dissertation's
  hot loop; it went from 40 seconds to 1.2.
• Ran the weekly homework club at a local youth centre for 14 months.
  Turned up every Tuesday, including the ones where nobody else did.

The second version is not from a better candidate. It's the same candidate, written down honestly. And every one of those three lines answers one of the three real questions — teachable, reliable, genuinely interested — without ever claiming to have had a job.

"I'd misread the spec and built the harder version by accident." No model writes that. No liar writes that. That's why it works.

What does the finished thing look like?

One last thing: apply anyway.

The requirements list on an internship posting is a wish list, assembled by a recruiter who is fully aware they're hiring people who have not done the job. It is not a gate, and treating it as one is the single most common reason good candidates never apply at all.

If you match most of it and you can write three honest, specific lines that say I can be taught, I show up, and I want this one — send it. The worst realistic outcome is silence, and silence costs you nothing but the twenty minutes you already spent.