Writing your first resume feels unfair. Every job asks for experience, and you have none to show. The good news is that recruiters hiring freshers know this. They are not looking for a work history. They are looking for evidence that you can learn quickly, finish what you start and communicate clearly. A fresher resume is simply a document that puts that evidence in front of them in under a minute.
This guide walks through each section of a one-page fresher resume in the order a recruiter reads it, with examples of what works and what to cut.
Keep it to one page
A fresher resume should fit on a single A4 page. Recruiters screening campus or entry-level applications often go through hundreds of resumes for one role. A second page full of school-level achievements and a "declaration" line does not help you; it dilutes the parts that matter. If you are struggling to fit everything, that is a sign you need to choose your strongest material, not shrink the font.
1. Contact details at the top
Start with your full name in a slightly larger font, followed by one line of contact information:
- A phone number you actually answer, with the country code if you are applying abroad.
- A professional email address. firstname.lastname at any mail provider is ideal. Avoid nicknames and numbers that look like birth years.
- Your city. A full home address is not needed.
- Links to your LinkedIn profile and, for technical roles, GitHub or a portfolio. Make sure they are clickable in the PDF and that the profiles are up to date.
Leave out your photo, date of birth, gender, marital status, religion and father's name. Most private companies do not need them, and some recruiters see them as a sign of an outdated template. Government job applications have their own forms that ask for these details separately.
2. A short objective or summary (optional)
A summary is only worth including if it says something specific. "Seeking a challenging position in a reputed organisation to utilise my skills" tells the recruiter nothing, and they have read it thousands of times. If you write one, keep it to two lines and name the role, your strongest skills and one proof point:
"Computer Science graduate (2026) focused on backend development with Java and Spring Boot. Built and deployed a REST API for a college event platform used by 1,200 students."
If you cannot write something that specific yet, skip the section. No recruiter rejects a resume for missing a summary.
3. Education
For freshers, education goes near the top because it is your most recent and relevant credential. List your degree, college, university, graduation year and CGPA or percentage. Many Indian employers have cut-offs such as 60% or 6.0 CGPA through 10th, 12th and graduation, so include your 10th and 12th scores in a compact form, one line each.
If your scores are low, do not hide them; recruiters will ask anyway. Instead, make sure your projects and skills sections are strong enough that the scores are not the deciding factor.
4. Skills
List skills in groups so they are easy to scan. For a developer, that might look like:
- Languages: Java, Python, SQL
- Frameworks and tools: Spring Boot, React, Git, Postman
- Concepts: REST APIs, OOP, data structures, relational databases
Only list what you can discuss in an interview. A good rule: if an interviewer asks you to explain or write something basic in that skill, could you do it without notes? If not, leave it out. Listing twelve technologies you touched once makes interviewers suspicious, and they will pick the weakest one to question you on.
Avoid progress bars and star ratings for skills. "Java: 4 out of 5 stars" means nothing to a reader, and applicant tracking systems cannot read the graphics.
5. Projects: the most important section
Projects are where a fresher proves ability. Choose two or three, and for each one write:
- A clear title and the technologies used.
- One line on what problem it solves and for whom.
- Two or three bullets on what you built, with numbers wherever possible.
- A link to the code or a live demo.
Compare these two descriptions of the same project:
Weak: "Library management system using Java and MySQL. Worked on frontend and backend."
Strong: "Library management system (Java, Spring Boot, MySQL). Designed the database schema for 6 tables and built 14 REST endpoints for issuing and returning books. Added overdue fine calculation and email reminders, which the college library used for one semester."
The second version shows design decisions, scale and real use. It also gives the interviewer good questions to ask, which means the interview will be about something you know well.
If your only projects are standard college assignments, consider building one more that solves a problem you personally have: a budget tracker, a timetable generator or a tool for your hostel. Personal projects make for better interview conversations than tutorials copied step by step.
6. Internships and training
Any internship counts, even an unpaid or short one. Write it like a job: company, role, dates and two or three bullets on what you did and what came of it. If you completed industrial training as part of your course, include it here too.
Be careful with "internships" that you paid for. Recruiters can usually tell when a certificate came from a paid training programme rather than real work. It is fine to list the skills you learned, but describe it honestly as training.
7. Certifications, achievements and activities
Keep this section short and relevant. Good candidates for inclusion are:
- Certifications from recognised providers that relate to the role, such as cloud, testing or analytics certifications.
- Hackathon results, coding contest rankings or a published paper.
- Leadership roles: organising a college fest, leading a technical club or running a student initiative. These show responsibility, which matters for any job.
Leave out participation certificates for every webinar you attended. Three meaningful items beat fifteen forgettable ones.
Formatting that passes both humans and software
Many companies run resumes through an applicant tracking system (ATS) before a person sees them. To make sure yours is read correctly:
- Use a simple single-column layout. Two-column designs with sidebars often scramble when parsed.
- Use standard section headings like "Education", "Skills" and "Projects".
- Use a common font such as Calibri, Arial or Georgia at 10 to 12 points.
- Save as a PDF unless the employer asks for Word, and name the file sensibly: Priya-Sharma-Resume.pdf, not resume_final_v3_new.pdf.
For more on what to avoid, read 11 resume mistakes that get you rejected.
Tailor it for each role
You do not need a brand-new resume for every application, but you should adjust it. Read the job description, note the skills and responsibilities it repeats, and make sure the matching items on your resume are easy to find. If a role emphasises SQL and your SQL project is buried at the bottom, move it up. Ten minutes of tailoring per application does more than sending the same resume to a hundred companies.
A final checklist
- Fits on one page, with your strongest projects visible without scrolling.
- No spelling mistakes. Read it aloud, then ask a friend to read it.
- Every skill listed is one you can be questioned on.
- Every project has numbers or a concrete outcome.
- Links work and point to tidy, current profiles.
- Saved as a clearly named PDF.
Once your resume is ready, browse jobs open to freshers. Each listing includes the typical interview rounds and resume tips for that role.