Software Engineer Resume Format: Section Order, Skills, and a Full Example

The software engineer resume format that clears Indian screening rounds is one page, with a Skills section (languages, DSA, frameworks, tools) placed right after Education, followed by 2-4 projects that each name real tools and a measurable result — not a list of tutorials. Service companies like TCS and Infosys screen mainly for CGPA cutoffs, no active backlogs, and basic coding-test scores; product companies and startups screen for DSA depth, project complexity, and GitHub activity. Both want to see a coding profile (LeetCode, Codeforces, or GeeksforGeeks) or a GitHub link somewhere visible, and neither wants a resume padded with every language and framework you've touched once. Below is the exact section order, what to actually put in Skills and Projects, a full worked resume example, and the mistakes specific to software engineer resumes.

What Indian recruiters screen for, and it's not the same for every company

The screening bar and the screening method both change depending on who's hiring.

Recruiter type	What they scan for first	Typical screening method
IT services (TCS, Infosys, Wipro, Cognizant)	CGPA cutoff (usually 60-65%), no active backlogs, basic DSA and aptitude	NQT/AMCAT/CoCubes-style aptitude + coding test, then HR round
Product companies and well-funded startups	DSA depth, project complexity, CS fundamentals, GitHub activity	Take-home assignment or live coding round on HackerRank/Codility, then system-design-lite discussion
Off-campus mass drives via portals	Resume keyword match against the JD, then coding test score	Naukri/LinkedIn application into the company's own ATS, filtered before a human sees it

Reported 2026 CTC bands give a sense of what these tracks actually pay, so you can calibrate which ones are worth optimizing your resume for: TCS NQT runs Ninja (₹3.36-3.6 LPA), Digital (₹7-7.5 LPA), and Prime (up to ₹12.26 LPA) tracks based on cognitive score and interview performance; Infosys's off-campus tracks run Systems Engineer (₹3.6-4.5 LPA), Digital Specialist Engineer (₹6.5-9 LPA), and Power Programmer (₹8-12 LPA). These figures come from candidate-reported offers and 2026 placement-drive coverage rather than official company statements, but they're consistent enough across sources to plan around.

The exact section order for a software engineer resume

1. Header — name, phone, email, city, LinkedIn, GitHub link
2. Resume headline — role + degree + top skills; see our resume headline guide for freshers if you need the formula
3. Education — degree, college, CGPA, year
4. Skills — grouped by category, not a flat list
5. Projects — 2-4, each with tools, what you built, and one measurable outcome
6. Internship (if any) — company, duration, one concrete line on impact
7. Certifications & Coding Profiles — LeetCode/Codeforces rating, relevant certs, hackathon results

Skills section: what to actually list

Group by category so it reads as a competency map, not a keyword dump.

• Languages: pick a primary (Java, Python, or C++) and one secondary — listing six languages you've each used once signals breadth without depth.
• Core CS fundamentals: Data Structures & Algorithms, Object-Oriented Programming, DBMS, Operating Systems, Computer Networks — these are exactly what service-company aptitude rounds and product-company phone screens both test.
• Web/Backend: REST APIs, and one framework — Spring Boot (Java), Django/Flask (Python), or Node.js/Express (JavaScript) — plus a frontend basic like React if you've built anything full-stack.
• Databases: MySQL or PostgreSQL, and MongoDB if you've used a NoSQL store in a project.
• Tools: Git/GitHub, Postman, basic Docker, Linux command line — these come up in almost every technical interview as a quick "have you used this" check.

Projects section: how to describe them so they read as engineering, not tutorials

The single biggest gap between a fresher resume that gets shortlisted and one that doesn't is how projects are written. "Built a machine learning project" and "Built a to-do app" are both instantly forgettable because they could describe a 2-hour YouTube tutorial. Name the tools, the scale, and one number.

Weak version	Rewritten with tools + outcome
Built an e-commerce website	Built a 15-endpoint REST API (Java, Spring Boot, MySQL) for product catalog, cart, and orders with JWT auth; 40+ JUnit tests, deployed on Render
Made a chat app	Built a real-time chat app (Node.js, Socket.io, MongoDB, React) handling 100+ concurrent WebSocket connections in local load tests; added Redis caching, cutting duplicate DB reads by ~40%
Did a machine learning project	Trained a Naive Bayes classifier (Python, scikit-learn) on a 10,000-row labeled news dataset, 87% test accuracy, exposed via a Flask API

Every rewritten version answers three questions in one line: what tools, how big/complex, and what happened when it ran. That's the template — apply it to whatever you've actually built.

Full worked example: a software engineer fresher resume

This is a complete, realistic resume using the format above. Copy the structure, not the specific projects — yours should reflect what you actually built.

Rohan Mehta

Bengaluru, Karnataka | rohan.mehta@email.com | +91-98xxxxxx10 | linkedin.com/in/rohanmehta | github.com/rohanmehta

Software Engineer Fresher | B.Tech CSE 2026 | Java, DSA, Spring Boot, React | 350+ LeetCode Problems Solved

Education

• B.Tech, Computer Science and Engineering — XYZ Institute of Technology, Pune | CGPA: 8.4/10 | 2022-2026
• Class XII (CBSE) — 89% | Class X (CBSE) — 91%

