Getting everything ready for you…

Loading courses, problems and your progress. This takes just a moment.

0s

Guides › Career

Fresher Software Engineer Resume: What to Write (and What to Cut)

A one-page resume that gets shortlisted — section order, how to describe projects with impact, the skills section, and the mistakes recruiters reject on sight.

A recruiter spends well under a minute on a fresher resume before deciding whether to read it properly. Your job is to make the important things — skills, projects and proof — visible in that time. Here is how.

The rules that matter most

  1. One page. As a fresher, nothing justifies two.
  2. A simple single-column layout. Many companies run resumes through an applicant tracking system (ATS) that struggles with tables, columns, icons and text inside images.
  3. Readable fonts (Calibri, Arial, Inter, Garamond) at 10–11 pt, with clear section headings.
  4. Save as PDF and name it properly: Firstname_Lastname_Resume.pdf.
  5. No photo, date of birth, father's name or full address unless the company explicitly asks. City and state is enough.

Section order for freshers

  1. Header — name, phone, professional email, city, LinkedIn, GitHub and portfolio links.
  2. Education — degree, college, year, CGPA (and 12th/10th percentages, which Indian campus drives often check).
  3. Skills
  4. Projects — your most important section.
  5. Experience / internships — move this above projects if you have a real internship.
  6. Achievements — contest ranks, hackathons, certifications, coding profiles.

Skip the "Objective" section. A one-line summary at the top is optional and only useful if it is specific.

Writing project points that get noticed

Most fresher resumes describe projects like this:

❌ Made an e-commerce website using MERN stack.

That says nothing about you. Use the formula action verb + what you built + how + result:

✅ Built a MERN e-commerce app with JWT login, cart and Razorpay test payments; deployed on Render and Vercel.

✅ Cut product-search time from ~2 s to under 200 ms by adding MongoDB text indexes and paginating results.

✅ Wrote 40+ API tests with Jest, catching 6 bugs before deployment.

For each project, include:

Only list projects you can explain in depth. Interviewers will ask about every line.

The skills section

Group skills so they can be scanned in seconds:

Languages:   Java, Python, JavaScript, SQL
Web:         React, Node.js, Express, HTML, CSS
Databases:   MySQL, MongoDB
Tools:       Git, GitHub, Postman, VS Code, Linux
Concepts:    Data Structures & Algorithms, OOP, DBMS, Operating Systems

Do not add skill bars or ratings ("Java ★★★★☆") — they mean nothing to a recruiter. And don't list something you used once in a tutorial; "Kubernetes" on a resume invites a Kubernetes question.

Achievements worth listing

Common mistakes recruiters reject on sight

Tailor it for each company

Keep one master resume, then adjust the order of skills and projects for each role. Applying for a frontend role? Put your React project first. Data analyst? Lead with SQL and Python and a dashboard project. Read the job description and make sure the words it uses appear where they honestly apply to you.

Next steps

Not sure your projects are strong enough? See which projects to build for each role — every one has a step-by-step guide on Projects. Then make sure the links on your resume lead somewhere good: a clean GitHub profile and a complete LinkedIn profile. A verifiable roadmap certificate is also worth listing.

With your resume ready, prepare for what comes after the shortlist: 12 DSA patterns for interviews, the Top 50 questions for Java, OOP, DBMS, OS and SQL, and 20 HR interview questions.

More guides