What do I put on a resume if I have no work experience?

Short answer: you put everything else. Education, coursework, projects, skills, volunteer work, freelance gigs, certifications, and relevant life experience all count. A resume with no formal employment isn't an empty resume — it's a resume where you show what you can do instead of where you've been paid to do it. Hiring managers evaluating entry-level candidates know the deal; they're looking for evidence of capability, not a job title.

The anxiety behind this question is real, but it's worth naming the reframe plainly: nobody's first resume has work experience on it. Everyone starts here. The candidates who stand out aren't the ones who had jobs — they're the ones who filled the page with proof that they can learn, finish things, and work with others.

Lead with education — and make it work hard

If you're a student or recent graduate, education goes at the top, and it should carry more than the school name and dates. Include your degree or expected graduation date, your major, and your GPA if it's strong (generally 3.5 or above on a 4.0 scale; below that, leave it off and let the rest speak). Then add the parts that show substance: relevant coursework, academic honors, a thesis or capstone project, and any teaching or research assistant roles.

Relevant coursework deserves its own line when you have no experience — it's the closest thing to a skills inventory a student has. List courses that map to the job: data structures for a programming role, financial accounting for a finance internship, research methods for an analyst position. Don't list every class you've ever taken; curate for relevance.

If you're not a student — a career changer, a returning worker — education still matters, but it may sit below a skills or projects section. Online courses and certifications from recognized providers belong here too; they're legitimate education, especially when they're current and relevant.

Projects are your experience section

Here's the core move: replace "Work Experience" with "Projects" and treat it with the same seriousness. A project entry has a title, a one-line description of what it was, what you did specifically, what tools or skills you used, and — critically — the outcome.

Class projects count. Personal projects count. A website you built, an analysis you ran on public data, a short film you edited, a small business you started, an app you prototyped — all of it counts. The bar isn't "was I paid"; the bar is "did I do real work with a real result." For each project, use the same bullet-point discipline you'd use for a job: start with a strong verb, quantify where you can ("analyzed 10,000 rows of sales data," "designed a 12-page portfolio," "grew a campus club's membership from 8 to 40"), and name the tools.

Two or three solid projects with concrete outcomes will outperform a page of vague job descriptions. Hiring managers for entry-level roles read projects closely because they're the best available signal of how you actually work.

Skills, done properly

A skills section is standard, but most first resumes waste it. "Hard worker, team player, detail-oriented" is noise — everyone claims those, and they can't be verified. Instead, list concrete, checkable skills: programming languages, software tools, languages spoken, lab techniques, design tools, data tools, certifications like first aid or food handling.

Be honest about proficiency. There's a meaningful difference between "familiar with Python" and "built two projects in Python," and interviewers will probe. A short, honest skills list beats a long, aspirational one — getting caught inflating a skill in an interview is worse than not listing it at all.

Group skills by category when the list gets long: technical, languages, tools. Keep it scannable. And mirror the job description's language where it's truthful to do so — if they ask for Excel and you have it, write "Excel," not "spreadsheet software."

Volunteer work, campus roles, and everything else

Volunteer work is experience. Organizing a fundraiser involved budgeting, coordination, and outreach — those are professional skills regardless of pay. Tutoring, coaching, leading a student organization, serving on a committee, helping at a community event: all of it demonstrates reliability, initiative, and the ability to work with people.

Frame these entries like jobs: organization name, your role, dates, and bullet points about what you accomplished. "Volunteer, Community Food Bank — coordinated weekend shifts for 15 volunteers; streamlined intake process, reducing wait times" reads as real experience because it was real work.

Don't overlook informal work either. Babysitting, yard work, helping in a family business — these involve responsibility, scheduling, money handling, and customer interaction. You don't need to dress them up as corporate roles, but you also don't need to hide them. "Provided regular childcare for three families; managed scheduling and payments" is honest and shows reliability.

The format rules still apply

No experience doesn't mean no standards. One page — always one page at this stage. Clean, simple formatting with consistent dates, clear section headers, and readable fonts. No photos, no graphics, no creative layouts unless you're applying for design roles where the resume itself is the portfolio.

Proofread ruthlessly. A typo on an experienced hire's resume is a blemish; on a first resume, with less else to judge, it carries more weight. Read it backward, read it aloud, have someone else read it. Then save and send it as a PDF with a sensible filename — your name, not "resume_final_v3."

Tailor each application. This is the advice everyone skips and it matters most when you have the least to show: reorder your bullets, adjust your skills list, and emphasize the projects most relevant to each specific role. A generic resume says you want any job; a tailored one says you want this job.

The cover letter does heavy lifting here

When your resume is thin, a short cover letter — or the modern equivalent, a thoughtful application message — can carry the narrative the resume can't. Three short paragraphs: why this role, what relevant thing you've done (project, coursework, volunteer work), and why you're a fast learner worth betting on. Keep it specific and brief. For entry-level hiring, genuine enthusiasm plus one concrete proof point goes a long way.

Getting past the applicant tracking system

Many companies filter resumes through applicant tracking software before a human reads them, and first-time applicants should know how it works. The system parses your resume into structured data — contact info, education, skills, dates — and matches it against the job description's keywords. Fancy formatting breaks this parsing: tables, text boxes, graphics, headers and footers, and unusual fonts can all cause the system to misread or skip sections.

The defense is simple: keep formatting boring. Standard section headings ("Education," "Skills," "Projects"), a single column, common fonts, no images, no tables. Save as a PDF unless the application specifically asks for another format — modern systems handle PDFs fine, and it preserves your layout for the human who reads it next.

Keywords matter, but honestly. If the posting asks for "data visualization" and you built charts in a class project, the phrase "data visualization" belongs on your resume — that's not gaming the system, it's accurate labeling. What doesn't work is a keyword dump disconnected from anything you've done; recruiters spot it instantly, and it undermines the credibility of the real skills around it.

References, portfolios, and proof

"References available upon request" is a wasted line — employers assume references exist and will ask when they want them. Don't spend resume space stating it. Instead, line up two or three references in advance: a professor, a volunteer coordinator, a freelance client, a coach. Ask their permission, tell them what roles you're applying for, and keep their contact details ready to send when requested.

A portfolio link does more work than any reference at the entry level. If your field produces visible work — writing, design, code, data analysis, video, photography — put a link at the top of your resume, right under your contact info. A GitHub profile, a personal site, a Behance page, even a well-organized Google Drive folder of class projects: anything that lets a hiring manager see the work beats a paragraph describing it. Make sure everything at that link is polished and current before you send the resume — it's part of the application now.

LinkedIn deserves a mention too. Even with no work experience, a complete LinkedIn profile — photo, headline describing what you're seeking, education, projects, skills — makes you findable and gives recruiters a second place to confirm what your resume claims. It's not a substitute for the resume, but it's cheap to maintain and occasionally the thing that gets you noticed.

The calm takeaway: your first resume isn't a record of employment — it's a portfolio of evidence. Education with substance, projects with outcomes, honest skills, and real volunteer or informal work, all formatted cleanly on one page and tailored to each role. Everyone's first resume looked like this. What matters is that yours shows a person who does things, finishes them, and can explain what they learned.