Gemini Prompts for Resume Writing
28 copy-paste prompts for a fact bank, a posting you do not score, bullet edits, projects, career changes, a Gem or a Doc, and a final audit. Gemini does not invent the job you did.
Last updated September 26, 2026
What this page is for
Resume writing prompts should make your evidence easier to read. They should not invent a stronger career. Gemini is a practical place to do that work when the notes already live in a Doc, a Drive file, or a Gem knowledge upload.
The prompts below ask for questions, tables, and a change log. They avoid a universal score. A score hides which line is unsupported. If you need standard headings and a keyword map aimed at applicant tracking systems, use the Claude prompts for an ATS-friendly resume. Those prompts solve a different problem.
For the surrounding steps, use How to Use Gemini for Resume Writing and How to Use Gemini for a Resume. This page stays on prompts you can paste.
Which prompt to run
| Job | Paste | Gemini must not |
|---|---|---|
| Build a fact bank | Rough notes, reviews, or a project list | Write the resume during the interview |
| Read a posting | The full job description and the fact bank | Return a match percentage |
| Edit a bullet | One bullet and the fact that supports it | Turn assistance into leadership |
| Career change | Old context and the target field | Rename you to the new job title |
| Use a Gem or a Doc | Master file plus this job's draft | Overwrite the master |
| Final audit | Draft and fact bank, side by side | Award a score or hide a gap |
How to brief Gemini
Open Gemini, attach the fact bank if uploads are available, and paste one prompt. If you create a Gem, put the standing rules in the instructions and the master file under Knowledge. Google's help pages say a Gem can take files from your device or Drive, and that a Drive file tracks the latest version when the connection is on. Paste the posting in the chat anyway.
In Docs, work on a copy. Accept or reject one suggestion. A single click that replaces the whole document is hard to audit. When the draft is stable, export the file the employer asked for and read it. Wording can be honest and the file can still be a poor export. That check is on the how-to, not in these prompts.
Other resume collections: AI resume prompts, resume prompts, ChatGPT for resume writing, and Gemini prompts.
28 copy-paste Gemini prompts
Replace every bracket. If Gemini adds an employer, a date, or a metric you do not recognise, delete that line.
Build a fact bank before any prose
Gemini should interview you and label the notes. The resume comes later, in a different prompt.
I am collecting a resume fact bank. Ask me up to eight questions about roles, dates, tools, and outcomes. Do not write bullets yet. If I skip a question, mark that field UNKNOWN. What I already know: [paste rough notes]
Split these notes into personal work and team work. For each line, label MINE, TEAM, or UNCLEAR. Do not turn a team result into a personal achievement. <notes> [paste] </notes>
Read this career note and return a table with columns: employer, official title, start, end, tools, decision I made, outcome, confidential detail to remove. Use UNKNOWN when a cell is not in the note. Do not infer a title from the duties. <notes> [paste] </notes>
Mark lines I should not upload to a consumer AI tool. Look for client names, health details, account numbers, home addresses, and unpublished financials. Suggest a placeholder for each. Leave the rest of the wording alone. <notes> [paste] </notes>
Read one posting without a match score
The posting is a target, not a script. Gemini should show gaps instead of filling them.
<job_description> [paste the full posting] </job_description> Split the posting into must-have duties, preferred qualifications, and workplace signals. Quote the posting. Do not score me. Do not rewrite a resume.
<job_description> [paste] </job_description> <fact_bank> [paste labeled facts] </fact_bank> Build a table: requirement, fact-bank ID or MISSING, and whether it belongs in the summary or only in a bullet. No percentages. No new facts.
From this table of matches, choose three requirements to foreground for [target title]. Say why the others should stay in the body or be left off. Refuse a requirement that is MISSING. <table> [paste the table from the previous prompt] </table>
List posting terms I should not copy. A term belongs on this list when my fact bank has no evidence for it. Quote the term and the closest true experience, or say NO NEIGHBOR. <job_description> [paste] </job_description> <fact_bank> [paste] </fact_bank>
Rewrite one claim at a time
One bullet, one audit. A full-page rewrite hides a change in seniority.
<bullet> [paste one bullet] </bullet> <fact> [the fact-bank row that supports it] </fact> Give two rewrites under 25 words. Version A keeps a number only if it is in the fact. Version B stays qualitative. Under each, list actor, action, scope, and time. Flag any word that upgrades my role.
This bullet says "supported" or "helped". Rewrite it only if my fact says I owned the decision. If I assisted, keep the assist and name what I actually did. Do not change "supported" into "led". <bullet> [paste] </bullet> <fact> [paste] </fact>
Compare the original bullet with this rewrite. Recommend KEEP, EDIT, or REJECT. Quote every change to actor, scale, tool, or certainty. Do not write a third version. <original> [paste] </original> <rewrite> [paste] </rewrite>
I have a performance review excerpt and I want resume facts, not the reviewer's adjectives. Extract duties and outcomes. Attribute opinions to the reviewer or drop them. Do not add metrics that the excerpt does not contain. <review> [paste] </review>
Summary, skills, and projects
Write the summary after the bullets exist. Skills and projects have to point at evidence.
Write two summaries under 50 words for [target title]. Use only these bullets. Summary A leads with domain. Summary B leads with a tool I can discuss. Cut "results-driven", "passionate", and "dynamic". If a sentence needs a fact I did not provide, write NEEDS FACT. <bullets> [paste approved bullets] </bullets>
Draft a skills list of at most 10 items from the fact bank. Group them as Tools, Methods, and Domain. Each item needs a six-word evidence note or NEEDS EVIDENCE. Do not add a skill because the posting named it. <fact_bank> [paste] </fact_bank> <posting_terms> [optional] </posting_terms>
Turn this project note into two resume lines: what I built, who used it, and the constraint. If there is no user or outcome, say so and keep the line descriptive. <project> [paste] </project>
I have more projects than paid roles. Propose an order: Projects, then Experience, then Education, or the reverse. Base it on which section has stronger evidence for [target role]. Do not invent a job title to hide the project work. <projects> [paste] </projects> <roles> [paste] </roles>
Career change, education, and a thin history
Adjacent experience can be clear without pretending it is the same job.
I am moving from [old field] to [target field]. Using only these facts, write three bullets that show the transferable work and name the old context so I do not look like I already held the new title. <facts> [paste] </facts>
Education section. Include school, credential, and dates as written. Add one coursework or thesis line only if it is in the notes and relevant to [target role]. Do not imply a degree is finished if the note says in progress. <education_notes> [paste] </education_notes>
My recent history is freelance and volunteer work. Format each item with organization, role, dates, and one outcome. Keep unpaid work labeled as volunteer. Do not merge clients into a fake full-time job. <notes> [paste] </notes>
I have a gap from [start] to [end]. Here is what I am willing to say: [paste] Give two plain wording options and the interview question each might raise. Do not hide the months or invent a job.
Gems, Docs, and uploaded files
These prompts use Gemini's file and Gem surfaces. They still cannot see a job you forgot to attach.
Gem instructions to save: You edit resumes. Use only the knowledge file and the job description in the chat. Never invent employers, titles, dates, tools, or metrics. Write MISSING instead. Ask before you assume. Return a change log with every rewrite. Rewrite those instructions so they are shorter, then list two example chats I should try before I trust the Gem.
I uploaded my fact bank. Read the file first and quote three facts you will rely on. Then wait. Do not draft a resume until I paste a job description in the next message. File name: [name]
I am working in a Google Doc that is the tailored copy, not the master. Suggest five comments I can accept or reject one at a time. Each comment needs the sentence, the replacement, and the fact-bank line that supports it. Do not rewrite the whole doc. <doc_excerpt> [paste] </doc_excerpt> <fact_bank> [paste] </fact_bank>
Two files are attached: master fact bank and this job's draft. List claims in the draft that are not in the master. Quote both. Recommend cut, or keep only if I add the fact to the master first. Do not blend the files.
Audit, privacy, and interview backup
The last prompts look for drift. You decide what gets submitted.
Audit this draft against the fact bank. Table: claim, fact-bank support or MISSING, date consistency, and tense. No match score. <draft> [paste] </draft> <fact_bank> [paste] </fact_bank>
Privacy pass. List personal data in this draft that a job application does not need, including full address, ID numbers, and other people's names. Suggest a placeholder. Do not remove my email or phone if I marked them as required. <draft> [paste] </draft>
Prepare interview backup for the three bullets most likely to be questioned. For each: situation, my action, the record I could show, and a detail I must not exaggerate. Use only the draft and the fact bank. <draft> [paste] </draft> <fact_bank> [paste] </fact_bank>
Final writing check for [target role]. Return: sentences that over-claim, tools named once without evidence, and the single edit that most reduces risk. Then stop. For parser-safe headings and keyword maps I will use a different prompt set. Do not give me a score.
Tips that keep the resume yours
- Finish the fact bank before you ask for a summary or a full draft.
- Paste the posting in every chat, even if a Gem already holds your master resume.
- Rewrite one bullet and read the change log before you continue.
- Leave [METRIC] in the draft when the number is not in your notes.
- Keep the master doc and the tailored doc separate so a bad rewrite cannot replace the source.
- Upload at most the files the prompt needs. Google documents a cap of about 10 files per prompt, and limits vary.
- Strip client names and identity numbers before the file goes into Gemini.
- Use the Claude ATS prompt page when the next problem is headings and parsing, not wording.
Primary sources
- Gemini Apps Help: upload and analyze files
- Gemini Apps Help: tips for custom Gems
- Gemini Apps Help: use Gems
Checked September 26, 2026. File counts, Drive connections, and plan limits change. Use the help page and the controls on your account if they disagree with this summary.
Gemini resume writing FAQ
What is a good Gemini prompt for resume writing?
Give Gemini a fact bank and one job to do, such as ask questions, rewrite a single bullet, or compare a draft with the notes. Tell it to write MISSING when a date, tool, or result is not in the notes. A prompt that says make my resume impressive invites invented metrics and a higher title than you held.
Can I upload my resume to Gemini?
Gemini Apps can upload files and, when your account allows it, use files from Google Drive. Google documents a limit of up to 10 files in one prompt, subject to availability, plus rolling usage limits that are higher on AI Pro and AI Ultra. Remove identity numbers, full home addresses, and confidential client names before you upload. A resume is personal data. Use an account your employer or school allows.
Should I make a Gem for resume writing?
A Gem is useful when you want the same rules on every application: use only the fact bank, never upgrade a title, and ask before assuming. You can add a master fact file under Knowledge from your device or Drive. Drive files follow the latest version when Workspace is connected and activity settings allow it. Still paste the target job description in each chat. A stored resume is not a stored posting.
How is this different from Claude ATS resume prompts?
The Claude page is a prompt set for parser-safe headings, posting-keyword maps, and a cover-letter handoff. This page is a Gemini writing set: fact banks, Docs and Drive, Gems, career changes, projects, and an honesty audit. Use the Claude prompts when the next risk is file parsing. Use these when the next risk is a sentence that overstates your work.
Can Gemini add numbers to my bullets?
Only numbers that appear in your notes. Ask it to leave [METRIC] where a figure would help and you still need to look it up. A precise qualitative result is safer than a percentage you cannot explain in an interview.
Will Gemini tailor my resume to any job?
It can reorder emphasis for one posting using evidence you already have. It should not copy every requirement into a skills list. Ask for a table of requirement, evidence, and MISSING, with no match score. Scores are not a hiring prediction.
Can I use Gemini inside a Google Doc?
If Gemini is available in your Google Docs account, keep the fact bank in one doc and the tailored draft in another. Ask for suggestions you can accept one sentence at a time. Do not replace the master doc with a generated version. Menus differ by account, so follow the controls you see.
How is this different from the Gemini resume how-to?
The how-to is the workflow: fact bank, matrix, layout, and a human check of the exported file. This page is the copy-paste prompt library for those steps. Use the how-to to decide the order. Use these prompts when you are in the chat.