How to Highlight Achievements on Your Resume Effectively

How to Highlight Achievements on Your Resume Effectively

By Rajesh Kumar

So a resume lands in front of a recruiter and the first thing they’re hunting for, whether they’d put it this way or not, is some sign you did anything other than occupy a chair. That’s the whole game in one sentence. Most resumes don’t pass it. They describe the chair beautifully. The person who sat in it stays invisible.

I’m going to skip the parts of resume-writing everybody already lectures you about. Fonts, margins, whether your name goes left or centre, the one-page-versus-two argument that nobody ever wins. None of that here. Just one section, the achievements, which on most Indian resumes barely exists, and which decides more callbacks than all the formatting put together. If you fix only this, you’ve fixed the thing that actually matters.

responsibilities versus achievements, and why nobody tells them apart

A responsibility is the thing they hired you to do. It’s the job description, more or less copied off the offer letter. “Managed a team of ten.” “Handled client accounts in the west.” “Prepared monthly reports.” Anyone holding your designation would have done these. They describe the post, and they say nothing about you.

An achievement is what happened because it was you in the seat and not the next person on the shortlist. Reports got out faster. Your team didn’t fall apart. A region that was bleeding cash stopped. That’s the difference a recruiter is actually scanning for, even the ones who couldn’t define it if you asked.

Here’s the part that gets people. Both versions can describe the exact same workday. “Prepared monthly reports” and “cut report turnaround from a week to two days by reworking how the data got pulled” might be the same person, same desk, same job. One reads as a task. The other reads as a result. You didn’t change what you did, only which half of it you put on the page.

And almost every resume I see gets the ratio backwards. Maybe eighty percent responsibilities, twenty percent achievements, when it wants to be the other way round. Sales executive, software engineer, HR person, doesn’t matter, the disease is the same one. People list what they were supposed to do and call it a record of what they did.

why a number does the heavy lifting

“Improved customer satisfaction” is a claim. You wrote it, so of course you’d say that. Now compare it with “lifted customer satisfaction by reworking how complaints got handled, so the average gripe got resolved in a couple of days instead of dragging on for a week,” which is a different animal. Suddenly there’s something to picture. A before, an after, and the thing you actually changed in the middle. The recruiter doesn’t have to take your word for it because you’ve shown your working.

(I’d add one warning right here, because it’s the whole reason this post exists. Quantify honestly. A rough, true number beats a precise, invented one every single time, and invented ones have a way of falling apart the second an interviewer asks a follow-up. If you genuinely don’t know whether it was a week or ten days, say “roughly a week” and move on. Don’t manufacture “reduced resolution time by 38.4 percent.” Nobody measures their own work to one decimal place, and a panel that’s been hiring for years can smell a made-up figure across the table.)

The good news is that almost every job throws off measurable outcomes if you go looking. IT, manufacturing, banking, retail, logistics, the lot. Trouble is never that the work can’t be counted. It’s that nobody ever taught you to hunt through your own years for the numbers that were sitting there the whole time.

finding achievements when you swear you don’t have any

This is where most people stall out completely. “I just did my job, there’s nothing impressive in it.” Maybe. Probably not. There’s a handful of questions I run a resume through, role by role, and they tend to shake something loose.

First one. When did somebody thank you? Think back to any moment a manager or a client or even a colleague said, in actual words, that you’d done well. Something triggered that. Whatever project or mess sat behind that compliment is almost always an achievement hiding in plain sight. Say your manager once thanked you for saving a client who was halfway out the door. The line on the resume isn’t “handled escalations.” It’s something like “talked a major account back from cancelling and got them to renew.” Same event. One version is a duty, the other is a save.

Second. When did you fix something that was broken? Every workplace is full of broken things, slow processes, errors that keep coming back, a system everyone complains about and nobody touches. If you were the one who touched it, that’s an achievement. Worked a support desk and dragged the average ticket from sitting around for two days down to a few hours? That’s not routine. Call it what it is, a thing you improved, with a before and an after.

Third, and this one’s looser. When did you go past what the job asked? Hit a target that was meant to be a stretch. Finished early. Carried more than your role technically required while someone was out. Nobody hands you a trophy for any of that, which is exactly why it never makes it onto the resume, and exactly why it should.

