How to Write a Resume in India
The complete India-focused guide. Whether you are a fresher preparing for campus placements at TCS, Infosys, or Wipro, or a working professional switching jobs in Bangalore, Mumbai, or Hyderabad, this guide covers every section, every format choice, and every India-specific convention you need to get your resume past the ATS, past the recruiter scan, and into an interview.
In this guide
- 1. What a resume is for
- 2. Why writing for India is different
- 3. The standard Indian resume format
- 4. Every section explained
- 5. Chronological vs functional vs hybrid
- 6. Step-by-step: how to write yours
- 7. Length, file format, naming
- 8. By experience level
- 9. By role and industry
- 10. Common Indian-resume mistakes
- 11. Resume → ATS → Interview
- 12. Frequently asked questions
1. What a resume is for
A resume is not a biography. It is a one-page sales document with a single goal: secure an interview. Every section, every bullet, every keyword on it should serve that goal. In the Indian job market specifically, a resume passes through three gates before it earns an interview:
- An Applicant Tracking System (ATS) parses the file and scores it against the job description. Most resumes are filtered out at this gate. Read the complete ATS guide for how scoring works.
- A recruiter spends about 7 seconds scanning the shortlisted resumes for impact and fit. They pass the strongest 10–15 candidates to the hiring manager.
- A hiring manager reviews the recruiter shortlist and selects the candidates to interview. Your resume is read in seconds again, looking for specific signals that match the role.
Each of these gates rewards different things. The ATS rewards keyword density and clean parsing. The recruiter rewards quantified outcomes and quick scanning. The hiring manager rewards depth and proof of skills. A good Indian resume satisfies all three at once — which sounds hard but is actually a small set of concrete rules.
2. Why writing for India is different
Most resume advice on the open web is written for the US market — US salary benchmarks, US recruiter habits, US-specific conventions like extensive use of Excel-trained ATS systems. Indian hiring has its own rules. Writing as if you were applying in San Francisco produces a resume that lands fewer interviews here.
Indian platforms weight skill tags heavily
Naukri, LinkedIn India, and Hirect rank candidates by skill-tag overlap with the job criteria. A candidate with an explicit Skills section listing "Python, SQL, Excel, Power BI" out-ranks an equally qualified candidate who only mentions those tools inside experience bullets. US-style resumes that bury skills inside narrative text under-perform on Indian platforms.
CGPA and degree institute matter
Indian campus recruiters at TCS, Infosys, Wipro, banks, and consulting firms screen on CGPA and institute tier (IIT, NIT, BITS, top private engineering colleges, premier B-schools). For freshers and 0–3 year candidates, CGPA is non-optional. For senior candidates it can be omitted only after about 7 years of experience.
Projects often replace work experience
With approximately 1.5 million engineering graduates entering India's workforce each year, fresher resumes look similar on paper — same degree, same institute tier, same internships. Strong project content (Indian recruiters love quantified outcomes from real projects) is the single biggest differentiator at campus placements and product company recruiting.
English fluency is implicit but signalled
Almost every white-collar Indian role assumes English proficiency, but recruiters still scan resumes for fluency signals — clean grammar, no typos, professional vocabulary. A resume with grammatical errors is a fast rejection at consulting firms, MNCs, and product companies regardless of qualification.
Salary expectations are negotiated separately
Unlike some markets, Indian recruiters do not expect salary numbers on the resume itself. Salary discussion happens in the application form (if asked) or the screening call. Putting expected CTC on the resume signals inexperience and weakens negotiation flexibility.
Tier-1 cities concentrate the jobs
Bangalore, Hyderabad, Pune, Chennai, and the NCR (Delhi, Gurugram, Noida) hold over 70% of India's tech jobs. If you are open to relocating, list your current city plus "open to relocation" explicitly — it expands your applicant pool without diluting the resume.
3. The standard Indian resume format
For 90% of Indian job applications — IT services, product companies, banks, consulting, MNCs, startups — the safe format is single-column reverse-chronological in PDF. The section order below is the most common layout Indian recruiters see and parse cleanly:
- 1. Header — Name, phone, email, LinkedIn, city.
- 2. Professional Summary — 2–3 lines. Role + years of experience + 1–2 quantified achievements.
- 3. Experience — Reverse chronological, 3–6 bullets per role, quantified.
- 4. Education — Degree, institute, year, CGPA or percentage.
- 5. Skills — Explicit tools, languages, frameworks, certifications.
- 6. Projects — 2–4 projects (especially for freshers and product roles).
- 7. Certifications — Coursera, NPTEL, AWS, Google, Microsoft, domain-specific.
- 8. Achievements / Awards — Optional. Hackathons, scholarships, leadership roles.
- 9. Declaration — Optional. PSU/banking/government often expect it; private sector skip.
Freshers swap the order: Education and Projects move up, Experience moves down (or merges with Internships). Senior candidates with 7+ years can drop CGPA from Education and shrink the Education section to 2–3 lines.
See concrete templates and examples at fresher resume format, experienced resume format, and resume PDF format guide.
4. Every section explained
Each section has its own rules, its own ATS-parsing pitfalls, and its own India-specific conventions.
Header / contact
Plain text, top of page, single line if possible. Name in slightly larger font. Phone in 10-digit Indian format (no country code unless applying internationally). Professional email — firstname.lastname or initials, never "cooldude_42@gmail". LinkedIn URL (full URL, not "LinkedIn: yes"). City — full city name, not abbreviated. No photo, no date of birth, no marital status, no father's name (these are remnants from older biodata-style resumes that hurt parsing today).
Professional summary
2–3 lines. Role + years of experience + 1–2 specific achievements with numbers. For freshers: degree + institute + most relevant project or internship. The summary is the single most-read block on the resume — recruiters often decide to scan further or move on within these three lines. Avoid generic openers like "Hard-working professional with a passion for excellence". Lead with a number: "Data analyst with 3 years building reporting pipelines that cut weekly reporting time from 8 hours to 30 minutes".
Experience
Reverse chronological. Each role: company name, role title, location, dates (Month YYYY – Month YYYY or "Present"). Then 3–6 bullets per role. Each bullet: action verb, what you did, quantified outcome. "Built a Python data pipeline that reduced report generation time from 8 hours to 30 minutes, saving the team 32 hours per week." Most recent role gets the most depth (6 bullets), older roles taper down (3 bullets), oldest roles can be 1–2 bullets or just a one-line entry. Browse role-specific examples in the resume examples library.
Education
Degree, institute, year of graduation, CGPA or percentage. Indian recruiters at TCS, Infosys, Wipro, banks, IIM-style B-schools, and PSU expect CGPA — for fresher and 0–3 year candidates this is non-optional. Tier-1 institute names are signal: write them out (IIT Bombay, NIT Trichy, BITS Pilani, IIM Ahmedabad, ISB) rather than abbreviating. List in reverse chronological order — postgraduate first, then undergraduate, then 12th and 10th if relevant (often optional once you have a degree).
Skills
Explicit, scannable list. Group by category if you have many: Programming, Tools, Frameworks, Databases, Soft Skills. List the exact tools and languages the JD asks for — Naukri and LinkedIn India weight skill tags heavily, and Indian campus recruiters frequently shortlist by skills filter before reading the body. Skip generic claims like "Microsoft Office" — list the specific products and your level: "Advanced Excel (pivot tables, VLOOKUP, macros), PowerPoint, Outlook". Browse skills-section deep-dives at resume examples by role.
Projects
Especially important for freshers. Each project: name, 1-line description, tech stack used, quantified outcome, optional GitHub or demo link. Quantify even small projects — "Built a Python web scraper that tracked 50 Amazon product prices daily, deployed on Heroku" is concrete; "Developed a web scraping tool" is empty. Indian recruiters at product startups and IT services companies use project content as the primary differentiator between similar-credential candidates.
Certifications
Recognized certifications add credibility. Coursera, NPTEL, AWS Certified, Google Analytics, Google Data Analytics, Microsoft, AICTE-approved courses, Tally for accountants, SAP modules for ERP roles, ICAI for CAs, CFA, FRM, PMP, Six Sigma. Format: Provider, Certification Name, Year. Skip generic completion certificates from random websites — they signal weak judgment.
Achievements (optional)
Hackathon wins, scholarships, leadership positions (technical society president, sports captain, club lead at college), competition placements (Flipkart GRiD, KPMG case competition, HackerRank Top 5%). Quantify where possible — "Won 1st place at Flipkart GRiD 5.0 (2,000+ teams)". Achievements are particularly strong for freshers and 0–3 year candidates where they signal ambition and capability beyond pure academic record.
Declaration (optional, India-specific)
The declaration ("I hereby declare that the above information is true and correct to the best of my knowledge") is a leftover from the biodata-era Indian resume. Some PSU, government, banking, and traditional corporate roles still expect it. For private-sector, IT, product, and MNC applications it adds nothing — skip it and reclaim the page space for stronger content.
5. Chronological vs functional vs hybrid
Three resume structures exist; one of them works for most Indian applications.
Reverse chronological (use this)
Experience listed newest-first. The dominant format in India and globally. Recruiters expect it, ATS systems parse it cleanly, and it makes career progression instantly readable. Use this format unless you have a specific reason not to.
Functional (avoid)
Skills-grouped instead of role-grouped, with experience reduced to a list of company names and dates. Often used to mask employment gaps or career changes. Indian recruiters and most ATS systems treat functional resumes as a red flag — they signal "something is being hidden." Avoid except in unusual cases where you have a strong narrative reason.
Hybrid (acceptable for career switchers)
Reverse chronological work history plus a prominent skills-grouping at the top. Useful for genuine career changers — a software engineer pivoting into product management, a marketing manager pivoting into data — who want to surface relevant skills before the recruiter reads the older role titles.
6. Step-by-step: how to write yours
Ten steps, in order. The first time you write a resume this is roughly an hour of work. Subsequent edits for new applications are 15–30 minutes each.
- 1
Pick a single-column, ATS-safe template
Start with a clean single-column layout. Avoid Canva multi-column designs, sidebars, or icon-heavy templates — they look polished but break ATS parsing on Naukri, LinkedIn, and corporate HRMS systems used in India.
- 2
Add a contact block in plain text at the top
Name, phone (10-digit Indian format), professional email, LinkedIn URL, city. No photo (Indian recruiters do not need one and it can break parsing). No links to social media outside LinkedIn unless directly relevant.
- 3
Write a 2–3 line professional summary
Lead with your role and years of experience, then 1–2 specific achievements with numbers. Freshers replace experience with degree + standout project or internship. Surface the title you want, not just the title you have.
- 4
List experience in reverse chronological order
Company name, role title, location, dates (Month YYYY – Month YYYY). Then 3–6 bullets per role using strong action verbs and quantified outcomes. Most recent role gets the most bullets; older roles get fewer.
- 5
Add an Education section with India-specific fields
Degree, institute, year of graduation, CGPA or percentage. Indian recruiters at TCS, Infosys, Wipro, banks, and PSU expect CGPA. Tier-1 institute names are signal — write them out (IIT Bombay, NIT Trichy, BITS Pilani, IIM Ahmedabad) rather than abbreviating.
- 6
Build a dedicated Skills section
List the exact tools, languages, frameworks, and certifications the JD asks for. Naukri and LinkedIn India weight skill tags heavily — a candidate listing "Python, SQL, Excel, Power BI" explicitly out-ranks an equally qualified candidate who only writes those skills inside experience bullets.
- 7
Add Projects (especially for freshers)
For freshers, projects often replace work experience as the differentiator at TCS, Infosys, Wipro, and product startup recruitment. Include 2–4 projects with: 1-line description, tech stack, quantified outcome, optional GitHub or demo link.
- 8
List Certifications and relevant coursework
Certifications from Coursera, NPTEL, AWS, Google, Microsoft, or domain-specific (Tally, SAP, ICAI for accountants) are recognized by Indian recruiters. List provider, certification name, and year. Skip generic completion certificates.
- 9
Save as PDF with selectable text and a clean filename
Export as PDF (selectable text — verify by opening and trying to highlight your name). Filename format: FirstName_LastName_Resume.pdf. Avoid spaces, version numbers, or dates in the filename — recruiter inboxes treat them as suspicious.
- 10
Run an ATS check before you apply
Before submitting, paste the resume and the job description into a free ATS checker. The score breakdown shows missing keywords, format issues, and content gaps — fix them in minutes instead of finding out through silence weeks later.
Skip the manual work: Rezup's free AI resume builder walks you through the same ten steps with India-tuned prompts and ATS-safe templates. AI bullet rewrites are pay-as-you-go (₹1 per rewrite, no subscription).
7. Length, file format, naming
Length
One page for under 10 years of experience. Two pages maximum for senior professionals with more than a decade of work and substantive achievements at each role. Three-page resumes are penalised by recruiters and ATS systems alike — they signal padding rather than seniority.
File format
PDF by default. PDFs preserve layout exactly across recruiter screens and ATS platforms. Word documents reformat unpredictably. The only exception is when a portal explicitly requires DOCX — follow the portal's requirement. See the resume PDF format guide for export specifics.
Filename
FirstName_LastName_Resume.pdf is the safest format. Avoid spaces, dates, version numbers, or vague names like "final_v3.pdf". A clean filename reaches recruiter inboxes intact and signals professionalism. If you are tailoring per role, use FirstName_LastName_RoleName_Resume.pdf.
Font and spacing
Standard fonts (Calibri, Arial, Helvetica, Times New Roman, Georgia) at 10–11 pt body, 12–14 pt headings, name slightly larger. 0.5 to 0.75 inch margins. Adequate spacing between sections. The visual goal is fast scanning, not aesthetic flourish.
8. By experience level
Fresher (0 years)
Education up top with CGPA. Projects are the primary differentiator — invest 2–4 high-quality quantified projects. Skills section explicit. Internships if any. Certifications visible. Achievements section adds depth. The campus-placement fresher format is well-defined; follow the fresher resume format guide for the exact section order, content rules, and the optional declaration handling.
Early career (1–3 years)
Experience moves above Education. CGPA still listed in Education. Projects (work or personal) still strong differentiators, especially when transitioning roles or domains. Skills section explicit and JD-aligned. Each role gets 3–5 bullets quantified.
Mid career (4–7 years)
Experience is the hero section. Most recent role: 5–6 bullets. Earlier roles: 3–4 bullets. CGPA optional after 5–7 years. Projects optional unless directly relevant. Promotions, scope increases, and team-size details add weight. See experienced resume format.
Senior (8+ years)
Two-page resume acceptable. Most recent 2–3 roles get full bullet treatment; older roles condense to 1–2 lines or just titles. Education shrinks to 2–3 lines. Skills section emphasises leadership, strategy, and tools used at scale. Achievements include awards, publications, speaking engagements, board roles. Salary expectations remain off the resume.
9. By role and industry
Different roles emphasise different sections, content, and keywords. Sample resumes by role:
Software Engineer resume
Tech stack, projects, GitHub
Data Analyst resume
SQL, Power BI, dashboards built
Marketing resume
Campaigns, ROI, conversion lift
HR Executive resume
Hiring funnel, retention, HRMS
Fresher resume
Projects, CGPA, certifications
Product Manager resume
Outcomes, scope, frameworks
Accountant resume
Tally, GST, audits
Sales Executive resume
Quota, pipeline, conversion
10. Common Indian-resume mistakes
The same set of mistakes shows up in 40–60% of Indian resumes that fail to convert. Each is fixable in minutes:
- Multi-column or table-based layout. Looks tidy in Word, breaks parsing in every modern ATS. Switch to single-column.
- No Skills section, or skills buried in narrative. Naukri and LinkedIn India rank by skill tags. Build an explicit Skills section with the JD's exact keywords.
- Generic responsibilities instead of quantified outcomes. "Responsible for testing" is empty. "Tested 12 release builds across 3 microservices, reducing bugs by 40%" is signal.
- Including photo, date of birth, marital status, father's name. Biodata-era fields. Hurt parsing, add no value, occasionally introduce bias risk. Remove them.
- Long objective statement. "Seeking a challenging role in a reputed organisation where I can utilise my skills…" — empty. Replace with a specific 2–3 line professional summary.
- Vague filename like "Resume_Final_v3.pdf". Use FirstName_LastName_Resume.pdf.
- Salary expectations on the resume. Belongs in the application form or screening call. Putting it on the resume narrows recruiter flexibility and weakens negotiation.
- Spelling and grammar errors. Particularly damaging in MNCs, consulting, and product company applications. Run the resume through a grammar tool before submitting.
- Missing CGPA on a fresher resume. Indian campus recruiters expect CGPA. Omitting it is read as a low score being hidden.
- Unrealistic claims that fail in interviews. Inflated impact numbers, fabricated tools, exaggerated leadership. Indian interview panels probe deeply — claims that fall apart in a 30-minute conversation are more damaging than a less-impressive but defensible resume.
11. Resume → ATS → Interview
A great resume is the start of a pipeline, not the end. The same resume passes through three stages, and each stage has its own optimization rules.
Stage 1
ATS parsing & scoring
Your resume hits an Applicant Tracking System first. Format must parse, keywords must match the JD, score must clear the recruiter's shortlist threshold. Read the full ATS guide.
Stage 2
Recruiter scan
A human recruiter spends about 7 seconds on the first pass. They look for the keywords the ATS already flagged, role title match, company names, and quantified outcomes in the most recent role.
Stage 3
Hiring manager review
The recruiter forwards the strongest 10–15 candidates. The hiring manager spends 1–2 minutes reading depth, looking for proof of skills, scope of impact, and signals that match the team's specific needs.
Verify before applying: Run your resume against the actual job description on Rezup's free ATS checker to see your score and the specific issues to fix. Free, no signup, results in 30 seconds.
12. Frequently asked questions
How long should a resume be in India?
One page for under 10 years of experience. Two pages maximum for senior professionals with more than 10 years. Indian recruiters at Naukri, LinkedIn, and internal HRMS systems treat resume length as a quality signal — long resumes signal padding rather than seniority.
Should I include a photo on my Indian resume?
No, for most private-sector applications. Indian recruiters do not require a photo, and many ATS platforms have parsing issues with photos in the contact block. Government and PSU applications occasionally request a photo — follow that specific portal's spec rather than embedding in the resume PDF.
Do I need a Declaration section on my resume?
Optional, and increasingly skipped. The traditional declaration ("I hereby declare that the above information is true and correct to the best of my knowledge") is still expected at some PSU, banking, and government roles. For private-sector, IT services, and product company applications it adds nothing — skip it and reclaim the page space.
What is the standard resume format for Indian freshers?
Header (name, contact), Summary (2–3 lines), Education (with CGPA), Internships (if any), Projects (2–4 with quantified outcomes), Skills (explicit tools and languages), Certifications, Achievements, optional Declaration. Single column, 1 page, PDF format. Rezup's fresher format guide walks through each section.
Should my resume be in PDF or Word format?
PDF, by default. PDFs preserve layout exactly across recruiter screens and applicant tracking systems. Word documents reformat unpredictably. The only exception is when a portal specifically requires DOCX — follow that requirement.
How do I write a resume if I have zero work experience?
Lead with Education and CGPA, then Projects (treat them like work experience — quantify outcomes), then Internships if you had any, then Skills explicit, then Certifications. Strong project content with measurable outcomes is the single biggest fresher differentiator at Indian campus placements and product companies.
Should I include salary expectations on my resume in India?
No. Salary discussion belongs in the application form (if asked) or the recruiter screening call, not on the resume. Putting expected CTC on the resume narrows the recruiter's flexibility and weakens your negotiation position.
Do Indian recruiters care about a LinkedIn profile?
Yes. LinkedIn has over 130 million members in India and recruiters use it as the parallel discovery channel to your applied resume. Make sure your LinkedIn matches the resume claims — same titles, same dates, same skill tags. Mismatches between resume and LinkedIn are a common rejection reason.
The bottom line
A resume that works in India is not a long, decorated, biodata-style document. It is a tight one-page sales pitch with explicit skills, quantified outcomes, India-aware sections, and a clean PDF that survives ATS parsing. The rules are well-defined, the tools to verify them are free, and most candidates skip the verification step. You do not have to.