It is the first question most people ask before using AI on an application, and it is usually asked in a slightly guilty tone. Will they know? It is a fair question, and the worry is not imaginary: hiring managers say in large numbers that they can spot AI writing, and some say they stop reading when they do.
However, the question is aimed at the wrong thing, and two ideas are worth separating before going further because they are almost always run together. Detection is somebody establishing how a document was produced. Recognition is somebody reading a document and finding it familiar. In other words, detection is a test you could fail, and recognition is an impression you make.
Only the second one is actually happening to your applications. And it is the one worth worrying about, because it is costing people interviews while they worry about the other one.
This guide covers three things: why nobody is really detecting anything, why AI writing reads as generic even when it is fluent, and how to use these tools without producing the thing that gets skimmed.
Nobody is detecting; everybody is recognising
There is no Turnitin for job applications. Nothing in a standard applicant tracking system checks a cover letter for AI, there is no shared tool or agreed practice across employers, and the detectors that do exist are unreliable in both directions — they flag human writing as machine-written often enough that nobody sensible makes a hiring decision on one. A recruiter holding eighty applications for one post has no reason to run any of them through anything.
What happens instead is duller and worse. A reader reaches the third sentence and recognises the shape of it, because four other letters that week opened the same way. They do not conclude that you used AI. They conclude there is nothing here to read, and move on. You are not being caught. You are being skimmed.
Why it reads as generic, and why that is not a writing problem
The instinct is to assume the writing was not good enough, and so the fix must be better prose. That instinct is understandable and it is backwards. AI prose is usually too smooth rather than not smooth enough — the grammar is clean, the transitions are tidy, and that polish is part of what makes it recognisable.
The real mechanism is simpler. A model asked to write your cover letter from a job title and a few lines of instruction does not know what you did. It cannot know. So it does the only thing available to it: it writes what somebody in your position would plausibly have done — the average of every paralegal application it has ever seen. That average is perfectly fluent, and it belongs to nobody.
In other words, the giveaway is not bad writing. It is the absence of anything only you could have written.
Weaker
I am excited to apply for the Paralegal position at your firm. With my strong attention to detail, excellent communication skills and genuine passion for the law, I am confident I would be a valuable asset to your team. I thrive in fast-paced environments and am eager to contribute to your continued success.
Stronger
Your advert puts volume of disclosure first. In my current role I run the first-pass review on document-heavy matters — most recently around 1,200 pages over three weeks, against a cut-off that moved twice.
The first is fluent, grammatical and completely interchangeable; take out the word paralegal and it would fit any job in the country. The second is plainer and shorter, and it contains two things no model could have supplied on its own: a number, and the detail about the deadline moving. That is the whole difference, and note what it is not — it is not a difference in writing ability. It is a difference in what went in.
How to use the tools without producing the average
Everything above points at one practical rule, which is that the useful work happens before you open anything:
- 01Write down what you actually did, with numbers, before you open any tool. Five or six items, each already a sentence. This is the bank, it takes an evening, and you build it once.
- 02Never let a tool supply a fact. Give it facts. If a draft contains a claim you cannot trace back to your own history, delete the claim — do not soften it.
- 03Cut the enthusiasm and keep the specifics. “Passionate”, “thrive” and “valuable asset” are the words a model reaches for when it has nothing concrete to say. If they are doing the work in your letter, the letter has no evidence in it.
- 04Read it aloud. Anything you would not say in those words to a person is a line that will read as borrowed, because it was.
- 05Check the most impressive sentence is one you can be questioned on, because you will be.
The other half of this
What to change for each application, and what never changes: how to adapt your cover letter to the job descriptionThe version that is worse than generic
A generic letter wastes an opportunity. There is a worse outcome, and it comes from the same cause: a tool with no facts to work from will sometimes fill the gap rather than leave it. It upgrades a job title, invents a system you have never opened, or turns “assisted with” into “managed”, because that reads better and nothing in it knows the difference.
The practical consequence arrives before any regulatory one. An interviewer will ask you about the most impressive thing in your letter — that is what the letter is for. Being asked to talk for two minutes about something you did not do is a specific and avoidable kind of bad afternoon.
And if you are heading for admission as a solicitor, or qualifying through CILEX, there is a longer-run reason to be strict: you will be assessed on character and suitability at the end of it, and an application is a document with your name on it. The habit of writing what you wish were true, in a profession built on not doing that, is one worth not forming.
In short
Almost nobody will detect that you used AI. Plenty of people will notice a letter that could have gone to anyone, and that is the one costing you interviews. The two are not the same problem. The fix is not better prose — it is putting in something only you could have put there.