New Grad Engineering Resume Guide: Internships, Projects, and Standing Out

New Grad Engineering Resume Guide: Internships, Projects, and Standing Out Without Industry Experience

New grad resumes operate under different rules than experienced-engineer resumes. You don’t have years of shipped systems to point to; your education, internships, and projects are what carry the page. Recruiters at FAANG, AI labs, and top startups review tens of thousands of new-grad resumes each cycle, and the heuristics they use to filter are specific. This guide covers the new-grad resume structure that actually works, the bullets that distinguish strong from weak, and how to avoid the padding traps that make new-grad resumes blur together.

The Order: Education First, Sometimes

For new grads with thin work experience, education goes near the top — directly after the header. This is one of the few cases where Education leads. Once you have meaningful internship experience (especially at recognizable companies), Experience leads and Education moves below.

The decision rule: lead with whichever section is your strongest signal. If you have a 3.9 GPA from CMU and one summer internship, lead with Education. If you have a strong Google internship and a 3.4 GPA, lead with Experience. New grads often lead with Education because that’s where their substance is.

What Goes in the Education Section

For new grads, Education is more substantial than at any later career stage:

School name, degree, major, expected graduation
GPA if 3.5+ (3.7+ is a positive signal; below 3.5 omit)
Honors (cum laude, dean’s list, Phi Beta Kappa, similar)
Relevant coursework — 4–6 courses, named
Senior thesis or capstone if substantive
Teaching assistantships if held for ≥1 semester

Don’t pad with every course you took. Pick the ones most relevant to the role: Operating Systems, Distributed Systems, Algorithms, ML, Compilers, Networks. Generic courses (Intro to CS, Calculus, Discrete Math) are assumed and add no signal.

Internships: The Highest-Value Signal

Internships are what most heavily distinguish new-grad resumes. If you’ve had 1–3 substantive internships, they should occupy substantial real estate. Each internship deserves 2–4 bullets if recent and relevant.

Strong internship bullets

Apply the same action+scope+outcome structure as experienced-engineer bullets. Even at internship scale, you can quantify:

Weak: “Software engineering intern. Worked on backend services.”

Strong: “Built batch reconciliation service for the payments team (handles ~14M daily transactions); reduced reconciliation latency from 6 hours to 22 minutes via PostgreSQL query optimization and concurrent processing.”

You almost certainly did something specific during your internship. Find the metric, scope, or outcome and put it in the bullet.

Mentioning the conversion / return offer

If you received a return offer and didn’t take it, you can hint at it briefly (“declined return offer to pursue [reason]”). This signals you performed well. Don’t make a big deal of it; one line is sufficient.

Multiple internships

Lead with the most recognizable / most-recent. Smaller-name internships earlier in school can compress to 1–2 bullets each.

Projects: The Substitute When Internships Are Thin

If you don’t have strong internship experience (or don’t have any), projects fill the gap. Strong projects can substitute for internship experience at the new-grad level — in fact, well-known open-source contributions or standout side projects can outweigh a generic internship.

What counts as a strong new-grad project:

An open-source library or tool with measurable adoption (GitHub stars, downloads)
A substantive personal project demonstrating depth (a small compiler, a database, a non-trivial ML system)
A team project from a senior capstone with real users or a working production deployment
Hackathon wins at recognized hackathons (Hack the North, MHacks, TreeHacks, etc.)
Notable competitive programming results (ICPC regional+, Google Code Jam advancement)
Kaggle competitions with strong placements
Research projects with publications (even workshop papers count)

What doesn’t count:

Tutorial-style projects (Coursera capstones, “follow this tutorial” walkthroughs)
Generic CRUD apps (todo lists, weather apps, recipe finders)
“Participated in” hackathons without placing
Class assignments listed as if they were independent projects

2–3 substantial projects beat 6 weak ones every time.

Skills Section

For new grads, the skills section is real estate worth using. Recruiters and ATS searches will look for specific languages and tools. Format as grouped categories:

SKILLS
Languages: Python, C++, Java, JavaScript
Frameworks: React, Node.js, FastAPI
Data: PostgreSQL, Redis, MongoDB
Tools: Docker, Git, Linux
ML: PyTorch, scikit-learn (basic)

Honest qualifiers (“basic,” “familiar”) are fine for technologies you’ve touched but aren’t deep on. Avoid star ratings or progress bars.

