Entry-level resume with no experience: what to put where

"I have no experience" is the opening line of nearly every first-job applicant's internal monologue — and it is almost always wrong. Most new grads, students, and career-starters have more resume-legible material than they realize. The problem isn't lack of experience; it's not knowing which things count as experience and how to present them on the page.

This guide covers what actually counts as experience, the page structure that works for entry-level candidates, how to write bullets when you don't have a full-time job to describe, and the four mistakes that keep strong new candidates from getting interviews. Pair this with our bullet points guide — the 4-part formula works even when you're writing about coursework or clubs.

What counts as resume experience (more than you think)

For entry-level candidates, all of these count as experience and belong on the resume if they involved real work, responsibility, or output:

• Internships (paid, unpaid, virtual, or co-op). Even 8-week internships.
• Class projects with real deliverables. Capstone projects, team software builds, research posters, marketing campaigns for a real client.
• Research assistantships and lab work. Even if unpaid. Especially if you contributed to a paper or poster.
• Teaching, tutoring, and TA work. Including informal peer tutoring if you led a cohort.
• Leadership roles in student orgs. Treasurer, president, events lead — these involve real budget, real people, real projects.
• Hackathons, case competitions, and design challenges. Including ones you didn't win. Participating and shipping matters.
• Part-time and retail work. Stock, scheduling, customer-service metrics, cash handling, shift-lead work — all quantifiable.
• Self-directed projects. A side website, a published article, an open-source contribution, a YouTube channel with real subscribers. Evidence of initiative is a scarce signal at this level.
• Volunteer work with scope. Organizing events, coordinating volunteers, running a small program — the verbs are the same as paid work.
• Freelance or gig work. One or two meaningful gigs (designed a logo, edited a book, built a website) count if you can describe the work and outcome.

The entry-level resume structure

Entry-level resumes follow a different structure than experienced-hire resumes. Education moves up; experience is replaced or supplemented by projects and activities. The full structure:

1. Header (name, email, phone, location, LinkedIn, portfolio/GitHub
                if applicable)
2. Education (school, degree, expected or actual graduation date,
              GPA if ≥ 3.5, relevant coursework, honors)
3. Experience (internships, part-time work, significant volunteer
                or project work — in reverse chronological order)
4. Projects (class projects with deliverables, hackathons,
              self-directed builds)
5. Skills (tools, languages, software — real skills, not "MS Word")
6. Activities & leadership (student orgs, clubs, teams)
7. Optional: Certifications, Languages, Awards

One page is the firm rule for entry-level. Two pages at this stage reads as padding.

Writing bullets without a "real" job

The 4-part bullet formula (Action + Scope + Method + Outcome) works for any kind of experience — paid, unpaid, class project, or club role. You just need to name what you did at what scale, using what method, with what result. Examples across common entry-level scenarios:

Internship bullet

Before: "Helped the marketing team with social media."

After: "Owned @CompanyName Instagram for 8-week internship
(posting 5x/week); grew follower count from 2,400 to 3,700
(+54%) and drove a 2.8% engagement rate vs company baseline
of 1.1% through content planning in Notion and CapCut
editing."

Class project bullet

Before: "Worked on a group project building an app."

After: "Led a 4-person capstone team building a React Native
fitness-tracking app; shipped to 180 test users in 10 weeks.
Owned the state-management architecture (Zustand + TanStack
Query) and the offline-sync layer. App awarded Best Technical
Implementation at UCLA CS capstone showcase."

Research assistantship bullet

Before: "Did research with Professor Smith."

After: "Research Assistant, Smith Lab (Computational Biology,
UCSD); ran RNA-seq differential expression analysis on 18
patient samples using DESeq2 + R, contributing to a paper
accepted at ISMB 2025 (3rd author). Weekly 1:1 with PI,
two-lab-meeting presentations."

Retail / part-time work bullet

Before: "Worked as a barista at Starbucks."

After: "Shift Supervisor at Starbucks (15-20 hrs/week over 18
months); promoted from barista in 6 months. Trained 4 new
baristas through onboarding; covered opening shifts (5am-1pm)
without supervisor oversight on weekends; hit store goals for
drive-thru times 14 of 18 months."

Student org leadership bullet

Before: "President of coding club."

After: "President, UCSB Coding Club (80 members, $4k annual
budget); grew active membership from 35 to 80 over 2 semesters
by launching weekly paired-coding sessions and a 12-person
mentorship program with alumni engineers from Google, Airbnb,
and Databricks."

What to do with your GPA, coursework, and honors

