Log in←Next →
Field reading12 min

Preparing with Claude the Right Way

By the end of this lesson you'll be able to say exactly where AI help is allowed in a frontier-lab hiring process and where it isn't, and you'll have five concrete ways to use Claude for preparation that stay well inside the rules.

Try itThe loop, stage by stageAnthropic · Application
What happensReportedA written answer to a question like "Why Anthropic?". Treat it as your first interview.
AI help at this stageOfficialWrite the first draft yourself; Claude may then help you refine it.
  • Practical coding
  • LLM system design
  • Project deep dive
  • Motivation and values ✓
2 / 7
Every stage carries a confidence label: Official (the company says it), Reported (several independent candidate accounts) or Anecdotal (one or two). The four chips are the rounds every loop keeps coming back to; the dark ones are tested at this stage. Snapshot checked 2026-10-08 to 2026-10-10; your recruiter overrides all of it.

Why this matters more than you think

You're preparing for jobs where AI is the product, so it's tempting to assume the interviews are relaxed about AI. At Anthropic the opposite is true for most of the process, and the rules are written down. Getting them wrong doesn't make you look modern. It makes you look like someone who didn't read the instructions, in a job that is mostly reading instructions carefully. The good news: the rules are short, and they leave a lot of room to prepare well. Step through the stages above and read the "AI help" card for each.

Anthropic's official guidance

Anthropic publishes guidance for candidates on using AI (last updated July 2025 when this lesson was checked on 2026-10-08). Everything in this section is Official, summarised in our own words; read the page itself before you apply, because it may change.

  • Application: write the first draft yourself; then Claude can help you refine it.
  • Take-homes: without Claude, unless Anthropic tells you AI is allowed for that assessment.
  • Interview preparation: encouraged.
  • Live interviews: "This is all you–no AI assistance unless we indicate otherwise."
  • Accommodations: tell your recruiter early.

The guidance draws the line with examples. Using Claude to put real experience into better words is fine, such as working out how to quantify the impact of a project you led. Using Claude to invent experience is not, and neither is using it during an assessment that hasn't allowed it.

The guidance stage by stage, and what it says about Anthropic's own use
Stage What the guidance says Label
Application (resume, written answers) Write the first draft yourself. Then Claude can help you refine it, for example by comparing your resume against the job description to find what to highlight. Official
Take-home assessments Do them without Claude, unless Anthropic tells you AI is allowed for that specific assessment. Official
Interview preparation Encouraged. Use Claude to research the company, practise your answers and prepare questions to ask. Official
Live interviews No AI assistance unless Anthropic says otherwise. In the page's own words: "This is all you–no AI assistance unless we indicate otherwise." Official
Accommodations If you need one, tell your recruiter early. Official

Three expectations sit on top of the rules: use Claude as a collaborator, thoughtfully, to strengthen your application and preparation; be yourself (AI should refine your ideas, not replace them); and be transparent, to the same standard Anthropic says it applies to its own use of Claude.

The page also says how Anthropic uses Claude on its side of hiring (for things like drafting job descriptions and transcribing interviews), that it doesn't train Claude on candidate data, and that Claude doesn't make hiring decisions. That's Official too.

The rule in one line: before the assessment and around your own words, Claude is welcome. Inside an assessment or interview, assume no AI unless told otherwise in writing. If you're unsure about a round, ask your recruiter: "Is any AI tool allowed in the take-home?" is a normal question and costs you nothing.

What "first draft yourself" actually means

This is the rule people bend without noticing. All of these break it:

  • Asking Claude for "a strong 'Why Anthropic?' answer" and then editing it into your voice.
  • Pasting your resume and asking Claude to "write my application answers".
  • Asking Claude for an outline and then filling it in.

The draft is the thinking. If Claude chose the structure and the points, the thinking isn't yours, however much you edit afterwards. A rough, short, slightly awkward draft that you wrote is the correct starting point. Then Claude can help.

You write a rough 150-word "Why Anthropic?" draft, then ask Claude: "Rewrite this to sound more impressive." Inside the rules?

Technically inside, but the wrong request. Refining your own first draft is allowed. But a full rewrite hands the voice and often the points to Claude, which is what "be yourself" warns against. Ask for critique, not a rewrite: "What's vague? Which sentence would work for any company? Where do I claim something without evidence?" Then make the changes yourself.

Five legitimate ways to prepare with Claude

  1. Mock questions you didn't write. Ask Claude to play an interviewer for one round type and ask original questions, one at a time, with follow-ups. Don't ask for "the real questions Anthropic asks": it doesn't have them, and anything it produces is a guess presented as fact.
  2. Critique of your own first draft. Paste your answer and ask what's vague, generic or unsupported. Make the edits yourself.
  3. Researching the lab. Build a study guide of essays, policies, products and engineering posts, then read the originals (Module C4). Check every specific fact against the source; models can be out of date.
  4. Practising explanations out loud. Explain a project and ask Claude to play a sceptical senior engineer who pushes on your weakest decision, or a non-technical listener who says where they got lost.
  5. Quantifying what you really did. The guidance names this one as encouraged. Ask which evidence would make the impact clearer and which numbers you should look up. Then look them up. Never let Claude fill in a number you don't know.
PROMPT TEMPLATES (paste after writing your own words first)

Mock round:   "Act as an interviewer for a <round type> round. Ask me one original
               question in the style of applied-AI interviews, wait for my answer,
               then follow up on my weakest point."
Critique:     "Here is my own first draft. Don't rewrite it. List what's vague, which
               sentence would work for any company, and where I claim something
               without evidence."
Quantify:     "Here's a project I led and the numbers I have. What evidence would make
               the impact clearer, and which numbers should I go and look up?"

What the other labs say

The picture outside Anthropic is much thinner. For OpenAI, no official public candidate AI policy was found when this lesson was checked; one candidate account of the forward deployed engineering loop describes an AI-enabled coding screen, and third-party guides say the policy varies by team and round. That's Anecdotal: one account, and guides are not candidate reports. For Perplexity, no public policy was found (Unknown). If you're interviewing at OpenAI, the only reliable answer is the one your recruiter gives you for each round, so practise both ways: unaided and with an assistant.

A simple test before every use

BEFORE I OPEN CLAUDE IN AN APPLICATION OR INTERVIEW PROCESS
[ ] Is this an assessment or a live interview?    -> If yes and nobody said AI is allowed: close it.
[ ] Am I starting from my own words?               -> If not, write them first.
[ ] Would I tell the interviewer exactly how I used it? -> If not, don't do it.

If all three answers are good, use Claude as much as you like. It's one of the best practice partners you'll have.

Cheat card

  1. Anthropic (Official): own first drafts, then Claude may refine; no AI in take-homes or live interviews unless told otherwise; AI-assisted preparation is encouraged.
  2. Refine real experience, never invent it. "Draft it for me", "outline it for me" and "rewrite it" all move the thinking to Claude; ask for critique instead.
  3. Other labs: no official OpenAI policy found (the AI-enabled screen is one account); none found for Perplexity. Ask the recruiter, per round.
Assessment or live? -> no AI unless told.  My words first?  Would I disclose exactly how?

Interview line "I wrote my answers myself and used Claude to critique them and to run mock rounds, and I asked my recruiter before each stage whether any AI tool was allowed."