Resume guide
How to write an entry-level resume with no experience
How to write a resume when you have little or no work history: what fills the space instead, why the objective statement hurts you, and how far the projects section can carry a page.
"No experience" is almost never true. It usually means no experience with a job title attached, which is a different and much smaller problem. Coursework, part-time work, volunteering, a club you ran, something you built for yourself: all of it is experience, and most of it belongs on the page.
What you're really working against is a blank-looking page. A first resume has fewer things to say, so every line carries more weight and the usual advice about trimming matters less than the advice about what to include in the first place.
Delete the objective statement
"Seeking a challenging position where I can utilize my skills and grow professionally." Some version of that sits at the top of most first resumes, and it's the least useful thing on the page. It says nothing specific, it's about what you want rather than what you offer, and every other applicant wrote one too.
If you use that space at all, write a summary instead: two or three lines naming what you've studied or built and what you're aiming at. "Final-year computer science student, two shipped side projects in Python, looking for a backend internship" tells a reader more than four lines of ambition ever will.
Projects are the section that does the work
For a first resume this is the strongest section available, and it's the one most people undersell. A project is evidence you can do something, produced without anyone requiring you to. That's close to the thing employers are actually trying to establish.
Write projects the way you'd write a job. What it was, what you used, what it does now, and if there's a number attached, use it. "Built a scheduling tool for my university club, used by about 60 members across two semesters" beats a bare technology list, because it shows something reaching real people.
This applies well outside software. A marketing student who ran a real campaign for a local business, a design student with a rebrand nobody assigned them, a finance student who managed a genuine portfolio: all projects, all evidence.
- Two or three real projects beat a long list of shallow ones.
- Say what you used, not just what it was.
- Add a number if one honestly exists. Don't manufacture one.
- Link to it when there's something to see.
Non-relevant jobs still count, if you write them right
Retail, hospitality, and warehouse work belong on an entry-level resume, and the instinct to hide them is wrong. They demonstrate reliability, which is the actual risk an employer is taking on a first hire.
Write them for what they show rather than what they were. "Trained four new starters and covered close alone on weekends" says responsibility and trust. "Handled customer complaints at a busy counter" says composure. Neither pretends the job was something else, and both answer a question the reader has.
Education sits higher, for now
This is the one stage where education goes above experience, because it's your strongest evidence. Include relevant coursework if it maps to the job, along with any capstone or thesis work, which often reads as a substantial project in its own right.
It moves back down once you have a year or two of real work. Until then it's earning its place at the top.
The GPA question depends on your field, and most advice ignores that
The usual rule is to include your GPA if it's strong and omit it otherwise, which is fine as far as it goes. What it misses is that fields differ sharply. Consulting, investment banking, and some graduate schemes screen on it explicitly, and leaving it off reads as an answer. Most software, design, and marketing roles barely look, and a portfolio outweighs it.
Find out which kind of field you're entering before deciding. It's a five-minute question to ask anyone one year ahead of you, and it's more reliable than a general rule written for everyone.
One page, and let it breathe
One page, without question, at this stage. But padding a thin resume to fill it is worse than leaving space. Inflated line spacing, a list of soft skills nobody verifies, and a language section claiming conversational Spanish from high school all read as filler, and readers notice.
If the page looks empty, the fix is another real project, not another paragraph about being a team player.
Quick steps
- 1Cut the objective
Replace it with a two-line summary naming what you have studied or built and the kind of role you want, or leave the space out entirely.
- 2Lead with education
Put it above experience while it is your strongest evidence, with relevant coursework and any capstone or thesis project.
- 3Build out the projects section
Two or three real projects, each written like a job: what it was, what you used, what it does, and any honest number.
- 4Keep the unrelated jobs
Write retail or hospitality work for what it demonstrates. Training people and being trusted to close are both worth saying.
- 5Decide the GPA question by field
Some fields screen on it and some ignore it. Ask someone a year ahead of you rather than following a general rule.
- 6Fit one page without padding
Leave white space rather than filling it. If it looks thin, add a real project instead of another line about teamwork.
Frequently asked questions
- What do I put on a resume with no work experience?
- Education first, then projects, then any work at all including unrelated jobs, then skills. Coursework, volunteering, clubs you ran, and things you built for yourself are all legitimate content. The section order changes at this stage; the sections themselves do not.
- Should I include an objective statement?
- No. It's the weakest line on most first resumes: vague, focused on what you want, and identical to everyone else's. A short summary naming what you have done and what you are aiming at does the same job usefully.
- Do part-time and retail jobs belong on my resume?
- Yes. They show reliability, which is the main risk on a first hire. Write them for what they demonstrate rather than the tasks: training new starters, being trusted to close, handling difficult customers.
- Should I put my GPA on my resume?
- It depends on your field more than on the number. Consulting, banking, and many graduate schemes screen on it, so omitting it is itself an answer. Most software, design, and marketing roles barely look. Ask someone a year ahead of you in your specific field.
- How long should an entry-level resume be?
- One page. But do not pad to fill it. Stretched spacing, unverifiable soft skills, and a thin languages section are obvious, and empty space reads better than filler.
- Are personal projects worth including?
- They are often the strongest section on a first resume, because they prove you can do something without being told to. Write them like jobs, with what you used and what the result was, and link to anything there is to see.