ChatGPT for the job hunt: prove, don't invent

The only rule on this page: ChatGPT may change how a true thing is phrased. It may never change whether the thing is true. A resume, a cover letter, and an interview answer are all promises about what you have done. A model can help you keep those promises clear. It cannot make new ones for you.

If you typed chatpt on the way to a job application, the spelling is the least of your problems; the naming answer is here. This guide is the sequence: evidence, resume, cover letter, interview, and the one failure that gets people caught.

The fabrication line

The failure mode is not “the writing sounded like AI”. It is a specific claim that collapses under one follow-up question.

A realistic example:

Invented: “Increased conversion by 32% by redesigning the checkout flow.”

What actually happened: you redesigned the checkout flow, and conversion went up, but the team also changed pricing and ran a promotion in the same month. You do not have a clean causal number.

The repair is not to make the number smaller. The repair is to state what you can defend:

“Redesigned the checkout flow with design and engineering; the release shipped in Q3 and the team used the new flow as the baseline for the next pricing test.”

That sentence is less impressive and more useful. It gives an interviewer something to ask about, and it does not put a number in your mouth that you cannot explain.

Use this test on every bullet: could I answer three follow-up questions about this sentence without inventing anything? If not, cut it or rewrite it.

Resume: evidence, not adjectives

A resume bullet is not a summary of your personality. It is a compressed argument: what you did, in what context, and what changed. The strongest bullets usually have a verb, a task, and a result — and the result can be a scope, an artefact, or a decision, not only a percentage.

The “so what” test

For each bullet, ask “so what?” until you reach something a hiring manager cares about.

• “Managed social media.” → So what? → “Built a content calendar for three channels.” → So what? → “Cut the weekly production time by moving approvals into one shared queue.”
• “Helped with onboarding.” → So what? → “Rewrote the first-week checklist for new hires.” → So what? → “New hires could complete the first three setup tasks without asking for the same password reset twice.”

The last version is specific, human, and checkable. It does not need a fake percentage.

The evidence prompt

Here is my actual experience: [role, tasks, tools, outcomes, and any numbers I can defend].
Here is the job description: [paste].

Build a two-column table:
1. requirement from the posting,
2. the evidence from my experience that meets it.

Mark every requirement with NO EVIDENCE if I do not have one. Do not invent a metric,
employer, date, skill, or tool.

Then write three resume bullets for the strongest matches. Each bullet must start with a
verb, name the context, and end with a result I actually stated. Do not add an adjective
unless I used it first.

The NO EVIDENCE column is the useful part. It tells you what to address in the cover letter, what to learn before the interview, and what not to claim.

When you have no numbers

Most jobs do not produce clean metrics. Do not invent them. Use one of these instead:

• Scope: how many people, regions, systems, or documents.
• Artefact: what you made that still exists — a checklist, a dashboard, a training doc, a process.
• Decision: what changed because of your work — a vendor chosen, a process retired, a deadline protected.
• Before/after in words: “the weekly report used to take two people a day; now one person updates it in an hour” only if that is true.

A truthful scope line is safer than a fake percentage in an interview.

Cover letter: the tailoring loop

The generic cover letter fails because it starts with the writer. The useful one starts with the match. Do the matching before you ask for prose.

The loop

1. Read the posting for requirements, not vibes. Extract the three things this role will actually screen for: a skill, a domain, a way of working.
2. Pick three facts from your experience that meet those requirements, with the proof you can give for each.
3. Write the opener last. The first line should name the match, not summarise your career.
4. Cut the enthusiasm you cannot support. “I have always been passionate about” is filler unless you can attach it to something you did.

The prompt

Job posting: [paste].
My evidence: [three facts from my experience, each with the proof I can give].

Step 1: extract the three requirements this role will actually screen for.
Step 2: map each requirement to one of my facts. If a requirement has no matching fact,
write NO MATCH and do not fill it.
Step 3: write a cover letter under 250 words. Open with the strongest match, not my life
story. Use plain language. Do not invent a company detail that is not in the posting, and
do not claim enthusiasm I did not mention.

