All posts

Which Claude is best for a resume? We ran one resume through all four models

One resume and a real job posting, sent to Claude Fable 5.2, Opus 5.5, Sonnet 5.5 and Haiku 5.5, then checked line by line. What each changed.

Guides Updated 13 Nov 2026 10 min read

Which Claude is best for a resume? On our test, Claude Sonnet 5.5 given clear rules, which is also the one on the free plan. We sent one resume and one real job posting to all four current Claude models on 13 November 2026, once with a bare "tailor my resume" prompt and once with a prompt that sets hard rules. With the rules, Sonnet 5.5 and Fable 5.2 were the two resumes in which nothing written past the evidence held up, and Sonnet's drew no flag at all. Opus 5.5, the model most people would pay for, stretched the most lines: three without rules, two with them.

No model invented a number, a tool or an employer. Every stretch was the same kind: the posting's own words written into the candidate's record. That is a prompt problem more than a model problem, and it is why the plan you need depends on how much you tailor, not on which model writes best.

Who ran this, and how: JobShifu, which sells a resume tailoring product built on Claude. The resume is our fictional test candidate, Alex Morgan. The posting is a live Robinhood listing. The checks are the code JobShifu runs on its own resumes. Every tailored resume, every flagged line and our verdict on each flag are in a public data file [1].

The test: one resume, one real posting, four models

The resume. Alex Morgan, a senior software engineer with 9 years in backend work: a billing pipeline moved to Kafka, a Redis cache that cut p95 latency from 820ms to 210ms, a feature-flag service serving about 40,000 evaluations per second, 4 engineers mentored. Fictional, built for testing, 630 words.

The posting. Robinhood's Senior Software Engineer, Backend, in Menlo Park and New York [2]. It asks for low-latency, large-scale distributed systems, highly concurrent systems, REST APIs that serve millions of customers, and mentoring "through code reviews, design discussions, and hands-on technical guidance". It is a close fit with gaps: Alex has billing, not trading or payments, and no customer-scale figure.

The models. Claude Fable 5.2, Opus 5.5, Sonnet 5.5 and Haiku 5.5, the current lineup [3]. Each got the same message through Anthropic's API, with no system prompt and each model's default settings.

The two prompts.

  • *Bare:* "Tailor my resume to this job posting. Give me the full tailored resume."
  • *Rules:* Prompt 6 from our free prompts guide [4]. Use only what is in the resume, list anything missing under "NOT WRITTEN", do not add or round a number, do not upgrade a verb, keep each bullet under its employer.

The checks. Each tailored resume was read by JobShifu's Calibration Engine [5], the same code that checks a JobShifu build:

  1. Numbers. Any figure the resume states nowhere.
  2. Posting echo. Any distinctive term from the posting that the resume never writes. In JobShifu this check blocks the build.
  3. Drift. A model check that compares each line with the resume lines it draws on, and flags a line that claims more or something different.

Then we read every drift flag ourselves against the resume, because the drift check is a model too and it can be wrong. Of 12 flags, 9 held up and 3 did not.

Without rules, every model rewrote the summary in the posting's words

Bare prompt Lines Kept word for word Invented numbers Posting echo Stretched lines (held up)
Fable 5.2 33 22 0 0 1
Opus 5.5 32 16 0 0 3
Sonnet 5.5 35 28 0 0 1
Haiku 5.5 34 23 0 0 1

All four kept most bullets close to the original and left the numbers alone. All four rewrote the summary, and every summary picked up something the resume does not say:

  • Opus 5.5: "payment-safe workflow orchestration, and high-concurrency services handling 40,000 requests per second". The resume has billing and a fix for duplicate charges, not payments, and its 40,000 is *evaluations* per second on one feature-flag service.
  • Sonnet 5.5: "billing, payments-adjacent and data-retention systems".
  • Haiku 5.5: "from billing and payments pipelines" and "large-scale distributed systems".
  • Fable 5.2: "distributed systems in production" with "a focus on correctness". The resume says "backend services and developer platforms" and never says correctness.

Opus 5.5 also changed two bullets. "Led the migration of the billing pipeline" became "Led the redesign", and "Mentored 4 engineers" gained "through code reviews, design discussions and hands-on guidance", the posting's own phrase. Opus flagged that one itself in its notes: keep the wording only if it is accurate.

Opus rewrote the most: 16 of its 32 lines kept Alex's wording, against 28 of 35 for Sonnet. More rewriting gives more chances to drift, and that is where its extra flags came from.

With the hard rules, the count fell, and Opus still slipped twice

