How to Write a Resume With No Work Experience

"Entry-level position, 2 years of experience required" is a running joke for a reason, and staring at a blank resume with no jobs to list makes it feel personal. Here's the reframe that changes everything: you don't have no experience, you have no job titles. Those are different problems, and the second one is very solvable.

What actually counts as experience

Employers hiring for entry-level roles are not expecting a work history. They're looking for evidence that you can learn, deliver, and work with other people. That evidence can come from almost anywhere:

• Projects. A capstone project, a personal website, an app you built, a research paper, a marketing plan you wrote for a class. If you produced something real, it counts, and if it's viewable online, link it.
• Coursework. Not the course list itself, but substantial work inside courses: a semester-long group project, a lab you led, a dataset you analyzed. "Relevant coursework" as a bare list of class names is weak; a project pulled out of a course and described like work is strong.
• Volunteering. Organizing a fundraiser, managing a nonprofit's social media, tutoring, staffing events. Unpaid work is still work, and it often comes with more responsibility than a first paid job would.
• Part-time and seasonal jobs. Retail, food service, babysitting, lifeguarding, a family business. Don't hide these. They prove reliability, customer handling, and working under pressure, which are exactly the things entry-level managers worry about.
• Clubs and student organizations. Treasurer of anything means you handled money and reporting. Organizing a 200-person event means logistics, vendors, and deadlines. Captain of a team means leadership. Describe the work, not the title.
• Freelance and informal work. Built a website for your uncle's shop, edited videos for a friend's channel, ran ads for a local business. Real clients, real deliverables.

The test for whether something belongs on your resume: did you do work that produced a result someone else could see? If yes, it's a candidate.

Structure for a first resume

Keep it to one page, no exceptions at this stage. A clean order that works when you have no job history:

1. Header — name, city (not full address), phone, email, LinkedIn, and a portfolio/GitHub link if you have one. Use a plain email address.
2. Summary (optional, 2 lines max) — only if it says something concrete: "Computer science graduate with three shipped web projects, seeking a junior frontend role." Skip it if it would just be adjectives.
3. Education — near the top, because right now it's one of your strongest sections. Degree, school, graduation date. Include GPA if it's 3.5 or higher. Add honors, scholarships, or a thesis title if relevant.
4. Projects — for most people with no work history, this is the section that gets you the interview. Treat each project like a job entry: name, a one-line description, and 2-3 achievement bullets.
5. Experience — everything from the list above: part-time work, volunteering, club roles. Give it an honest heading like "Experience" (not "Work Experience" if some of it was unpaid) and format it exactly like a normal job section: role, organization, dates, bullets.
6. Skills — tools, languages, software, spoken languages. Short and honest (more below).

Formatting: single column, standard font, no photo (in the US/UK/Canada), no graphics or skill bars. Applicant tracking systems and tired recruiters both prefer boring layouts that read cleanly.

Writing achievement bullets without job titles

The formula that works for seasoned professionals works for you too: action verb + what you did + outcome or scale. The raw material is different; the structure isn't.

Weak bullets describe duties or membership:

• "Member of the marketing club"
• "Responsible for social media"
• "Worked on a group project about databases"

Strong bullets describe actions and outcomes:

• "Organized the club's annual employer networking night; recruited 12 companies and drew 150+ student attendees, the largest turnout in the club's history"
• "Grew the debate society's Instagram from 300 to 1,400 followers in one semester by switching to short-form video recaps of tournaments"
• "Built a course-planning web app in React and PostgreSQL as a 3-person capstone team; owned the scheduling algorithm and the database design, used by 40 students in a pilot"

Notice what those do: a verb up front, your specific contribution named, and a number wherever one honestly exists. Numbers don't need to be impressive, they need to be real. "Tutored 6 students weekly" beats "tutored students." "Handled cash register and closing duties for a store with ~200 daily customers" beats "cashier duties."

