Entry level · 4 min read

How to write a resume with no experience (for graduates and first-time job seekers)

Updated October 2026 · By the ClaudeCV Editorial Team

Every working person started with an empty resume. If you are a recent graduate or applying for your first job, the blank space where "work experience" would normally go can feel scary. The good news is that employers hiring for entry-level roles do not expect a long job history. They look for evidence that you can learn, deliver and work with others. Here is how to show that on paper.

Start with the right structure

For someone with little or no work experience, put the strongest material first. A good order is:

1. Contact details and a short summary
2. Education
3. Projects
4. Internships, volunteering or part-time work
5. Skills
6. Certifications or activities, only if relevant

This order pushes your education and projects to the top, where a recruiter will actually see them, rather than leaving an awkward empty "Experience" section.

Write a focused summary

A summary is two or three lines at the top that tell the reader who you are and what you want. Avoid empty phrases like "hard-working team player seeking a challenging role". Instead, say what you studied, one or two concrete strengths, and the kind of role you want.

For example: "Computer science graduate with hands-on experience building web applications in JavaScript and Python. Looking for a junior developer role where I can contribute to product features and keep learning."

Make education work harder

List your degree, institution and graduation date. Add your grade point average or classification if it is strong. Then add information that shows relevant knowledge: key coursework, a final-year dissertation, a capstone project, academic awards or scholarships. If the course was closely related to the job, name three or four modules that match the job description.

Turn projects into experience

Projects are often the most important section on an entry-level resume. A project can be academic, personal, a hackathon entry or freelance work. Describe each one the way you would describe a job: what you built, what tools you used, and what happened as a result.

Compare these two lines:

"Worked on a group project about data analysis."
"Analyzed 12,000 customer survey responses in Excel and Python, identified three main complaint themes, and presented recommendations that the class voted best of 30 teams."

The second one gives scale, tools and an outcome. You do not need a job to write like that.

Count everything that shows responsibility

Part-time work, volunteering, student clubs, sports teams and family responsibilities all show useful traits. A weekend job in a shop shows reliability, communication and handling customers. Running a society event shows planning, budgeting and teamwork. Do not apologize for these roles; describe what you did and what you achieved.

Choose skills carefully

List specific, checkable skills rather than vague claims. "Good communication" tells the reader nothing, while "Presented weekly project updates to a team of eight" shows it. Group technical skills by type, such as programming languages, software tools and languages you speak, and keep the list honest. If you would be uncomfortable being tested on a skill in an interview, leave it out.

Keep it to one page

A one-page resume is the standard for entry-level candidates. If you are struggling to fit everything, cut older or weaker items: school achievements from many years ago, generic hobbies and duplicated points. Use a clean, single-column layout with readable fonts, since many employers use software that scans resumes before a human sees them.

Tailor it for each application

Read the job description and note the skills and phrases it repeats. If you truly have those skills, use the same wording in your summary, projects and skills sections. Tailoring takes ten minutes and often makes the difference between being noticed and being ignored.

What to leave out

A photo, date of birth or marital status, unless the country's norms expect them
Salary expectations
"References available on request", which is assumed
Spelling mistakes, which are especially damaging when you have little else to judge

If you have no projects yet

Make one. Choose something small in your field and finish it within two weeks: a simple website, a data analysis on a public dataset, a marketing plan for a local business, a lesson plan or a design portfolio. A finished small project is better than an empty page, and it gives you something real to talk about in interviews.

Before and after: turning a thin resume into a stronger one

Here is an illustrative example of how a small change in wording shifts the impression. Imagine a business graduate named Omar with only a summer café job, a class project and a student society role.

Before:

Worked at a café during summers
Member of the entrepreneurship society
Completed a marketing project in class

After:

Served 150+ customers per shift at a busy café, handled cash and card payments accurately and trained two new colleagues during peak season
Organized a networking evening for 60 students as events officer of the entrepreneurship society, coordinating four speakers and a budget of about 400 dollars
Built a marketing plan for a local bakery in a team of four, proposing a loyalty card and social media schedule that the owner chose to test

Omar did not gain any new experience. He simply described what he did, how big it was and what happened. The numbers can be approximate, but they must be honest and something you could explain if asked.

A one-week plan to finish your first resume

Day 1: collect everything: courses, projects, jobs, clubs, volunteering, awards, tools.
Day 2: pick three target job posts and mark repeated requirements.
Day 3: draft your summary and education section.
Day 4: write project and experience bullets using action, scale and result.
Day 5: build the skills section and cut anything you cannot discuss.
Day 6: format to one page, proofread aloud and check the file opens correctly as a PDF.
Day 7: ask one person to review it, then apply to your first five roles.

Frequently asked questions

Should I include high school? Only if you have no university education or a very strong achievement. Otherwise leave it out.

How do I handle a low grade? List it plainly if the employer asks for it, or leave it off if not required, and let projects and skills lead.

Is it okay to use a template? Yes, as long as it is clean and single-column, and you replace all placeholder text.

Final thoughts

An entry-level resume is not about hiding what you lack. It is about presenting what you have in a way that matches what the employer needs. Lead with education and projects, describe results, keep it concise and proofread it twice. Then apply widely, and treat every response as feedback to improve the next version.