Rules prompt Lines Kept word for word Invented numbers Posting echo Stretched lines (held up) Items on the NOT WRITTEN list
Fable 5.2 21 17 0 0 0 13
Opus 5.5 21 14 0 0 2 10
Sonnet 5.5 18 14 0 0 0 9
Haiku 5.5 21 17 0 0 1 12

The rules cut the resumes to about one page and kept most bullets word for word. Stretched lines fell from 6 to 3 across the four models.

Opus 5.5's two came from the one rule that invites them: "use the posting's own house language where it truthfully describes what I did." It opened the CI bullet with "Improved developer productivity", the posting's phrase and an outcome the resume never claims, and it turned "the duplicate-charge class of bugs" into "the duplicate-charge class of correctness bugs". Haiku 5.5 added "low-latency distributed systems" to the summary's stated focus.

What no model did: invent a number or a tool

Across all eight resumes the number check found 0 figures that the resume does not state, and the posting-echo check found 0 posting terms the resume never writes. No model claimed trading experience or gave Alex a customer count.

That is a better result than the same kind of test produced for resume tools. In our invented skill test, six of eight tools added something the resume did not say [6]. Two differences matter. This posting is a close fit, so there was less pressure to fill a gap. And a chat model given your whole resume tends to keep its facts; what it bends is the framing around them.

The NOT WRITTEN lists were the most useful part

With the rules prompt, all four models listed what the posting wants and the resume does not show, and the four lists agree on the core gaps:

  • no trading, brokerage, payments or ledger work in production
  • no figure close to "millions of customers"
  • nothing about designing for concurrency, beyond the 40,000 evaluations per second
  • REST APIs only at the junior job
  • mentoring with no detail about how

Fable 5.2's list was the longest, at 13 items, and it also named seven listed skills with no bullet behind them, such as gRPC and Terraform. Sonnet 5.5's was the shortest, at 9 items, and covered the same core gaps.

That list is the start of the next step, not the end of this one. Each item is either a gap to answer in a cover letter, or real work missing from your master resume. If it is real, add it there in your own words, so the next tailoring starts from more.

What each model cost to run

Model Output, rules prompt Output, bare prompt API cost, rules prompt (batch rate)
Fable 5.2 12,601 tokens 3,791 tokens $0.265
Opus 5.5 9,065 tokens 2,887 tokens $0.097
Sonnet 5.5 5,518 tokens 2,784 tokens $0.031
Haiku 5.5 11,545 tokens 3,710 tokens $0.003

In a Claude chat you do not pay per token, you spend your plan's usage limit, and longer answers from heavier models spend it faster. Fable 5.2 wrote more than twice Sonnet's output for the same job, at about eight times the cost per answer, and its resume was no cleaner.

So which Claude, on which plan

Plan details below were read off Anthropic's pricing page and help article on 13 November 2026 [7] [8].

If you Use Plan Why
Tailor for a few jobs a week Sonnet, with the rules prompt Free ($0) The only resume in our test with no flag at all; the free plan's limit is how much you can run, not quality
Tailor for most applications Sonnet for drafts, Opus 5.5 if you want a second opinion Pro ($20 a month, or $17 a month billed yearly) More usage, so you can run the checks below on every application
Want the "best" model Not Fable Any On Pro, Fable is paid with usage credits; on Max it is included up to half your weekly limit. It wrote the longest answer and no cleaner a resume

Two caveats. The free plan gives Sonnet and Haiku, not Opus or Fable [7]. And Anthropic does not say which Sonnet version each plan serves, so check the model menu in the app.

How to run the same test on your own resume

You do not need our code to catch what we caught. You need the rules, and a separate pass that reads the draft back.

  1. Create a Claude Project for your search. Projects are on the free plan, up to five of them [7].
  2. Add your master resume to the Project's knowledge. Use the long version with every number and tool in it, not the page you send. Every chat inside the Project can read it [9].
  3. Paste the hard rules into the Project instructions, from Prompt 6 in the prompts guide [4]. Consider deleting the "use the posting's own house language" line: in our test it is the rule Opus 5.5 used to add the posting's phrases.
  4. One chat per job. Before you spend one on a posting, check it is likely still open. Paste the posting, run the prompt, and ask for a change log that quotes the resume line behind every changed line.
  5. Read the summary first. Every stretch in our bare-prompt run was in the summary, plus two Opus bullets. Compare each phrase in it to your own words, and look hardest at any phrase that also appears in the posting.
  6. Check verbs and numbers against the change log. "Migration" to "redesign" and "evaluations" to "requests" are the kind of change a quick read misses.
  7. Keep the NOT WRITTEN list. Answer the gaps in a cover letter, or add real work back to your master resume.
