The advice freshers get is contradictory. Keep it to one page, but fill the page. Do not lie, but make it sound impressive. List your skills, but only ones you really have. What is missing is a structure — a decision about what goes on the page and in what order when you have not had a job yet.
Here is that structure. It works because it stops trying to imitate an experienced person's resume and instead presents what you actually have in the order a recruiter for entry-level roles reads it.
The order that works when you have no job history
Education goes above projects only until you have something genuinely strong to show. Once you have two solid projects, move them up — a recruiter for a technical role will read a good project before they read your CGPA.
- Contact — name, phone with country code, professional email, city, LinkedIn, GitHub or portfolio if relevant
- Professional summary — three lines: your degree, your specialism, and the one thing you have built or done that is most relevant
- Education — degree, institution, graduation year, and CGPA or percentage if it is 7.5/10, 75% or above
- Technical skills — grouped, specific, and honest about level
- Projects — the most important section on a fresher resume, treated with the same rigour as work experience
- Internships and training — real roles with real dates, described by what you did rather than what you observed
- Certifications and coursework — only substantive ones
- Achievements and activities — competitions, leadership positions, publications
How to write a project so it counts as experience
A project bullet fails when it describes a tutorial. It succeeds when it describes a decision. The difference is not the size of the project — it is whether you can say what problem it solved, what you chose to build, and what happened.
Three well-documented projects beat eight tutorial clones. If a project has no README and no commits beyond the initial push, it is working against you.
- Name the project and state what it does in one line
- Name your actual contribution if it was a team project — 'built the authentication and payments modules' not 'worked on an e-commerce site'
- Name the stack, specifically
- Give a number: users, records processed, accuracy achieved, load time, dataset size, marks awarded, competition rank
- Link to it — a live URL, a GitHub repository with a real README, a published notebook
What to do about the experience section
Include internships as real experience, with proper titles and dates, and describe them by what you produced. Include part-time work, family business work, freelance gigs and paid tutoring — all of it is employment, all of it demonstrates reliability, and freshers routinely omit it out of embarrassment.
If you genuinely have nothing, do not create an empty Experience section. An absent section is neutral; an empty one is conspicuous.
Honest about skills
The most damaging thing on a fresher resume is a skills section listing fifteen technologies you touched once. It survives the ATS and then collapses in the first technical screen, and the interviewer remembers.
Split your skills by real level: what you can build with unaided, what you have used in a project, and what you have studied. Being explicit reads as maturity, not as weakness.
One page, no exceptions
A fresher resume that runs to two pages tells the reader you cannot prioritise. Everything above fits on one page comfortably at 10.5pt with sensible margins. If it does not, you are including things that do not earn their place — school marks, hobbies without substance, every certificate you have ever received.
Frequently asked questions
- What should a fresher put in the experience section?
- Internships, part-time work, freelance projects, family business work, teaching or tutoring, and substantial volunteer roles — all with real titles and dates. If there is genuinely nothing, omit the section rather than leaving it empty.
- Should I include my CGPA or percentage?
- Include it if it is roughly 7.5/10, 75% or above, or if the employer asks for it — many campus and graduate schemes do. Otherwise leave it out; it is not required.
- How many projects should I list?
- Three to four, described properly. Depth beats count, and unfinished tutorial projects actively hurt.
- Should a fresher write a career objective?
- Write a professional summary instead. 'Seeking a challenging role in a reputed organisation' says nothing. Three lines naming your degree, your specialism and your strongest project say a great deal.
- Is a one-page fresher resume enough?
- It is not just enough, it is expected. Recruiters screening graduate applications spend well under a minute per resume; a second page will not be read.
- Should I put a photo on my fresher resume?
- Not for the UK, US, Canada or Australia. In India it is still occasionally seen but is no longer expected and is not an advantage — the space is better used for a project.