How to Write a Resume for Indian Companies vs. MNCs

The biggest mistake Indian job seekers make is treating all employers the same. They write one resume and send it everywhere — to IT services companies, to startups, to MNCs, to PSUs — hoping something sticks.

It doesn't work. Not because the experience isn't good enough, but because different companies look for fundamentally different things. The same set of skills and experiences, framed differently, can be compelling to one type of employer and mediocre to another.

Here's the breakdown by company type, what each values, and how to frame your resume accordingly.

The four types of employers in India

Indian IT Services companies (TCS, Infosys, Wipro, HCL)

What to emphasise on your resume:

• List your technology stack prominently in a dedicated Skills section at the top
• Name the domains you've worked in (banking, insurance, e-commerce, healthcare)
• List any client names you've worked with if you're allowed to — it signals domain familiarity
• Certifications get their own section — AWS, Azure, Oracle, SAP, Salesforce all carry weight here
• Include CGPA or percentage if it's above 7.0/70% — IT services companies filter on this, especially for freshers
• Mention team size in roles: "worked in a team of 12" or "onsite coordination with US client"

MNCs and global companies

What to emphasise on your resume:

• Every bullet point answers: what did you do, at what scale, with what result
• Quantify aggressively: users, requests per second, cost reduction %, revenue generated, time saved
• Show ownership: "Led the design of..." not "Contributed to..."
• Technical depth matters: algorithms, system design, architecture decisions
• Remove fluff: no "team player", no "strong communication skills" — use the space for achievements
• Keep it to one page if under 8 years of experience

Indian startups and product companies

What to emphasise on your resume:

• Highlight any 0→1 experience: built a product, started a team, created a process from nothing
• Show breadth: startups want people who can work across the stack or function
• Side projects, open source, and personal builds are highly valued — include them
• Mention company stage context: "Joined as the 8th engineer, grew to 40" signals you're comfortable with early-stage
• Leadership without authority: "Coordinated with design and product to deliver..." shows cross-functional work
• Outcomes over responsibilities — what shipped, what grew, what you saved

The one thing that applies to all four

No matter who you're applying to, your resume needs to clear the ATS before any human reads it. That means the right keywords, the right format, and a score that gets you past the filter. The framing changes by company type. The keyword matching requirement does not.

The practical workflow for any application:

• Identify the company type (services vs. product vs. startup vs. MNC)
• Read the job description carefully — what does it emphasise?
• Check your ATS keyword score against that JD
• Adjust your summary and skills section to match the JD's language
• Reframe 2–3 bullet points in your experience to match what this company type values

That's 15–20 minutes per application. The candidates who do this get callbacks at 3–5x the rate of those who don't.