TCS, Infosys & Wipro Resume Format: What Indian IT Recruiters Expect

The TCS resume format that clears screening in 2026 is a reverse-chronological, single-column document with your degree written in full (Bachelor of Technology, not B.Tech), CGPA shown with its scale, a substantial projects section for anyone under two years' experience, and an explicit notice period line — because TCS, Infosys and Wipro filter on exactly those fields, both in Naukri Resdex and in their own portals.

India's biggest IT services employers hire at enormous volume — campus batches plus continuous lateral hiring — so their screening is more mechanical than most. Recruiters and vendor teams scan for keywords, degree names, CGPA cutoffs and notice period before anything else gets read. Format your resume to make those checks instant, and you stop losing offers to formatting noise.

This guide covers the conventions specific to Indian IT services; if you're a fresher building from scratch, pair it with our complete fresher resume format guide, which walks the whole document section by section.

How Do TCS, Infosys and Wipro Actually Screen Resumes?

Three layers matter, and each reads different fields:

1. Naukri Resdex / internal database search: recruiters search by keyword, experience band, location and notice period before opening any file.
2. Applicant tracking / hiring portals: TCS iBegin, Infosys careers portal and Wipro's system parse your upload into structured fields — degree, skills, dates — and match them against the requisition.
3. Human review: often just 30–60 seconds per profile during bulk drives, checking eligibility (degree, percentage/CGPA, gap history) and relevance.

The practical consequence: your resume must survive keyword search, structured parsing, and a fast human skim simultaneously. That rules out creative templates entirely — the ATS keywords by industry list shows which technical terms these systems weight heavily for IT services roles.

Why Full Degree Names Beat Abbreviations

This is the single most common Indian resume mistake that costs matches. Screening systems and requisitions store degrees as "Bachelor of Technology", "Bachelor of Engineering", "Master of Computer Applications". If your resume says only B.Tech, B.E. or MCA, string-matching can fail even though you're qualified.

The pattern: full name first, abbreviation in brackets. Both humans and parsers get what they need. Include your specialisation branch — "Computer Science and Engineering" matters when the requisition specifies it. For lateral roles, also spell out certifications fully: "AWS Certified Solutions Architect – Associate", never just "AWS certified".

What about percentages and backlogs?

List Class X and XII scores only when applying as a fresher — mass recruiters still check them against eligibility criteria. Never hide backlogs; if cleared, "all backlogs cleared in first attempt" pre-empts the question. Once you have 2+ years' experience, drop school details entirely and keep only the degree.

How Should You Display CGPA?

• Show the scale explicitly: "CGPA: 8.4/10" — different universities use different scales, and 8.4 alone is ambiguous.
• Add the percentage conversion if favourable: "CGPA 8.4/10 (≈84%)" helps recruiters matching old eligibility criteria like "60% throughout".
• Above ~7.0: always display it; it clears most mass-recruiter cutoffs instantly.
• Below cutoff: omit the number but keep the degree — hiding education entirely triggers rejection faster than a modest score.
• Lateral applicants: CGPA stops mattering after about three years; experience keywords take over.

Campus placement resumes follow stricter one-page discipline — our TPO-focused campus placement resume guide covers that variant, including mini-project framing under deadline pressure.

Why Projects Carry So Much Weight in IT Services Hiring

Indian IT services recruiters expect freshers and sub-two-year candidates to prove capability through projects, because early project work maps directly onto what you'll do: maintenance, testing, support, module development on client stacks. A strong projects section can outweigh thin internship history completely.

Each project should follow this structure:

• Title + one-line context: "Online Blood Bank Management System — final-year web application (Java, MySQL, JSP)".
• Your specific role: built the donor-module backend; designed the schema; wrote 40+ JUnit tests.
• Tech stack named exactly: versions where relevant (Spring Boot 3.x, React 18).
• Outcome or scale: users, records handled, accuracy, deployment — anything measurable beats nothing.
• Freshers: list 2–3 projects; laterals: keep one or two only if directly relevant to the target stack.

For deeper examples and wording patterns, see our dedicated guide to the projects section for IT fresher resumes.

The Notice Period Field: Small Line, Big Filter

