How to write a software engineer resume with Gemini

Gemini is the AI tool a lot of software engineers reach for when they’re already in Google’s ecosystem — it’s built into Workspace, it’s free at the entry tier, and it has access to current web information that ChatGPT and Claude don’t by default. But Gemini has a specific failure mode on engineering resumes that’s different from both ChatGPT and Claude: it hallucinates facts. Dates, version numbers, framework features, and tool capabilities all get confidently mixed up in ways that can leave a candidate looking either dishonest or out of date.

This guide walks through what Gemini does to a software engineer resume by default, where it genuinely outperforms other tools (it’s actually the best of the three at one specific task), the prompt structure that works around the hallucination problem, the failure modes to fix manually, and a real before-and-after. (For the ChatGPT version of this guide and the Claude version, see the sister articles.)

What Gemini does to software engineer resumes

Gemini’s default behavior on a software engineer resume is to produce output that reads as confident, current, and specific — which is the problem. The tool will happily generate bullet points referencing technologies you didn’t use, version numbers that don’t match your experience, and dates that drift away from your actual employment history. None of this is malicious. Gemini is pulling pattern-matched details from its training data and sometimes from its web access, then mixing them with the content you provided in ways that produce plausible but incorrect output.

The most common pattern: you paste a bullet about migrating an authentication service, and Gemini returns a tailored version that mentions OAuth 2.1 even though your real work used OAuth 2.0, or specifies that you used Spring Security 6 even though your project predates that version. The reader has no way to know these are wrong. You do, but only if you read carefully. The danger is that the bullet sounds more impressive in the wrong way and you ship it without catching the drift.

Gemini also has a tendency to inflate version numbers and feature claims toward the bleeding edge. If your training data shows that a popular framework had a new release recently, Gemini will sometimes assume you used the new version even if your bullet says nothing about versions. This is the failure mode most likely to get caught in a technical interview, because the interviewer will ask about a feature you don’t actually know.

Where Gemini is genuinely useful for software engineer resumes

Gemini’s web access and its strong instincts for surfacing recent information make it the right tool for one specific task: identifying what the current version of the technology stack at your target company looks like and what keywords are showing up in the job postings you’re applying to. ChatGPT and Claude both have older training cutoffs (most of the time) and can’t check what a company’s engineering blog published last week. Gemini can.

The pattern that works: use Gemini for the parts of the job application research process that benefit from current information, and use a different tool (or your own editing pass) for the parts where accuracy on your own resume content matters more than recency.

1. Researching the target company’s current stack. Ask Gemini to summarize what technologies a specific company’s engineering team has written about in the last year. Use the result to identify which of your skills you should foreground.
2. Surfacing keyword gaps in your resume vs. a job posting. Paste your resume and a job posting and ask Gemini to list every technology, methodology, or tool the job mentions that doesn’t appear in your resume. Then you decide which ones you have legitimate experience with.
3. Finding what’s changed in your stack since you last updated your resume. If you wrote your last resume two years ago and your tools have moved forward, Gemini is the best of the three at telling you what new conventions or framework features you might want to mention.
4. Pulling salary and OTE benchmarks for your role and region. Not directly resume work, but useful context when you’re negotiating an offer.
5. Drafting LinkedIn and X posts about your job search. Gemini’s instinct toward current, conversational copy is closer to what works on social platforms than ChatGPT’s more formal default voice.

The prompt structure that works for software engineer resumes

The fix for Gemini’s hallucination problem is a prompt that explicitly forbids invention. Gemini responds well to numbered rules and explicit constraints on what it’s allowed to add. The default “tailor my resume” ask is what produces the version-number drift. A constrained prompt that locks Gemini to the source content produces output that’s much closer to usable.

Here’s a prompt that consistently produces better output for software engineer resumes from Gemini:

Tailoring vs rewriting: pick the right mode

The tailoring-vs-rewriting distinction matters more for Gemini than for any other tool, because Gemini’s hallucination risk scales with how much freedom you give the model. In tailoring mode, the constrained prompt above limits the damage because you’re only asking the model to rewrite bullets you provide. In rewriting mode — where you’re asking Gemini to modernize an old resume from scratch — the failure mode explodes, because the model has more room to add details that drift from your real work history.

The practical implication: never use Gemini in unconstrained rewriting mode for the final draft of a resume. If you need a structural rewrite, do it yourself or use a different tool, then use Gemini in tailoring mode against the rewritten draft.

The exception is the research mode covered in the ‘genuinely useful’ section above — Gemini’s web access is a real advantage when the task is ‘tell me about the target company’ rather than ‘tell me about my resume.’ Use the tool for what it’s good at and stop using it for what it isn’t.

What Gemini gets wrong about software engineer resumes

Even with the constrained prompt above, Gemini has predictable failure modes on software engineer resumes. These are the ones to watch for in every draft and correct manually before the resume goes out:

