[{"data":1,"prerenderedAt":11},["ShallowReactive",2],{"$fLaQcZBr6530AubQHYWniJ3LPMviLODiV3fsfqMRNqWQ":3},{"slug":4,"title":5,"description":6,"date":7,"author":8,"content":9,"excerpt":10},"show-dont-tell-how-to-quantify-your-achievements-on-a-resume","Show, Don't Tell: How to Quantify Your Achievements on a Resume","Generic resumes list duties. Good ones prove you can actually do the job. Here’s how to dig up the numbers and metrics hiding in your work history.","2026-03-10","Resume Workshop","\u003Cp>Last week, a friend sent me her resume. She’s a project manager, been at it for about four years. The document was clean, well-formatted, no typos.\u003C/p>\n\u003Cp>It was also totally forgettable.\u003C/p>\n\u003Cp>Every bullet point started the same way. \u003Cem>Responsible for... Led a team of... Managed the budget for...\u003C/em>\u003C/p>\n\u003Cp>I texted her back: “This reads like someone copied the job description from your company’s internal wiki. Where’s the stuff you actually \u003Cem>did\u003C/em>?”\u003C/p>\n\u003Cp>She got a little defensive, which I get. It’s hard to write about yourself. But here’s the thing: a resume that just lists what you were supposed to do doesn't tell me if you were any good at it.\u003C/p>\n\u003Cp>Anyone can “manage a budget.” Did you blow through it in March? Or did you stretch it to get three extra projects done by December?\u003C/p>\n\u003Cp>That’s the difference between telling and showing.\u003C/p>\n\u003Ch3>Why Your Brain Defaults to Boring\u003C/h3>\n\u003Cp>We fall into the “responsibilities” trap because it’s safe. It’s verifiable. You \u003Cem>were\u003C/em> responsible for that thing. HR put it in your offer letter.\u003C/p>\n\u003Cp>But hiring managers? They’re skimming. They’ve got a stack of 200 resumes and a coffee that’s gone cold. They’re looking for a reason to put yours in the “maybe” pile.\u003C/p>\n\u003Cp>If all they see is a list of duties, they have to guess whether you were good at them. And people, honestly, are lazy. They won’t guess. They’ll just move on.\u003C/p>\n\u003Ch3>The “So What?” Test\u003C/h3>\n\u003Cp>Here’s a trick I use when I’m coaching people. Write down everything you did at your job. Just rough notes. Then, for each line, ask yourself: “So what?”\u003C/p>\n\u003Cul>\n\u003Cli>“I wrote weekly newsletters.” So what? \u003Cem>The open rate went from 18% to 34% over six months.\u003C/em>\u003C/li>\n\u003Cli>“I trained new hires.” So what? \u003Cem>New reps were handling calls on their own two weeks faster than before.\u003C/em>\u003C/li>\n\u003Cli>“I answered customer support tickets.” So what? \u003Cem>My customer satisfaction score was 97% last quarter, top on the team.\u003C/em>\u003C/li>\n\u003C/ul>\n\u003Cp>See the shift? The first part is the duty. The second part is the \u003Cem>impact\u003C/em>. That’s where the numbers live.\u003C/p>\n\u003Ch3>Where to Find the Numbers (Even if You’re Not in Sales)\u003C/h3>\n\u003Cp>People freeze when I say “quantify your achievements.” They think, \u003Cem>I don’t work with spreadsheets all day. I don’t have numbers.\u003C/em>\u003C/p>\n\u003Cp>You’ve got more than you think. You just haven’t looked at your work through this lens before.\u003C/p>\n\u003Cp>\u003Cstrong>Size and scale.\u003C/strong> Even if you didn’t track performance metrics, you probably know scope. “Handled customer complaints” becomes “Resolved 40+ customer issues per week.” “Organized company events” becomes “Coordinated quarterly all-hands meetings for 150+ employees.”\u003C/p>\n\u003Cp>\u003Cstrong>Improvements and efficiencies.\u003C/strong> Did you change a process? Did it save time? Even ten minutes a day adds up. “Created a new filing system” becomes “Cut document retrieval time by roughly 20 minutes per search, saving the team about 5 hours a week.”\u003C/p>\n\u003Cp>\u003Cstrong>Money.\u003C/strong> This one scares people, but don’t overthink it. Did you help a client choose a more expensive plan? Did you process invoices? Did you catch a billing error? “Assisted with vendor contracts” becomes “Identified duplicate vendor payments, recovering about $4k in erroneous charges.”\u003C/p>\n\u003Cp>\u003Cstrong>The “attaboy” evidence.\u003C/strong> Performance reviews, emails from happy clients or frustrated bosses who turned grateful. I knew a guy who dug through his old emails and found a note from a client saying he’d saved their launch after the agency dropped the ball. That’s a story. That’s a bullet point.\u003C/p>\n\u003Ch3>One Line, Two Versions\u003C/h3>\n\u003Cp>Let’s look at how this plays out on the page.\u003C/p>\n\u003Cp>\u003Cstrong>Version A (The Teller):\u003C/strong>\u003C/p>\n\u003Cblockquote>\n\u003Cul>\n\u003Cli>Managed social media accounts for the company.\u003C/li>\n\u003Cli>Assisted with the launch of new product line.\u003C/li>\n\u003Cli>Worked with the engineering team to fix bugs.\u003C/li>\n\u003C/ul>\n\u003C/blockquote>\n\u003Cp>\u003Cstrong>Version B (The Shower):\u003C/strong>\u003C/p>\n\u003Cblockquote>\n\u003Cul>\n\u003Cli>Grew Instagram engagement by 30% in Q3 through a shift to user-generated content.\u003C/li>\n\u003Cli>Coordinated cross-functional launch of the X200 headphone line; sold out within 48 hours.\u003C/li>\n\u003Cli>Triaged an average of 15 weekly bug reports, prioritizing critical fixes for the dev team.\u003C/li>\n\u003C/ul>\n\u003C/blockquote>\n\u003Cp>Version B isn’t fancier. It’s not using bigger words. It’s just \u003Cem>specific\u003C/em>. It paints a picture. You can see the person doing the work.\u003C/p>\n\u003Ch3>What If You Don’t Have the Exact Number?\u003C/h3>\n\u003Cp>Don’t lie. That’s stupid. You’ll get caught in the interview when they ask you to walk through it.\u003C/p>\n\u003Cp>But estimation is fine. Round numbers. Use ranges. “Saved the team roughly 10 hours a month.” “Increased upsells by about 15-20%.”\u003C/p>\n\u003Cp>If you have zero data? Start collecting it now. For your current job, pick two or three things you do regularly and track them for a month. How many calls? How many words? How many problems solved? You’ll have numbers for your next resume, and you might learn something about where you’re actually spending your time.\u003C/p>\n\u003Ch3>A Note on “Culture Fit” and Soft Skills\u003C/h3>\n\u003Cp>People ask me: “How do I quantify things like leadership or teamwork?”\u003C/p>\n\u003Cp>You don’t, really. Not directly.\u003C/p>\n\u003Cp>What you do is quantify the \u003Cem>result\u003C/em> of that leadership. “Mentored three junior associates; two were promoted within 18 months.” That’s leadership. That’s a number.\u003C/p>\n\u003Cp>Or: “Stepped in to mediate conflict between design and product teams, unblocking a feature that shipped two weeks late instead of two months.” That’s teamwork (and conflict resolution, and probably a drink after work).\u003C/p>\n\u003Ch3>The Gut Check\u003C/h3>\n\u003Cp>When you’re done rewriting, read your resume out loud.\u003C/p>\n\u003Cp>Does it sound like a person talking about work they actually did? Or does it sound like a corporate robot reciting a job description?\u003C/p>\n\u003Cp>If you stumble over a line, cut it. If you get bored halfway through a bullet point, rewrite it.\u003C/p>\n\u003Cp>Your resume isn’t a list of everything you touched for the last five years. It’s a marketing document. The product is you. And the only way to convince someone to buy is to show them what happens when you turn the machine on.\u003C/p>\n\u003Cp>Stop telling them you’re good at your job. Show them.\u003C/p>\n\u003Chr>\n\u003Cp>\u003Cem>Want to create a professional resume? Try our \u003Ca href=\"/builder\">free resume builder\u003C/a> today.\u003C/em>\u003C/p>\n","Last week, a friend sent me her resume. She’s a project manager, been at it for about four years. The document was clean, well-formatted, no typos. It was also totally forgettable. Every bullet point...",1773508966110]