Anthropic live technical screen interview

Round 3 of 8 · 4 questions reported

See the whole loop
Length
55 min
Format
One engineer on video with screen share, usually in CodeSignal (Google Colab for research roles), Python by default; one practical problem that grows in parts
They grade
Working code, how you reason out loud, how you absorb new requirements
AI use
No AI; looking up documentation and searching the web is fine
Heads-up
Problems are practical components (for example stack traces, file deduplication, a concurrent crawler, a tokenizer), not puzzles. The base problem takes about a third of the hour; follow-ups on scale, IO versus CPU and parallelism fill the rest. The recruiter often describes the problem's theme in advance. Research roles choose from a menu instead (ML programming, coding and design, RL debugging, prompting in a notebook, or a take-home); some screens are an agent loop with tool use.

Questions Anthropic asks in this round 4

  • QKV attention programming with einsum fluencyML designA short programming screen around sequence models and scaled dot-product attention, plus quick ML knowledge questions. Reading equations and expressing the math with einsum-style…
    Last asked Feb 2026
  • Min stackCodingDesign a stack that supports push, pop, top and returning the current minimum element, each in constant time. Explain how the minimum stays correct after pops, how you handle…
    Last asked Feb 2026
  • IPv4 range iterator with reverse and CIDR supportCodingAn IPv4 address such as "172.16.4.9" is four octets, each 0 to 255. Taken together, the octets form one unsigned 32-bit number. Build iterators that walk IPv4 addresses lazily…
    Last asked Jan 2026
  • Design the front end of a desktop AI chat appSystem designDesign the client side of a desktop chat app for an AI assistant: the conversation list, the chat view and the model's replies as they stream in. This is a front-end system design…
    Possibly retired