Listing Skills You Have But Never Named on Your CV

You've probably done things at work that never made it onto your CV, not because you were hiding them, but because they didn't feel like achievements at the time. You just did them. Sorted out a scheduling mess. Trained the new starter. Kept a difficult client calm during a bad week. None of that felt CV-worthy in the moment, so it never got written down. Years later, it's still missing, and it's often exactly what a job description is asking for.

Why obvious skills go unrecorded

The skills you use every day tend to feel invisible to you precisely because they're routine. If you've been proofreading colleagues' emails for two years, you probably don't think of yourself as having strong written communication — you just think of it as something you do. The gap isn't in your experience. It's in the translation from lived task to written claim.

This matters more than it sounds like it should, because a lot of recruitment is keyword and phrase matching, at least in the first pass. If a job asks for stakeholder management and your CV describes the same behaviour as 'liaised with departments to sort out delivery issues', a human reader might join the dots, but plenty of screening won't.

A quick way to surface them

Rather than trying to remember achievements from scratch, work backwards from your ordinary week. Pick a recent stretch of a few months and ask what you actually spent time doing, not what your job title implies you did.

• What did people come to you for, that wasn't officially your job?
• What have you explained to someone else more than once, because you were the person who understood it?
• What would fall apart in your absence, even briefly?
• What do you do automatically now that used to take you real effort?

Answers to these questions are usually skills. 'People come to me when the spreadsheet breaks' is data troubleshooting. 'I explain the onboarding process to every new hire' is training and documentation. 'Things stall if I'm off' might be process ownership or informal project management.

If a task feels too small or too obvious to mention, that's often exactly why it's missing from your CV — and why it's worth a second look.

Match the language, not just the list

Once you've named the skill for yourself, check how the job description phrases it. Employers have their own shorthand — 'cross-functional collaboration', 'process improvement', 'client relationship management' — and using their term, where it's genuinely accurate, helps a reader (human or software) recognise what you're offering without extra translation work on their end.

This isn't about inflating what you did. It's about not underselling it by using vaguer, more modest language than the role actually calls for. There's a real difference between 'helped with the rota' and 'managed weekly scheduling for a team of eight', if the second one is true.

A short exercise worth doing before you next apply

1. List five things you did in the last month that weren't formally assigned to you.
2. For each, write the underlying skill in plain terms.
3. Check the job description for that skill's more formal name.
4. Add one line to your CV using that phrasing, only if it's accurate.

You'll likely find two or three skills that were sitting in your day-to-day work the whole time, just never written down anywhere a recruiter could see them.

FixMyCV reads the job description alongside your CV, flags the skills you've likely undersold or left out entirely, and asks you to confirm them before rewriting anything in the role's own language.