A software engineer resume in India has to clear two different screens with one document: the keyword-and-project scan that IT services firms run at volume, and the scale-and-impact read that product companies and global capability centres apply. The format that survives both is one to two pages, single-column, opening with a two-line summary, followed by grouped technical skills and experience bullets that name the stack, the scale it ran at, and the number that moved. Everything a recruiter cannot use — photo, date of birth, marital status, declaration and signature — comes off.
Two markets, two rubrics
India's software hiring splits into two screening styles, and a large share of silent rejections come from sending the document built for one rubric into the other.
IT services — TCS, Infosys, Wipro, HCLTech, Cognizant, LTIMindtree and the staffing partners who feed them — screen against a requirement sheet. A recruiter or sourcing tool matches your resume to a shopping list: exact technology names, the years attached to each, the delivery domain (BFSI, retail, telecom, healthcare), and whether you have shipped something that ran in production for a client. Certifications carry real weight here because they are cheap to verify.
Product companies and GCCs — Flipkart, Zomato, Razorpay, Zoho, Freshworks, PhonePe, plus the India engineering centres of global firms — screen for what you built and what changed because of it. A hiring manager reads your bullets for ownership, system design instinct, and traffic or data volume somewhere near their own. An undifferentiated skills list reads as padding, and a bullet that only says you "worked on" something reads as describing someone else's work.
| Screening dimension | IT services and staffing | Product companies and GCCs |
|---|---|---|
| First filter | Keyword and years-of-experience match against the requirement sheet | Hiring manager or senior engineer reading bullets for scope and ownership |
| Skills section | Broad and explicit — list every technology you can defend in an interview | Tight and layered — depth in a primary stack matters more than breadth |
| Projects | Client name or domain, team size, your module, technologies used | The problem, your design decision, the scale, and the measurable result |
| Certifications | High signal — cloud, security and platform certifications are checked | Low signal — treated as supporting evidence, never as the headline |
| Numbers that land | Team size, release cadence, defect reduction, uptime against SLA | Requests per second, p95 latency, data volume, cost per transaction |
| Common rejection reason | Missing an exact keyword the requirement sheet demanded | Duties listed with no evidence you owned or changed anything |
You do not need two entirely separate resumes. You need one clean base document and a disciplined habit of re-ordering the skills line and rewriting the top three bullets for whichever lane you are applying into.
The structure that works
- Header: name, phone with the +91 code, a professional email address, LinkedIn URL and GitHub URL. City is worth including, because location is one of the first shortlist filters.
- Summary, two lines: role plus years plus core stack plus one standout achievement. No objective statement.
- Skills, grouped: Languages, Frameworks, Cloud and DevOps, Databases, Tools. Grouping helps a human skim and gives the parser clean, labelled clusters.
- Experience: reverse chronological, quantified bullets, strongest first inside each role.
- Projects: essential for freshers and for anyone switching lanes. Tech stack, your contribution, outcome.
- Education and certifications: brief, at the bottom — unless you are a fresher, in which case education moves above experience.
What comes off an Indian software resume
Many templates circulating in India still carry fields inherited from government application forms. Remove the photograph, date of birth, father's or spouse's name, marital status, nationality, passport number, full postal address, and the signed declaration block at the end. Drop "References available on request" too — it is assumed, and it eats a line you could spend on a result.
The two-line summary that earns its space
A weak summary announces that you are a hardworking engineer seeking growth. A strong one is a pitch a recruiter can repeat to a hiring manager: "Backend engineer with four years building payment and order services in Java and Spring Boot on AWS. Owned the migration of a monolith checkout flow to microservices, cutting p95 checkout latency by more than a third." Role, years, stack, one proof point.
Bullets that pass a product-company screen
The single biggest quality gap in Indian software resumes is the duty bullet — a sentence describing what you were assigned rather than what you delivered. Compare these two versions of the same work:
- Weak: "Worked on backend APIs using Node.js as part of the order management team."
- Strong: "Built order-service APIs in Node.js handling peak traffic of 40,000 requests per minute; cut p95 latency by 38 percent by introducing a Redis cache layer and batching downstream inventory calls."
Every bullet should answer four questions in one sentence: what did you build, with what, at what scale, and what changed because of it. If you genuinely cannot attach a number, attach a consequence — a release that stopped failing, a manual process that became automatic, an on-call page that stopped firing. Recruiters consistently report that specificity, not vocabulary, is what separates a shortlist from a reject pile.
Two practical notes. First, keep each bullet to one or two lines; dense multi-sentence paragraphs are the most common parsing problem on Indian resumes and they defeat a six-second skim as thoroughly as they defeat an algorithm. Second, write in past tense for previous roles and present tense only for the role you currently hold, and stay consistent — mixed tense across a single role reads as copy-paste.
Map every skill to a role, not just to a list
Most modern applicant tracking systems do not simply count how often a keyword appears. They associate a technology with the employment dates of the role in whose description it appears, which is how a recruiter searches for something like "Kubernetes, three or more years". If Kubernetes appears only in a skills block at the top of your document, with no role underneath it claiming Kubernetes work, you can be invisible to a duration-filtered search despite genuinely having the experience.
So do both. Keep the grouped skills section for the human skim and for exact-match keyword searches, and then make sure each significant technology also appears inside at least one experience or project bullet, attached to a dated role. Match the job description's exact wording as well — if the posting says Kubernetes, do not write only k8s, and if it asks for continuous integration and continuous deployment, write the phrase out alongside CI/CD so both forms of the search find you. For a full breakdown of which terms carry the most weight and how to categorise them, read our guide to software engineer resume keywords, then run your draft against a specific posting with JD Screening to see exactly which terms you are missing.
The India-specific fields recruiters filter on
Indian recruiters shortlist on a set of variables that barely exist in other markets, and getting them wrong wastes interview slots on both sides.
- Notice period: Indian employment contracts commonly specify notice periods of 30, 60 or 90 days, and a hiring team filling an urgent requirement will filter on it before reading your bullets. State it plainly in one line near the top — "Notice period: 60 days, negotiable to 30" — rather than making a recruiter call to find out.
- Current and preferred location: Say which city you are in and which you will move to. Relocation willingness is a genuine differentiator for roles in Bengaluru, Hyderabad, Pune, Chennai, Gurugram and Noida.
- CTC: Keep current and expected CTC off the resume itself. It anchors a negotiation before you have demonstrated value. Put it in the application form or the job portal field where it belongs, and keep the conversation open in the interview.
- Portal parity: Your resume, your LinkedIn headline and your Naukri profile should agree on job title, current employer and years of experience. Recruiters cross-check, and a mismatch reads as either carelessness or exaggeration. Our Naukri profile guide covers the headline and key-skills fields that drive recruiter search results on the platform.
Freshers, campus placements and the first two years
If you have no full-time experience yet, the ordering changes but the standard does not. Put education directly under the summary, include your CGPA or percentage if it is competitive, and then let projects carry the document. Two or three substantial projects described properly will outperform eight one-line entries every time.
Describe a project the way you would describe a job: the problem, the stack, your specific contribution if it was a team effort, and something measurable — dataset size, number of users, response time, accuracy, or a working deployment link. Add internship work as experience rather than burying it under education. If you have a meaningful competitive programming or open source footprint, one line with the profile URL and a concrete marker of standing is worth including; a vague claim of "good at DSA" is not.
Two habits to avoid at campus drives: do not list every technology you touched in a single semester course, and do not inflate a guided tutorial project into a system you architected. Both collapse in the first technical round, and interviewers in India ask about resume projects far more often than candidates expect.
Switching from services to product
Engineers moving from an IT services firm into a product company face a specific framing problem: their experience is genuinely strong, but it is written in the language of client deliverables and support tickets. Rewrite it in the language of systems. Instead of naming the client, name the system and its scale. Instead of describing the process you followed, describe the design decision you made and its trade-off. If you worked in maintenance or production support, that is not a weakness — reframe it as reliability work, with the incident volume you reduced or the root causes you eliminated.
Also address the mismatch product interviewers quietly worry about: whether you have owned anything end to end. One bullet showing a feature you took from design to deployment, or a side project you shipped and maintained, answers that question before it is asked.
Formatting rules that decide whether you are read at all
None of the writing above matters if the file cannot be parsed. Keep to a single-column layout — two-column templates with dates in a sidebar routinely scramble when a parser reads straight across the page, merging job titles with dates and breaking the experience calculation entirely. Use standard section headings (Summary, Skills, Work Experience, Projects, Education, Certifications) rather than creative ones. Export a text-based PDF, not a scanned image or a screenshot, and name the file with your name and target role. Avoid tables, text boxes, icons, skill rating bars and graphics, and keep contact details in the body of the document rather than in the page header, which some legacy systems do not read.
Before you send anything, put the file through a parser and see what a machine actually extracts from it. Our ATS resume checker shows you the parsed output field by field, so you can catch a scrambled work history or a missing phone number before a recruiter does.
FAQ
How long should a software engineer resume be in India?
One page for freshers and engineers with under three years of experience, and a maximum of two pages beyond that. Length is not seniority. A senior engineer with a tight two-page document that quantifies impact will outrank a four-page chronology of every ticket closed.
Should I include my photo, date of birth or CTC on an Indian resume?
No to all three. A photo and date of birth add nothing a hiring decision should rest on and take space from your results. Current and expected CTC belong in the application form or job portal field, not the resume, so you keep room to negotiate after the interview has demonstrated your value.
Do certifications actually help for software engineering roles in India?
They help far more in the IT services and staffing lane, where a verified cloud or platform certification maps directly to a client skill requirement. At product companies they are supporting evidence at best. List them briefly at the bottom with the issuing body and year, and never let them displace project or impact content.
How do I show a career gap or a notice period without hurting my chances?
State both plainly. Put your notice period in a single line near the top so recruiters can filter accurately. For a gap, give it a dated entry with an honest one-line description — upskilling, health, family responsibility, preparing for higher studies — and mention anything you built or learned during it. Hidden gaps surface in background verification, which is a far worse outcome than an explained one.
Is one resume enough for both service companies and product companies?
One base document is enough, but the top third should change. Re-order your grouped skills so the stack the posting names appears first, and rewrite the summary plus your top two or three bullets to match the rubric — keyword and domain coverage for services roles, scale and ownership for product roles. That is a ten-minute edit per application, not a rewrite.
What should a fresher put in the experience section with no job history?
Internships first, then substantial academic or personal projects described with the same rigour as a job — problem, stack, your contribution, and a measurable outcome. Freelance work, hackathon builds and maintained open source contributions all count. What does not count is a list of technologies with no evidence you built something with them.
Build it, then have it checked
A strong Indian software engineer resume is not a writing exercise so much as an evidence exercise: name the system, name the scale, name what changed. If turning your raw project notes into that shape is the slow part, the AI resume builder drafts quantified, ATS-safe bullets and formats them in a single-column layout that parsers read cleanly. Targeting a senior or a product-company role where the stakes are higher? Put the finished document in front of a person with an expert resume review before you apply.
Put this into practice. Check your resume with the ATS Resume Checker, then follow our Software Engineer resume guide for role-specific bullets — and see Resumere pricing (pay-per-use, no subscription) when you're ready to build.
