TL;DR: Lead with your stack and level, write bullets as what you built + how + the impact, show scale with numbers (users, latency, cost), keep it to one page under 5 years, and tailor the tech keywords to every job post.
Software engineering roles in India attract a huge number of applications. Recruiters and hiring managers skim for three things: your level, your stack, and evidence of impact. Here’s how to show all three, from your first job to senior roles.
The structure that works
- Header: name, phone, email, city, GitHub, LinkedIn, portfolio
- Summary: level + stack + one proof + target role (2 lines)
- Skills: grouped (languages, frameworks, cloud, databases, tools)
- Experience: reverse-chronological, 3–5 impact bullets per role
- Projects: essential for freshers, optional for seniors
- Education and certifications
Write bullets that show impact
Use: built/changed X, using Y, which resulted in Z (with a number).
| Weak | Strong |
|---|---|
| Worked on backend APIs | Built 14 REST APIs in Spring Boot for the payments flow, handling 2M requests a day |
| Improved performance | Cut p95 API latency from 900 ms to 220 ms by adding Redis caching and query indexes |
| Did testing | Raised unit test coverage from 35% to 78%, cutting production bugs by roughly half |
If you don’t have exact numbers, use honest estimates and be ready to explain them.
Examples by level
Fresher (B.Tech 2026)
Summary: Computer science graduate skilled in Java, Spring Boot and SQL. Built a library management system used by 400+ students. Looking for a backend developer role.
Project: Library management system (Java, Spring Boot, MySQL): 400+ active student users; JWT login; reduced manual book tracking for the college library.
Mid-level (3–6 years)
Summary: Full-stack engineer with 4 years in React and Node.js. Shipped 3 customer-facing products from scratch, each with 10k+ monthly users.
Senior (8+ years)
Summary: Backend engineer with 9 years in distributed systems on AWS. Led a team of 6 to rebuild a payments platform processing ₹2,000 crore a month.
The skills section
Group skills so they’re easy to scan, and mirror the job post’s wording:
– Languages: Java, Python, TypeScript, Go
– Frameworks: Spring Boot, React, Node.js, Django
– Cloud and DevOps: AWS, Docker, Kubernetes, CI/CD
– Data: PostgreSQL, MongoDB, Redis, Kafka
Only list what you can discuss in an interview. See our 150+ resume skills list for more.
Projects and GitHub
For freshers, projects are your experience. Link a GitHub with clean READMEs. A deployed demo link is even better. For experienced engineers, one or two open-source contributions or side projects can help, but experience comes first.
Common mistakes
- Listing 40 technologies with no evidence
- Describing tasks (“worked on…”) instead of outcomes
- Two pages for 2 years of experience
- No links to GitHub or portfolio
- Skill bars and star ratings (ATS can’t read them)
Tailor it in minutes
Every engineering job post emphasises different things: one wants Kafka and microservices, another React and accessibility. On GoResume you can paste the job description and see which keywords you already cover and which are missing, then get a tailored copy.
Build your software engineer resume free →
See also the software engineer resume example and full stack developer example.
FAQ
Should a software engineer resume be one page?
Yes under about 5 years of experience. Senior engineers can use two.
Should I include competitive programming ratings?
For freshers and roles that value problem-solving, a strong rating (e.g. a CodeChef or LeetCode rating) can help. List it under achievements.
Do I need a summary?
A two-line summary helps recruiters place your level and stack quickly.
Is a GitHub link necessary?
For freshers, strongly recommended. For experienced engineers, helpful but not essential.
