1p3a Experience · May 2026

anthropic software engineer onsite interview experience and tips

SWE Onsite newgrad
2 upvotes 30 replies

Interview Experience

内容其实没啥,标准流程电面coding Q1, HM chat (20 minutes, team match?) VO coding Q2, sys design Q1 然后是hiring manager, culture, technical deepdive 总体来说,coding就是要快,天下武功唯快不破,当然适当的显示你的能力,比如文件去重,md5和sha系列的hash有什么区别,应该用哪个之类的。 system design 我觉得简单了……我觉得我的系统没搞得特别好,但是面试官(我校友!)看起来挺满意,可能是有些地方我回答的比较好, 比如如何bring up GPU machines faster 之类的 那些软的面试反而是难的,因为没有标准答案。尽量表达出真实的自我吧,做过的事情你就自然的能讲好,没做过的编出来他们也不会信 猎头说feedback really positive,等过reference check和offer了 :)

Full Details

🔒

Unlock all Anthropic questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

Topics

System Design

About Anthropic Interview Reports

This question was reported by a candidate who interviewed at Anthropic. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Anthropic are the higher-signal extractions to take from this report.

For broader preparation context, the Anthropic interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Anthropic reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Anthropic Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Anthropic reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.