Nobody Cares What You Were Responsible For

The first resume I ever helped rewrite belonged to a woman named Sara. She'd spent four years as a customer service manager at a mid-sized e-commerce company, dealt with probably a thousand escalations, built the whole complaints tracking system from zero because the old one was a spreadsheet someone made in 2014. She was smart. She was good at her job.

Her resume said: "Responsible for managing customer service team and handling customer complaints."

Twelve words. Four years. I remember staring at it and not knowing where to start.

Here's the thing about "responsible for" — it tells me nothing about whether you were any good at it. Every person who ever held a job was responsible for something. The question is what you actually did with that responsibility. Sara had built a whole system. Her resume read like she'd answered some emails.

We rewrote it. Took about two hours. By the end it said: "Rebuilt complaints tracking system from a shared Excel file to a live database; reduced average resolution time from 9 days to 3.5; team handled 340% more monthly volume without adding headcount."

She got three callbacks the following week. First ones in four months.

I think about Sara a lot when people send me their resumes.

The 6-second thing is real, and it should make you uncomfortable

Ladders ran an eye-tracking study a few years back — they put recruiters in front of resumes and tracked where their eyes actually went. Six seconds. That's the average time before a recruiter decided whether a resume was worth reading or not. Six seconds is roughly how long it takes to read two sentences slowly.

I don't say this to stress you out. I say it because it changes how you have to write.

You are not writing a document that someone will sit with, coffee in hand, reading carefully from top to bottom. You're writing something that needs to survive a very fast scan. Which means the most important information has to be visible without effort. The reader shouldn't have to dig. If they have to dig, they won't.

Most resumes are written as if the reader has infinite patience and genuine interest in your life story. They don't. They have a pile. You're in the pile.

What your resume actually is

I've described this to a lot of people and the version that lands best is this: your resume is a marketing document, not an autobiography.

An autobiography says: here is everything that happened to me, in order, with context and nuance.

A marketing document says: here is the problem you have, here is evidence that I can solve it, here is why me over everyone else.

Those are completely different things to write.

When you write your resume as an autobiography — which is what most people do, because it feels honest — you end up including things that are true but useless. The internship from eight years ago that isn't relevant. The job title that doesn't convey what you actually did. The list of responsibilities that describes the role, not you.

When you write it as a marketing document, you ask different questions. Not "what did I do?" but "what did I accomplish?" Not "what was I responsible for?" but "what changed because I was there?"

Sara didn't just manage a customer service team. She cut resolution time by 62% and tripled throughput without growing headcount. Those are two completely different sentences about the same four years.

The summary at the top: stop writing objective statements

If your resume starts with something like:

"Seeking a challenging position where I can apply my skills and grow professionally."

Delete it. Delete the whole thing. That sentence says nothing except that you want a job, which is already implied by the fact that you sent a resume.

Objective statements were standard advice in the 1990s and they've been outdated for at least fifteen years. Nobody told the internet, apparently, because I still see them constantly.

What you want instead is a summary. And there's a real difference.

An objective statement is about what you want. A summary is about what you offer. Recruiters do not care what you want. They care what they need. Your summary should answer two questions, in three or four lines: who are you professionally, and what specifically can you bring to this role?

Here's a bad summary:

"Motivated and dedicated marketing professional with 5 years of experience looking to contribute to a dynamic team."

Every word of this is filler. Motivated. Dedicated. Dynamic. These are words people put in when they don't have anything specific to say. And "looking to contribute" puts you back in autobiography mode — it's about your goals, not their needs.

Here's a better one, for the same person:

"B2B content marketer with 5 years focused on SaaS companies. Grew organic traffic 180% at my last company through a mix of SEO restructuring and a LinkedIn strategy that now brings in about 40% of our inbound leads. Comfortable owning content end-to-end — strategy, writing, analytics."

Same experience. Completely different impression.

The other thing about summaries: customize them. Not completely — the bones can stay — but the specific things you call out should shift depending on the job. If you're applying somewhere that cares about SEO, lead with the SEO number. Applying somewhere that cares about brand voice, lead with the writing. The job posting tells you what they care about. Use that.

I know customizing feels like a lot of work. It is a little work. But you're competing against people who sent the same resume to 40 companies without changing a word. You don't need to be that much better than them. You just need to be slightly more relevant.

The before/after that changed how I think about this

I want to show you something more concrete because "results not responsibilities" sounds obvious when I say it but turns out to be genuinely hard to do.

Here are five real resume lines I've seen, and what they became after we worked on them.

Original: Assisted with social media management for company accounts. Rewrite: Grew Instagram following from 4,200 to 31,000 over 14 months; posts averaged 8.3% engagement rate vs 2.1% industry benchmark.

