The advice 'just write what you've done' is useless if you believe you haven't done anything. The reality is that every new grad and career switcher has material — coursework projects, club leadership, volunteering, internships, freelance gigs, side projects. The task is framing, not invention. This article gives you the exact structure.

The no-experience resume structure

  1. Header: name, email, phone, LinkedIn, GitHub (or portfolio)
  2. Summary: 2 lines — you can skip this if you're under 2 years of college
  3. Education: moved up, includes coursework, GPA (if 3.5+), relevant classes, projects
  4. Projects: the heart of the resume — treat each one like a mini-job
  5. Experience: any internship, part-time, volunteering, freelance — in reverse chronological order
  6. Skills: tools and languages, grouped not bulleted

How to write a project like a job

Each project gets the same treatment as a work bullet: what you built, what technology, what the outcome was, with numbers. A course project that processed 10K records and cut a query from 8s to 200ms belongs on your resume as a one-line hire signal.

Example: course project → resume entry

Distributed File Cache (CS 162 final project) — Built a 3-node replicated cache in Go with LRU eviction, achieving 99.2% cache hit rate on a simulated read-heavy workload of 50K ops/sec. Benchmarked against Redis single-node baseline. [GitHub link]

Sources of experience you may have overlooked

  • Class projects with measurable outcomes
  • Research assistantships (even one semester)
  • Open source contributions (even one merged PR)
  • Hackathons (list them with outcome, not participation)
  • Freelance / gig work (tutoring, design, development)
  • Student org leadership (treasurer, president, committee chair)
  • Volunteering (especially with measurable impact)
  • Bootcamp or certification projects
  • Paid side work (DoorDash, retail, camp counselor) — for soft-skill framing only, not primary
Don't use part-time retail as your main pitch
A summer retail job is fine as a supporting entry, but it should never be the strongest block on a technical resume. If your projects are stronger, lead with projects.

The internship question

If you had one internship, it's the most credible entry on your resume and should be the most detailed. Write four bullets minimum, each quantified. If you had zero internships, do not leave the 'Experience' section empty — put volunteering, freelance work, or student-org leadership there with 'Experience' as the section header.

Skills section rules for new grads

  • Group by category: Languages, Frameworks, Tools
  • List only what you'd be comfortable being quizzed on in interview
  • Do not include 'Microsoft Word' — it's filler
  • Do include certifications, relevant coursework, and languages (spoken) if notable

What recruiters look for in a no-experience resume

  1. Did they ship something real? (project with a GitHub link beats any coursework description)
  2. Do they write clearly? (bullets, not paragraphs; metrics, not adjectives)
  3. Did they take initiative somewhere? (founder of X, organized Y, led Z)
  4. Does the stack match what we use? (mirror the JD's tech names)
Try it free
Fitted Resume works for new-grad resumes too — paste your current draft and the JD, and it flags weak framing and missing keywords. Three free runs a day.