Notice period is a hard filter in lateral hiring. Vendor recruiters shortlist by joinability windows — many requisitions demand joiners within 30–60 days, and profiles showing 90 days may never surface regardless of fit.

• Serving notice: "Notice Period: 30 days (serving, last working day 15 Oct 2026)" — precision signals professionalism.
• Currently employed: state the real number ("90 days") rather than omitting; omission forces recruiter assumptions, usually pessimistic ones.
• Immediate joiner: say so prominently — "Immediately available" is a genuine advantage for backfill roles and deserves headline placement, not a footnote.
• On probation: "15 days' notice (on probation)" reads as highly flexible.

We cover every wording scenario — including buyout norms and how recruiters actually query this field — in the full notice period in resume guide.

Naukri Resdex Parsing Quirks You Must Work Around

Resdex doesn't just store your PDF — it parses your uploaded resume into searchable profile fields, and mismatches between the two cause silent misses:

• Key Skills field vs resume text: recruiters search the structured skills tags first. Keep your Naukri profile's key-skills list synced with your document — up to 30–50 tagged skills are allowed; use them.
• The headline is searched, ranked and displayed in results — mirror target titles there ("Java Full Stack Developer | Spring Boot · React · Microservices"). Our fresher resume headline examples show the formula.
• Total and relevant experience get parsed separately: label career gaps and non-IT stints clearly so "total experience" doesn't inflate while "relevant experience" reads as zero.
• Preferred locations must be set in profile settings, not just written inside the CV — search filters read the field, not your prose.
• Profile completeness and recent-update activity influence visibility in recruiter results — stale profiles sink. The systematic fix is covered in our Naukri profile optimization guide.
• Upload format: Naukri's own parser handles simple single-column Word/PDF layouts best; heavy tables and columns produce garbled skill tags that then misrepresent you in search.

The meta-point: your Naukri profile and your attached resume are two different artefacts evaluated by two different mechanisms. Optimise both, identically worded where it counts. The same tailoring logic applies everywhere — our walkthrough of tailoring a resume to a job description generalises the approach beyond Naukri.

The Section Order Indian IT Recruiters Expect

Deviations from this sequence slow down bulk screening, which is exactly what you can't afford:

1. Contact details + LinkedIn (+ headline mirroring target role)
2. Professional summary (2–3 lines, years + primary stack + domain)
3. Technical skills (grouped: languages, frameworks, tools, databases, cloud)
4. Work experience (reverse chronological, month-year dates, metrics per bullet)
5. Projects (freshers: above experience; laterals: below or trimmed)
6. Education (full degree names, institution, year, CGPA with scale)
7. Certifications (full official names, credential IDs, years)
8. Additional: notice period, preferred location, languages

Keep it to one page for freshers, two pages maximum laterally. Single column, standard fonts, no photos, no tables holding core content, no declaration lines with place-and-date signatures — those waste space modern recruiters don't read. The one exception to brevity: never compress skills into abbreviations-only lists; spell out each technology at least once.

Fresher vs Lateral: What Changes?

Lateral candidates should additionally mirror service-line vocabulary — "incident management", "change requests", "SLA compliance", "stakeholder coordination" — because support and maintenance requisitions screen on those phrases, not just coding skills. Freshers should emphasise training readiness: relevant coursework, hackathons, internships converted to offer letters.

Sample Summary Lines Built for IT Services Screening

Your summary must compress years, primary stack, and domain into two lines a bulk reviewer can process mid-scroll. Compare these patterns:

• Lateral (Java): "Java backend developer with 4 years in banking applications (Spring Boot, Microservices, Oracle). Owned 6+ production modules for a Tier-1 UK retail client, including an onboarding flow processing 50K applications monthly."
• Lateral (support/maintenance): "Application support engineer with 3 years on SAP MM incidents for manufacturing clients. Managed 40+ weekly tickets at 98% SLA compliance; ITIL v4 certified."
• Fresher: "Bachelor of Technology (Computer Science) graduate with internship experience in React front-end development. Built 3 full-stack academic projects deployed on AWS free tier; NQT-eligible."