If a bullet genuinely has no measurable outcome, anchor it with scope instead: team size, budget, frequency, duration, audience.

One more upgrade: write bullets in the language of the job posting. If the posting says "data analysis" and your project bullet says "looked at survey results," change it to "analyzed 300 survey responses in Excel and presented findings to faculty." Same truth, better match.

The skills section: useful, short, honest

The skills section is where entry-level resumes most often go wrong, in both directions.

Do list:

• Hard skills you could use tomorrow if asked: Excel, Python, Figma, Canva, WordPress, SQL, Google Analytics, a CRM you've touched
• Spoken languages with an honest level
• Certifications, even small ones (Google Analytics cert, food-safety card, first aid)

Don't list:

• Soft skills as words. "Team player, hard-working, detail-oriented" convinces no one; your bullets should show these.
• Tools you opened once. If you list SQL, expect a SQL question in the interview. The fastest way to blow an interview is a skills section you can't back up.
• "Microsoft Word" and similar baseline items, unless the posting explicitly asks.

Honesty here isn't just ethics, it's strategy. A short list of skills you can demonstrate on the spot is worth more than a long list that collapses under one follow-up question.

A worked example outline

Here's the skeleton of a real-shaped first resume, for a graduate applying to junior marketing roles:

> Amara Osei > Manchester, UK · amara.osei@email.com · 07XXX XXXXXX · linkedin.com/in/amaraosei > > Education > BA Business Management, University of Manchester — expected June 2026 > Dissertation: "Short-form video and purchase intent in Gen Z consumers" · 2:1 average > > Projects > Social media relaunch — Withington Food Bank (volunteer) · Jan-May 2026 > - Rebuilt the charity's Instagram presence with a weekly content calendar; grew followers from 220 to 900 and drove a 30% rise in volunteer sign-up form submissions > - Interviewed 8 volunteers and donors to build three recurring story formats > > Course project: go-to-market plan for a student fintech app · Autumn 2025 > - Led a 4-person team producing a launch plan (pricing, channels, 12-week calendar); graded top 3 of 22 teams and presented to a panel including two industry guests > > Experience > Barista, Caffè Nero · Jun 2024 - present > - Serve 150+ customers per shift and train new starters on till and closing procedures > - Chosen by manager to run weekend shift handovers for a team of 4 > > Events officer, Marketing Society · Sep 2024 - Jun 2025 > - Organized 6 speaker events (30-120 attendees); negotiated free venue space, saving the society roughly £400 per year > > Skills > Canva, CapCut, Meta Business Suite, Google Analytics (certified), Excel, French (conversational)

Nothing in that outline requires a job title, and all of it is checkable, specific, and relevant. That's the bar.

What to skip

Cutting the right things matters as much as adding the right things:

• The objective statement. "Seeking a challenging position where I can grow and contribute to a dynamic team" tells the reader nothing and costs your best real estate. Either write a concrete two-line summary or start straight at Education.
• "References available upon request." Universally assumed. Delete the line.
• High school details once you're in or past university, unless a specific achievement is genuinely notable.
• Every club you ever joined. Two or three entries with real bullets beat eight entries with none.
• Hobbies filler. "Reading, travel, music" adds nothing. A hobby earns its place only if it's substantial or relevant: "run a 5,000-subscriber cooking channel" yes, "cooking" no.
• Padding to fill the page. White space is fine. A three-quarter-page resume of real content beats a full page of fluff, and experienced readers can tell the difference in seconds.

One resume is not enough

Here's the part most first-time applicants miss: the resume you just built is the base, not the final product. Every posting weights things differently, and your projects section especially should reorder and reword to match each role. Doing that by hand for dozens of applications is the grind that makes people give up and mass-send one generic PDF. This is exactly the part Qlivik automates: it matches you to roles that fit what you actually have and tailors your resume to each posting, so every application leads with your most relevant evidence.

You have more experience than you think. The job now is to write it down like it matters, because it does.