New-Grad Resume: How to Write One When You Have No Experience

Every senior engineer was once a new grad staring at a blank resume template, convinced they had nothing to offer. They were wrong, and so are you. The mistake most new grads make isn't having too little experience — it's not knowing how to frame the experience they already have. This guide will show you exactly what to put on your resume, how to structure it, and what hiring managers actually care about when they're looking at entry-level candidates. No fluff, no "build your personal brand" nonsense — just a practical playbook for getting your first real job.

Your GPA and Coursework Are Real Credentials — Use Them Correctly

Most new grads either over-rely on their GPA or ignore it entirely. Neither is right. Here's the rule: include your GPA if it's 3.5 or above. If it's below 3.3, leave it off entirely. The 3.3–3.5 range is a judgment call — if you're applying to a company that explicitly screens on GPA (Google, Jane Street, some finance firms), include it; otherwise, omit it and save the space.

Coursework is underused. A one-line "Relevant Coursework" section is not padding — it's signaling. If you took Distributed Systems, Algorithms, or Machine Learning, those are keywords that land in ATS filters and give a technical recruiter a quick read on your preparation. Keep the list tight: 4–6 courses maximum, no intro-level filler.

The education block for a new grad should look like this:

• Degree and major (bold, top of section)
• University name and graduation year
• GPA (if ≥ 3.5)
• Relevant coursework (4–6 courses in a single line or comma-separated list)
• Honors or awards (Dean's List, scholarship names — one line max)

Put education at the top of the page. You are a new grad. Your degree is your primary credential. Moving it to the bottom to look like an "experienced" candidate is a mistake — it makes recruiters hunt for the most important context they need.

Projects Are Your Work Experience — Treat Them That Way

This is the most important mindset shift in this entire guide. If you don't have internship experience, your projects section is your experience section. Rename it if you have to: "Engineering Projects," "Selected Projects," "Technical Projects" — not "Personal Projects," which sounds like a weekend hobby.

Every project entry should follow the same structure as a work experience bullet:

1. What you built (the artifact)
2. What technology you used (the stack)
3. What result it produced (the outcome — quantified if possible)

Bad: "Built a web app using React and Node.js."

Good: "Built a real-time collaborative task manager using React, Node.js, and WebSockets, supporting concurrent editing for up to 50 simultaneous users with sub-100ms latency."

The second version tells a hiring manager you understand concurrency, have thought about performance, and can communicate technically. The first tells them nothing except that you followed a tutorial.

What counts as a project?

• Capstone or senior design projects
• Hackathon submissions (especially if you placed)
• Open-source contributions (even small ones — a merged PR counts)
• Research assistant work with a faculty member
• Independent apps, tools, or scripts you built and deployed
• Club or student organization technical work

Aim for 3–4 projects on your resume. Any fewer and the section feels thin. Any more and you're signaling that you can't prioritize. For each project, include a GitHub link or a live URL. No link means it probably doesn't exist as far as a recruiter is concerned.

One Internship Beats a Perfect GPA — Go Get One Before You Graduate

If you are reading this before you've graduated and you have zero internship experience, stop everything and prioritize landing one. Even a mediocre internship at a no-name company is more valuable than a 4.0 GPA with no real-world work. Why? Because it proves you can show up, work on a team, and ship code under someone else's direction — skills that are genuinely hard to assess otherwise.

"Hiring managers aren't looking for perfection on a new-grad resume. They're looking for evidence that you can function in a real engineering environment."

If you have internship experience, it goes above your projects section and below education. Format each internship with 2–4 bullet points that follow the same outcome-oriented structure as your projects. If your intern project wasn't technically impressive, focus on scope and collaboration: how large was the codebase, how many engineers worked on your team, did you go through code review, did you ship to production?

If your internship was at a company no one has heard of, don't be embarrassed about it. Add a one-line context setter in parentheses: (Series B SaaS startup, 80 engineers). That reframes it immediately.

The Skills Section Is a Keyword Game — Play It Deliberately

Almost every company with more than 50 employees uses an Applicant Tracking System (ATS) to filter resumes before a human sees them. ATS systems pattern-match on keywords. Your skills section is where you feed the machine.

Here's how to build an effective skills section:

1. Pull the exact language from the job description. If they say "REST APIs," write "REST APIs" — not "RESTful services" or "HTTP APIs."
2. Organize by category: Languages, Frameworks, Tools, Platforms. Don't dump everything in a single comma-separated wall of text.
3. Only list things you can actually discuss in an interview. You will be asked about anything on this section. "Familiar with Kubernetes" is an invitation to be destroyed in a technical screen.
4. Put your strongest skills first within each category. Recruiters skim left-to-right.
5. Drop technologies you used once in a tutorial. They create risk without adding value.

For a CS new grad in 2026, a reasonable skills section might look like:

• Languages: Python, Java, TypeScript, SQL
• Frameworks & Libraries: React, Spring Boot, Node.js
• Tools & Platforms: AWS, Docker, Git, PostgreSQL
• Concepts: REST APIs, Distributed Systems, Data Structures & Algorithms

Keep the total to 15–20 items. More than that and it stops being a signal and starts being noise.

One Page Is Not Negotiable for New Grads

You do not have ten years of experience. You have, at most, four years of school, a couple of internships, and some projects. All of that fits on one page — and it fits comfortably if you're not padding. Two-page new-grad resumes are a red flag. They signal either that you don't know how to prioritize or that you're trying to compensate for thin content with volume.

Practical tips for hitting one page without sacrificing quality:

• Use 10–11pt font for body text (10pt minimum — don't go below)
• Set margins to 0.5–0.75 inches
• Cut your objective statement entirely (no one reads them; they're space-wasters)
• Remove references and "references available upon request" (assumed)
• If a bullet takes more than two lines, rewrite it
• Remove high school entirely unless you went to a magnet school that's genuinely impressive in a technical context

The one exception: if you have a legitimate publication, patent, or significant research contribution, you can add a one-line Publications or Research section and push to one page by tightening elsewhere.

Tailor Each Application — But Not in the Way You Think

Conventional resume advice says to rewrite your resume for every single job. That's overkill and it's not how most successful job seekers actually operate. Here's the practical version:

Maintain one master resume. For each application, make three targeted changes:

1. Swap keywords in your skills section to mirror the job description's exact language.
2. Reorder your project bullets so the most relevant project to that role appears first.
3. Adjust your summary line (if you have one — more on this below) to name the company or role explicitly.

That's it. You're not rewriting the resume from scratch. You're making surgical edits that take 10–15 minutes per application. This keeps your process scalable while still giving each application a better shot at clearing ATS and landing with a recruiter who feels like you actually read the job posting.

On summaries: a two-line professional summary at the top of a new-grad resume is optional but can help if you're applying to roles slightly outside your major or making an unusual pivot. Keep it factual and specific: "Computer Science graduate from University of Waterloo with internship experience in backend systems and a focus on distributed systems and API design." That's better than "passionate, driven, and eager to learn." Never use those words. They mean nothing.

Formatting Kills More Resumes Than Content Does

A technically weak resume that's easy to read will outperform a technically strong resume that's hard to parse. This is the uncomfortable truth that a lot of new grads discover after sending 100 applications into the void.

Formatting rules that are non-negotiable:

• Use a single-column layout. Two-column resumes break ATS parsing. A recruiter's ATS might read your skills section as part of your education. Single column, always.
• Use a standard font. Calibri, Garamond, Georgia, or Arial. Not anything decorative. Not anything that requires special rendering.
• Save as PDF. Not .docx, not .pages, not a Google Doc link. PDF preserves your formatting across every system.
• Don't use tables, text boxes, or graphics. They look good in Canva and are invisible to ATS.
• Consistent date formatting. "May 2024" and "2024–05" should not both appear on the same resume.
• Left-align dates on the right margin. Recruiters scan dates on the right side of the page. Center or left-aligned dates slow them down.

If you want a template, use a simple LaTeX template from Overleaf, or a plain Word/Google Docs template that passes the ATS test. Jake's Resume on GitHub is a widely recommended LaTeX option that's clean and ATS-safe. Avoid anything from resume builder sites that exports in HTML or proprietary formats.

Next Steps

You now have a framework. Here's what to actually do in the next seven days:

1. Audit your current resume against this guide in the next 24 hours. Check: Is education at the top? Are your projects framed with outcomes? Is it one page? Are you using a single-column layout? Fix every violation.
2. Add GitHub links to all project entries. If a project isn't on GitHub and publicly visible, push it this week. A recruiter who clicks a dead link or gets a 404 will not follow up.
3. Run your resume through a free ATS scanner (Jobscan or Resume Worded both have free tiers). Identify which keywords you're missing for a specific target role, then add them to your skills or project descriptions.
4. Write three tailored versions of your resume for three real job postings you actually want to apply to. Practice the keyword-swap and project-reorder process until it takes under 15 minutes.
5. Send your resume to one working engineer for feedback — not a career counselor, not a parent. A working engineer at a company similar to where you want to work. Post in relevant Discord servers, LinkedIn, or cold message someone you admire. Most engineers will spend 15 minutes giving honest feedback if you ask respectfully and make it easy for them.

Your resume isn't a document about who you are. It's a sales tool designed to get you a 30-minute phone screen. Once you internalize that, every decision — what to include, how to word it, where to put it — becomes a lot clearer.

Related guides

• New-Grad Software Engineer Resume Template — Projects, Internships, and the No-Experience Pivot — New-grad SWE resumes win when they turn school, internships, and projects into evidence of engineering judgment. This template shows how to structure a no-experience or light-experience software resume with real technical signal.
• Bootcamp Grad Resume Template — Projects, Capstone, and Getting Past the No-CS-Degree Filter — A bootcamp grad resume template for positioning projects, capstone work, transferable experience, and ATS keywords so hiring teams see practical engineering proof even without a CS degree.
• Projects Section on a New-Grad Resume — What to Include and How to Describe Impact — For new grads, projects can carry the weight that work experience has not yet earned. Learn which projects to include, how to write impact-focused bullets, and how to avoid the common project-section traps.
• Career-Change Resume Template: Translate Experience Across Industries — Stop hiding your past. Learn how to reframe your experience so hiring managers in a new industry see a perfect fit, not a risky hire.
• Intern Software Engineer resume template — landing your first internship with no work history — You can build a credible intern SWE resume without formal work history by leading with projects, CS fundamentals, tools, and proof you can learn. This template shows what to include, how to write project bullets, and which mistakes cost interviews.