Can an AI chatbot tailor your CV for a job?

You have a job posting open in one tab and your CV (resume) in another, and a general-purpose assistant in a third that will rewrite the whole thing in one pass. The question is not whether it will produce something. It will, and it will usually read better than what you pasted in. The question is whether what comes back is a document you can sit in front of an interviewer and defend, line by line.

This guide does not answer that by telling you what happens inside any assistant. Nobody can see that from the outside, and this page does not guess. It answers it with an experiment you can run in one sitting: one posting, one CV, one prompt, and four checks you run on whatever comes back — the same four checks you should be running on the output of any tool, this one included. Nothing below names a product, and nothing below asks you to take a claim about somebody else's software on trust. Where this guide describes an output, it describes what to look for in the output you produce.

The short version, which sits on the home page in a sentence: a general-purpose chatbot writes toward a convincing document, and nothing in it checks each line against what you actually did. Run the experiment and decide for yourself whether that is a fair description.

This guide is about two ways of getting a tailored CV. Doing the rewrite yourself, by hand, is how to tailor your CV to a job description. What happens to the finished document after you press apply — inside the employer's applicant tracking system (ATS) — is a separate question, answered from the vendors' own documentation in how an ATS reads your CV.

What both methods are handed

Both procedures below get exactly the same two inputs. Run it on your own CV and a real posting you are actually considering; the shapes matter more than the words.

Example — a composite posting and a composite CV, assembled to show the shape. Not a real vacancy and not a real candidate.

The posting:

Operations Analyst. You will own the weekly performance reporting cycle and work with our logistics partner on delivery performance.

Must have: three years in an operations or analytics role · SQL, including building and maintaining reports · experience owning a weekly reporting cycle end to end · experience managing a third-party logistics provider.

Nice to have: dashboard tooling · experience in a regulated environment.

The CV, the one role that matters here:

Operations Analyst, 2021–2025.

• Built and maintained the weekly performance pack in SQL for the operations director.
• Worked with the warehouse team to improve stock accuracy.
• Ran the monthly stock count and wrote up the variances.
• Supported the rollout of a new picking process.

Read the two side by side and the problem is visible before any tool touches it. Three of the four must-haves are answerable from this CV: the dates cover the experience, SQL is named outright, and the weekly pack is the reporting cycle described in the candidate's own words rather than the posting's. The fourth is not there at all. The CV says the warehouse team — people inside the company. The posting says a third-party logistics provider — a company outside it. Those are different jobs, and the gap between them is exactly the kind a fluent rewrite can smooth over without anybody deciding to lie.

Keep that fourth requirement in mind. It is the whole experiment.

What a general-purpose assistant returns

The prompt. Open any general-purpose assistant. Paste this one line first, then the whole job posting, then your whole CV, in that order, all in a single message:

Here is a job posting and my CV. Rewrite my CV so it is tailored to this posting.

That is the ordinary version of the request — not a clever prompt, not a trick, the thing people actually type. Use it as written the first time. A more careful prompt will change what comes back, and you should test that afterwards; it does not change the procedure, and the procedure is what this guide compares.

Example — the shape of an output, not a transcript. Nothing here was produced by running an assistant, and none of it is offered as what any particular tool will say. It is a list of the kinds of line worth hunting for in your own run.

What arrives is usually a complete, well-formatted CV in one voice — that much you will see immediately. Sort what is in it into four kinds of line, because they are not equally safe:

• Your sentence, tightened. Built and maintained the weekly performance pack in SQL comes back as something like Owned the weekly performance reporting cycle, building and maintaining the pack in SQL. Every fact in it is one you supplied. This is the assistant doing the thing it is good at.
• Your fact, in the posting's words. The phrase end to end is the posting's, not your CV's. It may well be true of you — but it arrived from the other document, and you are the only person who can confirm it.
• The posting's words attached to something adjacent. Worked with the warehouse team to improve stock accuracy comes back as something like Managed relationships with logistics partners to improve delivery performance. The vocabulary is the posting's. The fact underneath it is the warehouse team. This is the line to hunt for.
• A line with no source in your CV at all. The summary paragraph at the top, any skills list, and any number are the three places to look for one first.

Whether all four show up in your run is the thing to observe, and it is worth doing more than once. The point is not that any particular sentence is guaranteed to appear. It is that the method gives you no way to tell the four apart. The output arrives as one document, in one voice, with no marks on it — nothing labelled this came from your CV, nothing labelled this came from the posting, nothing labelled this came from neither. Sorting them is real work, and the method leaves that work with you, after the fact, on a document you did not write.

That is a statement about a procedure, not about any software's reasoning, and you can confirm or refute it in ten minutes with your own CV. That is the only kind of claim this guide makes about the other method.

What this does with the same posting and the same CV

Same two inputs, a different procedure. HireReady24 runs in four steps, and here is what each one puts on the screen.

Base CV. You bring your real CV once. It becomes the source every tailored version is built from, so the raw material is your own document rather than a paraphrase of it.

Job. You paste the job description and it becomes a requirement list — must-haves and nice-to-haves, as separate rows. On the posting above that is four must-have rows, one of them experience managing a third-party logistics provider. A requirement that is its own row is a requirement that can be answered, or not answered, visibly.