What to Cut From a New-Grad Resume

Objective statement
“Career summary” written in third person
High school information (once you have a college degree)
Generic class projects (“Implemented Dijkstra’s algorithm in CS 251”)
Long lists of every hackathon attended without placements
Personal interests / hobbies that don’t connect to engineering
Clubs or organizations without leadership roles
SAT or ACT scores (almost never relevant)

Length: One Page

One page, full stop, for new grads. Two pages signals you’re padding. If your one page feels too sparse, the answer is to do more substantive work (open source, projects, internships), not to spread thin content over more space.

Sample New-Grad Structure

[Name]
[City, State] | email | phone | LinkedIn | GitHub

EDUCATION
University of Wisconsin-Madison                                   Expected May 2026
B.S. Computer Science | GPA: 3.84 | Cum Laude
Relevant Coursework: Operating Systems, Distributed Systems, Algorithms, Machine Learning, Compilers
Honors: Phi Beta Kappa; Dean's List 7/8 semesters

EXPERIENCE
Stripe — Software Engineering Intern                              Summer 2025
- Built fraud-signal evaluation harness used by ML team for offline model evaluation
- Reduced average evaluation runtime from 4.5 hours to 28 minutes via parallel batch processing
- Shipped to production; mentored two younger interns through onboarding

Acme Robotics — Software Engineering Intern                       Summer 2024
- Implemented vision-pipeline caching layer cutting startup time by 65%
- Wrote unit and integration tests; raised module coverage from 41% to 87%

PROJECTS
Spectre — Collaborative Markdown Editor (github.com/jdoe/spectre)
- Built peer-to-peer Markdown editor using WebRTC + Yjs CRDTs; 1.4k GitHub stars
- Deployed to 800+ active users via Cloudflare Pages
- Featured on Hacker News (#3, August 2024); wrote 3-part series on CRDT design

Distributed-Pi — Pi Estimator on Distributed Cluster
- Built MPI-based distributed Monte Carlo Pi estimator for class project
- Achieved 0.94 parallel efficiency on 64-node cluster
- Open-sourced; used by next year's class as starter code

SKILLS
Languages: Python, C++, JavaScript, Go (basic)
Frameworks: React, Node.js, FastAPI
Data: PostgreSQL, Redis, Kafka
Tools: Docker, Kubernetes, Git, Linux

Frequently Asked Questions

What if I don’t have any internships yet?

Lean heavily on projects, hackathons, competitive programming, research, and TAships. Substantial open-source contributions are particularly valuable here. The new-grad resume without internships needs strong substitutes; it’s not impossible to land top-tier roles without internships, but the projects need to be genuine. Avoid tutorial-style projects; focus on building one or two things at depth.

How important are research experiences vs internships?

Depends on the role. For research-flavored positions (Google Research, FAIR, AI labs, hedge fund quant research), research experience often outweighs typical internships. For standard SWE roles at FAANG, industry internships outweigh research. If you’re targeting both tracks, having one of each (one industry internship, one research project) is the strongest profile.

Should I include my GPA if it’s around 3.4–3.5?

3.5 is a reasonable cutoff to include; 3.4 or below is usually better omitted. Some employers (top quant firms, Google’s most competitive new-grad funnels) filter on 3.5+, so listing it lets you pass that filter. Below 3.5, the GPA more often hurts than helps. If your major GPA is significantly higher (3.7+ in CS courses while overall is 3.4), list “Major GPA” instead — this is honest and gives the better signal.

Do I need a personal website / portfolio for new grad applications?

Helpful for frontend roles, optional otherwise. A clean GitHub profile with a few well-presented repos is usually enough for backend, ML, and infrastructure roles. A personal website becomes useful when you have writeups, talks, or projects worth presenting beyond what fits in a README. Don’t build one from scratch as the first priority; polish your GitHub first.

How many companies should I apply to as a new grad?

For competitive funnels (FAANG, top AI labs, top hedge funds), apply to all of them — the noise in interviewer assignments and timing means even strong candidates benefit from applying broadly. Spend time on referrals where possible (former interns, alumni networks, friends in industry). 50–100 applications across the recruiting cycle is normal for new-grad funnels. Don’t apply to roles you couldn’t legitimately interview for; don’t be too narrow either.