How to Stand Out When Every CV Looks AI-Generated

The job application landscape is a mess. Hiring managers and recruiters say the applications they’re getting are better-formatted, but that’s about it - the substance is still lacking. You see the same empty phrases over and over: “passionate and results-driven software engineer with a proven track record of delivering high-quality solutions”. It’s meaningless.

When I review applications, a few red flags pop out. There are the abstract noun clusters that don’t actually say anything. Phrases like “leveraging innovative methodologies to drive cross-functional alignment and deliver scalable solutions” are just buzzword soup. You could swap out the words and it wouldn’t change the meaning.

And then there are the achievement statements that don’t include numbers. “Significantly improved application performance” - what does that even mean? When did it happen, and by how much? If someone’s not providing specifics, it’s probably because they’re not describing something they actually did.

I also notice that a lot of applications use the same sentence structures over and over. It’s like they’re following a template: “Led the development of… Collaborated with cross-functional teams to… Spearheaded the implementation of…” It feels formulaic, not like someone’s actually describing their work.

And don’t even get me started on the generic company enthusiasm in cover letters. “I’m excited about the opportunity to join [Company] and contribute to its mission” - it’s just a copy-paste from the company website. You can spot it from a mile away.

So, what makes an application stand out? Specificity. I’d much rather see a CV bullet that says: “Reduced checkout page load time from 4.2s to 1.1s by replacing a synchronous payment validation call with an async webhook-based flow; bounce rate on that page dropped 23% the following month”. It’s not fancy, but it’s credible. It’s got numbers, it’s got a specific technical intervention, and it’s got a connection to a business outcome. That’s not something you can generate from a job description - it requires actual knowledge.

That’s the bar. Not fancy writing, but specific writing. And it’s not just about writing a certain way - it’s about showing you’ve actually engaged with the company’s work. If you can write one sentence that shows you’ve read an engineering blog post, or noticed a specific technical decision they made, that’s worth more than three paragraphs of generic fluff. Hiring managers notice it because it’s rare.

Numbers are hard for AI to replicate. If someone writes “reduced query latency from 800ms to 120ms”, you know they’ve actually worked on that system. But if someone writes “significantly improved database performance”, that’s just vague.

AI writing tools can be useful for cleaning up your application and making it more readable. They can help you standardise your formatting, ensure consistent tense, and remove redundancies. But they’re not good at writing about your specific achievements, or capturing your unique voice. That’s what makes an application memorable - a specific perspective that reads like a real person.

If you want to stand out in a crowded job market, focus on specificity. Use numbers, show you’ve actually engaged with the company’s work, and write like a real person. That’s where the opportunity is. And it’s not easy - it takes work to be specific, to actually know what you’re talking about. But it’s worth it.

See what Xeito does end-to-end. Browse all features — application tracker, AI resume + cover letters, interview coach, 130+ job-board sync, built for remote-first developers.

Related articles

• AI Agents in Your Portfolio: How to Showcase Agentic Development Skills
• Building in Public: How Sharing Your Work Accelerates Your Tech Career
• GitHub Portfolio vs. LeetCode: What Hiring Managers Actually Look For in 2026
• Building a GitHub Profile That Gets You Remote Developer Jobs
• Mastering the ATS: How to Get Your CV Past Automated Screening