CrackingWalnuts
Checked 3 August 2026. Anthropic describes the tools used and the interview style but publishes no round count, duration or timeline. Everything structural here is commonly reported by candidates. Source: anthropic.com/careers.
| Round | Duration | What it tests |
|---|---|---|
| Phone Screen | 60 min | Practical coding plus background. |
| Take-Home Exercise | 4 to 6 hours | Build a small project they read carefully. |
| Take-Home Discussion | 60 min | Walk through your take-home decisions. |
| Practical Coding | 60 to 90 min | Live coding with API integration. |
| System Design (Light) | 60 min | Claude integration or eval system design. |
| Behavioral / Values | 45 min | How you think, how you slow down. |
IC3 is the mid level. The bar is "writes careful code with tests, thinks before acting, communicates clearly in writing". You are expected to own small projects and make sound local decisions, not to drive cross-team strategy.
The Anthropic loop is slower and more thoughtful than other AI labs. The take-home sits at the center of the loop, and a real person reads your code line by line.
Writing matters as much as code here, because the company runs on docs and design memos, not hallway conversations. Even at the mid level, safety-mindedness is a real signal.
Targeted guidance per round in this loop. Each section links to the matching track on the site. There is no shortcut list, the bar moves loop to loop, so build the pattern recognition and the stories from real practice.
Work the pattern templates until the recognition is instant. Trace one mock problem per pattern. Practice stating time and space complexity out loud before you write code.
Anthropic IC3 (Software Engineer, Mid) has one design round: System Design (Light) (60 min): Claude integration or eval system design.. Bar is a clean end-to-end design at modest scale, with a sensible API and one trade-off discussion. Pick problems from the track at the scale this loop tests and rehearse the structure: requirements, numbers, high-level design, data model, API, deep dive on one part, trade-offs.
Junior bar. You now have real production work. Stories should center on features you owned, bugs you debugged, and how you collaborated with senior engineers. Skip multi-team and multi-quarter scope; that comes at Senior. Frame stories around safety-mindedness, mission alignment, and judgment under uncertainty about capabilities.