The new-grad resume, when you have "no experience"
You have far more than you think. The trick is structure and honest framing — not stretching a thin page into a thick lie.
The first resume is the hardest one you'll ever write, because it feels like a form asking for things you don't have yet. No job titles. No decade of impact. Just a degree, a couple of projects, and maybe an internship you're not sure counts. Here's the reframe that changes everything: a resume isn't a record of jobs, it's evidence that you can do the work — and you've been generating that evidence for years, in projects, coursework, part-time jobs, and clubs. This is how to arrange what you actually have into a page that reads as ready, not empty.
Projects are experience — treat them like jobs
A project you can talk about beats an internship you coasted through. Recruiters don't care whether you got paid; they care whether you built something real and can explain it. Give your best projects the same structure you'd give a job: what it was, what you built, what it did, who used it.
Same project. The second sounds like engineering because it names scope, users, and a real tradeoff you made. Every project deserves this treatment.
List coursework selectively — relevance signals focus
Dumping all 40 courses signals that you couldn't tell which ones matter. List the handful that map directly to the job you want, and turn a big course project into its own bullet — coursework doing double duty as experience.
- Applying for data roles? Machine Learning, Statistics, Databases — not Intro to Philosophy.
- Name the capstone or thesis if it produced something concrete you can discuss.
- Skip "Dean's List" filler unless the GPA genuinely helps your case.
Count the things that don't feel like "real" experience
The part-time and volunteer work you're tempted to leave off is often your best proof of the exact traits employers screen for — reliability, ownership, working with people.
- The campus job where you trained new hires? That's leadership.
- The club event you ran? Budget, logistics, a team, and a deadline.
- The tutoring gig? Communication and consistency — quantified by how many students, how often.
You don't have to pretend these were corporate roles. You just have to describe them with the same concrete, quantified language you'd use for one.
Lead with education — for now
Until you have a role or two under your belt, your degree, projects, and relevant coursework carry the top of the page. That's not a weakness; it's the correct ordering for where you are. Put Education near the top, make your projects section substantial, and let experience sit below. The moment you land the first job, this flips — and it flips fast.
One page, always — and why that's good news
You are not a senior staff engineer yet, and trying to look like one is the fastest way to look junior. A single, tight page reads as confidence and focus; two padded pages read as someone who couldn't tell what mattered. The constraint is on your side — it forces you to keep only your strongest evidence.
Cut the objective statement, cut the skills you listed just to fill space, cut the third mediocre project. What's left — a few real things, described in concrete terms you can defend in an interview — is a genuinely strong new-grad resume. That's the whole job.