How to Write a Fresher Resume With No Work Experience

What recruiters look for in a fresher

When a company hires graduates, whether through campus placements in India, a graduate scheme in the UK, or new-grad roles anywhere else, the people screening resumes know every candidate is inexperienced. What separates applicants is not experience but evidence of potential. In practice that means:

• Relevant skills, shown through something you built or did, not just listed.
• Academic foundation: the right degree, and grades that clear any eligibility cut-off.
• Initiative: projects you started yourself, internships you went after, things you organised.
• Follow-through: work you finished and can explain, rather than ten courses you started.
• Communication: a clean, error-free, well-organised resume is itself evidence of this.

Everything on the page should feed one of those signals. If a line does not, it can probably go.

The right order of sections

Experienced candidates lead with work history. Freshers should lead with whatever is strongest, which usually means education and projects. A reliable order for most freshers is:

1. Name and contact details: phone, professional email, city, LinkedIn, and GitHub or portfolio link if relevant.
2. Summary or objective: two or three lines saying what you studied, your strongest relevant experience, and the role you want.
3. Education: degree, college, years, CGPA or percentage, and Class 12 and 10 results if the employer asks for them (common in Indian campus placements).
4. Internships, if you have any. If you have done a substantial internship, it can go above education.
5. Projects: academic, personal, or hackathon projects with real detail.
6. Skills: technical skills grouped by type, plus languages.
7. Certifications: only ones that are relevant and that you completed.
8. Achievements and extracurricular activities: competitions, leadership roles, volunteering, sports at a serious level.

Education: CGPA, percentages and coursework

For a fresher, education is close to the top and should be precise. List your most recent qualification first. For each one, include the degree and branch, institution, city, start and end years (or expected end year), and your result.

• Write the grade the way your institution reports it: “CGPA 8.1/10” or “72%”. Do not convert between scales unless the employer asks; if they do, use your university’s official conversion formula.
• Many Indian companies set eligibility cut-offs on Class 10, Class 12 and graduation scores, so campus resumes usually show all three. For off-campus or international applications, school results are usually unnecessary unless asked for.
• If your CGPA is low, you can leave it off for off-campus applications, but expect the question in interviews and have an honest answer. Don’t leave it off when the form explicitly asks.
• Add a line of relevant coursework only if it is relevant to the role and not obvious from the degree. “Relevant coursework: Data Structures, DBMS, Operating Systems, Computer Networks” helps a CS student applying to a non-tech company’s IT team; it adds nothing to a software role.
• Mention a final-year thesis or major project by title if it relates to the job, and describe it fully in the projects section.

Projects: your substitute for work experience

Projects are where most fresher resumes win or lose. A project section that says “Library Management System — Java, MySQL” tells the recruiter you completed a standard assignment like everyone else in your batch. A project section that explains what you built, the decisions you made, and what happened when people used it tells them you can do the job.

For each project, give a title, the tools used, a link if one exists, and two to four bullets covering: what problem it solved, what you personally did (especially in a team project), any technical decision worth noting, and the outcome, such as users, accuracy, speed, a grade, or a prize.

• Two or three well-described projects beat six one-liners.
• For team projects, say what you did: “Built the payment flow” rather than “We built an app”.
• Non-technical students have projects too: a market research study, a case competition, a business plan, a field survey, a design portfolio, a published article.
• Make sure every GitHub or portfolio link works and that the repository has a readable README. Interviewers do click them.

Internships, training and part-time work

Treat an internship exactly like a job: company, your title, location, dates, and bullet points that start with action verbs and describe what you did and what it led to. A two-month internship where you shipped one feature or produced one useful report is worth more on paper than a vague six-month one.

Part-time and unrelated jobs also count. Tutoring, retail, delivery work or helping in a family business shows reliability, customer handling, and time management. Keep these to one or two bullets that draw out a transferable skill. Industrial training and in-plant training that are part of your degree can be listed here too, as long as you describe what you actually did rather than just the company’s name.

Skills, certifications and extracurriculars

Skills should be specific and honest. Group them (Languages, Frameworks, Tools, Domain) instead of one long list, and only include skills you could be questioned on. Writing “Python, Java, C++, JavaScript, Go, Rust” when you have used two of them seriously invites an interviewer to pick the one you are weakest in.

Avoid self-rating bars and percentages such as “Java — 80%”. They are meaningless to the reader, and they often trip up resume parsers. Soft skills like “teamwork” and “leadership” are better demonstrated in your project and activity bullets than listed.

Certifications help when they are relevant, recognised, and finished. An AWS Cloud Practitioner or a Google Data Analytics certificate tells a recruiter something; a list of fifteen short online course completions does not. Pick the two or three most relevant.

Extracurriculars are evidence of the soft skills you were tempted to list. Being the treasurer of a college club, organising a technical fest, captaining a sports team, or volunteering with an NGO all show responsibility. Give them a line each with a concrete detail: the budget you managed, the number of participants, the result.

A full sample fresher resume

Here is a complete one-page resume for a computer science graduate applying for software developer roles. The details are invented for illustration; replace every line with your own facts.

Notice what is missing: no photo, no date of birth, no father’s name, no declaration at the bottom, no “hobbies: listening to music”. Some employers and countries still expect personal details, so check the norms where you are applying, but for most private-sector applications the version above is what you want.

Common fresher mistakes

• Copying a senior’s or a friend’s resume. Recruiters at campus drives see the same template and the same phrases from a whole batch, and identical resumes blur together.
• A generic objective: “To work in a reputed organisation…” wastes the most valuable lines on the page.
• Going over one page. A fresher rarely has two pages of relevant material; a second page usually means padding.
• Listing every skill you have heard of. You will be asked about them.
• Vague project descriptions with no personal contribution or outcome.
• A declaration (“I hereby declare that the above information is true…”) and signature line. It is a holdover from older formats and takes space; leave it out unless a specific employer asks for it.
• Unprofessional email addresses. Create a simple firstname.lastname style address for job hunting.
• Typos and inconsistent formatting: different date styles, mixed fonts, bullet points that end with and without full stops. For a fresher, polish is part of the evidence.
• Sending a designed, graphics-heavy resume with columns, icons and skill bars to a portal that parses text. Keep the layout clean and readable by software.

Frequently asked questions