TL;DR — With no work history, your résumé leads with education and projects, not jobs. Pull "experience" from coursework, clubs, volunteering, and side projects; write every line as a verb-first bullet with a real result; mirror the posting's wording for things you've actually done; and keep the layout single-column so software can read it. One page, saved from a word processor.

Your first résumé feels impossible because every section seems to assume you've already had a job. You haven't — and that's normal. Hiring managers for entry-level and internship roles know they're reading résumés from people early in their careers. What they're looking for isn't a long work history; it's evidence that you can learn, follow through, and do the thinking the role needs. You almost certainly have that evidence already — you just have to present it like it counts.

What actually counts as experience

"Experience" is not the same as "paid full-time jobs." For a first résumé, all of the following are fair game, and recruiters expect to see them (Harvard career services makes exactly this point):

Coursework and academic projects — especially anything with a deliverable: a research paper, a capstone, a data analysis, a working prototype.
Clubs and student organizations — particularly if you held a role, ran an event, or grew membership.
Volunteering and community work — recurring commitments show reliability.
Part-time, seasonal, or gig work — retail, food service, tutoring, and babysitting all build real, transferable skills.
Personal projects — a website you built, a budget you tracked, a small business or side hustle, a portfolio of designs.

If you did the thing and can talk about it, it can go on the résumé. Two rules keep this from turning into padding. First, describe it accurately — a shift lead is a shift lead, and treasurer of a club is treasurer of a club; the work is worth listing on its own terms and inflating the title is the fastest way to lose a reader. Second, don't scatter it: club, volunteer, and part-time roles belong in one Experience section, tagged inline where it matters ("Treasurer, Photography Club (Volunteer)"), not broken out into three thin blocks that make the page look emptier than it is.

Lead with your education

With little work history, education is your headline section — put it near the top, right under your contact info. Don't reduce it to one line. Include:

Your school, degree, and expected graduation date (an expected date is completely normal).
Your GPA if it's roughly 3.5 or higher — otherwise leave it off; a missing GPA is unremarkable.
Relevant coursework — three or four courses that map directly to the job, not a copy of your transcript. Pick the ones a hiring manager for this role would recognize.
Honors, scholarships, or a Dean's List mention if you have them.

For most students, education is the single most actionable lever you have, so give it room. This placement is temporary, though: once you have a year or two of full-time work behind you, education moves to the bottom and the jobs take the top.

Turn skills into proof

A transferable skill is one that carries from where you learned it to the job you want. The trick is to name the skill the employer cares about, then prove it with something you actually did.

Read the posting and notice the verbs and nouns it repeats — "communicate," "organize," "analyze," "deadline." Those are the skills to surface. Then map each to evidence, written as a verb-first bullet with something concrete at the end — a result where you have one, the size of the work where you don't:

Ran the front register during the dinner rush → "Handled 100+ transactions a shift with zero till discrepancies."
Organized a 40-person club event → "Coordinated scheduling, venue, and catering for a recurring 40-person club event."
Built a class project in a team of four → "Built a data dashboard with a 4-person team and presented findings to faculty."

"Coordinated scheduling for a 40-person event" beats "was in charge of the event" every time.

A word on numbers, because this is where first résumés go wrong in both directions. Numbers help — but never invent one. Reviewers catch invented metrics quickly, they read as lying rather than achieving, and a single figure you can't defend puts every other line in doubt. If you don't have a real number, quantify the scope you sat in rather than an impact you caused: how many people, how many shifts, how many customers a day, how big the event, how large the dataset, how long the commitment ran. "Front desk and phones for a 200-person department" claims nothing false and still sizes the work. Prefer the steady-state figure over your busiest day — a number you can defend beats a big one. And a percentage with no before-state ("improved efficiency 30%") is worse than no percentage at all, because the first interview question will be "compared to what?"

Add a projects section

If your work history is thin, a Projects section is the most powerful thing you can add — it shows capability directly instead of relying on a job title to imply it. For each project, answer three things in one or two lines: what you built, how you built it, and what came of it.

Campus Sustainability Dashboard — Built a web dashboard tracking dorm energy use with a 4-person class team; presented findings to facilities staff, who adopted two of the recommendations.