Fit report. Before a word is rewritten you get the fit report: a match score with its band, the must-have line — how many of the posting's must-haves your CV answers today — and every requirement marked covered or open. Each requirement marked covered points at the line in your CV that covers it. On the example above, the SQL row is covered and the evidence under it is Built and maintained the weekly performance pack in SQL. The third-party-logistics row is marked open, and there is nothing under it, because there is nothing in the CV that says it.

The score is not a forecast. It measures your CV against this posting's requirements, and HireReady24 does not present it as a chance of an interview.

Gaps, answered with your own stories. An open requirement asks you for a real story rather than writing one. Tell it, and it becomes a line in your CV. Have none, and the requirement stays open — you keep the information that this posting asks for something your history does not show, which is worth having before you spend an evening on the application.

Result. The tailored CV is built only from the base CV and the stories you confirmed. You review every change before it is yours, then export the PDF.

Alongside that, four things it will not do, because they are the reason the document holds up when somebody asks about it: it will not invent experience; it will not add a keyword your history cannot back up — the gap is shown to you instead; it will not promise you an interview; and it will not train AI on your CV, which is used only to generate your own outputs.

Every sentence in this section describes a screen the product renders. None of it is a claim about how well it writes.

The one difference that matters

Everything above is procedure. Here is the single place where the two procedures hand you different work, and it is the requirement the CV cannot support.

With the prompt. You get back one document. Somewhere in it there may be a sentence about logistics partners. Finding out means reading the output against your original, line by line, looking for vocabulary that arrived from the posting and landed on the wrong fact — and doing that on prose that is smoother than what you wrote, which is precisely the condition under which skim-reading fails. And if no such sentence appears, the requirement is not marked absent. It is just absent. The document tells you nothing about it either way, so you apply without knowing whether the employer's fourth must-have is answered.

With the fit report. The requirement is a row and the row says open. Nothing is written under it until you supply something real, and the row is on the screen before the rewrite rather than buried in it afterwards. If you have run a third-party provider and simply never wrote it down, you say so and it becomes a line. If you have not, the row stays open and you decide what to do with that — apply anyway and be ready for the question, or spend the evening on a posting you fit better.

The difference is not accuracy, and this guide does not claim that one method writes better sentences than the other. It is that one procedure has a place to put the answer I have not done this and the other does not have to say anything at all. An honest open row is a worse-looking document and a better-informed decision.

When the open row is one you think you might be able to close — the work is there but the CV never said it — the method for getting it onto the page truthfully is a STAR story for the requirement your CV lacks, including the case where the honest answer is that you have not done it.

What a general-purpose assistant is genuinely good at

A comparison that finds nothing good on the other side is an advertisement, so here is the part that is plainly true. A general-purpose assistant is very good at:

• Tightening a sentence you supply. You give it the facts; it gives you back a shorter, clearer line. This is the single most useful thing it does for a CV, and it is low risk because you are the source.
• Explaining a posting. Unfamiliar jargon, an acronym, a responsibility phrased in an industry's own dialect — ask what it means and what a person doing that job would actually do all day.
• Getting you unstuck on a blank page. A rough first paragraph you then rewrite in your own voice beats an empty box, as long as you do rewrite it.
• Interview preparation. Ask it what questions the posting invites, then answer them out loud. Nothing about that step needs to end up in a document.
• Being available. No account, no waiting, at eleven at night, on any posting, with no limit on how many times you change your mind.

Notice what those have in common: you supply the facts and you keep the judgment. That is the shape where it is strong. Several of the manual steps in how to tailor your CV to a job description go faster with one open beside you. What changes when you hand over the whole document is not the quality of the writing — it is who is holding the judgment when a sentence turns out to be a little more generous than the truth.

Check any tool's output yourself, in four steps

Run these on anything that hands you a rewritten CV — an assistant, a CV service, this product. They take about ten minutes and they are the only part of this guide you should treat as advice.

1. Trace every line back to a source. Put the output and your original side by side and go line by line. For each line, point at the sentence in your CV it came from. Some will be tightened, some merged, some reworded — fine. Any line you cannot point at is new. For each new line, answer one question: is this true of me, and could I talk about it for two minutes? Delete every line where the answer is no.
2. Take the must-haves one at a time. Write down the posting's must-haves — four, in the example above. For each one, find the line in the output that answers it, and then find the thing you actually did that stands behind that line. A requirement with a line but no underlying fact is the dangerous case. A requirement with neither is an honest gap, and it is better to know.
3. Search the output for the requirement you already know you cannot support. You identified it before you started — in the example, third-party logistics provider. Search the text for the posting's own word for it. If it is there, read what it is attached to. If it is attached to something adjacent that you did, that sentence is the reason this check exists. If the phrase is absent, write open next to that requirement yourself; you have just done by hand what a fit report does on the screen.
4. Check the furniture. Job titles, employer names, dates, and every number. These are the details a fluent rewrite changes most quietly — a title nudged toward the posting's title, a date range rounded off, a percentage you have never seen before. Read them against the original character by character. A number you did not write is a number you cannot defend.

If steps 1 and 2 are quick, the tool has done the work of showing you where each line came from. If they are slow, the tool has handed that work to you and called it a tailored CV. That is the whole comparison, and it is a property of the procedure rather than an opinion about anyone's software — which is why you can settle it yourself, with your own CV, this afternoon.