A resume is supposed to be the document that gets you the interview. For a lot of people it doesn't, and it's often not because the person isn't good enough for the role. It's because the resume is showing a version of them that hides what they can actually do.

There are two patterns that account for most of it. They're both reasonable mistakes, and they're both fixable.

The job-title trap

The first pattern is leading with job titles. The resume opens with 'Customer Service Representative, 2019 to 2022' and then a list of duties. This makes sense, structurally; most resume templates ask for it. But job titles are inconsistent across organisations. A customer service representative at one company is doing front-counter triage. At another, the same title is running an entire cross-functional support program. The title alone doesn't tell the reader what was happening in the role.

The reader of a resume has roughly twenty to forty seconds to form an impression. If they're scanning a list of titles and trying to guess what the work was, they're working too hard, and they'll often default to the most common interpretation of the title rather than your specific version of it. That's how a candidate who was running serious work gets placed in the 'general support' bucket and never makes the shortlist.

The duty-list trap

The second pattern is the bullet-pointed duty list. 'Responsible for processing customer enquiries.' 'Managed daily operations.' 'Liaised with stakeholders.' These are everywhere, and the issue is that they describe what the role nominally involved without saying anything about what you actually did, what you were good at, or what changed because you were there.

Two people in the same role can have wildly different versions of it. One might be the person other team members route the hard cases to. Another might be the one who quietly improved the documentation so new starters could ramp up faster. A third might be the one who held everything together when a colleague went on extended leave. The duty list looks the same for all three of them; the capability is what separates them, and the duty list is the place where the capability gets lost.

Capability-led writing

The fix is to write capability-led rather than duty-led, and to back each capability with the evidence that proves it. The format that tends to work has three parts: a short, specific capability statement written as something the reader can recognise as a real skill; a concrete example showing you doing it, in one or two lines; and the result, where there is one.

Compare these two versions of the same role.

The duty-led version: 'Customer Service Representative, RetailCo, 2019 to 2022. Responsible for resolving customer issues, processing returns, and liaising with internal teams.'

The capability-led version: 'Customer Service Representative, RetailCo, 2019 to 2022. Became the team's go-to for de-escalating angry customers, including the long-standing accounts that other reps avoided. Reduced complaint escalations to head office by about 40 percent over two years. Trained two new starters, both of whom passed probation on time.'

Same role, same person. The second version tells the reader exactly what the candidate brings, gives them evidence, and lets them imagine the candidate doing the same thing for them. The first version leaves them guessing.

What this means in practice

A few practical shifts make most of the difference.

Lead each role with one or two capability statements before the detail. Tell the reader what you brought to the role in language that translates outside the company. 'Became the team's de-escalation specialist' translates; 'Customer Service Representative' on its own doesn't.

Replace duty bullets with capability bullets where you can. Instead of 'managed daily operations', try 'kept the rota covered through three staff transitions and one extended sick leave with no shifts dropped'. The second version is the same fact, but with the capability and the evidence visible.

Put numbers in where you have them. You don't need fancy metrics; specific numbers do most of the work. 'Reduced wait times' is vague; 'reduced average wait times from 8 minutes to under 4' is specific. If you have a number, even an estimated one, use it.

Don't be afraid to claim things that feel small. The capabilities that seem too obvious to mention are often the ones that distinguish you. 'Always followed up the day after a difficult interaction' is a small habit, but it's a real one, and a hiring manager reading it knows immediately what kind of colleague you'd be.

When the role didn't have a title that helps

A lot of people have done the most skill-building work of their life in roles that didn't come with an impressive title. Carer, parent, volunteer, community organiser, small business owner trading under their own name. Those roles can absolutely go on a resume, written the same way: capability, evidence, result.

'Carer, 2018 to 2023. Coordinated medical appointments, medication schedules, and home support services for a parent with progressive dementia. Maintained continuity through three changes in primary GP and two hospitalisations.'

That's serious work. Written like this, a reader can see it.

A resume that shows what you can do isn't longer than one that hides it; it's just written from a different angle. You're not adding anything that isn't true. You're naming what was actually happening, in language a stranger can read.