← Back to Directory

Anthropic interview notes, page 20 of 32

Mid-sized

Most of these Anthropic write-ups come from Software Engineers (277), then Machine Learning Engineers (31) and Product Managers (10). The most reported rounds are the technical phone screen (129), the system design round (86), the behavioral / leadership round (45) and the hiring manager screen (17).

319 interview notes · updated Sep 2026

Anthropic·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineer role at Anthropic, just one question about a favorite project. Not much to go on but here's what I remember.
  • Tell me about a project you've worked on that you're particularly proud of.

“Pretty standard opener but I fumbled it a bit.”

View Post

Anthropic·Software Engineer·Take-home Assignment

Jun 2026
Interviewed for a software engineer role at Anthropic. The second part of the process focused on optimizing an AI agent to reduce how many turns it takes to answer questions, which could pull in prompt engineering or other skills depending on how you approach it.
  • Given a working agent, how would you optimize it to answer questions in fewer conversational turns?

“This is the kind of problem that looks like a prompt engineering task on the surface but probably isn't just that.”

View Post

Anthropic·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Anthropic for a software engineer role, centered entirely on designing a prompt playground product from scratch. The scope was surprisingly broad, covering everything from streaming architecture to multi-tenancy and cost accounting. Left feeling like I undercooked the evaluation pipeline section.
  • Design a prompt playground web app where users can author prompts, run them against LLMs, compare outputs across models, save versioned templates, and run batch evaluations over small datasets.
  • How would you handle streaming LLM responses back to the browser with sub-second first-token latency?
  • How would you design the prompt template and versioning storage system, including support for named variables and team sharing?
  • Walk through how you'd build the batch evaluation pipeline that runs a saved prompt over a dataset and surfaces per-row outputs.
  • How would you implement cost and usage tracking per user and per team, including rate limiting?
  • How would you manage secrets and credentials for multiple LLM providers in a multi-tenant environment?
  • How would you cache identical prompt and parameter combinations to reduce redundant LLM calls?
  • What does graceful degradation look like when one of the LLM providers goes down?

“This is the core question and it ate the whole session.”

View Post

Anthropic·Product Manager·Hiring Manager Screen

Jun 2026
Interviewed for a PM role at Anthropic. Only one question to speak of, and it was pretty squarely about prompt engineering, which makes sense given what they build.
  • How do you approach prompt engineering?

“Tricky one to prep for because it sits between technical and product thinking.”

View Post

Anthropic·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Anthropic system design round with a twist: instead of building something from scratch, you get a finished design doc for an inference API and have to poke holes in it. Felt more like a code review than a design session, which threw me off a bit.
  • You are given a completed design document for an inference API. Identify the flaws, gaps, or risks in the design.

“Not what I prepared for.”

View Post

Anthropic·Software Engineer·Technical Phone Screen

Jun 2026
Got a coding question at Anthropic that's pretty much a classic file dedup problem. Nothing too exotic, but it requires you to think carefully about how you structure the grouping.
  • Given a list of directory path strings, where each string encodes a root directory and its files with their contents, find all groups of files that share identical content and return their full paths grouped together.

“The parsing part is what trips people up first.”

View Post

Anthropic·Software Engineer·Technical Phone Screen

Jun 2026
Anthropic software engineer screen with a ledger simulation problem. The kind of question that looks manageable until you realize the expiry-ordering constraint basically forces you toward a heap, and if you miss that, your solution falls apart on the efficiency requirement.
  • Design and implement a prepaid credit ledger that supports adding time-limited grants, spending credits (always consuming the soonest-to-expire credits first), and querying the current balance, where expired grants are dropped before any spend or balance check.

“My first instinct was a plain sorted list and I started coding that up before catching myself.”

View Post

Anthropic·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral loop at Anthropic for an ML Engineer role, heavy on leadership and culture fit. Four questions, all situational, no technical content at all which surprised me a bit.
  • Walk me through a time you had to quickly adapt to a company or team culture that was very different from what you were used to. What did you actually do, and did it work?
  • Tell me about a difficult leadership situation you faced, like unclear goals, a struggling team member, or conflict across teams. What happened and what did you do?
  • How do you make sure everyone feels included and heard when you're working across cultures or in a setting with multiple interviewers or stakeholders?
  • How do you handle giving and receiving tough feedback, and can you give an example of feedback you actually acted on, especially if it came at an unexpected point in a process?

“I went in with a story about joining a team that moved way faster than my previous org and how I shadowed people before pushing my own opinions.”

View Post

Anthropic·Software Engineer·Technical Phone Screen

Jun 2026
Two-problem coding interview for a software engineer role at Anthropic. First problem was a staircase printing exercise with a sneaky follow-up, second was a distributed systems design question that kept evolving. Left feeling like I did okay on the first and only halfway survived the second.
  • Write a function that prints a staircase of n rows, where row i contains i items separated by spaces, with no trailing space on any line. Then write test cases for it, including edge cases. Follow-up: modify it so the items are consecutive integers across the whole output.
  • You have 10 worker nodes, each holding a local partition of an integer dataset. Using only read_local (10 bytes/sec), send (1 byte/sec), and recv (1 byte/sec), design an approach to compute the global mode and/or global median. The interviewer will push you to improve on your initial solution in terms of communication volume and end-to-end time.

“The core staircase part was fine, took maybe five minutes.”

View Post

Anthropic·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineering role at Anthropic and got a system design question around task lifecycle management. Pretty focused, single-question format from what I can tell.
  • Design a task system that supports setting a TTL (time-to-live) on each task, where the task is automatically deleted or expired once the TTL elapses.

“First instinct was a simple cron job sweeping for expired tasks, which works but they pushed back pretty fast on scale.”

View Post