How to Write a Fresher Resume with No Work Experience

If you're a fresher, the "Work experience" section of your resume is probably empty, and that's normal. Recruiters hiring freshers know this. What they look for instead is evidence that you can do the work: projects, skills you've actually used, internships, and how clearly you present them.

This guide covers what to include, in what order, how to write strong bullet points, and how to format your resume so it can be read by applicant tracking systems (ATS).

Keep it to one page

For a fresher, one page is enough. A focused page with three strong projects beats two pages of filler. If you're struggling to fit everything, that's a sign to cut weaker items, not to shrink the font.

The sections, in order

1. Header: name, phone number, a professional email, city (optional), and links to your LinkedIn and GitHub or portfolio. No photo, date of birth or full address are needed for most private-sector applications.
2. Summary (optional, 2 lines): what you are and what you're looking for. Skip it if it would just repeat the rest of the page.
3. Education: degree, college, graduation year, and your CGPA or percentage if it helps you. Many companies have a cutoff, so include it if you meet common thresholds.
4. Skills: grouped and honest (see below).
5. Projects: the most important section for a fresher. Two to four projects.
6. Internships or training: if you have any, these go above projects.
7. Certifications and achievements: only those relevant to the role. Hackathons, coding contest ranks and a strong final-year project award are worth including.

Writing project bullet points

Each project needs a one-line description and two or three bullet points. A simple formula for each bullet:

Compare these two versions of the same project:

The strong version tells the interviewer exactly what you did, which also gives them good questions to ask you, questions you'll be ready for.

Only include numbers that are true. "Handled 200+ test records" is fine if you did. Invented numbers are easy to expose in a single follow-up question.

The skills section

Group your skills so they're easy to scan:

• Languages: JavaScript, Python, SQL
• Frameworks and libraries: React, Node.js, Express
• Tools: Git, VS Code, Postman

List only what you can answer basic interview questions on. A good test: if an interviewer asked you to write a few lines in that language or explain one core concept, could you? If not, leave it off. Skip skill "progress bars" and star ratings; they don't mean anything to a reader.

Make it ATS-friendly

Many companies use an applicant tracking system to collect and search resumes. These systems extract the text from your file, so the safest formatting is simple:

• Use a single-column layout. Two-column templates can be read in the wrong order.
• Use standard section headings: "Education", "Skills", "Projects", "Experience".
• Save as a text-based PDF (exported from Word, Google Docs or a similar editor), not a scanned image.
• Don't put important text inside images, icons, text boxes or the page header area.
• Use the same words as the job description where they honestly describe you. If the posting says "REST APIs" and you built REST APIs, write "REST APIs".
• Use a common font such as Arial, Calibri or Times New Roman at 10 to 12 pt.

A quick check: open your PDF, select all the text and paste it into a plain text editor. If the text comes out in a sensible order, an ATS can most likely read it too.

Common mistakes

• An objective that says nothing. "Seeking a challenging position in a reputed organisation" fits every candidate. Write something specific or leave it out.
• Listing school-level details at length. Class 10 and 12 marks can be one line each (some companies ask for them); hobbies and "strengths" lists can usually go.
• Spelling and grammar errors. Read it out loud, and ask a friend to check it.
• An unprofessional email address. Use a simple firstname.lastname style address.
• Broken links. Open every link on your resume before sending it. Make sure your GitHub projects have a short README.
• One resume for every job. Reorder your skills and projects to match each role you apply for; it takes ten minutes.

A final checklist

• One page, single column, text-based PDF
• Name, phone, email, LinkedIn and GitHub links that work
• Two to four projects with action-verb bullet points
• Skills you can actually answer questions on
• No spelling mistakes; file named like Firstname-Lastname-Resume.pdf

Next step: your LinkedIn profile

Recruiters often look at your LinkedIn profile after your resume, so keep the two consistent: the same projects, the same dates, and a headline that says what you do, such as "Computer Science graduate | React and Node.js | Looking for frontend roles". Our Fresher Resume & LinkedIn Guide includes resume templates and a LinkedIn checklist if you'd like a ready-made starting point.