That single entry demonstrates technical skill, teamwork, communication, and impact — more than most job titles do on their own.

Match the posting's language

This is the step most first résumés skip. Recruiters search their applicant database for the literal terms in the job description, so if the posting says "data analysis" and your résumé says "worked with numbers," you simply don't turn up in the results. Nothing rejects you — you're just not in the set.

So tailor each application: pull the key skills and tools straight from the posting and — where they're genuinely true for you — echo that wording in your skills, coursework, and bullets. Where they aren't true, leave them off. Matching the vocabulary makes you findable; it doesn't make you qualified, and padding the list with things you can't discuss only relocates the rejection to the interview. (Doing it by hand for every job is tedious, which is what our Tailor Résumé tool exists to speed up.) There's more on how these systems really behave in résumé keywords and the ATS.

Make it ATS-readable

The goal is a file software can parse cleanly. When it can't, you don't get rejected — your details land in the wrong database fields, which amounts to the same thing, because nobody finds you:

Use a single-column layout. A two-column or table layout often gets read straight across the page and merged into word salad (Jobscan documents this failure mode in detail). Keep one column, top to bottom.
Skip skill-bar graphics, icons, and headshots — they parse as nothing.
Build it in a word processor (Google Docs, Word) and submit what the application asks for. When there's no instruction, a text-based PDF (exported from your document — not scanned or printed-to-PDF) or a .docx both parse well; some ATS portals actually prefer .docx. The thing that breaks parsing is the design, not the file extension.
Use a standard font and clear section headings ("Education," "Experience," "Projects," "Skills").

A quick example

Here's the skeleton for someone with no formal job history — education first, then proof:

JORDAN RIVERA
[email protected] · linkedin.com/in/jordanrivera · github.com/jrivera

EDUCATION
B.S. Computer Science, State University — Expected May 2027
GPA 3.7 · Relevant coursework: Data Structures, Databases, Statistics
Dean's List (3 semesters)

PROJECTS
Campus Sustainability Dashboard — Built a web dashboard tracking dorm
energy use with a 4-person team; 2 recommendations adopted by facilities.

EXPERIENCE
Barista, Local Coffee Co. (2024 – Present)
- Handled 100+ transactions per shift with zero till discrepancies
- Trained 3 new hires on the point-of-sale system

SKILLS
Python, SQL, Git, Excel, Tableau, data visualization

Note what the skills line does and doesn't hold: tools and languages only, no "teamwork" or "hard worker." With little work history the skills section is often the thing carrying you, so make it dense with real, specific, interviewable tools — and make sure each one also shows up somewhere in a bullet or a project.

Contact info: what to include and leave off

Include: a professional email (some variant of your name — not your old gamer tag), your city/state, a LinkedIn URL, and a portfolio or GitHub link if relevant. Leave off: a photo, your date of birth, marital status, and your full street address. None of those help, and some invite bias.

Common first-résumé mistakes

Listing duties instead of results. "Responsible for stocking shelves" says nothing. "Cut restock time by reorganizing the stockroom" says plenty.
A generic objective statement. "Seeking a challenging role where I can grow" is filler. If you want a summary, make it a specific one or two lines tying your degree and one transferable skill to this role — and only if it adds something. Otherwise, give the space to projects.
Inflating titles, skills, or numbers. If you can't speak to it in an interview, don't claim it. A claim that outruns the role you actually held is the fastest way to make a reviewer doubt everything else on the page — and honesty gets you matched to roles you'll actually thrive in.
One résumé for every job. Tailor the keywords and top bullets to each posting.

A first résumé doesn't need to be impressive in the corporate sense — it needs to be specific, honest, and easy to read. Get those three right and you're ahead of most of the pile. What it can't do is manufacture demand: entry-level hiring is genuinely tight, and a quiet inbox usually says more about how many openings exist than about your document. Make the résumé good once, then spend the hours on targeting and on people. When your draft is solid, the next step is a cover letter and pointing it at real, active jobs worth applying to.

Sources

Harvard FAS Career Services — No work experience? Here's what to highlight instead
UC Berkeley Career Engagement — Résumés
Jobscan — Can an ATS read tables and columns?

How to Write a Résumé With No Work Experience