1. It hallucinates version numbers. Gemini will confidently insert version numbers (Spring Boot 3.2, React 19, Python 3.12) that don’t match what you actually used. Read every version reference in the output against your real experience.
2. It adds bleeding-edge features. If your bullet mentions OAuth, Gemini might add “with PKCE.” If you used React, Gemini might add “with Server Components.” Strip any feature you didn’t actually use.
3. It inflates scale. Same as ChatGPT, but worse because Gemini sometimes attaches specific numbers (“handling 10K QPS,” “reducing p99 latency by 40%”) that come from training-data patterns, not from your work.
4. It mixes up similar technologies. Gemini will sometimes substitute one tool for a similar one (FastAPI for Flask, gRPC for REST, Kafka for RabbitMQ). Always verify the tools named in the output match what you wrote.
5. It drifts on dates. If your resume covers 2020-2024, Gemini will occasionally produce bullets that reference technologies that didn’t exist until 2025. Cross-check.
6. It produces overconfident senior-role claims. Gemini is the opposite of Claude here — it tends to over-credit your work, especially for staff/principal roles. It will use “led” or “designed” for projects you contributed to. Same fix as ChatGPT: be careful with these verbs.

A real before-and-after

Here’s a real before-and-after using the same observability bullet from the ChatGPT and Claude guides, this time showing Gemini’s default failure mode (hallucinated specifics) and the manual edit pass that fixes it.

What you should never let Gemini write on a software engineer resume

There are a few categories of content where Gemini’s output should never make it into a software engineer resume without being rewritten by hand. Most of these overlap with the ChatGPT and Claude guides, but Gemini’s hallucination tendency adds a few unique ones.

1. Any version number Gemini added. If your source bullet doesn’t mention a version and Gemini’s output does, delete the version. Always. It’s either invented or a guess.
2. Any technology you didn’t list. Gemini will add adjacent tools (Redis when you used Memcached, Kafka when you used RabbitMQ, gRPC when you used REST). Strip every tool you didn’t actually use.
3. Quantified results that came from nowhere. If your source bullet has no numbers and Gemini’s output has numbers, delete them. (For the related issue of how to tailor a resume without lying, see our broader piece.)
4. Headcount or org-impact claims. Same as the other two guides: never let an AI tool generate claims about how many people you mentored or led.
5. System scale claims you can’t walk through. Gemini is the most likely of the three tools to produce numbers like “processing 10M events/day” that sound plausible but aren’t from your experience. These are the easiest things to verify in a technical interview.

Frequently asked questions

Why does Gemini make up version numbers and tool features?

Because Gemini was trained on a corpus that includes a lot of documentation, blog posts, and changelogs for popular tools. When it generates a tailored resume bullet, it pattern-matches your work against similar work it has seen and pulls in technical details from that pattern — including version numbers and feature names. The model has no way to know that the details it pulled don’t match your actual project. The fix is to give Gemini an explicit instruction not to add any technical detail you didn’t provide, and to read every specific in the output against your real experience.

Is Gemini's web access useful for resume writing?

For research, yes. For the final draft, no. The web access lets Gemini pull current information about the target company’s tech stack, recent product launches, or open job postings — useful inputs when you’re deciding which of your skills to foreground. But the same web access also makes Gemini more likely to import technical details that aren’t yours into the resume itself. Use the web access for the research phase, then turn it off (or switch to a more constrained tool) for the actual rewrite.

Should I use Gemini Pro or Gemini Flash for resume work?

For tailoring with the constrained prompt above, Flash is enough. Pro is more capable on long-context reasoning but resume tailoring is a short-context task. Flash is faster, cheaper, and equivalent on this specific job. The exception is if you’re pasting in a very long resume (multi-page senior-engineer history) along with a very long job description — in that case, Pro’s context handling is genuinely better.

Will Gemini get the dates right on my work history?

Mostly, but not reliably. Gemini sometimes references technologies that weren’t released until after your stated employment dates, which creates a contradiction a careful recruiter will catch. The cleanest workaround is to do a final read-through after Gemini’s pass and verify that every technology mentioned in a job entry is something that existed during the dates of that job. This sounds tedious but takes about 30 seconds per role.

How does Gemini compare to ChatGPT and Claude for resume work?

Gemini is best for research (target company stack, current job-posting language, salary benchmarks). ChatGPT is best for direct bullet rewrites with quantified outcomes. Claude is best for cover letters, professional summaries, and editing for voice. None of the three is a one-click resume writer. The honest workflow that produces the best result uses all three: Gemini to research, ChatGPT to draft bullets, Claude to write the summary and cover letter, and then a human edit pass on the whole thing.

The recruiter test

The recruiter test for a Gemini-drafted resume has one extra step compared to ChatGPT and Claude: read every specific. Every version number, every tool name, every quantified result. If anything in the output is more specific than what you wrote in your source, it’s probably wrong, and the wrong specifics get caught in technical interviews more reliably than any other failure mode.

Gemini is a useful tool for the research phase of resume work and a risky tool for the final draft. The constrained prompt above produces output that needs less editing than the unconstrained version, but the manual verification pass for hallucinations is non-negotiable. The same structural problem applies as with ChatGPT and Claude: doing this by hand for every job application takes time you don’t have if you’re applying to 20 or 30 roles. That’s the gap purpose-built resume tools fill — they constrain the model in ways that prevent the hallucination failure mode by default.

Related reading for software engineer candidates