How to get a job at Anthropic

Most advice about getting hired at Anthropic assumes you want to be a research scientist. Right now that describes a minority of the jobs. Of the 599 roles open today, 317 are outside engineering and research entirely, and Sales alone (113) is nearly the size of the whole AI Research & Engineering org (66).

That is the first thing worth knowing, because it changes who should be applying. The second is that Anthropic publishes more direct advice to applicants than almost any company at its scale, and most people never read it.

Take their resume advice literally

On its careers page, Anthropic says: “If you've done interesting independent research, written a thoughtful blog post, or contributed to open source, put that at the top of your resume.”

That is not a throwaway line. It is an instruction about document structure, and it inverts the convention most people follow, where employment history goes first and anything self-directed gets a “Projects” footnote on page two. They are telling you the artefact matters more than the employer attached to it.

The same page notes that about half their technical staff had no prior ML experience, that about half have PhDs, and that plenty of colleagues never went to college. If you have been assuming a doctorate is the price of entry, they have said in writing that it is not.

The engineering and research split is deliberately blurry

Anthropic describes it plainly: engineers there do lots of research, and researchers do lots of engineering, and their papers regularly list engineers as authors, including as first author. If you are a strong engineer without a research background, that is a door rather than a wall, and it is worth reflecting in how you describe your work.

They want you to use Claude on your application

Anthropic explicitly encourages candidates to use AI tools when applying, to show what you can do with them. This is genuinely unusual. Most companies at least discourage it and many now screen for it.

The useful reading is not “generate your cover letter.” It is that a submission which is obviously the model's default voice tells them nothing about you, whereas one where the tool clearly did the heavy lifting on something specific tells them quite a lot.

Where the roles actually are

San Francisco dominates at 351 of 599 roles. Remote accounts for 83, and Anthropic's stated policy is that most staff are in the Bay Area with regular office presence, with remote possible for people willing to visit monthly. Treat listings outside those hubs as genuinely scarce rather than as the default.

They sponsor visas and green cards for eligible roles, which is worth knowing before you rule yourself out.

What the interview loop looks like

Anthropic itself confirms the mechanics: interviews run over Google Meet with timezone flexibility, technical rounds use live coding environments such as Colab and CodeSignal, and you may reference documentation while coding, though they advise being comfortable enough with syntax and standard libraries that looking things up does not consume your time. Non-technical interviews are conversational and focus on how you approach problems and why you want to be there.

Beyond that, the detail comes from candidate write-ups rather than from Anthropic, so treat it as reported rather than official: a recruiter screen, then a technical or take-home stage, then role-specific and values-based rounds, with the whole process commonly described as taking a few weeks. Several accounts describe a take-home for research roles built around an ambiguous problem, where the point is your reasoning rather than a polished result.

The most consistent claim across those accounts is that the values round is where candidates most often fail. Anthropic's stated values are helpfulness, honesty and harmlessness, with an emphasis on high-trust, low-ego communication and direct feedback. Being able to talk seriously about deploying capable systems responsibly, without either dismissing the risks or catastrophising, appears to matter more here than at a typical employer.

If it does not work out

Anthropic's policy is that you can reapply after twelve months, or sooner if something material about your situation changes. Given 267 roles opened in the last thirty days alone, the board you were rejected against is not the board you would be applying to.

The practical version

• Put your best self-directed work at the top of your resume, because they asked you to.
• If you are not a researcher, look at the 317 roles that are not research or engineering before assuming there is nothing for you.
• Have one project you can talk about in real depth, including what you got wrong.
• Be ready to discuss safety as a practical engineering constraint rather than a slogan.
• Assume San Francisco unless a listing says otherwise.

Quotations and policies above are from Anthropic's careers page. Interview-loop details not attributed to Anthropic come from published candidate accounts, including interviewing.io, and should be treated as indicative rather than official. Role counts are read from Anthropic's live job board and refresh daily.