Internship hiring is different from full-time hiring in an important way: the interviewer is almost never asking "can this person do this job?" because the answer is often "not yet". They are asking "would I want to work with this person for three months while they learn?"
That changes what the resume needs to signal.
What internship teams actually look for
Four things, in order:
- Evidence of initiative. Have you built or attempted something on your own? Side projects, hackathons, open-source contributions — anything that shows you do things without being told.
- Evidence of learning ability. Grades, coursework, independent study. Not because they care about grades, but because they care that you can learn a new codebase, tool, or process quickly.
- Evidence of collaboration. Team projects, group coursework, part-time jobs. Interns work in teams, and the team wants someone who will fit.
- Evidence of interest. The resume shows you care about the field, not just about having a job. Specific technologies, specific projects, specific reasons.
Structure for an internship resume
The order that works best:
- Contact header
- Summary (2 sentences)
- Education (degree, institution, relevant modules)
- Projects (coursework, personal, hackathon)
- Skills
- Any work experience
- Awards and activities
Note: projects come before work experience. This is deliberate. For interns, projects usually demonstrate more about you than a part-time retail job.
Make projects do real work
Most internship applicants list projects as one line: "Built a web app". This wastes space. A project entry should include:
- What it does — one sentence, concrete.
- What you used — the stack, briefly.
- What happened — a result. Number of users, grade, deployment, stars, presentation at a hackathon.
- What you learned — optional, but useful when the outcome was modest.
Example: "NoteGraph — local-first note-taking app with graph-based linking, built during the Recurse Center mini-batch. Uses TypeScript, React, and SQLite WASM. Deployed to 200+ early users."
That line tells the team more about you than three generic skills claims.
Coursework is evidence
If a specific module gave you experience with the technology the internship uses, list it. "Relevant modules: Distributed Systems, Databases, Machine Learning" is a valid education line, not filler.
If you completed a significant coursework project that is relevant, describe it — but frame it as a project, not as a module. "Replicated key-value store (Distributed Systems module)" is a project.
Skills — be specific
List concrete technologies, not categories. "Python" is specific. "Programming" is not. "AWS EC2 and S3" is specific. "Cloud computing" is not.
If you have used a technology in a project, say so explicitly: "Python (used for data processing in the NoteGraph project)". This removes ambiguity about whether you have actually built anything with it.
Two-sentence summary
A good internship summary:
- Sentence 1: Who you are and what you study.
- Sentence 2: What you have built and what you want to build.
Example: "Second-year Computer Science student at the University of Bristol. Built and shipped three side projects in Go and TypeScript, including a local-first note-taking app with 200+ active users. Looking for a software engineering internship where I can work on systems that other engineers depend on."
Do not pad your summary with "passionate about technology" or "eager to learn". Every internship applicant is passionate and eager. Show evidence, not adjectives.
Start with an internship-ready template
Our student templates are tuned for internship applications — projects lead, skills are prominent.