The CS Student Internship Resume Template (with Examples)
Most CS-student resume advice online is generic and unhelpful. Here's a template that actually works for internship applications, with real bullet examples, an explicit structure, and an honest take on what to leave out.
The one-page rule
Non-negotiable for student internship resumes. Recruiters spend 6 to 30 seconds on each resume in the initial screen; a second page doesn't get read, and using it signals you couldn't edit. If you're struggling to fit content on one page, your bullets are too long, not your content too rich.
The template structure
In this order, top to bottom:
- Header. Name, email, phone, GitHub, personal site (if any), LinkedIn. No physical address; recruiters don't need it.
- Education. University, degree, expected graduation, GPA if 3.5+, relevant coursework if you have room.
- Projects. For students with limited internship experience, this section is above Experience. Two or three real shipped projects.
- Experience. Internships, research assistantships, campus jobs, retail. If you have nothing here as a freshman, that's fine.
- Skills. Languages, frameworks, tools. Honest, not aspirational.
For students with internship experience, swap the order of Projects and Experience.
How to write each section
Header
Name big, contact info on one line below. No "Objective" statement (those went out of fashion around 2010 and recruiters skim past them). No photo, no flag, no graphic icons.
Example:
Alex Johnson alex.johnson@university.edu · github.com/alexjcs · alexj.dev · linkedin.com/in/alexjcs
Education
University name, degree, graduation date, GPA if it helps. Coursework is optional but useful when you don't have related experience yet.
Example:
University of State, B.S. Computer Science Expected May 2028 · GPA 3.78/4.00 Relevant coursework: Data Structures, Operating Systems, Algorithms, Web Development
Projects (the section recruiters actually read for early-career)
Two or three projects, each with: name, one-line description, technologies used, link to repo or live demo. Each project gets 2-3 bullet points describing what you built and what you learned.
Good bullet patterns:
- Action + thing + measurable impact: "Built a Chrome extension that auto-fills job applications, used by 50+ classmates during internship recruiting season."
- Action + thing + technical detail: "Implemented a Redis-backed rate limiter in Node.js handling 200 requests per second."
- Action + thing + scope: "Designed and built a full-stack web app for tracking class assignments across 4 universities, with 200 active student users."
Bad bullet patterns to avoid:
- "Worked on a project using React and Node.js" (vague, no outcome)
- "Created a tool that helps users" (no specifics, no scope)
- "Familiar with Python" (Skills section, not Projects)
Experience
Same bullet patterns as Projects. If your only experience is a campus job or retail, include it; the "I've held a job" signal still counts. Quantify impact where you can: "Trained 5 new tutors on session-management workflow" beats "Helped train new staff."
Skills
Group by category. Languages, frameworks, databases, tools. Be honest: list what you can actually use under time pressure in an interview, not what you've seen mentioned in a tutorial.
Example:
Languages: Python, JavaScript/TypeScript, Java, SQL Frameworks: React, Node.js, Express, Flask Tools: Git, Docker, AWS (S3, Lambda), PostgreSQL
What to leave out
- High school (after freshman year, unless it was nationally ranked)
- GPA below 3.5 (skip the number; "Computer Science" alone is fine)
- "Objective" statements (recruiters skim past them)
- Soft skills as bullets ("team player," "detail-oriented"); show in your other bullets instead
- Skills you list because they look impressive but you couldn't whiteboard in (you'll get caught)
- Headshots and graphic design. ATS parsers eat them, and recruiters don't need them
How to tailor for specific roles without rewriting
Don't keep one resume per role. Keep two or three versions (e.g., frontend-leaning, backend-leaning, generalist), each with a different ordering of projects and a slightly different Skills section. Pick the closest version for each application. Tailoring beyond that has diminishing returns at the internship volume game.
After your resume is done: filling applications faster
A polished one-page resume is the one-time investment. The recurring cost is filling out 200 applications using that resume, which is where most students burn out. Lentra reads your resume, extracts your profile (name, contact, education, work history, skills), and fills application forms in about 20 seconds.
The 5-to-10-minute Workday form becomes 20 seconds. Free, no quotas, no paid tier. Built for exactly this volume.
Install Lentra Free, takes one minute.