At Google, Amazon, and Flipkart India, a recruiter spends 6–10 seconds on initial resume review. If your resume doesn't communicate impact immediately, it's rejected before a human ever reads it carefully. And before that, an ATS has already filtered out resumes with formatting issues.
Most Indian software engineers at TCS, Infosys, Wipro, and Cognizant have resumes optimized for service company hiring — listing technologies, project names, and responsibilities. Product companies evaluate resumes completely differently. They want to see impact, scale, and problem ownership.
This guide walks you through exactly how to restructure your resume for product company ATS systems, how to write bullets that make recruiters stop scrolling, and what specific elements FAANG and Indian unicorn recruiters look for.
In this guide
Service Company Resume vs Product Company Resume
The fundamental difference: service companies care about technologies you've touched; product companies care about problems you've solved and the scale at which you solved them.
| Dimension | Service Company Resume | Product Company Resume |
|---|---|---|
| Bullet style | "Worked on microservices using Spring Boot" | "Reduced checkout API P99 latency by 340ms (62%) by rewriting synchronous service calls to async using Kafka, handling 2M daily active transactions" |
| Focus | Technologies used, tools, frameworks | Impact, scale, ownership, problem solved |
| Project names | Client/project name ("Citibank digitization") | What the system does + scale ("Payment processing pipeline for 15M users") |
| Team/role | "Team size: 12 members" | "Led 3-engineer team to deliver X in 8 weeks" |
| Metrics | Rare or absent | Mandatory — latency, throughput, cost savings, user impact, revenue |
| Format | Often 2–3 pages, verbose | 1–2 pages max, dense, white space intentional |
ATS: The First Filter You Must Pass
ATS (Applicant Tracking Systems) — used by Greenhouse, Workday, iCIMS, and Lever at most product companies — parse your resume before any human sees it. A poorly formatted resume can score 0% on ATS even if you're perfectly qualified.
ATS Do's
- Use standard section headers: "Work Experience", "Education", "Skills" (not creative alternatives like "My Journey" or "Technical Arsenal")
- Single-column or simple two-column layout only — no text boxes, tables for content, or headers/footers
- Standard fonts: Calibri, Arial, Garamond, Times New Roman, Georgia (10–12pt body, 14–16pt name)
- Save as .docx or PDF (PDF is fine for most modern ATS; .docx is safer for older systems)
- Include keywords from the job description verbatim — ATS does exact and fuzzy matching
- Spell out acronyms once: "React.js (React)" or "Kubernetes (K8s)"
ATS Don'ts
Tables for layout · Images or icons · Headers and footers with contact info · Text boxes · Graphics · Two-column layouts with parallel columns · PDF created from Canva/Figma (often image-based) · Fancy section dividers · Custom bullet symbols that don't parse
Keyword Strategy
For each job application, run this process:
- Copy the job description into a text doc
- Identify 10–15 technical keywords (languages, frameworks, tools, methodologies)
- Check which ones appear in your resume — add missing ones if genuinely applicable
- Make sure key phrases appear in context, not just in a skills dump
Common high-value keywords for Indian product company roles:
Resume Format and Structure
Page Length — Settled Once and For All
| Experience | Page Length | Why |
|---|---|---|
| 0–2 years (fresher) | 1 page | Not enough signal to justify more; pad = red flag |
| 2–5 years | 1 page | Product companies prefer dense and impactful over comprehensive |
| 5–10 years | 1–2 pages | Include only the last 3–4 roles; drop old irrelevant work |
| 10+ years | 2 pages max | Focus on last 7 years; earlier roles can be one-liners |
Section Order
For experienced engineers (3+ years):
- Contact Information
- Summary (optional — only if you have 8+ years or are making a significant career pivot)
- Work Experience
- Skills
- Projects (if relevant and impressive)
- Education
For freshers / 0–2 years:
- Contact Information
- Education (college, branch, CGPA if 7.5+)
- Projects (2–3 strong ones)
- Skills
- Internships / Work Experience
- Achievements (competitive programming, hackathons)
Writing Impact Bullets — The STAR Method for Resumes
Every bullet in your Work Experience section should follow this structure:
Before / After Examples
Worked on the backend API for the e-commerce platform using Java Spring Boot and MySQL. Responsible for maintaining the existing codebase and adding new features as per requirements.
Rebuilt product catalog API in Java Spring Boot with Redis caching layer, cutting average response time from 1.2s to 180ms (85% reduction) and supporting 50K RPS during peak sale events on a 12M-SKU catalog.
Developed microservices for the banking application. Collaborated with team members and delivered features on time. Used Docker and Kubernetes for deployment.
Decomposed monolithic fund transfer service into 4 independent microservices (auth, ledger, notification, audit), containerized with Docker/Kubernetes on AWS EKS; reduced deployment cycle from 4 hours to 12 minutes and enabled per-service horizontal scaling.
Worked on machine learning pipeline for client. Responsible for data preprocessing and model training. Used Python and scikit-learn.
Built real-time fraud detection ML pipeline in Python (scikit-learn + PySpark) processing 8M transactions/day; achieved 97.2% precision at 0.3% false positive rate, preventing an estimated ₹18Cr/year in fraudulent transactions.
Strong Action Verbs for Engineers
Responsible for · Worked on · Involved in · Assisted with · Helped · Participated in · Contributed to
Section-by-Section Breakdown
Contact Information
- Name (large, bold, top of page)
- Phone (Indian format: +91 XXXXX XXXXX)
- Professional email (firstname.lastname@gmail.com — not funky handles)
- LinkedIn URL (customize it: linkedin.com/in/yourname)
- GitHub URL (if you have meaningful public repos)
- City, India (no full address needed)
Passport size photo · Date of birth · Gender · Marital status · Father's name · Religion or caste · Aadhaar number — these are standard on service company resumes but signal to product companies that you're unfamiliar with their culture.
Work Experience
- Format: Company Name | Role Title | City | Month Year – Month Year
- 3–5 bullets per role for recent positions; 1–2 for older roles
- Start with your strongest bullet (not chronological within the role)
- Every bullet should have a metric — if you don't have one, estimate and say "estimated" or "approximately"
- Don't include NDA-protected client names at service companies; describe the domain instead ("a tier-1 Indian bank's retail lending platform")
Education
- Include: Degree, Branch, College, Year of Graduation, CGPA (only if 7.0+)
- For IIT/NIT/BITS: mention it prominently — it's a strong signal at Indian product companies
- For non-tier-1 colleges: make your skills and impact sections stronger to compensate
- If 5+ years of experience: education can go below Experience
- Don't include 10th/12th marks — this is an Indian service company convention that looks out of place
Projects
- Include only if they demonstrate real system building: side projects, open source contributions, or academic capstone projects
- 2–3 projects maximum; each with a 1-line description + 1-line tech stack + 1-line impact/scale
- GitHub link is mandatory for projects — without it, product company reviewers will be skeptical
- If your projects are CRUD apps, don't include them — they subtract more than they add
Skills and Keywords Section
The Skills section is your ATS keyword zone. Organize it by category, not as a random list. But only include skills you can genuinely speak to in an interview — interviewers often start by asking about something from your Skills section.
Recommended format:
- Languages: Java, Python, Go, JavaScript/TypeScript
- Frameworks: Spring Boot, React, Node.js, FastAPI
- Databases: PostgreSQL, MySQL, Redis, MongoDB, Cassandra
- Infrastructure: AWS (EC2, S3, Lambda, RDS), Docker, Kubernetes, Terraform
- Messaging: Apache Kafka, RabbitMQ, AWS SQS
- Tools: Git, Jenkins, GitHub Actions, Datadog, Splunk, Grafana
| Technology | Include? | Why |
|---|---|---|
| Technologies you use daily | Yes | Strong signal, safe to discuss in interview |
| Technologies you've used in projects | Yes | Relevant, can discuss at medium depth |
| Technologies you've only read about | No | Will be exposed in interview, damages credibility |
| MS Office / Excel | No | Not relevant for software engineering roles |
| Outdated tech (Struts, SVN, COBOL) | Context only | Only if the role specifically requires it |
| Soft skills ("team player", "leadership") | No | Demonstrate in bullets, don't list as skills |
Full Resume Sample (Mid-Level Engineer, 4 Years)
- Redesigned loan disbursement API using asynchronous Kafka pipeline, reducing end-to-end processing time from 8 minutes to 42 seconds for 35,000 daily transactions
- Led migration of legacy Oracle monolith to PostgreSQL + Redis microservices for the loan origination module; improved query performance by 70% and reduced infrastructure cost by ₹1.2Cr/year
- Built auto-scaling Kubernetes deployment on AWS EKS handling 10× traffic spikes during festive seasons with zero downtime (previously: 3–4 outage incidents per quarter)
- Mentored 2 junior engineers; conducted 15+ technical interviews; authored internal wiki used by 40-person team
- Implemented claims auto-adjudication engine in Java Spring Boot processing 2M claims/month; reduced manual review queue by 60%
- Automated regression test suite with JUnit + Mockito + TestContainers, achieving 78% code coverage and cutting QA cycle from 5 days to 6 hours
- Built a distributed key-value store in Go implementing Raft consensus protocol; supports 50K ops/sec, fault-tolerant up to N/2 node failures
- Real-time stock screener using WebSockets + Redis Pub/Sub serving 1,200 concurrent users with <50ms update latency
Final Checklist Before Submitting
ATS Format
Single or simple two-column layout, no tables for content, no images, standard font, saved as .docx or PDF (not image-based).
Every bullet has a metric
Go through each bullet — if there's no number, add one. Latency, throughput, users, cost, percentage improvement, time saved.
Tailored to the job description
Have you added the key technical terms from the JD into your resume? Don't send the same resume to every company without customization.
No photos, DOB, gender, or personal details
Product companies (especially with FAANG-style hiring) will find these unprofessional or even concerning from a bias-avoidance standpoint.
LinkedIn matches your resume
Recruiters cross-check LinkedIn. Dates, titles, and companies must be consistent. Update your LinkedIn headline to the role you're targeting.
GitHub links work
If you've listed projects with GitHub links, click each link on your final PDF to confirm they open correctly and repos are public.
Proofread for spelling and grammar
Product companies value attention to detail. One typo doesn't disqualify you; multiple typos signal carelessness. Use Grammarly as a pass.
10 Resume Mistakes Indian Engineers Make When Applying to Product Companies
| # | Mistake | Fix |
|---|---|---|
| 1 | Listing client project names instead of describing the system | Replace "Citibank KYC project" with "KYC verification system for 2M retail bank customers" |
| 2 | Putting a photo and personal details | Remove everything except name, email, phone, LinkedIn, city |
| 3 | "Responsible for" and "worked on" bullets | Rewrite with action verbs + metrics |
| 4 | Listing every technology you've ever touched in Skills | List only what you can discuss for 10+ minutes in an interview |
| 5 | 3+ page resume for 4 years of experience | Compress to 1 page, 2 at absolute maximum |
| 6 | Objective statement that says "looking for a challenging role" | Delete it or replace with a 2-line summary showing your strongest achievement |
| 7 | Including 10th and 12th marks | College degree only; CGPA only if 7.0+ |
| 8 | Generic skills like "MS Office", "communication", "team player" | Remove all soft skills and irrelevant tools from skills section |
| 9 | Not customizing for each application | Spend 15 minutes adding JD keywords for each application |
| 10 | LinkedIn not updated to match the resume | Keep both in sync — especially titles, dates, and accomplishments |
A Great Resume Gets You the Interview — We'll Help You Ace It
Prepflix's structured program prepares Indian engineers for every round at product companies — DSA, system design, behavioral, and mock interviews with an Ex-Microsoft, IIT Kanpur mentor.
Start Your Prepflix Journey →Frequently Asked Questions
Should my software engineer resume be 1 page or 2 pages in India?
For 0–5 years of experience: 1 page. For 5–12 years: 1–2 pages. For 12+ years: 2 pages max. Product companies and FAANG in India overwhelmingly prefer concise, dense resumes over padded multi-page ones.
Do Indian product companies use ATS to screen resumes?
Yes. Google, Microsoft, Amazon, Flipkart, PhonePe, and most product companies use ATS. Your resume must be ATS-compatible: single-column or simple two-column layout, standard fonts, no tables/images, and keyword-rich content matching the job description.
What format should I use for my software engineer resume in India?
Use a reverse-chronological format. Sections in order: Contact info → Summary (optional) → Work Experience → Skills → Projects → Education. For freshers: flip Projects and Education before Work Experience.
How do I write resume bullets that get noticed at product companies?
Use the STAR format: Accomplished [X] as measured by [Y] by doing [Z]. Lead with action verbs, include specific metrics (latency, throughput, cost, revenue), and quantify impact wherever possible. Avoid weak phrases like "responsible for" or "worked on."
Should I include my current CTC or expected CTC in my resume?
No. Never include salary information in your resume. It anchors recruiters before they've evaluated your fit, and product companies don't expect it. Salary discussions happen during or after the offer stage.
I'm at a service company with NDA client names — how do I write my experience?
Describe the domain and scale without naming the client: "Tier-1 Indian private bank's retail lending platform serving 8M customers" instead of "HDFC Bank." Focus on what you built and the impact — not who you built it for.
Is a summary/objective section useful on an Indian software engineer resume?
For 5+ years of experience or a significant career pivot (e.g., service to product), a 2-line summary can be helpful. For most mid-level engineers, skip it — your most impactful bullet from Work Experience tells a better story.