Software Engineer Resume Example and Guide
A complete sample, plus what to write when your only real code is in college projects.
For freshers and engineers with 0–4 years, including anyone switching from a service company to a product team.
Most fresher software engineer resumes fail on the same thing: a long list of languages and frameworks with nothing underneath them. A reviewer who sees Java, Python, C++, React, Node, MongoDB, Docker and Kubernetes on a resume with no job history assumes none of it is deep. The resumes that get shortlisted pick two or three technologies, then prove them with a project that has a working link, real users or a measured result.
What recruiters look for first
- A GitHub link that opens and shows commits, not an empty profile.
- Two or three technologies used properly, rather than twelve names in a row.
- Projects described with scale: requests handled, rows processed, users, or response time.
- Data structures and algorithms signal, because most Indian product companies still screen on it.
- For experienced applicants, what you owned, not what the team shipped.
Summary examples
Computer science graduate who has shipped two deployed side projects, including a bus-tracking app used by 300 students on campus. Comfortable in Python and JavaScript end to end, from schema design to deployment, and solved 400+ DSA problems.
Backend engineer with 3 years building payment and order systems in Go and Node.js. Owned the refunds service end to end at 2M requests a day, and cut p95 checkout latency from 1.4s to 380ms.
Bullet points, before and after
Worked on the backend using Node.js and MongoDB
Built the order-tracking API in Node.js serving 1,200 merchant integrations, with p95 latency under 200ms
Names what the service does, who consumes it and how fast it is, so the reader can judge the difficulty.
Developed a college project using React and Firebase
Built a bus-tracking web app in React used by 300 students daily, with live location refreshed every 15 seconds
A project with real users and a real refresh interval reads like engineering, not coursework.
Responsible for fixing bugs and writing unit tests
Raised backend test coverage from 34% to 78% and cut production incidents from 6 to 1 per quarter
Testing work is easy to dismiss unless you attach the defect number it moved.
Participated in code reviews and agile ceremonies
Reviewed around 15 pull requests a week and wrote the service's onboarding guide, cutting new-joiner ramp-up from three weeks to one
Turns a routine activity into a measurable contribution to the team.
Keywords to include
Terms that job descriptions for this role use, and that applicant tracking systems are often configured to match. Include the ones that are genuinely true of you.
Languages
- Java
- Python
- JavaScript
- TypeScript
- Go
- C++
- SQL
Backend and data
- Node.js
- Spring Boot
- REST API
- Microservices
- PostgreSQL
- MongoDB
- Redis
- Kafka
Frontend
- React
- Next.js
- HTML
- CSS
- Tailwind CSS
- Responsive design
Practices
- Data structures
- Algorithms
- Git
- Docker
- CI/CD
- AWS
- Unit testing
- Agile
Mistakes specific to this role
Listing every framework you have touched
If you put twelve technologies on the page, an interviewer will pick the one you know least. Keep the list to what you are willing to be questioned on for fifteen minutes, and move the rest into a project line where the context is obvious.
A GitHub link with nothing behind it
Recruiters at product companies do open the link. An empty profile, or three forked repositories with no commits, is worse than no link. Pin two repositories with a README that explains what the project does and how to run it.
Projects with no scale or outcome
"E-commerce website using MERN stack" appears on thousands of fresher resumes and says nothing. Add the part that is yours: how many products it handles, whether anyone used it, what was hard about it.
Hiding behind the team at a service company
"Worked on a banking client project" tells a reviewer nothing about you. Name the module you owned, the number of screens or endpoints, and what changed because you were on it, within whatever your contract allows you to say.
Putting a photo, age, father's name and marital status at the top
This is still common on Indian fresher resumes and it wastes the most valuable part of the page. Product companies do not want it, and some applicant tracking systems garble the header when a photo sits in it.