Skills

• Languages: Java, Python, JavaScript
• Core CS: Data Structures & Algorithms, OOP, DBMS, Operating Systems, Computer Networks
• Web/Backend: Spring Boot, REST APIs, Node.js, Express.js, React.js
• Databases: MySQL, MongoDB
• Tools: Git, GitHub, Postman, Docker (basic), Linux

Projects

• E-commerce REST API (Java, Spring Boot, MySQL) — Built a 15-endpoint REST API for product catalog, cart, and order flow with JWT authentication; wrote 40+ unit tests with JUnit achieving 85% code coverage; deployed on Render. (github.com/rohanmehta/ecommerce-api)
• Real-Time Chat Application (Node.js, Socket.io, MongoDB, React) — Built a chat app handling 100+ concurrent WebSocket connections in local load testing; added Redis-based session caching to cut duplicate DB reads by ~40%; deployed frontend on Vercel, backend on Railway. (github.com/rohanmehta/chat-app)
• Fake News Classifier (Python, scikit-learn, Flask) — Trained a Naive Bayes/logistic regression model on a 10,000-row labeled news dataset, reaching 87% test accuracy; exposed predictions through a Flask API with a minimal HTML frontend. (github.com/rohanmehta/fake-news-classifier)

Internship

Software Engineering Intern, [Startup Name], Pune — May 2025 to July 2025. Fixed 12 bugs and shipped 2 minor features in a Django-based internal tool used by 30+ employees; wrote migration scripts that cut a manual data-cleanup task from 3 hours to 10 minutes.

Certifications & Achievements

Solved 350+ problems on LeetCode (top 15% India rank on a recent contest) | Codeforces rating: 1350 (Pupil) | Winner, 24-hour hackathon, college tech fest, 2025 | AWS Cloud Practitioner Essentials (Coursera)

Coding profiles, GitHub, and certifications: what to include and what to skip

• LeetCode/Codeforces/GeeksforGeeks: include a number only if it's genuinely worth mentioning (100+ problems, a contest rating). A low number framed honestly is fine too — just don't inflate it, since a live coding round will expose the gap immediately.
• GitHub: pin your 3 best repositories with a proper README (what it does, how to run it, a screenshot if it has a UI). Forty empty or forked repos with no commits signal a profile built for appearance, not use.
• Certifications: keep them role-relevant — AWS/GCP basics, a DSA course, a backend specialization. A generic "MS Office" or "Typing certificate" next to Spring Boot dilutes the technical signal you're trying to send.

Common mistakes specific to software engineer resumes

1. Listing every language and framework you've touched once. A recruiter reading "Java, Python, C++, C, JavaScript, Go, Rust, PHP, Kotlin" assumes shallow exposure to all of them, not mastery of any.
2. No live or deployed links, only GitHub source. A deployed link (Render, Vercel, Railway) that a recruiter can click and actually use takes your project from "claim" to "proof" in one click.
3. A DSA-only resume with zero built projects. Fine for a pure service-company aptitude round, but product companies and most off-campus product-adjacent roles want to see something you shipped, not just problems you solved.
4. Backlog history formatted inconsistently. If you cleared a backlog, don't leave stale semester gaps unexplained — a one-line note under Education is enough.
5. Copy-pasted tutorial projects with no differentiation. "Tic Tac Toe," "Calculator," and "Netflix Clone" are the three most repeated fresher projects in India — if you built one, add a twist (multiplayer over WebSockets, a recommendation feature, a real dataset) or replace it with something more original.

What happens after your resume gets shortlisted

Getting past the resume screen is one filter, not the finish line. Service-company drives move straight into an aptitude-plus-coding test followed by a technical and HR round — if that's your track, look at real TCS interview questions or Infosys interview questions so you know what's actually asked before you walk in. Product-company and startup interviews tend to dig deeper into the exact projects on your resume — expect to explain your design choices, not just recite what's written, and run your resume once more through an ATS format check if you're applying through an online portal rather than a referral.

Frequently Asked Questions

What is the ideal resume format for a software engineer fresher? One page, reverse-chronological, with Education followed immediately by a categorized Skills section and 2-4 projects that each name tools and a measurable outcome. See our broader resume format guide for freshers for the base structure this builds on.

How many projects should a fresher software engineer resume have? Two to four is the sweet spot. Fewer than two looks thin; more than four usually means some are weak and diluting the strong ones.

Should I include my LeetCode or Codeforces profile on my resume? Yes, if the number is decent (100+ solved, or a rated contest performance) — it's a fast proxy for DSA ability that both service and product companies use.

Do service companies like TCS and Infosys care about GitHub? Less than product companies do, but it doesn't hurt — their first filter is usually CGPA and an aptitude/coding test score, not your GitHub activity. Product companies weight it more heavily.

What CGPA cutoff do most Indian IT companies use? Many service companies apply a soft cutoff around 60-65% aggregate or equivalent CGPA for campus and off-campus drives, though this varies by company and hiring cycle — check the specific drive's eligibility criteria rather than assuming.

Should DSA and web development both appear on the resume, or should I pick one? Both, if you have them — DSA signals problem-solving ability for coding rounds, and a built project signals you can actually ship something end to end. Together they cover what service-company tests and product-company interviews each check for.