How to Make AI Write Your Resume the Way You Talk

The output is generic because the input was. This makes the agent interview you six ways per role — including the thing that went wrong — before it writes a word, so the draft is specific before anything is polished.

By Zaira

01The Problem

Everyone pastes the same prompt, so everyone gets the same person

Convergence here is arithmetic, not laziness: one widely-copied prompt and a thin input produces the same competent average every time, and hiring managers now describe reading exactly that.

Generic input produces the average candidate

This is not the model being careless. It is arithmetic: when a whole market supplies the same thin input — a job title and a list of duties — the output converges on the middle of what those inputs support, which is a document that reads like nobody. Hiring leads describe the result as a sea of perfect sameness that does the opposite of standing out, and average volume per corporate posting runs past two hundred and fifty applications. If your document is interchangeable with the ones on either side of it, the cause is upstream of the writing.

You are describing your job in the language of a job description

Responsibilities, team, process, scope — that is the vocabulary of the posting, and it is what most people paste. But it is the vocabulary of the role, not of the work you did inside it, and an agent can only reflect back what it is handed. The specific, unrepeatable details — what was broken when you arrived, what you tried that failed, what you decided against someone's advice — are the ones that make a document yours, and they are the ones a job-title prompt cannot elicit.

You cannot fix it afterwards

Polishing a generic draft produces a more polished generic draft, and it is the most recognisable shape on the page: fluent, evenly structured, and interchangeable. This is the mechanical reason a rewrite often makes a document worse rather than better. The register has to be set before the first sentence exists, which means the work happens in the conversation rather than in the editing pass.

02The How-To

The interview-first method, step by step

Copy it into Zaira. It fixes your register before it asks anything, works through your roles one at a time, and refuses to write until it has asked the questions that produce specific answers.

Interview-first resume drafting
Automate it with Zaira

Step 0: Set the register from me, not from you

Act as my interview partner, not my writer. You are not writing my resume yet. You are extracting what actually happened from me, in my own words, and only then writing from that. - How I talk about my work, in three sentences, unedited: [paste, do not tidy it] - Words I would never use about myself: [list] - Words I actually use about my own work: [list] From these, in one paragraph, tell me what my register is, and show me three words that would sound wrong in my resume because they are not mine. Do not go past this step until you have shown me that paragraph. Do not rewrite my three sentences.

Step 1: Interview me, one role at a time

For each role, ask these six questions in this order and wait for my answer before the next one: 1. What was broken, slow, missing, or unbuilt before you arrived? 2. What did I personally do, as opposed to the team? 3. What did it cost, and how do I know? 4. What did I try that did not work, and why? 5. What did I decide that other people disagreed with? 6. What would I do differently now? Do not offer an answer. Do not hand me a template. Do not summarise what I said back to me before the next question. If my answer is vague, ask again — do not rewrite it into something better sounding. Role 1: [describe it roughly] Role 2: [etc.]

Step 2: Show me the pattern across my answers

Before you write anything: - which question produced the most concrete detail across all my roles - which of my answers sound borrowed from a job description rather than lived - the one claim I make most often that I cannot evidence Show me that as a short list, then ask me about the third one.

Step 3: Write only from what I said

Now write the experience section. Constraints: - every line traces to a specific Step 1 answer, and you tell me which one - no adjective that was not in my Step 0 vocabulary - no number I did not give you - where the honest answer was a failure, keep it and put the learning after it - if a role produced nothing concrete, say so and leave it thin rather than inflating it

Step 4: Read it back against me

Read the draft as if you were me. Tell me whether this sounds like something I would say out loud. Quote the three lines you are least sure about and say why.

Output rules

You may not introduce a fact, a scope, a title, a credential, or a metric that did not come out of my mouth in Step 1.
03Why People're Using

Spend the effort up front instead of polishing after

Three outcomes, one loop. The draft is written from things you actually said rather than things a job description implies, the lines that read as true are the ones you are least embarrassed to defend, and you are not polishing a generic document into a slightly less generic one.

Your register, established before anything is written

Step 0 runs first and is not skippable. Three unedited sentences plus a list of words you would never use gives the agent a style boundary, and the three words it rejects are usually the ones doing the damage — leveraged, dynamic, passionate. This is the whole difference between the average candidate and a specific one, and it costs three sentences of typing.

The questions that produce the lines that read as true

Questions 4 and 5 are doing the work. What you tried that failed, and what you decided against someone's advice, are the two answers no job description contains and no amount of rewriting can manufacture. They are also the most defensible lines on any résumé, because you remember them.

Thin where it has to be, not full

Step 3 is told to leave a thin role thin and say so, rather than filling it. A role that produced nothing concrete is a real finding about the document, and padding it puts the weakest lines on the page. You would rather send three evidenced lines for a role than six you would struggle to expand on.

04FAQ

Frequently asked questions

The questions people ask before letting an agent interview them for their own résumé.

By making the voice an input constraint rather than an instruction. "Write it like me" is unactionable, because the model has never heard you talk about work. What it can act on is evidence: three unedited sentences in your own words, a list of words you would never use about yourself, and a list you actually use. That gives it a boundary it can check each line against, which is why Step 0 runs before any drafting and refuses to proceed until it has shown you the paragraph describing your register back.

The routine is not the material, the situation is. Question 1 — what was broken, slow, missing, or unbuilt when you arrived — works on almost any role, because every job exists because something was insufficient. Question 4 works too: almost everyone has a process they inherited and tried to change and could not, and that answer says more about how you work than a list of duties. If six questions genuinely produce nothing, that is a finding about the document rather than about you, and the method says so instead of manufacturing a bullet to fill the space.

A specific one, and this method asks for one on purpose. Question 4 asks what you tried that did not work and why; question 5 asks what you decided against someone's advice; question 6 asks what you would do differently. Those three answers together produce a short, honest account of judgement rather than a list of duties, and it is now the thing reviewers are looking for — the concern about AI-written résumés is overclaiming, not assistance. What does not belong is an apology dressed up as a lesson, or a failure with no decision attached.

Better than the alternative, because you are not being asked to write one. You are being asked six questions per role about work you did, which is a much easier thing to answer than describing yourself in a summary. That summary is the part most people freeze on, and the method deliberately never asks you to write it — Step 3 writes only the experience section, from what came out of the interview. If you have never held a role, the honest starting point is a different page about building from coursework and projects.