Resume Writing Tips for Software Engineers India 2026: ATS-Optimised, 1-Page, Achievement-Focused

Resume format for Indian software engineers:

1. Length: one page for 0-7 years experience; two pages maximum for 8+ years. One focused, achievement-filled page consistently outperforms two sprawling pages for mid-career engineers.

2. Sections and order (most important first): - Contact info: name, phone, email, LinkedIn URL (linkedin.com/in/yourname), GitHub URL, city - Skills: technologies, languages, frameworks listed concisely - Experience: reverse chronological (most recent first) - Projects: critical for freshers; optional for experienced engineers with strong experience - Education: reverse chronological

3. ATS-friendly format: - No tables, text boxes, headers/footers, graphics, or charts (ATS parsers skip content inside these) - Plain text with standard headings ('Experience', 'Education', not 'What I Have Done' or 'Where I Went') - Single-column layout - Consistent font at 10.5-12pt body; 14-16pt for name

1. File format: PDF is safest (preserves formatting across all systems). Submit .docx only if the application explicitly requires it.

1. File name: 'FirstName-LastName-Resume.pdf'. Never submit 'resumefinalv3USETHIS.pdf'.

Achievement-focused bullet formula: [Action verb] + [What you did] + [Measured impact]

Examples:

Weak: 'Responsible for backend API development.' Strong: 'Built a checkout API handling 50K transactions per day with 99.95% uptime, reducing payment failures from 1.2% to 0.15% by implementing idempotent retries and Redis-based deduplication.'

Weak: 'Worked on improving system performance.' Strong: 'Reduced P99 API latency from 800ms to 120ms by profiling hot queries, adding 6 targeted PostgreSQL indexes, and implementing Redis cache-aside for the 50 most-queried endpoints.'

Weak: 'Member of the team that migrated the monolith to microservices.' Strong: 'Led the migration of the billing monolith to 4 microservices (Node.js + Go), reducing deployment time from 2 hours to 8 minutes and enabling independent scaling of the payment processing service during peak load.'

Action verbs that signal ownership: Built, Designed, Led, Reduced, Increased, Optimised, Migrated, Launched, Scaled, Automated.

Avoid: Assisted, Helped, Worked on, Contributed to, Participated in (they signal you did not own the outcome).

If you did not own something, still quantify your contribution: 'Key contributor to migration: owned the payment service module, wrote 40% of the codebase.'

ATS keyword strategy:

1. Match the job description: if the JD says 'microservices', use 'microservices' exactly (not 'micro-services' or 'service-oriented architecture'). ATS systems match keywords literally.

1. Read the JD for 5 key technical terms: for each application, identify the 5 most repeated technical skills in the JD and ensure your resume uses those exact words at least once. This is not dishonest; it is signal alignment.

1. Skills section formatting: list skills in a scannable format: 'Languages: Python, Java, Go | Frameworks: FastAPI, Spring Boot, React | Databases: PostgreSQL, Redis, DynamoDB | Tools: Docker, Kubernetes, Terraform, GitHub Actions, AWS'.

1. Do not keyword stuff: having 'machine learning' in your skills when you have no ML experience creates a credibility gap when the interviewer asks about it. Only list skills you can confidently discuss.

1. LinkedIn consistency: if your resume says 'senior software engineer at X', your LinkedIn title should match. Recruiters cross-reference, and inconsistencies raise red flags.

1. Common keywords that matter for Indian product companies in 2026: Microservices, REST API, Docker, Kubernetes, AWS/GCP/Azure, System Design, Redis, Kafka, PostgreSQL, CI/CD, Distributed Systems, Spring Boot, React, Node.js, Python.

Resume guide for freshers (0-1 year experience):

1. Projects section (most important for freshers): 2-3 projects, each with: project name, technology stack, brief description of what it does, and quantified impact or scale if available. Example: 'HireStepX Clone (Personal Project) | React, Node.js, PostgreSQL | Built a mock interview platform with voice recording and automated feedback; 200+ practice sessions logged by 50 beta users. GitHub link.'

1. Skills section: list languages (Java, Python, C++, JavaScript), frameworks (Spring Boot, React, Node.js), databases (MySQL, PostgreSQL, MongoDB), tools (Git, Docker, AWS basics). Only list what you can discuss.

1. Education: CGPA (include if above 7.5; omit if below 7.0). Relevant coursework if it adds value (Data Structures, Algorithms, DBMS, OS, Computer Networks). Certifications (AWS Cloud Practitioner, CS50, Google Data Analytics) are worth listing for freshers.

1. Internship (highest priority): treat internship bullets exactly like work experience bullets. Action verb + what + measured impact.

1. Hackathon wins or open-source contributions: include under 'Achievements' if you have won a hackathon or have PRs merged to a well-known open-source project.

7 common resume mistakes by Indian software engineers:

1. Objective statement at the top: 'Seeking a software engineering role where I can utilise my skills...' wastes space. Replace with a tight skills block or remove entirely.

1. Responsibilities over achievements: 'Developed backend APIs using Spring Boot' says nothing. What was the scale? What did you improve? Add numbers.

1. Same resume for every application: tailor the skills section and the order of bullet points to match each company's JD. 15 minutes per application of customisation doubles the callback rate.

1. Listing every technology you have ever touched: 8 programming languages and 15 frameworks signals shallow breadth. List what you can discuss confidently for 10+ minutes.

1. Inconsistent tense: current role bullets in present tense; past roles in past tense. Mixing them signals carelessness.

1. Using a template with headers/footers or tables: ATS parsers cannot read content inside tables or text boxes. Use a plain text-compatible format (Google Docs default styles work well).

1. Not including a GitHub link (for freshers and mid-career engineers with public projects): your code is evidence that your resume claims are real. A GitHub profile with 2-3 quality projects can be the difference between shortlisting and rejection.