Making a CV That Still Sounds Like You
Right now, the candidates having the easiest time are simply the ones using AI in the right order, rather than handing it the whole job. Our own guide to what to actually include on a CV covers the structural side of this in more depth, but the underlying principle is simple.
Write your own achievements first, in your own words, before AI touches anything. Keep the specific, slightly odd detail that AI would normally smooth away: the actual problem you solved, rather than the polished description of solving it. Instead of “responsible for improving team performance,” write down what was actually broken and what you did about it, something closer to “reorganised the handover between two shifts that was costing us a day of downtime a fortnight.” Then use AI for what it's genuinely useful for: tightening sentences, checking structure, and catching formatting issues that trip up applicant tracking systems.
Tailor the CV for each application rather than sending one generic version everywhere. It takes longer, but a CV that clearly speaks to one specific role will usually beat ten identical ones sent everywhere else. Keep the keywords from the job description that actually apply to you, rather than every keyword going, since stuffing in skills you can't back up tends to surface at exactly the wrong moment in an interview. Before you send anything, ask yourself one simple question about each line: could I comfortably explain this if someone asked me about it tomorrow? If the answer's no, change it. And read the finished version out loud. If it doesn't sound like something you'd actually say, it probably needs another pass.
A CV only has to get you as far as a conversation. Nobody's ever been hired because their personal statement called them results-driven, they got hired because it turned out to be true. If you're ready to put that to the test, take a look at our current job search and see what's out there.