1p3a Experience · May 2026

anthropic software engineer tech phone screen: task management oa

SWE Phone Screen newgrad
3 upvotes 3 replies

Interview Experience

题目是Task management, 第一,二问很基础,就不赘述了 第三问:可以给task设置一个ttl, task要在到这个ttl的时候,自动被删除 第四问:你需要保存用户的在某个时刻的task list, 然后可以返回该用户任何时刻的task list 时间很紧,疯狂码代码,跪求能进下一轮~~~~ 1, FYI, 一些个人的感觉,我感觉test case测试的不是很严谨,主要还是测了happy path. 所以你如果有一些小的bug, 可能不会被test case发现。 2, 自己准备的OA的感觉来看,想好数据结构的方式,比逻辑更重要。因为逻辑都没有特别难,但是如果你数据结构选的不好了,第一,你容易在第三四问发现需要重构代码,第二或者你的一些实现需要写更多的代码,容易出bug

Full Details

🔒

Unlock all Anthropic questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

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.