Software Engineer Resume
A developer resume is not a list of technologies. It shows what you built, how well it worked and what you personally did. This guide covers the structure, bullet writing and common mistakes, for freshers and experienced engineers.
Keep it to one page (two only if you have many years of relevant work). Put a short summary and tech stack first, then experience or projects with specific, honest results, then skills and education. Match the technologies named in the job post, but only list tools you can discuss in an interview.
What a hiring team wants to see
Whoever reads your resume, whether a recruiter at a service company, a product startup or a campus drive, is trying to answer three questions quickly. Can this person work with our stack? Have they built something real? Can they explain their own work?
Your resume should answer all three without making the reader dig. That means the technologies are easy to find, each project or job says what you did, and the results are concrete. A resume that only says “worked on backend development” answers none of them.
Also remember that many companies pass resumes through an applicant tracking system first. Plain headings and simple formatting matter more than design. Our guide on ATS-friendly resumes explains this in detail.
The right section order
Order depends on where you are in your career. Lead with your strongest evidence.
| Your stage | Recommended order |
|---|---|
| Final-year student or fresher | Header, summary, skills, projects, education, internships, certifications |
| 1 to 5 years of experience | Header, summary, skills, experience, projects, education |
| 5+ years of experience | Header, summary, skills, experience, education, optional selected projects |
The header should carry your name, phone, professional email, city, and links to GitHub and LinkedIn. Make sure the GitHub link opens to a profile with at least a few readable repositories. An empty profile does you no favours.
Write a summary that names your stack
Two or three lines are enough. Mention your role, your years of experience (or “final-year B.Tech student”), your main stack and one thing you are good at.
Fictional example, 3 years of experience:
Backend developer with 3 years of experience building REST APIs in Java and Spring Boot for a logistics platform. Comfortable with PostgreSQL tuning, Redis caching and AWS deployments. Looking for a backend role in a product team.
Avoid vague lines such as “hard-working professional seeking challenging opportunities”. They could belong to anyone. See more patterns in our resume summary examples.
Turn duties into bullets that show impact
A good bullet follows a simple shape: action, what you worked on, how, and the result. The result can be speed, reliability, cost, users served, time saved or even a code quality improvement. Use a number only when you know it is true. If you cannot measure something, describe the outcome plainly instead of guessing.
Before: Responsible for API development.
After: Built 14 REST endpoints for the order-tracking service in Spring Boot, with request validation and unit tests covering the main flows.
Before: Worked on database optimisation.
After: Added indexes and rewrote two slow report queries in PostgreSQL, bringing the nightly report job from about 25 minutes to under 10.
Before: Fixed bugs in the React app.
After: Fixed recurring form-state bugs in the checkout page by moving state into a single reducer, which stopped the repeat tickets raised by support.
These are fictional rewrites to show the pattern. Replace the details with your own, and keep the numbers you can defend if an interviewer asks.
A worked experience section (fictional example)
Software Engineer, BrightCart Retail Technologies (fictional), Pune | Jul 2023 to Present
- Own the product-search service (Java, Spring Boot, Elasticsearch) used by the web and Android apps.
- Added caching for category pages with Redis, cutting repeated database reads and lowering p95 response time from roughly 900 ms to 450 ms.
- Set up a GitHub Actions pipeline with automated tests and staging deploys, reducing manual release steps from nine to two.
- Mentored two new joiners on code review practice and the team's testing conventions.
Notice what this does. The first line states ownership, the next two show measurable improvement with the tool named, and the last shows collaboration. Four bullets are enough for a role. Older jobs can have two or three.
Projects: the fresher's main proof
If you have little or no work experience, projects carry the resume. Pick two or three and write each so a stranger can understand it in ten seconds. Our page on the projects section goes deeper.
Fictional example:
Hostel Mess Feedback App | React, Node.js, MongoDB | GitHub link
- Built a web app where students rate daily meals and the mess manager sees weekly averages.
- Designed login with JWT and role-based access for students and managers.
- Deployed on a free cloud tier; used by about 60 students in my hostel for one semester.
Include the link, your own role (especially for team projects), and an honest scale. A small real project beats a copied tutorial clone with inflated claims.
Organise skills so they can be scanned
Group skills by type instead of one long comma list.
- Languages: Java, Python, JavaScript, SQL
- Frameworks: Spring Boot, React, Express
- Databases: PostgreSQL, MongoDB, Redis
- Tools and cloud: Git, Docker, GitHub Actions, AWS (EC2, S3)
Put the technologies from the job description first, if you genuinely know them. Do not add skill bars or “80% Python” graphics; they say nothing real and confuse parsers. More ideas in skills for resume.
Mistakes to check before you send
- Listing every tool you have ever touched. Keep to what you could discuss for ten minutes.
- Writing “team player” and “quick learner” as skills instead of showing them in bullets.
- Using a photo, columns or graphics from a design template that ATS software may misread.
- Sending one generic resume to every company. Adjust the summary and skills order for each role.
- Broken or private GitHub and LinkedIn links.
- Spelling a technology wrongly, such as “Javascript”, “Node js” or “Postgre”.
Read the whole resume aloud once. Anything you stumble on in an interview should either be fixed or removed.
Build your developer resume — free
Pick a clean, ATS-friendly template, edit your bullets and download a PDF.
Create my resume →Frequently asked questions
Should a software engineer resume be one page?
For freshers and engineers with up to about five years of experience, one page is the safest. Senior engineers with a long relevant history can use two pages, as long as the first page carries the strongest points.
What if I do not have work experience?
Lead with projects, internships, open-source contributions or hackathon work. Describe what you built, your role and the tools, and link to the code.
Do I need a GitHub profile?
It is not mandatory, but for developer roles it helps a lot to have a few clean repositories with readable README files. Do not link an empty or messy profile.
Should I add percentages and metrics to every bullet?
Only when they are true and you can explain how you measured them. If you cannot measure, describe the outcome in plain words rather than inventing a number.
Is a photo or a career objective needed?
A photo is generally not needed for tech roles. A short summary of two or three lines works better than a generic objective.