Original: Responsible for onboarding new employees. Rewrite: Redesigned onboarding program for 200+ annual new hires; cut average time-to-productivity from 11 weeks to 7.

Original: Managed inventory for retail store. Rewrite: Cut inventory shrinkage from 4.2% to 1.8% by implementing weekly cycle counts; saved approximately $43K annually.

Original: Handled customer inquiries and resolved issues. Rewrite: Maintained 94% customer satisfaction score across 1,200+ monthly interactions; escalation rate dropped 31% after I introduced a new triage protocol.

Original: Participated in product development process. Rewrite: Led UX research for three product releases; one feature I flagged in testing became the most-used in the app within 60 days of launch.

Notice what's happening in each rewrite. It's not just adding numbers — it's adding causation. Not just "I did X" but "I did X and here's what happened because of it." That's the whole shift.

How to find the numbers when you think you don't have any

The most common pushback I get when I tell people to quantify their achievements is: "I don't have those kinds of numbers. My job isn't really measurable."

Almost everyone says this. Almost everyone is wrong.

Here's a method that works for most people. For every job or project you've had, ask yourself three questions:

Before and after: What was the situation when I got there, and what was it when I left? This works even for things that are hard to count. If you inherited a chaotic process and left it orderly, how did that show up? Fewer errors? Faster turnaround? Less overtime?

Scale: How many? How much? How often? How many people did you work with, manage, train, sell to? How large was the budget, project, team, customer base? How many times a week, month, quarter did you do the thing?

Comparison: Against what baseline? Against last year? Against industry standard? Against when the previous person held the role? Comparison gives any number context.

If you genuinely cannot find a number after asking these questions, you can still be specific about scope. "Led a 7-person cross-functional team" is more useful than "led a team." "Supported 3 simultaneous product launches in Q3" is more useful than "managed multiple projects."

Vague is the enemy. Specific is your friend. Even if specific means "I ran 34 status meetings and reduced the average length from 50 minutes to 22," that's real and it tells me something.

STAR isn't just for interviews

You've probably heard of the STAR method for behavioral interview questions — Situation, Task, Action, Result. It's usually taught as an interview technique. But it's actually the underlying logic of any good resume bullet point, just compressed.

When you're writing about an achievement, you're doing this:

Situation: There was a problem or a context. (Inventory shrinkage was at 4.2%.) Task: You were the person who needed to do something about it. (Managing inventory for the store.) Action: You did something specific. (Implemented weekly cycle counts.) Result: Something changed. (Shrinkage dropped to 1.8%, saving ~$43K.)

In a resume bullet you can't write all four. There isn't room. So you compress it: keep the action and the result, and imply the situation. Cut inventory shrinkage from 4.2% to 1.8% by implementing weekly cycle counts; saved approximately $43K annually.

Situation implied. Task implied. Action and result visible. That's the whole formula.

The reason I mention STAR is not because you need to think through all four steps every time you write a bullet. It's because "Action → Result" is a check you can run on any resume line. If there's no action, you're listing a responsibility. If there's no result, you're listing an activity. You want both.

"Responsible for managing social media" — responsibility, no action, no result.

"Managed social media accounts" — action, no result.

"Grew Instagram from 4,200 to 31,000 followers by shifting to a Reels-heavy strategy in early 2024" — action, result, even a little context. That's the version you want.

The part about 2026 specifically

A few things have changed about resumes in the last couple of years that are worth knowing.

Most companies now run resumes through an ATS — an Applicant Tracking System — before a human ever sees them. The ATS is scanning for keywords from the job description. If your resume doesn't contain those keywords, it might never reach a person. This doesn't mean you should stuff your resume with keywords. It means you should actually read the job posting carefully and make sure your resume uses the same language they use.

If the job says "project management" and you wrote "project coordination," the system might count those as different things. If they want "data analysis" and you wrote "working with data," same problem. This isn't about gaming the system — it's about being legible to it.

The other 2026 thing: AI-assisted job hunting has made it way easier to send a lot of applications fast. Which means more applications per job, which means more competition for the same number of spots, which means your resume needs to be sharper than it did three years ago. The pile is bigger. Your ninety seconds got shorter.

The advice hasn't changed. The stakes for ignoring it have.

Sara sent me a message a few months after we rewrote her resume. She'd gotten the job — operations manager at a company about twice the size of her old one. She said the interviewer had specifically referenced her complaint resolution numbers in the first five minutes.

The numbers were accurate. She'd actually done the work. We just wrote it down in a way that made it visible.

That's all a good resume does. It makes the real work visible.

If you haven't done real work yet, a better resume won't fix that. But if you have — and most people have, they just don't know how to describe it — then the problem isn't your experience. It's that your resume is written like a job description instead of an argument.

You're not responsible for things. You accomplish them.