• GPA: Include if 3.5+ (some recruiters filter on this). Include in-major GPA if higher. Omit if under 3.5.
• Relevant coursework: Include 4-8 courses that match the role. "Machine Learning, Distributed Systems, Databases, Computer Networks" is more useful than listing all 40 classes you took.
• Honors: Dean's List (note semesters), academic scholarships, cum laude and higher, major-specific awards — all worth including.
• Study abroad: Include if substantial (a semester or more); skip for 2-week programs unless directly relevant to the role (e.g. applying to international consulting and spent a semester in Singapore).

Four mistakes that quietly sink entry-level resumes

Mistake 1: Claiming "experience" you don't have

Padding a resume with fake responsibilities at a real part-time job is the single fastest way to fail the interview. Hiring managers can tell within two questions whether your "led a team of 5" at the pizza place is real or invented. Be honest about scope — the honest version is always stronger than the inflated one.

Mistake 2: Listing soft-skill filler

"Motivated team player with strong communication skills, detail-oriented and eager to learn" is the entry-level equivalent of experienced-hire buzzword-stuffing. Every candidate has those. Replace the space with concrete projects or wins, even small ones.

Mistake 3: Formatting like an experienced-hire resume

Two pages with Education at the bottom, 10 bullets per job, and a dense skills section reads as miscalibrated. Entry- level resumes look different on purpose. One page, Education prominent, projects section, activities section — follow the entry-level structure, not the senior-candidate structure.

Mistake 4: Omitting the portfolio or GitHub URL

At entry level, evidence of self-directed work is the scarcest and most valuable signal. A personal website, a GitHub profile with real projects, a design portfolio on Behance, a writing portfolio on Medium — any of these moves you ahead of candidates who only list coursework. If you don't have one, build one this weekend; it's higher-leverage than another resume edit.

When internships are "required" but you don't have one

Many entry-level postings list internships as required. Most of those postings are still open a month later because qualified candidates interview elsewhere. Apply anyway if:

• You have substantial project work that demonstrates the required skills.
• You've worked at a comparable scale in a student organization, research lab, or self-directed project.
• You can name the specific tools, frameworks, or methods the posting asks for in your projects or coursework.

In the cover letter, name the absence of formal internship experience directly and reframe — don't hide it. See our career-change resume guide for the reframing pattern (it works the same way for no-internship candidates).

The self-project-heavy resume (when school is the bulk)

For CS, design, and writing-heavy roles, self-directed projects often matter more than the internship you didn't have. Pattern:

• Projects section becomes primary, not secondary. Move it above Experience if your projects are stronger than your internships.
• Link to live work. Portfolio URL, GitHub repo links, deployed app URLs. Skip projects that don't have something to show.
• Include 3-5 projects, not 10. Curate. One fully-documented project with clear architecture beats five half-finished ones.
• Write bullets like you would for internships. Tool, scope, method, what the project does. "Built a full-stack inventory management app with Next.js, PostgreSQL, and Supabase Auth; deployed to Vercel with 40 real test users; code at github.com/yourname/inventory- app".

One-page template for entry-level candidates

[Your Name]
email@domain.com  ·  (555) 555-5555  ·  City, State
linkedin.com/in/yourname  ·  github.com/yourname  ·  yourportfolio.com

EDUCATION
  [University Name], [City, State]                  [Month Year]
  B.S. [Major], [GPA if 3.5+], [In-major GPA if higher]
  Relevant coursework: [4-6 courses matching the role]
  Honors: Dean's List [semesters], [Scholarships], [Awards]

EXPERIENCE
  [Role Title] | [Company/Org] | [Month Year – Month Year]
    · Bullet using 4-part formula (action + scope + method + outcome)
    · Bullet 2
    · Bullet 3

  [Role Title] | [Company/Org] | [Month Year – Month Year]
    · Bullet 1
    · Bullet 2

PROJECTS
  [Project Name] | [Tech stack / Tools]          [Month Year]
    · What the project does, at what scale
    · Link: github.com/yourname/project or yourproject.com

  [Project Name] | [Tech stack / Tools]          [Month Year]
    · Description
    · Link

SKILLS
  Technical: [relevant hard skills — languages, tools, frameworks]
  Languages: [natural languages if relevant]

LEADERSHIP & ACTIVITIES
  [Role] | [Org] | [Month Year – Present]
    · One-line description of scope

  [Role] | [Org] | [Month Year – Month Year]
    · One-line description

Where to find more

For the bullet-writing mechanics that work at every career stage (including entry-level), see our resume bullet points guide. For the foundational resume structure and what recruiters actually look at, how to write a resume covers the general rules. If you're applying to a role that requires experience you don't yet have, the career-change resume guide covers the reframing pattern for non-traditional backgrounds. And for clean, ATS-safe entry-level resume starting points, our template gallery has single-column minimal layouts that work well at this stage.

You almost always have more to put on a resume than you think. The work is identifying which parts of your life count and presenting them at the scale they deserve. Strong entry-level resumes aren't longer — they're more specific.