A chatbot cannot write your resume, because it doesn't know what you did. What it's very good at is the part people find hardest: turning a shapeless pile of "I worked there and did stuff" into clear, specific lines, then reshaping those lines for each job you apply to. Below is the whole process in six steps, with the prompts, plus an honest section about applicant tracking systems — because most of what's written about beating them is nonsense.
Want the same path as a short course? Open AI Earn on Google Play — that listing is the official app page.
Step 1: Dump the raw material before you ask for anything
Do not open a chat and type "write my resume". You'll get a plausible resume for a person who doesn't exist, and you'll spend longer correcting it than writing from scratch. Instead spend fifteen minutes producing raw material: every job title, employer, rough dates, and — this is the part that matters — what you actually did each week, what changed because you were there, and anything you can attach a number to. Messy is fine. Bullet fragments are fine. Write down the things that felt too small to mention; those are usually where the concrete details live.
Prompt: "I'm building a resume. Here's my raw history, unedited: [paste everything]. Don't write the resume yet. Ask me the questions a recruiter would want answered but my notes don't cover — especially about scale, results, and what I personally did versus what my team did. Ten questions, one at a time."
Answering those questions is the actual work of resume writing. Everything after this is formatting.
Step 2: Turn duties into results
The one structural upgrade that matters is moving from what you were responsible for to what changed. "Responsible for social media" says nothing; "grew the shop's Instagram from 400 to 1,100 followers in six months by posting three times a week" says who you are. Numbers help, but only real ones — from your records, your manager's feedback, an old report, your own logs.
Prompt: "Rewrite each of these into resume bullets that lead with the result, then the action, then the context. Keep them under 25 words. If a bullet has no measurable outcome, don't invent one — instead mark it and tell me what kind of number I should look up. Here they are: [paste]."
The "don't invent one" instruction matters. Left to itself, an assistant will happily produce "increased efficiency by 30%", and that figure will follow you into an interview where someone asks how you measured it.
Step 3: Tailor to one job at a time
This is where the time savings are real. Rewriting a resume by hand for each application is tedious enough that most people skip it; with a draft and the job description in front of you, it's a five-minute pass. The goal isn't to change what you did — it's to lead with the parts of your history that this employer cares about, and to use their vocabulary where it honestly matches yours.
Prompt: "Here's my resume: [paste]. Here's the job description: [paste]. Tell me: which of my experiences map most directly to their requirements, which requirements I don't meet, and which of my bullets should move to the top or be cut for this application. Don't rewrite anything yet — give me the analysis first."
Read the "requirements I don't meet" list before you apply. Sometimes it tells you to write the cover letter differently. Sometimes it tells you not to apply, which is also useful information.
Step 4: Applicant tracking systems, honestly
Most medium and large employers put your application into software that stores it, parses it into fields, and lets recruiters search and filter. That's the real function: a database with search, not a robot judge that scores your personality. There is no secret formula, and anyone selling you an "ATS hack" is selling a hack for a system they haven't seen — configurations differ by employer.
What genuinely helps is being easy to parse. Use standard section headings that mean what they say (Experience, Education, Skills). Keep the layout to one column; multi-column designs and text boxes can be read out of order. Don't put contact details in a header or footer, where some parsers won't look. Don't use graphics, icons or charts to carry information. Save it in the format the posting asks for, and if it doesn't ask, a clean .docx or a text-based PDF are both safe. Use the job's own terms where they truthfully describe your experience — if they say "accounts receivable" and you say "invoicing", say both.
What doesn't help: white text keyword stuffing, invisible layers, keyword lists jammed into the margins. It's detectable, recruiters do find it, and it costs you the application. It's also a small dishonesty in a document whose entire value is that it's true.
Prompt: "From this job description, extract the terms and skills a recruiter would most likely search for: [paste]. Group them into ones I clearly have, ones I partly have, and ones I don't. For the first group only, suggest where in my resume they'd fit naturally: [paste resume]."
Step 5: Decide what stays human
An unedited AI draft has a smell — balanced sentences, safe verbs, "passionate about delivering results". Recruiters read hundreds of these a week now, and it reads as effort not spent. The fix is deciding in advance which parts you write yourself.
| Part of the job | Hand to the assistant | Keep yourself |
|---|---|---|
| Remembering what you did | Asking you the right questions | Every fact, date, title and number |
| Bullet phrasing | Tightening, cutting, leading with results | Final wording of the two or three best bullets |
| Tailoring to a posting | Mapping and reordering | The decision about what to emphasize |
| Summary line at the top | Draft options to react to | The version you actually send |
| Formatting and parseability | Checklists and structure advice | The final file and how it looks |
| Cover letter | Structure and a first draft | The specific reason you want this job |
| Interview prep | Practice questions and pushback | Your stories, told in your words |
Prompt: "Here's my resume draft: [paste]. Flag every phrase that sounds generic, corporate, or like it could appear on anyone's resume. Don't rewrite them — just list them, so I can replace them in my own words."
Step 6: Audit it for truth, then have a human read it
Before the file leaves your computer, go line by line against reality: job titles as they appeared on your contract, dates that match, numbers you could defend if asked "how did you get that figure?" Assistants drift toward flattering phrasing, and a small exaggeration you didn't consciously make is still yours once you send it. The same verification habit applies here as anywhere else — see how to fact-check AI.
Then read it aloud. Then send it to one person who knows your work and one who doesn't. The second reader catches jargon; the first catches the thing you undersold.
What not to do
- Don't let it invent anything. Employers, titles, dates, degrees, percentages. A fabricated line is a fireable offence later, not just a rejection now.
- Don't paste your full personal details. Home address, phone number, national ID, date of birth — none of that is needed for the writing. Strip it, work on the text, add contact details in the final document. More on that in using AI safely.
- Don't send one AI-written resume to fifty postings. Volume without tailoring is the worst of both approaches: generic text and no targeting.
- Don't accept the first draft. The first output is raw material. Ask for shorter, blunter, more specific — the follow-up is where the quality is.
- Don't hide keywords. White text, tiny fonts, off-page lists. It's detected, and it ends the application.
- Don't let it write your summary line. It's the first thing read and the easiest to spot as generated. Draft options with it if you like, then write your own.
- Don't skip the read-aloud. If you can't say a sentence out loud without wincing, you can't defend it in an interview either.
After the resume
The same method extends naturally: a cover letter drafted from your resume plus the posting, then rewritten in your voice; interview practice where you ask the assistant to role-play the hiring manager and push back rather than encourage you. Both work better once your resume is honest and specific, because everything downstream is built from it. What you can attach, upload or save as reusable instructions depends on your plan and changes over time — the current answer is on help.openai.com rather than in any guide. If your prompts are producing bland results throughout, the cause is usually one of the patterns in common AI mistakes beginners make, and the everyday prompt templates include a role-play template you can point at your next interview.