After the letter, list the two sentences most likely to be asked about in an interview, and
what I should have ready.

The last instruction turns the letter into interview preparation. If you cannot defend a sentence, it does not belong in the letter.

What not to ask for

• “Write me a cover letter for this job” from the posting alone. You will get a letter that could be sent to fifty companies.
• “Make it sound more passionate.” You will get adjectives, not evidence.
• “Add a metric to make it stronger.” If you did not measure it, it is not a metric; it is a liability.
• “Pretend I have experience with [tool].” No. This is the line. A cover letter is not a creative writing exercise about your past.

Interview prep vs live assistance

Preparation is legitimate. Performance assistance is not.

Preparation looks like this:

• drilling the three questions the hiring manager will care about most;
• turning your evidence into STAR-shaped answers: situation, task, action, result;
• asking the model to push on the weak part of an answer;
• practising the “tell me about a time” questions you keep rambling on;
• preparing questions for them, which is the part candidates skip.

I am interviewing for [role]. Here is the job description and my evidence: [paste].

Ask me one question at a time, starting with the three a hiring manager will care about most.
After each answer, tell me:
1. what was vague,
2. what evidence I left out,
3. the follow-up they would ask next.

Do not answer for me. Do not tell me what to claim; only what I can support from the
evidence I gave you.

Live assistance looks like this: a second device, an earpiece, a hidden window, or a model feeding answers while the interviewer is talking. It fails on its own terms even before the ethics: you cannot listen, think, and read a generated answer at the same time without sounding delayed. It also misrepresents the one thing the interview is designed to measure — how you think when you do not already know the answer.

The line is simple: preparation before, no feed during. If the employer allows notes or a prompt sheet, use what they allow. If they do not, do not smuggle one in.

The detection question

You will see claims that a detector can identify AI-written applications with a specific accuracy. We do not publish a number, because we cannot verify one and the methods are not stable enough to promise.

What we can say is more useful: the thing that gets caught is usually a fabricated specific. An interviewer asks “how did you measure that?” and the candidate cannot explain the baseline. A hiring manager checks the company name in the cover letter and it is the wrong one. A resume says “led a team of 12” and the reference says “contributed to a project with 12 stakeholders.”

Prose style is a weak signal. A false claim is a strong one. Keep the claims true and you have removed the failure mode you can actually control.

A 45-minute application pass

A repeatable sequence for one role:

1. 10 minutes — read and extract. Highlight the three requirements, the three responsibilities, and any named tool or domain. Do not open the chat yet.
2. 10 minutes — evidence table. Fill the two-column table. Mark the gaps. Decide which gap you will address in the letter and which you will simply not claim.
3. 10 minutes — resume bullets. Rewrite only the three or four bullets that match this role. Keep the rest of the resume stable.
4. 10 minutes — cover letter. Run the tailoring loop. Read it aloud once. Cut the first sentence if it is about you rather than the match.
5. 5 minutes — interview prep. Ask for the three likely questions and the follow-ups. Write one line of evidence under each. Stop.

Then send it. The last five minutes are not for another rewrite; they are for checking that every claim is yours.

What not to paste

A job application contains more personal data than people remember:

• your full home address, date of birth, or government ID;
• salary history and banking details;
• references’ names, emails, and phone numbers;
• your current employer’s confidential strategy, pipeline, or unreleased numbers;
• health, family, immigration, or accommodation details that are not required for the application;
• a take-home assignment that belongs to the employer and may be confidential.

Use the minimum needed. A resume prompt does not need your home address. An interview-prep prompt does not need your reference’s phone number.

The short version

Use it to find the match, shape the evidence, and rehearse the conversation. Do not use it to invent a metric, a tool, or a version of your career that you cannot defend. The goal is not a letter that sounds generated or a letter that sounds human. The goal is a letter that is true, specific, and yours.