Situational · written by career coaches
Internship resume example
A finished internship resume you can read end to end — the summary, the bullets, and the keywords these postings actually contain. Adapt the structure; never copy the numbers.
An internship resume is built from coursework, projects, societies and part-time work, ordered by relevance rather than chronology. Name the internship you want, put education first, and write every entry with a result attached — an intern who writes like a professional stands out immediately.
Summary section
Second-year computer science student seeking a summer software engineering internship. Built and shipped a course-scheduling tool now used by roughly 300 students at my university, and placed third of 40 teams at a national hackathon.
Achievement bullets that work
Written to show the result first and the method second. Adapt the structure — never copy the numbers.
- Built and shipped a course-scheduling web app now used by roughly 300 students, handling authentication, database design and deployment independently.
- Placed third of 40 teams at a national hackathon, building a working prototype and presenting it to judges within 36 hours.
- Completed a group capstone for a local charity, delivering a donor-tracking tool the charity still uses a year later.
- Worked 15 hours a week in retail throughout term time while maintaining a first-class average — evidence of workload management under real constraint.
- Contributed three merged pull requests to an open-source library, including one fixing a race condition in its caching layer.
Internship resume keywords for ATS
Terms that postings for this role commonly contain. Use the ones that are true of you, in the posting’s own wording.
- internship
- Python
- Java
- JavaScript
- Git
- teamwork
- communication
- problem solving
- data analysis
- Microsoft Office
- time management
- research
- project work
Name the internship you want
Internship applications are screened fast and in volume. A resume that does not say what it is for makes the reader work, and at intern volume they will not. One line — "second-year computer science student seeking a summer software engineering internship" — costs nothing and frames everything below it.
Order by relevance, not by date. If a personal project is your strongest evidence for the role, it goes above the retail job, whatever the calendar says.
Write like a professional and you will read like one
The single fastest way to stand out in an intern pile is structure. Most intern resumes are lists of nouns: "Python, Java, teamwork, communication". A bullet that says what you built, for whom, and what happened puts you in a much smaller group immediately.
Part-time work counts, and undervaluing it is a mistake. Fifteen hours a week of retail alongside a first-class average is direct evidence of exactly the reliability an employer is trying to assess in someone with no professional record.
Computer science internship resumes: projects are the experience
For a software or data internship, a projects section does the job a work history does for everyone else, so it sits directly under education. Give each project one line on what it does, one on the stack, and one on proof it is real: users, a live link, a merged pull request, a benchmark. A GitHub link with three pinned, documented repositories is read; a link to forty forks of tutorials is not.
List languages and tools in a single skills line and let the projects prove them. "Python, TypeScript, React, PostgreSQL, Git, Docker" is scannable and matches the posting filter; a skills section rated in stars or percentages is neither, because nobody can say what "Java 80%" means. Relevant modules — algorithms, operating systems, databases, machine learning — earn one line under education, not a section of their own.
Engineering internship resumes: show the design work
Mechanical, electrical and civil internship screens look for evidence that you can take a problem through design, analysis and test. Student competition teams, lab reports and capstone builds are that evidence when written as engineering: the constraint, the tool, the result. "Designed the rear suspension upright in SolidWorks, cutting mass 18% while passing FEA at a 1.5 safety factor" beats "member of Formula Student team".
Name the software and standards postings filter on — SolidWorks, AutoCAD, MATLAB, ANSYS, LTspice, PLC programming — and only the ones you have used on real work. Hands-on workshop skills such as machining, soldering or wiring belong in the same skills line, because many engineering internships involve the build and test side more than the office.
Which template suits a internship
A clean single column that looks complete at one page, so a short history reads as focused rather than sparse.

Fair questions.
One page. Always. A second page at this stage makes thin content more visible rather than less.
In first year, briefly, if they are genuinely notable. By second year, university work should have replaced them.
Build one small thing and ship it — a tool that solves a real annoyance for people you know beats a tutorial clone. Two weekends of work produces the most useful line on the whole page.
Include it when it is strong or when the posting asks for it — many engineering and finance internships screen on a minimum. Leave it off when it is weak and the posting does not ask; an interviewer will not assume the worst from its absence.
Now write yours. Scored as you go.
Start from your real history — the coach asks for the specifics rather than inventing them, and scores every edit against the posting you're targeting.
Other resume examples
Next steps
- Internship cover letter exampleThe cover letter written for this same candidate — the other half of the application.
- ATS score checkerIf you already have a internship resume, check whether an ATS can read it before you apply.
- Resume templatesAll 14 layouts export selectable text, with the roles each one suits.