How to Write an Internship Resume (With Examples)

Internship applications are uniquely competitive: hundreds of qualified candidates, similar educational backgrounds, and minimal work history differentiating anyone. The students who get interviews aren't necessarily the most qualified — they're the ones who figured out how to present what they have most effectively.

A good internship resume has a different structure than a professional resume, uses different sections as its primary weight-bearers, and requires specific attention to the types of experience that distinguish one student from another.

The Internship Resume Structure

For most students applying to their first or second internship:

1. Header (name, contact, LinkedIn, GitHub if relevant)
2. Education (moved to the top — this is your primary credential right now)
3. Relevant experience (internships, part-time work, research)
4. Projects (academic or personal — treated like work experience)
5. Skills (technical skills and tools)
6. Activities / Leadership (clubs, teams, student organizations)

The major difference from a professional resume: Education and Projects carry the weight that Work Experience carries for professionals.

Education Section

For internships, your education section should be thorough:

Bachelor of Science in Computer Science — Expected May 2027
University of Michigan, Ann Arbor | GPA: 3.6/4.0

Relevant Coursework: Data Structures & Algorithms, Operating Systems,
Database Management, Machine Learning, Software Engineering (Agile)

Dean's List: Fall 2024, Spring 2025

If you have a strong GPA, include it. If it's below 3.0, omit it. Anything between 3.0 and 3.5 is judgment call — generally include it if the rest of your resume is thin on credentials.

Relevant coursework helps when your target role requires specific knowledge — it proves to a recruiter that you've studied the relevant material even without applied experience.

The Projects Section Is Your Work Experience

If you've done any meaningful technical, analytical, or creative projects — coursework, personal, hackathon, open source — list them as experience:

Class Project: Campus Parking Optimization | Fall 2025
• Modeled campus parking utilization using real sensor data from
  U of M transportation services; applied linear regression and
  K-means clustering to identify underutilized zones
• Presented findings to a panel of campus administrators; 2 recommendations
  incorporated into 2026 parking policy update
• Python, pandas, scikit-learn, Matplotlib

Internship Experience (If You Have It)

If you've done a previous internship, this is your strongest section. Write the bullets exactly like professional work experience:

Software Engineering Intern | Notion | Summer 2025
• Built internal admin dashboard for support team using React + Supabase;
  reduced ticket routing time by 35%
• Contributed 8 PRs to the core codebase; 6 merged into production
• Shipped real-time notification system used by 500+ internal users

Even if the work felt small, find the numbers: how many users, how many tickets, what percentage improvement, how many PRs.

The Education Section vs. Skills Section Trade-Off

The more technical your target role, the more important your skills section becomes. For software engineering or data internships, your skills section is the first thing a technical recruiter scans:

Languages: Python, Java, JavaScript (TypeScript), SQL
Frameworks: React, Node.js, FastAPI
Tools: Git, Docker, VS Code, Figma, Jupyter
Cloud: AWS (S3, Lambda basics), Firebase

Certifications and courses add credibility: "AWS Cloud Practitioner (in progress)," "Completed Stanford Machine Learning Specialization on Coursera."

What Differentiates Strong Internship Applicants

In a pool of students with similar GPAs and similar coursework, what creates separation:

1. Actual experience — Previous internships, part-time technical work, research assistant roles

2. Project quality — Projects where you built something real, used production tools, or produced measurable outcomes

3. Open source contributions — Even a few accepted PRs to a recognizable repository signal self-initiative

4. Specificity in bullets — Students who write "Contributed to web development team" versus "Built user authentication module using Node.js + JWT; handled 500 concurrent sessions in testing" are in different categories

5. Skills alignment — Are the tools you've listed the ones the company uses? Research their tech stack on LinkedIn or their engineering blog.

One page, clean format, achievement-based bullets wherever possible. The principles are the same as professional resumes — just applied to a different set of experiences.