Last Tuesday, I was sitting in my home office in Pune, cup of chai going cold beside my laptop, when I opened a resume that made me actually put my head in my hands. This person had twelve years of experience at some genuinely impressive companies. They had led teams, shipped products, won internal awards. And their resume? It was three pages long, used four different fonts, had a photo from what looked like a wedding, and opened with the line "I am a hardworking and dedicated professional seeking new challenges." I wanted to reach through the screen and shake them.
Look, I have been reviewing resumes for over a decade now. I have seen thousands. And honestly, the gap between what people think makes a good resume and what actually gets you interview calls is enormous. So let me share what I have learned, not from reading articles about resume writing, but from being the person on the other side of the table, the one deciding in six seconds whether your application goes in the "yes" pile or the "not right now" pile.
Stop Sending the Same Resume Everywhere
I know this sounds like a lot of work. It is. But here is the thing - when I open a resume and the skills section perfectly mirrors the job description we posted, I notice. When someone has rearranged their experience to highlight the stuff that matters for our specific opening, I notice that too. And when someone sends a generic resume that talks about "diverse skill sets" and "proven track records" without any connection to what we actually need? That goes into the pile of five hundred other generic resumes.
The trick is not to rewrite your entire resume from scratch each time. That would be insane. Keep a master document with everything you have ever done. Then for each application, pull out the bits that matter most. Rearrange your bullet points so the relevant ones come first. Swap out a few skills. Tweak your summary. Twenty minutes per application, maybe thirty. That is all it takes, and the difference in response rates is shocking. I am not going to throw out a specific number because it varies so much by industry, but I have seen people go from zero callbacks to landing three interviews in a week just by doing this one thing.
The ATS Problem Nobody Explains Properly
Everyone tells you to "optimise for ATS." Fine. But most people have no idea what that actually means in practice. So let me break it down simply.
An Applicant Tracking System is basically software that reads your resume before any human does. Big Indian companies like Infosys, Wipro, TCS, and pretty much every MNC uses one. The software scans your resume looking for keywords that match the job description. If it does not find enough matches, your resume gets filtered out. A real human never sees it. This is not some kind of conspiracy theory. It is just how hiring works at scale when you have six hundred applicants for one position.
So what do you actually do about it?
- Use normal section headings. "Work Experience" not "My Professional Journey." "Education" not "Academic Adventures." Seriously, I have seen both of those.
- Copy keywords straight from the job posting into your resume. If they say "data analysis using Python," write "data analysis using Python" somewhere in your resume. Not "coding" or "programming" - the exact phrase.
- Do not put important information inside images, text boxes, headers, or footers. The ATS often cannot read those.
- Stick with a simple, clean format. One column. Standard fonts. No fancy design templates from Canva. I know they look pretty, but they are resume killers when it comes to ATS parsing.
- Save as PDF or DOCX. Nothing else.
That said, I want to be honest - I am not totally sure how every ATS handles every format. They are all different. Some are more sophisticated than others. But the advice above works for the vast majority of systems you will encounter in the Indian job market.
Your Summary Needs to Actually Say Something
Can we please, collectively as a nation, agree to stop writing "Seeking a challenging position where I can utilise my skills and grow professionally"? Every time I read that line, a small part of me dies. It says nothing. It could be written by anyone about any job.
Your summary should be three or four lines that tell me who you are, what you have done, and why I should care. Here is an example of one that actually worked on me recently: "Backend engineer with 5 years building payment systems at scale. Built the UPI integration at [company] that processes 2 lakh transactions daily. Strong in Java, microservices, and system design. Looking to take on architecture-level challenges." That is it. Short. Specific. I immediately knew this person could do the job we were hiring for.
Compare that to "Experienced software professional with strong problem-solving skills and a passion for technology." Which one would make you want to keep reading?
Numbers. Put Numbers on Things.
"Managed a team" means nothing. "Led a team of 8 engineers, delivered a product redesign 2 weeks ahead of schedule, resulting in a 28% increase in user retention" - now that tells me something. I cannot stress this enough. The single fastest way to make your resume stronger is to go through every bullet point and ask yourself: can I put a number here?
How many people were on the team? What was the budget? By how much did things improve? How many clients did you work with? Even rough numbers are better than no numbers. "Reduced customer complaint resolution time from roughly 48 hours to about 12 hours" is way better than "improved customer service processes."
And before you say "but my job does not involve numbers" - yes it does. Every job does, somehow. If you are a content writer, how many articles did you write per month? What was the traffic? If you are in HR, how many people did you hire? What was the offer acceptance rate? If you are a teacher, how many students? What were the results? Think harder about it. The numbers are there.
Formatting: Less is More
I once received a resume printed on pink paper with a decorative border. For a finance role. At a bank. I am not making this up.
Your resume does not need to be beautiful. It needs to be readable. Clean. Professional. The recruiter looking at it should be able to find what they need in seconds, not minutes. Here is what works: one column layout, consistent font (I personally like Calibri or Inter, but Arial is fine too), clear section headings with a bit of space between sections, and bullet points that are one to two lines each. That is really it.
For most Indian professionals with under ten years of experience, one page is enough. I know that feels limiting when you have done a lot, but trust me on this - a tight one-pager beats a sprawling two-pager almost every time. If you have fifteen-plus years of experience and genuinely need two pages, fine. But be ruthless about what makes the cut. That internship from 2009? Probably time to let it go.
A Note About Design Templates
I see a lot of resumes now that use those trendy two-column designs with a sidebar for skills and a photo and colourful progress bars showing "Python: 80%" or whatever. These look great as screenshots on Instagram. They perform terribly in actual hiring processes. The ATS mangles them. Recruiters find them harder to scan quickly. And those skill progress bars? Nobody takes them seriously. What does "80% Python" even mean? Compared to whom?
Stick with simple. I know it feels boring, but boring gets interviews.
Your Skills Section is Probably Wrong
I see two common mistakes with skills sections. The first is listing skills that are so generic they add nothing. "Communication." "Teamwork." "Problem-solving." "Microsoft Office." Unless the job specifically asks for these (and even then), they are filler. Everyone claims these skills. They do not differentiate you at all.
The second mistake is listing every technology or tool you have ever touched, even if you used it once for a college project three years ago. If someone puts "Machine Learning" on their resume and I ask them about it in an interview and they say "well, I did one Coursera course," that is worse than not listing it at all. It feels dishonest.
What works better: be specific and be honest. Instead of "Microsoft Excel," write "Advanced Excel - pivot tables, VLOOKUP, conditional formatting, macros." Instead of "digital marketing," write "Google Ads, Meta Ads Manager, Google Analytics 4, SEMrush." Group your skills into categories if you have enough of them - Technical Skills, Tools, Platforms, that kind of thing. And only include skills you could actually demonstrate or discuss in an interview without breaking into a sweat.
Action Verbs Matter More Than You Think
There is this weird default mode people go into when writing resumes where everything becomes "was responsible for" and "was involved in" and "duties included." These phrases are passive. They are vague. And they make it sound like things happened around you rather than because of you.
Switch to active verbs. "Built." "Led." "Designed." "Reduced." "Launched." "Negotiated." "Grew." Each bullet point should start with a strong verb that tells me exactly what you did. Not what your team did. Not what your department did. What you did. Hiring managers want to hire people who take ownership, and the language you use on your resume signals whether you are that person or not.
One more thing on this - use different verbs for different bullet points. If every line starts with "managed," it gets monotonous and I start to wonder if you actually did different things or just had one job with slightly different flavours.
Certifications - Be Strategic, Not Exhaustive
The certification landscape in India right now is wild. You can get certified in almost anything from a dozen different platforms. And I have seen resumes where people list fifteen or twenty certifications, most of which are those three-hour LinkedIn Learning courses that, let us be real, do not carry a lot of weight.
What actually impresses me: certifications that are hard to get and relevant to the role. AWS Solutions Architect. Google Cloud Professional. PMP. CFA. The NPTEL courses from IITs, especially the ones with proctored exams. Scaler or upGrad programmes that involve actual projects. Even some of the better Coursera specialisations from top universities are worth listing.
But that free "Introduction to Excel" certificate from 2019? Leave it off. Five relevant certifications beat twenty irrelevant ones every single time. And always include the issuing body and the date. A certification without a date looks like you are trying to hide when you got it, which makes me suspicious.
LinkedIn and Your Resume Need to Match
This is something that catches people off guard. About eight out of ten recruiters I know check your LinkedIn profile after looking at your resume. And when the two documents tell different stories - different dates, different job titles, missing roles - it raises questions. Are they lying on one of them? Did they forget? Are they sloppy?
Put your LinkedIn URL on your resume. Make it a custom URL - linkedin.com/in/yourname, not the random string of characters LinkedIn generates by default. Make sure your LinkedIn summary expands on your resume summary rather than contradicting it. Your job titles and dates should match exactly. Use LinkedIn to add the stuff that does not fit on a one-page resume: project details, recommendations from colleagues, articles you have written, volunteer work.
And please update your LinkedIn photo. If it is a cropped group photo from a friend's birthday party, change it. You do not need a professional headshot - just a clean, well-lit photo where you look approachable and professional. First impressions count, even digital ones.
Proofread Like Your Career Depends on It
Because it kind of does. I rejected a resume last month from someone who misspelled the name of the company they were applying to. In their cover letter. That is an extreme example, but smaller mistakes happen all the time and they all leave the same impression: this person does not pay attention to details.
Here is my proofreading process, which I recommend to all my clients. First, finish your resume and walk away for at least a few hours. Come back with fresh eyes. Second, read it out loud - you will catch awkward phrasing and errors your eyes skip over when reading silently. Third, read it backwards, sentence by sentence. This breaks the flow enough that your brain actually processes each sentence instead of auto-filling what it expects to see. Fourth, run it through Grammarly or a similar tool. Fifth, and this is the most important one, give it to someone else. Ideally two people - one person in your industry who can check the content, and one person outside your industry who can check whether it is clear and readable to a normal human being.
Print it out if you can. Errors show up differently on paper than on screens. I do not know why. But they do.
"A resume is not your autobiography. It is a highlight reel. Every line should make the reader think 'I want to talk to this person.'"
I sometimes wonder if we overcomplicate this whole thing. At the end of the day, a good resume is clear about who you are, specific about what you have done, and honest about what you can do. It does not try to be everything to everyone. It does not use fifty-rupee words when five-rupee words will do. It respects the reader's time.
I have been doing this work for twelve years now, and the resumes that stick with me, the ones where I read them and immediately want to pick up the phone, they are never the flashiest ones. They are the ones that feel real. Where I can picture the actual human being behind the bullet points. Where someone took the time to think about what they genuinely bring to a team, not just what sounds impressive.
Maybe that is the most important tip of all, and it is not really a tip so much as a reminder. Your resume is not a test. It is an introduction. Treat it like one.
I still think about some of the resumes I have read over the years. The ones that got it right. The ones that did not. I think about the twelve-year veteran with the wedding photo and the four fonts, and I wonder if they ever fixed it, if someone sat them down and explained what was going wrong. I hope so. There was a good career story in there, buried under all that noise. There usually is.
Comments