Software Engineer Fresher Resume Format
A software engineer fresher resume should be one page: education, internship, projects, skills, achievements. Projects carry most of the weight, so give them the most space. Below is a full sample and what to put in each section.
The layout: Jake's Resume
Jake's Resume is the plain single-column layout most tech recruiters already know, so nothing distracts from your projects. It parses cleanly in every ATS and fits a fresher's content on one page at 11 pt.
Sections, in this order
Education
As a fresher your degree is the most recent thing you have done, and campus and off-campus forms filter on CGPA and graduation year first. Add one line of coursework only if it matches the job.
Internship
Even a two-month internship shows you have shipped code in a real codebase with reviews and deadlines. If you have none, drop this section and move projects up.
Projects
This is where you prove you can build. Two or three projects with a live link or GitHub, the stack, and one result each beat six tutorial clones.
Technical Skills
Grouped skills let a recruiter match you to the job in one glance. Keep it to what you could be interviewed on.
Achievements
Coding ratings, hackathon results and club work separate you from classmates with the same degree. Keep each to one line with a number.

Skills to list, grouped
- Languages
- Java, Python, JavaScript, Go, SQL
- Web and backend
- React, Node.js, Express, REST APIs, Flask
- Databases and tools
- PostgreSQL, MongoDB, Git, Docker, Linux, Postman
- Core CS
- Data Structures and Algorithms, OOP, DBMS, Operating Systems
List only what you could answer interview questions on, and match the words the job description uses.
From a weak bullet to a strong one
- Before
- Made a hostel food app using MERN stack.
- After
- Built a meal booking app in React, Express and MongoDB for a 400-student hostel; food wasted per day fell from about 30 kg to 18 kg in the first month.
- Before
- Worked on backend APIs during internship.
- After
- Built REST endpoints in Node.js and PostgreSQL for an invoice module used by 300 small businesses, plus a nightly job that catches about 40 duplicate invoices a week.
Applying in India
- Write CGPA the way your university does (8.4/10). Add Class X and XII percentages only if the company form asks for them or they are strong, since many service company drives still filter on 60% or 70% across all three.
- Many campus drives set a no-active-backlogs rule. Do not hide backlogs on the resume, but you do not need to list cleared ones either.
- Put your GitHub and LeetCode or Codeforces links in the header. Interviewers for SDE roles in India often open them before the call.
- If you are applying off campus, write your city and say "open to relocate" in your Naukri profile, not on the resume.
- Leave out photo, date of birth, father's name, and a "Declaration" line at the bottom. They take space and are not needed for software roles.
Mistakes to avoid
- Listing every language you touched in a first-year lab. If you cannot write a loop in it today, remove it.
- Projects with no link. A recruiter cannot check a project that only lives on your laptop.
- A career objective like "seeking a challenging role in a reputed organisation". It says nothing; cut it.
- Copying the same to-do and weather apps as everyone in your batch, with no change or result of your own.
- Going to two pages. Freshers almost never need more than one.
Start from this format, then fit it to each job
Fill in a simple form or import the resume you have, and Shortlist lays it out in the Jake's Resume template. Paste a job description and the AI suggests changes using only what is in your resume, and you keep the ones you like. Building your resume is free.
Build my software engineer fresher resume