"I have no experience" is the most common self-assessment of recent graduates writing their first real resume. It's almost always wrong. What's usually true is that they have material — class projects, internships, summer jobs, campus roles — and no structure that lets a recruiter see it in the fifteen seconds they'll spend on the page.

This post is about the structure. Once the structure is right, most recent grads find they have more to work with than they thought.

The five sections

A working recent-grad resume runs in this order: header, education, projects (or experience), experience (or projects), skills, activities. The order varies by what you have most of; if you have strong internship experience, that goes above projects. If you've done substantial projects but no internships, projects go first.

Education leads, but tightly. Two or three lines. Degree, school, graduation year, GPA if 3.5 or above, one line of honors if applicable. Skip the "Relevant Coursework" list unless the coursework directly maps to the JD — and even then, three to four courses, not twelve. For more on placement logic, see resume-education-placement-top-or-bottom.

Projects often do the heaviest lifting. For technical roles especially, a capstone project, a substantial class project, or a personal portfolio piece can carry more weight than a junior-level internship. Structure each project the same way: a single line on what the project did, one or two bullets on what you specifically built (not what the group did), and a line on tech stack or measurable outcome. Real code on GitHub helps. Screenshots in a portfolio help.

Internships and part-time work are experience. A summer internship at a real company should be formatted exactly like a full-time job: title, company, location, dates, three bullets. Don't downgrade internships by labeling them differently. A part-time job that taught real skills — front-desk work, retail management, lab assistance, tutoring — also belongs here, framed for the transferable skills that matter. "Resolved 30+ customer escalations daily, achieving 95% first-call resolution" is a real bullet from a part-time service job.

Skills section, specific. Real tools, frameworks, languages you can demonstrate in an interview. Not "leadership" or "communication." If the JD names Python, R, SQL, or specific software, list the ones you've actually used.

Activities and leadership last. Real leadership roles count — president of a club, captain of a team, founder of an initiative. Listing memberships ("Member, Honor Society") doesn't help; it pads. Recruiters can tell.

What strengthens vs. weakens

The strengtheners share a pattern: they're specific and verifiable. A class project with a real GitHub repo and a brief one-line outcome ("processed 2M rows of weather data to predict precipitation 12 hours out, 73% accuracy") is concrete enough that a recruiter can engage with it. An internship with three real deliverables, even unpaid, is concrete. A part-time job reframed for transferable skills is concrete.

The weakeners share a pattern: they're either generic (padded skills sections, vague "experience in...") or padded (every course as relevant coursework, every club as activity). The recruiter brain registers these as resume-padding, which actively works against the candidate. The implicit message is "I don't have much, but here's a lot of words" — and the page-length-but-low-density combination is worse than a shorter, denser resume.

The hardest discipline for recent grads is leaving things off. The temptation to list everything you've done in college is strong; the reality is that less is more if what's left is specific.

For the underlying work of turning duties into achievements, see achievements-vs-responsibilities. For quantifying without obvious metrics, see quantifying-resume-without-metrics.

The "no experience" reframe

The phrase "no experience" usually means "no resume structure that surfaces what I've done." Most recent grads have material:

• Class projects with deliverables. Code, papers, presentations, lab work, design portfolios.
• Internships, paid or unpaid. Even short ones.
• Summer jobs and part-time work. Retail, food service, ops, lab assistant, tutoring.
• Volunteer and campus roles. RA positions, peer mentoring, club leadership, student-government work.
• Personal projects. Side projects you've built, open-source contributions, freelance work.
• Academic research. Working with a professor on real research, even unpublished.

The fix is rarely "do more things." It's "frame what you've done in language a recruiter can scan in fifteen seconds."

A specific entry-level antipattern

There's a category of common entry-level resume tactics that look helpful and aren't:

• The "Objective" section. "Recent graduate seeking opportunities to apply my skills in a dynamic environment." This says nothing. Replace with a one-line summary tied to a specific role, or omit entirely.
• Three columns of skills. Visually busy, ATS-hostile. A short clean list works better.
• "References available on request." Default assumption. Listing it wastes a line.
• Every project listed at equal weight. Pick the two or three that are strongest. Quality over quantity is the rule.

When the GPA goes off

The GPA convention: list it if it's 3.5 or above, omit it otherwise. Below 3.5, the absence is normal and doesn't draw attention; presence of a 3.1 actively works against you because it confirms a number the recruiter didn't need.

If your major GPA is meaningfully higher than your overall GPA, you can list it: "Major GPA: 3.7" alongside the degree.

After three years of full-time work, GPA should come off the resume entirely.

The internship that wasn't great

A specific awkward case: you had an internship that you don't feel was a real experience — three months of administrative work, no project of your own. How to handle it?

The honest move is to find the most concrete thing you did, however small. "Built a tracking spreadsheet that consolidated three team workflows" is a real bullet. "Compiled monthly reports reviewed by senior leadership" is a real bullet. Don't fabricate; don't omit. List it, find the most concrete contributions, and move on.

What this isn't

A few clarifications:

• It's not a magic formula. A well-structured resume from a recent grad still loses to a poorly-structured resume from someone with three years of experience. The structure compensates partially, not entirely.
• It's not a license to embellish. Specific is good. Invented is interview-killing.
• It's not the same for every field. Creative and design fields rely more on portfolio; technical fields on projects with code; consulting on case-team experience. Adjust.

The short version: education tight at the top, projects or experience next based on which you have more of, internships and part-time work formatted as real jobs, skills specific and verifiable, activities only when real. "No experience" is almost always a structure problem, not a content problem.