Then there’s the performance reviews, and honestly, this one’s hit or miss. (Plenty of reviews are so vague they’re useless. “Meets expectations across all parameters” tells you nothing about anything.) But if there’s a comments box, dig through it. Sometimes you’ll find a phrase you forgot about, “handled the migration well” or “consistently ahead on quarterly numbers,” and each one is a thread you can pull on until an actual achievement comes out.

Do this for every job you’ve held. Write the raw, ugly answers down first, don’t polish them yet. You’ll end up with more than you thought you had. People always do.

STAR, but squeezed

Situation, Task, Action, Result. You’ve heard of it, everybody has. On a resume the trick is throwing most of them away. A bullet is one line. It can’t carry a four-part story. So you keep the Action and the Result, keep a sliver of Situation for context, and bin the rest.

The full spoken version of something might run: the project was weeks behind when you took it over, you split the team in two and got the client to drop a couple of features that didn’t matter, and it shipped ahead of the redrawn deadline so the company dodged a penalty. Four sentences. Fine for the interview, where you’ve got air to breathe.

On a resume that same thing is one line. “Took over a project running weeks late, restructured the team and renegotiated scope with the client, and delivered ahead of the revised deadline.” That dodged penalty could go in if you actually know the number, left out if you don’t. Same information, roughly a quarter of the words. Compression like that is a skill, and like most skills it’s annoying the first few times and automatic after that. Practise it on the raw notes you just made.

the verb you open with

The first word of a bullet sets everything after it. “Was responsible for” is dead on arrival, it’s passive, it’s the offer letter talking, and it tells the recruiter nothing about whether you actually moved anything. “Led,” “built,” “cut,” “rebuilt,” those words have a hand on the wheel from the first syllable.

Rough buckets, if it helps. Things you made: built, designed, launched, set up, created. Anything you grew takes increased, expanded, grew, scaled. Stuff you fixed wants cut, reduced, resolved, reworked, simplified. Running people gives you led, managed, coordinated, mentored. And figuring things out leans on analysed, identified, assessed, forecasted. You don’t need all of them, you need the most exact one. “Led a team of twenty-five engineers” beats “managed a team,” because “led” and the actual headcount are both doing work. Pick the verb that earns its spot and drop the rest.

where this is almost too easy: sales

Sales is the gift industry for this, because everything’s already measured before you even sit down to write. If you’re in sales and your resume still reads like a list of chores, there’s genuinely no excuse, the numbers were handed to you every quarter.

Take the weakest possible line: “Managed sales for the north region.” Now picture what it could say instead. Something like “grew north-region revenue by roughly half over two years and came in ahead of target.” Notice I’m not quoting you exact crore figures, because I don’t know your numbers and neither should you be inventing tidy ones, but you see the shape. A direction, a rough size, a comparison to what was expected. That’s the upgrade.

Or “responsible for acquiring new clients,” which is just the job description wearing a tie. The stronger version names a rough count and a segment, “brought in a few dozen new enterprise clients in the banking space and grew our share of that vertical.” Again, round it, keep it honest. “A few dozen” that’s true reads far better than “47” that you pulled out of the air.

Key accounts, channel partners, same treatment. “Managed key accounts” becomes “held onto almost all of a handful of large accounts while growing what each was worth through cross-selling.” The pattern repeats, but I’d rather you internalise the move than memorise a template, because a template applied to all eight bullets is its own kind of obvious. Vary it. Some lines lead with the number, some with the verb, some with the problem you solved.

IT and software, where people undersell on purpose

Engineers are strange about this. They’ll take a system they rebuilt from the studs and describe it as “worked on backend improvements.” I think it’s partly modesty and partly that the impressive part feels obvious from the inside, so it doesn’t occur to them to spell it out.

“Developed a web application using React and Node” is a fact, not an achievement. What did it do once it existed? If that self-service portal meant customers stopped flooding the support queue, say so, “built a self-service portal that cut support tickets by a good chunk.” Put automated testing in and watch the thing stop falling over so often, and that’s “added automated testing and brought the crashes way down,” not “fixed bugs.” And “worked on cloud migration” is hiding an actual story, “moved a load of our applications off the old servers onto the cloud and got deployments happening far more often, daily instead of once a month or whatever it was.”