Note the recurring elements: client names or tiers ("Tier-1 UK retail"), volume figures, SLA percentages, and stack keywords in requisition order. Indian IT services reviewers are trained to spot client-facing scope — naming it explicitly, even as "Fortune 500 banking client under NDA", adds credibility that generic duty descriptions never do.

Do Mass Drives and NQT Hiring Read Resumes Differently?

Yes — and it changes what you emphasise:

• Off-campus/NQT drives: eligibility gates run first (degree, CGPA cutoffs, graduation year, gap policy). Your resume's job is to make those five fields findable within seconds — which is exactly why full degree names and scaled CGPAs matter most here.
• Campus placements: TPO formats apply, one page is mandatory, and projects dominate since nobody has work history yet.
• Lateral hiring via Resdex: keyword search plus notice-period filters decide visibility before any human look.
• Contract-to-vendor pipelines: staffing coordinators skim for rate-relevant skills and immediate availability; joinability outranks polish.

The same document can serve all four if built to this guide's structure — you're adjusting emphasis, not architecture.

Submission Hygiene: Files, Emails and Portal Fields

Small mechanical details still trip up otherwise strong applicants:

• File name: "PriyaSharma_Java_Developer_4yrs.pdf" beats "resume_final_v7.pdf" — recruiters who download hundreds of files search their folders by candidate name.
• Portal fields override your PDF: if TCS iBegin asks for degree separately from upload, fill every structured field with identical wording to your document; mismatches flag applications for manual review, slowing them down.
• Email body matters: when applying by email (still common at smaller vendors), paste your summary + notice period + location into the body; attachments-only emails read as spam.
• One profile per company: duplicate registrations across TCS/Infosys portals cause application merges and rejections during verification.

Frequently Asked Questions

Should I include my photo on an Indian IT resume?

No. Unlike some European markets, Indian IT services employers neither expect nor want photos — they add file weight, confuse parsers, and expose you to bias-controlled screening practices adopted by larger firms.

Do I need a declaration line ("I hereby declare...")?

It's a legacy academic convention that mass recruiters ignore and modern portals mangle. Skip it; use the space for certifications instead.

How current CTC should I mention?

Never in the resume itself. Compensation discussions belong after interview stages — resume CTA figures anchor negotiations and can screen you out of bands you'd have accepted anyway.

Which Mistakes Get Indian IT Resumes Skipped?

• "B.Tech" with no expansion failing degree-string matches.
• CGPA without scale leaving recruiters guessing whether 8.0 means excellent or borderline.
• Skills listed once as bare acronyms — write "Structured Query Language (SQL)" style expansions for anything unusual; common tools are fine abbreviated after first mention.
• No dates on projects, making freshness unverifiable.
• Missing notice period, causing lateral profiles to be filtered out preemptively.
• Two-column designed templates that scramble into nonsense through Resdex parsing.

Every one of these is a five-minute fix — none requires new qualifications. That asymmetry is why mechanical correctness is the cheapest interview-landing lever available in mass-recruitment markets. Before your next application, run your document against the actual requisition text: JD2CV's job description matcher shows exactly which degree strings, skills and eligibility keywords your resume is missing.

One page or two for TCS-style applications?

Freshers: strictly one page. Laterals: two pages maximum, with everything decision-critical on page one — reviewers in bulk drives often never scroll further. If your second page contains only old roles from a decade ago, compress them into a single "Earlier career" line instead.

Do hobbies and languages belong on the resume?

Only when relevant: "Languages: English (fluent), Tamil, Hindi" helps for client-facing requisitions with regional requirements. Generic hobby lines ("reading, cricket, music") add nothing and cost a line you'll want back.

Key Takeaways

• Spell degrees fully with abbreviation brackets; show CGPA with its scale.
• Freshers lead with projects (2–3, tech stack + role + outcome); laterals lead with quantified ownership.
• State your notice period explicitly — it's a hard recruiter filter.
• Sync your Naukri key-skills tags, headline and resume text so search, parsing and human review all agree.

Want a template already structured to these conventions? Build your resume with JD2CV's ATS-safe resume templates for India — full-degree-name education blocks, grouped skills sections and clean single-column parsing built in, then check your match score against any TCS, Infosys or Wipro posting before you submit.