HireToolX

Resume example4 years

Software Engineer Resume Example & Format

Software engineering hiring in India runs through two very different doors. IT services companies often screen for a wide stack and project exposure across clients, while product companies, startups and global capability centres (GCCs) look for ownership: what you designed, what broke, what you fixed and how you measured it. A good software engineer resume makes that ownership obvious in the first few lines.

Recruiters and hiring managers usually check three things quickly: the languages and frameworks you have used recently in production, the scale you have worked at (users, requests, data volume or team size), and whether your bullets describe outcomes or only duties. Coding profiles, open-source work and system design exposure help, but they support the experience section rather than replace it.

The sample below is for an engineer with about four years of experience who moved from an IT services firm to a fintech product company. Use its structure, then replace every line with your own work and numbers you can explain in an interview.

Sample Software Engineer resume

Fictional candidate. Names, employers, colleges and figures are illustrative; replace every line with your own work.

Rohan Example

Software Engineer II · Backend & APIs · Python, Go, AWS

  • Bengaluru, Karnataka
  • rohan.example@example.com
  • +91 9XXXX XXXXX
  • linkedin.com/in/rohan-example
  • github.com/rohan-example

Summary

Backend-focused software engineer with 4 years of experience building payment and logistics systems in Python and Go. Comfortable owning a service end to end, from design review and data modelling to deployment, monitoring and on-call. Looking for a senior backend role on a team that ships to large user bases.

Experience

Software Engineer II

Contoso Payments Pvt. Ltd. · Bengaluru

  • Designed and built a Go payout reconciliation service that matches about 2 million transactions a day, cutting the finance team's manual reconciliation from 6 hours to under 1 hour daily.
  • Reduced p95 latency of the merchant dashboard API from 820 ms to 310 ms by adding Redis caching and rewriting three N+1 PostgreSQL queries.
  • Moved 14 cron jobs to an event-driven Kafka pipeline, which removed duplicate settlement alerts and roughly halved weekly on-call pages for the team.
  • Reviewed 300+ pull requests, wrote the team's API error-handling guidelines and onboarded 2 new engineers.

Software Engineer

Fabrikam Technologies Ltd. · Pune

  • Built Django REST APIs for a logistics client's shipment tracking portal used by 1,200+ warehouse staff across 9 cities.
  • Raised unit test coverage on the booking module from 38% to 81% with pytest, catching regressions before client UAT.
  • Containerised the app with Docker and set up GitHub Actions pipelines, cutting release time from half a day to about 25 minutes.
  • Traced and fixed a memory leak in a Celery worker that caused weekly outages; no related incidents in the following 6 months.

Projects

Token-bucket rate limiter

Go, Redis

  • Open-source rate limiting library with sliding-window support and benchmarks; adopted by two internal services at Contoso.

Skills

  • Languages: Python, Go, Java, TypeScript, SQL
  • Backend: Django, FastAPI, gRPC, REST APIs, Kafka, Celery
  • Data stores: PostgreSQL, Redis, MongoDB
  • Cloud & DevOps: AWS (EC2, S3, Lambda, RDS), Docker, Kubernetes, GitHub Actions
  • Practices: System design, Unit and integration testing, Code review, Agile / Scrum

Education

B.Tech, Computer Science and Engineering

Example Institute of Technology · Pune · CGPA 8.4 / 10

Certifications

  • AWS Certified Developer – Associate

What makes this resume work

  • The headline states level, focus area and core stack, so a recruiter knows within seconds which roles this resume fits.
  • Every bullet starts with a strong verb and ends with a result: latency, hours saved, coverage, incidents or scale.
  • Numbers are specific but believable, and each one is something the candidate can explain in a system design or project round.
  • Skills are grouped by type instead of one long comma list, which helps both ATS keyword matching and human skimming.
  • The IT services experience is framed around engineering wins, not client names or generic duties, which helps when moving to a product company.
  • One relevant project and one certification add signal without pushing the resume past a single page.

Software Engineer resume keywords for ATS

Recruiters and applicant tracking systems search for these terms. Use the ones that genuinely match your experience, in your bullets as well as your skills section, and mirror the wording of each job description.

  • Software Engineer
  • Backend Development
  • Python
  • Go
  • Java
  • REST APIs
  • Microservices
  • System Design
  • Data Structures and Algorithms
  • PostgreSQL
  • Redis
  • Kafka
  • AWS
  • Docker
  • Kubernetes
  • CI/CD
  • Unit Testing
  • Code Review
  • Agile
  • Scalability
  • Performance Optimisation
  • Distributed Systems

Software Engineer resume mistakes to avoid

  • Listing every technology you have touched. Keep the skills you can be interviewed on and that appear in your bullets.
  • Writing duties such as "responsible for developing modules" instead of what you built and what changed because of it.
  • Leaving out scale. Requests per second, users, data volume or team size tell the reader what level you work at.
  • Spending space on a photo, date of birth, marital status or a full address. They are not needed and use space better spent on work.
  • Sending the same resume to every opening. Reorder skills and bullets so the stack in the job description appears first.

Frequently asked questions

What is the best resume format for a software engineer in India?

A reverse-chronological format works best: contact details and links, a two or three line summary, experience, skills, projects and education. Use a single column, standard section headings and a plain font so applicant tracking systems can parse it. Save it as a PDF unless the portal asks for Word. Freshers can move education and projects above experience, but experienced engineers should lead with work.

Should a software engineer resume be one page?

Under about five years of experience, one page is usually enough and forces you to keep only your strongest work. Senior engineers with several relevant roles can use two pages, as long as the first page carries the most recent and most impressive experience. Recruiters skim quickly, so a tight one-page resume often performs better than a padded two-page one.

Should I add my LeetCode, Codeforces or GitHub profile?

Add them when they show something real: a solid contest rating, a consistent problem-solving record, or repositories with readable code and a clear README. Put the links in the header next to LinkedIn. An empty GitHub or a profile with a handful of solved problems adds little, so leave it out rather than invite a reviewer to look at it.

How do I move from an IT services company to a product company?

Rewrite your bullets around engineering decisions and measurable results rather than client names and process. Highlight design work, performance fixes, testing, automation and anything you owned end to end. Add a side project or open-source contribution if your day job was narrow. Prepare for data structures, algorithms and system design rounds, since product companies weigh those heavily.

Should I mention my current CTC and notice period on my resume?

No. Salary details do not belong on a resume and can work against you in negotiation. Naukri and many company portals ask for current CTC, expected CTC and notice period in separate fields, and recruiters will ask on the first call. If you can join early or are serving notice, mention it briefly in your cover note or application message instead.

Make your Software Engineer resume

Start from a clean ATS-friendly template, fill in your own experience, then check it against the job description.