Early-career job seekers
How to Build a Resume With No Work Experience
8 min read
If you've never had a job, the standard resume advice — "list your work history" — is useless to you. This guide is for the actual situation: you need a resume today, and the work-experience section is going to be thin or empty. Here's what real hiring managers actually respond to instead.
Start with what you've actually done, not what you haven't
Every resume guide tells you to list work experience. Skip that advice and start from a different question: what have you actually spent time doing? School projects, group assignments, a sport you compete in seriously, an instrument you practice, a Discord community you moderate, a small business idea you tried, caregiving for a family member, volunteering, a class president or club role. These aren't padding — they're real evidence of the same underlying things a job would show: you follow through, you show up, you can work with other people, you can be responsible for something.
Structure that actually works with no jobs to list
Use this order instead of the traditional "Experience first" layout:
- Contact info and a one-line summary of what you're looking for
- Education (school, expected graduation, relevant coursework if it's directly relevant to the role)
- Relevant projects or activities — this replaces "Experience" as your main section
- Skills (be specific: "Excel — pivot tables, VLOOKUP" beats "proficient in Microsoft Office")
- Volunteer work or leadership roles, if any
How to describe a non-job the way you'd describe a job
The skill here is translation. A hiring manager doesn't care that you ran your high school's Instagram account for the debate club — they care what that proves about how you'd behave in the role. Use the same format you'd use for a real job: an action verb, what you did, and a concrete result or scale.
- Weak: "Helped organize a fundraiser."
- Strong: "Coordinated a team of 6 volunteers to plan and run a fundraiser that brought in $1,200 for a local shelter, handling logistics and a supply budget."
- Weak: "Group project for marketing class."
- Strong: "Led a 4-person team to design a marketing plan for a local business as a class project, including a competitor analysis and a proposed social media calendar, presented to the class and instructor."
Notice both strong versions include a number. You don't need to inflate anything — just look for the real number that's already there (team size, dollar amount, number of people reached, hours per week) and include it. Numbers are what make a bullet point sound specific instead of generic.
What to leave off
Don't add a "References available on request" line — it's assumed and wastes space. Don't list every single class you've taken — only ones directly relevant to the role. Don't use an objective statement like "Seeking a challenging position where I can grow" — it says nothing about you and nothing about the employer's actual need.
One real thing that helps more than a perfect resume: a portfolio of actual work
If the role is anything creative, technical, or writing-based, a small portfolio of real work you've made — even unpaid, even just for practice — often matters more than the resume itself. A free personal site or a public GitHub/behance/Google Drive folder with 2-3 real examples gives an employer something concrete to look at, which a resume with no work history can't fully provide on its own.
Before you apply
Read the job posting back against your resume and ask: does every bullet point on this resume connect to something this specific job actually needs? If a bullet point doesn't help make the case for this particular role, cut it — a shorter, focused resume beats a longer, generic one.