Three things that are true at once in a bare chat window: what you paste is the posting plus whatever your resume happened to say, what the model holds about you is one static read for as long as the window keeps it, and at a gap it continues because continuing is the job.
Why a chat window drifts toward the posting.

What JobShifu runs, and why it is not on the newest models

Powered by Anthropic's Claude, JobShifu's resume tailoring runs the same loop with two things a chat window does not have.

As of 13 November 2026, the tailoring pass runs on Claude Opus 4.8, Claude Sonnet 4.6 reads postings and runs the scope, entailment and drift checks, and Claude Haiku 5.5 flags phrasing that reads as generated [10]. We move a step to a newer model only when a test on real resumes says so. The drift judge that read this test's output is the production one, on Sonnet 4.6. In September we tested Sonnet 5.5 for the entailment check, and it caught 38 of 42 planted fabrications against Sonnet 4.6's 42, so the check stayed on 4.6.

The first difference is the material. Career facts live in a Vault, each one confirmed with a source, and every proposed line names the facts it draws on. The second is where the check sits. In a chat window the checks above are advice. In JobShifu eleven checks run on every build and two block it: a line that cites nothing, and a line carrying a posting term found nowhere in your Vault or uploaded resume. The drift check is one of the nine that only report. When it flags a line in Express mode, your original wording goes back in [5].

The same request in two contexts. In a bare chat window the material is the posting plus whatever you pasted, so at a gap a plausible line gets made out of the posting. With confirmed facts behind the same model, the line is left off and the gap is named.
Only the material and the check change.

The cost is the same as the benefit: the Vault has to be filled in before tailoring is any good. The free tier needs no card and includes two fully tailored resumes every day [11]. You do not need a Claude subscription to use it.

What this test does not show

It is one resume, one posting and one run per model, so a one-line difference between two models is within noise. Alex's resume is a close fit for the posting. A career changer against a stretch posting is where models are most tempted to write past the evidence, and that was not tested here. We called the models through Anthropic's API, which does not apply the Claude app's own system prompt, so a chat in the app may answer a little differently.

Common questions

Is Claude Pro worth it for resume writing?

If you tailor for most of your applications, yes. You get more usage than the free plan and access to Opus 5.5 [7], which lets you run the draft and the checks on every application. In our test, though, the free plan's Sonnet with the rules prompt produced the only resume with no flag at all, so Pro buys volume, not a better draft.

Is Claude Fable worth it for a resume?

No. In our test Fable 5.2's resume was no cleaner than Sonnet's. With the rules prompt its answer was more than twice as long, and it cost about eight times as much per answer through the API. On Pro it runs on usage credits, and on Max it is capped at half your weekly limit [8].

Is ChatGPT or Claude better for a resume?

We did not test ChatGPT here, so we cannot name a winner. The result that matters for either is the one above: the hard rules and a separate check do more than the choice of model.

Can Claude write a resume from scratch?

It can produce something shaped like a resume, but every specific in it will come from the posting or from what resumes usually say, because nothing of yours was in front of it. Build a master document first and ask the model to select and reorder [4].

Sources

  1. JobShifu, four-model resume test data file, 13 November 2026: claude-model-resume-test-2026-11-13.json, CC BY 4.0. Every tailored resume, every flagged line with the check's reason, and our verdict on each.
  2. Robinhood, "Senior Software Engineer, Backend": boards.greenhouse.io/robinhood/jobs/7264931. Fetched 13 November 2026.
  3. Anthropic, models overview: platform.claude.com/docs/en/models/overview. Model IDs as listed 13 November 2026.
  4. JobShifu, "ChatGPT prompts to tailor a resume to a job description, free": /blog/tailor-resume-to-job-description-with-ai-free. Prompt 6 used as written, with a one-page target.
  5. JobShifu, the Calibration Engine: /calibration. Read 13 November 2026.
  6. JobShifu, "We asked eight resume tools to add a skill the resume doesn't have": /blog/resume-tools-invented-skill-test. Published 12 November 2026.
  7. Anthropic, Claude plans and pricing: claude.com/pricing. Read 13 November 2026.
  8. Anthropic Help Center, "Claude Fable models on your plan": support.claude.com/en/articles/15424964-claude-fable-models-on-your-plan. Read 13 November 2026.
  9. Anthropic Help Center, "What are projects?": support.claude.com/en/articles/9517075-what-are-projects. Read 3 October 2026.
  10. JobShifu, "Which AI model does JobShifu use?": /faq. Model split from JobShifu's own configuration, 13 November 2026.
  11. JobShifu pricing: /pricing.
← All posts