The resume is the only thing standing between you and an interview at Swiggy, Razorpay, or Google India. Yet most Indian software engineer resumes either cram everything into a template that ATS systems cannot parse, use vague bullet points that convey nothing ('responsible for backend development'), or list skills that turn into liabilities the moment an interviewer asks about them. This guide covers the format that gets shortlisted, how to write bullet points that quantify impact, which skills to list (and which to remove), and specific guidance for freshers, mid-level engineers, and senior engineers.
The format that consistently gets shortlisted at Indian product companies: (1) One page for 0-5 years of experience. Two pages for 6+ years only if the content genuinely requires it. Indian recruiters scan a resume in 6-10 seconds: a dense, well-organised one page is always preferable to a sparse two-page document. (2) Reverse chronological order (most recent experience first), not functional or skills-based formats. Indian ATS systems (Taleo, Workday, Greenhouse) parse reverse-chronological formats reliably; functional resumes are often partially lost. (3) Section order for experienced engineers: Header (name, phone, email, LinkedIn, GitHub, no photo, no date of birth, no gender, no full home address, no marital status, no references). Skills. Work experience (most important section). Projects (if you have meaningful projects beyond your day job). Education. Certifications (if relevant). For freshers or engineers with less than 2 years of experience: put Education immediately after the header, before skills and experience. (4) Typography: Arial, Calibri, or Garamond at 10-11pt. Margins 0.5-0.75 inches. Single column (not multi-column): ATS systems scan left to right, top to bottom; a multi-column layout can result in content from the right column being inserted mid-sentence from the left column. No tables, text boxes, images, or icons, as all of these cause ATS parsing failures.
The XYZ formula (from Google's recruiting guidelines): 'Accomplished [X] as measured by [Y] by doing [Z].' Before and after examples: Weak: 'Worked on the search feature.' Better: 'Improved search relevance and latency.' Strong: 'Reduced search API p99 latency from 340ms to 90ms by replacing a full-table scan with a composite index on (user_id, created_at, is_deleted) and adding Redis caching for the 10% of queries that account for 70% of traffic, serving 2 million daily searches.' What makes a bullet strong: (1) Starts with an active verb in past tense (reduced, built, designed, migrated, automated, eliminated, implemented, not 'responsible for', 'helped with', 'worked on', or 'involved in'). (2) Quantifies impact specifically (latency in ms or percentile, throughput in requests/second, cost reduction in Rs or percentage, user count affected, deployment frequency, error rate reduction). (3) Names technology specifically (Redis specifically, not 'caching'; Kafka specifically, not 'message queue'; PostgreSQL specifically, not 'database'). (4) Communicates scale (if you can say 'serves 5 million requests per day', 'processes Rs 500 crore in daily transactions', or 'manages 10TB of data per week', do so: scale differentiates senior from mid-level candidates). What to do if you have no metrics: estimate conservatively and be prepared to explain the estimate in an interview. A specific estimate ('reduced load time for 150,000 daily active users') is always more credible than a vague statement ('improved performance for users').
The skills section is a commitment: every item is fair game in an interview. A skills section with items you cannot speak to fluently is worse than a shorter, accurate section. What to include: Programming languages (only languages where you are comfortable being asked to write code in an interview). Frameworks (React/Next.js, FastAPI/Django, Spring Boot, Express.js, listed specifically, not 'web frameworks'). Databases (PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, Cassandra, only ones you have used in production or can discuss the query model and performance characteristics). Cloud platforms (AWS with specific services: EC2, S3, RDS, Lambda, ECS, SQS, CloudFront; 'AWS' alone is too vague at senior level). DevOps tools (Docker, Kubernetes, Terraform, GitHub Actions, ArgoCD, Jenkins). What to remove: Microsoft Office or Google Workspace (baseline competencies, not engineering skills). Programming languages from your 2019 college course that you have not used since (you will be asked about them). Vague terms like 'problem-solving', 'teamwork', 'communication' (soft skills do not belong in the skills section; demonstrate them in bullet points). Tools you have used only superficially. The ideal skills section length: 6-12 specific, accurate items that you can confidently discuss for 5-10 minutes each.
Fresher resume priorities (0-2 years experience, campus placement): Projects are the most important section. Aim for 2-4 projects with: a one-sentence description of what the project does, the technology stack (specific, not 'web technologies'), one specific technical challenge you solved ('Implemented optimistic locking to prevent concurrent booking conflicts' is specific; 'solved a hard database problem' is not), and a GitHub link. Good project ideas for freshers: full-stack web app with user authentication and a database (proves you can connect the layers), a REST API with pagination and filtering built in FastAPI or Express.js (proves backend fundamentals), a React app with state management (Context or Zustand) that calls a public API (proves frontend skills), or a ML project trained on a public dataset with a web interface for inference (proves ML basics). Competitive programming credentials (Codeforces Expert 1600+ or Specialist 1400+, CodeChef 3-star, LeetCode top 5% or 500+ problems solved): include your handle and rating/count. Open-source contributions (one merged PR to a well-known project): include the repository link and a one-sentence description of what your PR fixed or added. This is worth more than most projects.