Ian Klosowicz
Almost every job has numbers hiding in it. You can put metrics on accomplishments you think weren't measurable by estimating volume, frequency, time, or money instead of waiting for a tracked KPI that may never exist.
Most resumes from people without formal analyst experience read like a list of job duties. "Assisted customers." "Managed inventory." "Trained new staff." None of that tells a recruiter anything about scale, speed, or impact. And the reason people write it that way isn't laziness. It's that they genuinely believe their work wasn't measurable because no one handed them a dashboard with their name on it.
That belief is costing them interviews.
I hear this constantly from people trying to break in. They have 5 years of real work experience and they're writing one-line bullets that could describe anyone. The numbers were always there. They just weren't labeled "metrics" by anyone in charge.
A recruiter reading "managed a team" and "managed a team of 12" processes those 2 bullets completely differently. The second one answers a question. The first one raises one.
Numbers do 3 things on a resume that words alone can't:
For someone breaking into data analytics specifically, this matters even more. You're applying for roles where your entire job will be turning raw information into meaningful numbers. A resume that doesn't demonstrate you can think in numbers is a problem before you even get to the interview.
Start here. Before you try to quantify any specific bullet, run each job through these 4 lenses. Most people find numbers in at least 2 of them immediately.
Volume is the most common and easiest to recall. How many? How often? How much?
Time is the second lens. How fast? How long? What changed?
Money is the most attention-grabbing lens, but also the one people assume they don't have. Most do.
Percentage or rate is the most analytical lens and the one that plays best on a data analyst resume. What changed, and by how much?
You won't always have exact percentages from memory. That's fine, which is why the next section exists.
Estimates on a resume are not dishonest. Every finance team uses estimates. Every analyst builds models on assumptions. The standard is reasonable and defensible, not perfect and audited.
Here's how to build an honest estimate for a resume bullet.
Start with what you do remember. You may not know the exact number, but you probably remember whether it was "a lot" or "not that many." That's a range. Work from the range.
For example: you managed the morning shift at a coffee shop and you roughly remember being slammed. Was it 50 customers? 100? You probably remember whether it took 3 minutes per order or 5. If it was a 4-hour rush and you were processing roughly 1 customer every 2 to 3 minutes, that's 80 to 120 customers. Write "100+" or "80 to 120" depending on what you remember leaning toward.
Use conservative estimates consistently. Round down, not up. "Processed approximately 80 transactions per shift" sounds more credible than "over 200 transactions per shift" if a recruiter pushes back in an interview and the real number was 90. You want to be able to defend it.
Look for documentation you already have. Old emails, performance reviews, scheduling records, sales reports you still have screenshots of, even a text to a coworker asking about numbers. Many people are surprised by what they can find when they actually look.
If you genuinely can't estimate a number without fabricating it, don't include it. That bullet either stays qualitative or gets cut. The goal is honest quantification, not manufactured credibility.
When I built the Analyst Hive curriculum, one of the things I had to think through was how to help people find numbers in jobs that weren't analytical by title. It came up constantly. 125,000 people on LinkedIn asking some version of "my job doesn't have metrics, how do I quantify anything?" The answer is almost always in volume, time, or money, once they start looking for it.
Here's what this looks like in practice. These are the kinds of rewrites that turn a generic resume into something a recruiter stops on.
Retail / customer service
Before: "Helped customers find products and resolve complaints."
After: "Handled 80 to 100 customer interactions per shift, resolving complaints at the register with a same-day resolution rate above 90% and no escalations in 6 months."
Food service / hospitality
Before: "Managed tables and coordinated with kitchen staff during dinner service."
After: "Managed 6 to 8 tables during peak dinner service, turning covers every 45 minutes across a 120-seat section, with consistent order accuracy above 95% per shift."
Warehouse / logistics
Before: "Processed shipments and maintained inventory accuracy."
After: "Processed 150 to 200 inbound shipments per shift across 4 product categories, maintaining inventory accuracy at 99%+ over an 8-month period."
Administrative / office
Before: "Managed scheduling and handled communications for the team."
After: "Managed scheduling for a team of 14, coordinating 30+ meetings per week and reducing double-booking incidents by roughly 80% after building a shared calendar system."
Training / supervision
Before: "Trained new employees on company procedures."
After: "Onboarded and trained 11 new hires over 18 months, reducing average time-to-full-productivity from 3 weeks to under 2."
Notice what happened in every rewrite. The job didn't change. The scope of the work didn't change. All that changed is that the bullet now answers: how many, how fast, how consistently, and with what outcome.
If you're working through this process alongside building your full resume for a data analyst application, the Analyst Hive program covers resume quantification as part of the resume module in month 1. It's at analysthive.io.
This is where well-intentioned people go wrong and end up worse off than before they added any numbers at all.
Don't fabricate exact figures you can't defend. "Increased sales by 34%" when you have no idea what the actual number was is a trap. An interviewer who asks "how did you measure that?" will expose it in 30 seconds. Estimates you can reason through out loud are fine. Invented precision isn't.
Don't add numbers that make you look smaller than you were. "Served 3 customers per hour" in a quiet boutique is accurate, but if you were also managing inventory, training staff, and handling vendor calls, that one metric undersells the role. Pick the numbers that reflect the full scope.
Don't pad bullets to hit a metric quota. Some bullets are legitimately qualitative. "Maintained a calm, professional tone during high-stress escalations" is better as a clean statement than a stretched attempt at "resolved 100% of escalations calmly." The latter sounds made up even if it's true.
Don't use percentages without a baseline. "Improved accuracy by 15%" begs the question: from what? "Improved order accuracy from 88% to 99% over 3 months" tells a complete story. The baseline is what makes the percentage meaningful.
Don't forget that ranges are acceptable. "80 to 100 calls per day" is more honest and just as strong as "100 calls per day" when the actual number varied. Recruiters understand that jobs have variability.
What if I genuinely don't know the numbers from an old job?
Start with what you do remember: roughly how busy were you, how many people were involved, how long did things take? Build an estimate from memory and use conservative language like "approximately" or "80 to 100." If you can reach an old manager or find old records, do that first. If not, a defensible estimate beats a vague bullet every time.
Is it okay to use approximate numbers on a resume?
Yes. Approximations are standard practice, not dishonesty. Use ranges ("40 to 60 tickets per week") or qualifying language ("approximately 200 orders per shift") to signal that you're estimating. The only line to stay on the right side of is whether you could explain your reasoning out loud in an interview without flinching.
What if my job had no measurable outcomes at all?
That's rarely true. The 4 lenses in this post (volume, time, money, rate) apply to almost every role. If none of them surface anything, look at the scope of your responsibility: how many people, accounts, locations, or dollars were you adjacent to? Even proximity to a number is more useful than a qualitative-only bullet.
Do I need numbers on every bullet point?
No. Aim for at least 1 metric per job entry, ideally 2 to 3 of your strongest bullets. The rest can stay qualitative if they're genuinely stronger that way. A resume with 3 excellent metric bullets is better than one where every bullet has a stretched number stapled to it.
Will an ATS care about numbers in my resume bullets?
ATS systems primarily scan for keywords, not numbers. But the human recruiter who reads after the ATS pass will notice immediately whether your bullets are quantified. Numbers also improve your chances of being cited by AI tools that extract resume highlights for recruiters. The audience for your numbers is the human, not the machine.
How specific should the numbers be?
Specific enough to be credible, not so specific that they require documentation you don't have. "Approximately 150 shipments per shift" is more credible than "147 shipments per shift" if the second number came from rough memory. Round to the nearest sensible unit and use hedging language when exact recall isn't possible.
If you're building your full application package for a data analyst role, Analyst Hive walks you through resume, LinkedIn, portfolio projects, and interview prep on a day-by-day schedule. It's built for people breaking in without a traditional analytics background. Join at skool.com/analysthive/about.
