"No experience" almost never means no evidence. It means your evidence isn't arranged in the shape a resume expects — a list of employers with dated bullets underneath. Rearranging what you already have is most of the work.
Start by counting what you actually have
Before writing anything, inventory these. Most people find four or five items they'd dismissed:
- Coursework with output — a capstone, a thesis, a term project that produced something
- Personal or open-source projects — anything deployed, published, or used by someone else
- Unrelated jobs — retail, hospitality, warehouse, tutoring, campus work
- Volunteering and societies — especially anything where you held a role with responsibility
- Freelance or informal work — a website you built for a family friend counts, if you'd defend it
- Certifications and structured learning — completed, not in progress
That list is your resume. What's left is arranging it so a reader can see the scope.
Unrelated jobs count more than you think
The most common mistake on a first resume is omitting the café job because "it's not relevant". It's relevant — not for the coffee, but because it's the only verifiable evidence you have that someone paid you and you showed up.
The trick is writing it for transferable scope rather than duties:
Written as duties
“Worked as a barista. Responsible for taking orders and making drinks.”
True, and indistinguishable from every other applicant who ever worked in a café.
Written as scope and outcomes
“Served 200+ customers per shift in a 6-person team; trained 3 new staff on POS and opening procedures.”
Volume, teamwork, and the fact that you were trusted to train people.
Training someone, handling a rush, closing a till, resolving a complaint, covering a rota — these are all evidence of reliability and judgment, which is most of what anyone is screening a junior candidate for.
Projects are your strongest asset
For technical and creative fields especially, a projects section outperforms everything else you can write, because it's direct evidence rather than a claim. It only works if the project is real.
Counts as evidence
- Something deployed, published, or used by someone other than you
- A link a reviewer can open in ten seconds
- Scope stated plainly — data size, users, duration, team
- Your specific contribution named, if it was a group project
Reads as padding
- A tutorial you followed, presented as original work
- Six near-identical course exercises listed separately
- 'Familiar with' technology lists dressed up as projects
- Anything you couldn't walk through line by line in an interview
One substantial project beats six small ones. If you only have coursework, pick the one with the most real output and give it three bullets — scope, what you built, what happened.
The structure for a first resume
- 1
Summary — three lines naming the field you're entering
Substitute education and project scope for years. Nobody expects duration.
- 2
Education — near the top while it's your strongest credential
Degree, institution, graduation year, plus relevant coursework if it maps to the posting.
- 3
Projects — with links and real scope
Above work experience when your work history is unrelated.
- 4
Experience — every paid job, written for transferable scope
Yes, including the unrelated ones. Real dates, real titles.
- 5
Skills — only what you can defend
In the posting's vocabulary. A short honest list beats a long aspirational one.
Education moves below experience once you have two or three years of relevant work — but not before.
What to leave off
High school, once you have anything after it. Your GPA if it's unremarkable, and in most fields at all after your first year of work. "References available on request" — assumed. An objective statement asking for growth opportunities; see summary vs objective. Skills you've heard of but never used, which is the fastest way to fail an interview you worked hard to get.
Applying when you don't meet the requirements
You won't meet them, and that's expected. Postings routinely list more than any junior candidate has, and the "2+ years required" on an entry-level role is frequently aspirational.
Apply anyway, with two conditions: your resume covers what you can prove in the posting's vocabulary, and you're not claiming the parts you can't. The gap list existing isn't a reason to disqualify yourself — but neither is it a reason to fill the gaps with things that aren't true.
The one exception is hard gates: licences, clearances, statutory qualifications. Those aren't preferences, and no application gets past them.
Check it against a real posting
Score your first resume against an actual entry-level posting rather than guessing. The free checker shows which of the posting's requirements you're covering and which you're missing — and for a first resume, the gap list doubles as a study plan for the next three months.
Frequently asked questions
- What do I put on a resume with no work experience?
- Coursework with real output, personal or open-source projects, unrelated paid jobs, volunteering, freelance work and completed certifications. "No experience" almost always means evidence that isn't yet arranged as employers with dated bullets underneath.
- Should I include unrelated jobs like retail or hospitality?
- Yes. They're verifiable proof that someone paid you and you showed up. Write them for transferable scope rather than duties — customers served per shift, team size, people you trained — which is most of what anyone screens a junior candidate for.
Written by
MeritSlate Team
The team building MeritSlate's deterministic scoring engine — nine evidence-anchored axes, a nine-vendor ATS parse simulation, and every point backed by receipts.