If you write code for a living, go open your resume right now and check whether you’ve done the “worked on backend improvements” thing. I’d put money on it being in there somewhere.

marketing

Marketing sits in an awkward middle. The numbers exist, they’re sitting in some analytics dashboard or a campaign report, but they don’t fall into your lap the way sales figures do. You have to go pull them.

“Managed the company’s social media” is the weak one, naturally. The stronger version points at growth and, ideally, at what the growth did, “grew the Instagram following several times over with a focused content push, and a real chunk of sales started coming through social.” “Worked on SEO” becomes “got a stack of target keywords ranking on the first page, and organic traffic climbed a lot as a result.” Keep the figures rough and real. “Traffic climbed a lot” with a true story behind it is fine. A precise percentage you can’t defend is a trap you’re setting for yourself.

operations, manufacturing, HR

Operations is straightforward once it clicks. “Responsible for plant operations” is the chair again. The achievement version talks about capacity going up and waste coming down, maybe a long safety streak if you had one, “lifted output meaningfully through leaner processes while cutting waste, with no lost-time injuries for a couple of years running.” Supply chain’s the same idea, “consolidated the supplier list down to about half its size, which cut procurement costs and actually improved on-time delivery.” (Two birds, and recruiters love the lines where the obvious tradeoff didn’t happen.)

HR I’ll be straight about: it’s the hardest function to do this for. So much of the work is relational and refuses to become a number. How do you quantify “made the place less miserable to work at”? You mostly can’t. Reach instead for whatever metrics do exist, time-to-hire, retention, how many people you trained, engagement scores if your company even bothers to track them. And plenty don’t, especially the smaller outfits where that data was never collected in the first place. If that’s you, lean on scale and on specific outcomes you can actually point at. “Recruited a large batch across several business units and brought the average time-to-hire down by about half” works even without a perfectly audited figure behind it. Honest and roughly right beats precise and invented. That rule never stops applying.

where these lines go on the page

Placement matters more than people think, because recruiters don’t read, they scan, and the top third of the page eats most of the attention before anyone’s properly concentrating.

If you’ve got a summary up top, park your two or three best achievements there. Inside each role, lead with the achievement, not the duty, the first bullet under a job title should be the best thing you did in it. Four bullets to a job? Make three of them achievements and let one stay a responsibility for context. Senior people with long histories can sometimes get away with a small “career highlights” block near the top, three to five of the biggest things across every role, so a recruiter gets the impact before they’ve waded into the chronology. It’s not for everyone, but for the right CV it works.

awards, and the process stuff that travels everywhere

An award with no context is half an award. “Received Star Performer Award” tells me nothing, because I don’t know if that went to one person or to forty percent of the floor. Give it the frame, “Star Performer for the quarter, given to a small slice of the sales team,” and now I understand how hard it was to get. The selectivity is the achievement, not the certificate.

Process improvements deserve their own mention because they belong to every function, not just the obvious ones. Redesigned a workflow that cut turnaround, automated something tedious, standardised a procedure so the same mistake stopped happening, all of it counts and every employer quietly values it. The shape is always the same: the verb, the thing you changed, then roughly what shifted because of it. Big company, mid-size firm, three-person startup, the pattern doesn’t care where you work.

leadership, which isn’t about the headcount

If you’ve managed people, the resume question isn’t whether you managed them. Obviously you did, it’s in the title. The question is what those people pulled off because you were the one running them. So not “managed a team of twenty-five engineers” but something closer to “built a twenty-five-person engineering team from nothing and got it shipping reliably.” Their output is your achievement. Headcount is just the setting.

Mentoring counts here too, and people forget it. If you brought along a batch of juniors and a good number of them got promoted, or a couple went on to run their own teams, that says your effect outlasted your own desk. Which is, when you think about it, most of what leadership is supposed to mean.

The whole thing comes down to one stubborn habit. Pull the achievements out of the work you’ve already done, find the rough true numbers, squeeze them into action-then-result lines, and put the best ones where the eye lands first. A recruiter clocks the difference in about ten seconds, and those ten seconds are the only ones you’re getting. So the question worth sitting with isn’t whether your resume lists what you were responsible for. It almost certainly does. What’s worth asking is whether anyone reading it could tell that the job was done by you and not by whoever held the post before you. Could they?

– Rajesh Kumar