Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

37 stories

Likes earn the author +10 XP for the first 3 likes each day

AnthropicSoftware Engineer
Apr 2026

Full Onsite Loop, Rejected at the HM Round

It's a bit of a shame — I ended up getting rejected at the HM round. I think I went through a relatively new process: complete the full interview loop first, then do team match afterward. Phone Screen The question was File Deduplication. The whole conversation went smoothly and I didn't feel like there were any obvious issues. About an hour after the interview ended, I got notified that a Virtual…

RejectedOnsite0
AnthropicSoftware EngineerSenior+
Apr 2026

Two-Day Onsite, Likely Failed on System Design

A premium story — unlock it to read the full loop.

RejectedOnsitePremium0
AnthropicSoftware Engineer
Mar 2026

OA, a Python LRU Cache Phone Screen, and Rejection After a Full Onsite

Posting my Anthropic interview from a while back. I felt like I nailed everything. The culture round and the hiring manager round also went okay. In the end I still didn't pass. It feels way too arbitrary. (Maybe my background just wasn't a great match — I was interviewing for a billing platform team, but I've never worked on payments.) OA - recipe manager Phone screen - coding Q2 - LRU cache, th…

RejectedOnsite0
AnthropicSoftware Engineer
Mar 2026

Onsite Loop with a 1-on-1 Chat System Design, File Dedup Coding, and a Culture Round I Couldn't Read

The phone screen was Q1 image processing — using PIL to do grayscale, scale, and resize. The first step handled small images, the second step handled large images, and improving performance meant using ProcessPoolExecutor. The recruiter had mentioned beforehand that I should be comfortable with parallelism/concurrency, which was basically a hint. Time was a bit tight and the interviewer had to nu…

In progressOnsite0
AnthropicSoftware Engineer
Feb 2026

Five Onsite Rounds, Including a Prompt-Playground System Design

Locked — open it to unlock the full story with XP.

OnsiteXP0
AnthropicEngineering Manager
Feb 2026

Five Rounds and a Suspiciously Familiar Design Review

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
Anthropic
Jan 2026

Forced Into Single-Threaded Code, Then Rejected

I recently did a phone screen with Anthropic. I actually had a lot of goodwill toward this company going in, but the interview experience was extremely bad — I felt like the interviewer led me straight into a trap. Writing this to recap what happened, and also to ask everyone here for advice: when you run into an unprofessional interviewer during an interview, how do you save yourself? And is the…

RejectedTechnical Screen0
AnthropicSoftware Engineer
Jan 2026

Failed a One-Round Java Coding Screen

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0
AnthropicPerformance Engineer
Nov 2025

Five Onsite Rounds After a GPU-Kernel Take-Home

Locked — open it to unlock the full story with XP.

In progressOnsiteXP0
AnthropicSoftware Engineer
Oct 2025

A Web Crawler Question Derailed by a Concurrency Stumble

Classic interview question: web crawler. You can also find this one on the usual practice-problem site. First single-threaded, then the follow-up was multi-threaded. Only need to consider pages under a single hostname. The extra piece compared to the practice-site version is that you need to handle the fragment — the #... part of the URL needs to be stripped. No need to worry about URL normalizat…

RejectedTechnical Screen0
AnthropicSoftware Engineer
Oct 2025

A Full Onsite Loop That Ended in Rejection

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
AnthropicSoftware EngineerSenior+
Sep 2025

A Surprise Extra Round, Then a Downlevel to Senior

Overall the problems weren't hard, but there was a lot of code to write. The phone screen was one round of coding — they asked the file deduplication problem (Q2), done on Replit. The onsite (VO) had 5 rounds total — it was originally supposed to be 4, but they added one more afterward: Round 1, Coding: asked the web crawler question (Q1). The interviewer asked if I'd seen a similar problem befor…

OfferOnsite0
AnthropicSoftware Engineer
Sep 2025

A Web Crawler Question That Turned Into a Late Multithreading Push

Phone screen, and there's a problem on LeetCode that's almost identical to what they asked. Write a web crawler that only scrapes pages under the same hostname. The URL they gave me was for a real website (I think it might have been their CEO's blog?). The interview format was a bit different though — he didn't have me jump straight to writing multi-threaded code. You do it single-threaded first,…

RejectedTechnical Screen0
AnthropicEngineering ManagerSenior+
Sep 2025

Cut in the Management Style Round

I interviewed for an L6-7 EM role, in the pretrain org. The technical rounds were: project retrospective system design There were 3 non-technical rounds: management style strategy and execution culture The project retro was the only round with an actual engineering leader from the relevant area sitting in, and I felt like that one went pretty positively — they asked some pretty sharp questions. T…

RejectedOnsite0
AnthropicSoftware Engineer
Sep 2025

In-Memory Banking OA, Then a Surprise LLM Classifier Screen

After mass-applying online, HR reached out really fast — they basically sent the OA in the second week. The OA was pretty simple: design an in-memory banking system, four levels total. There's discussion of this question all over the forum. The first level was designing three functions: add account, pay, and deposit. The logic was simple — just define a dict to track accounts and balances. The se…

Technical Screen0
AnthropicSoftware Engineer
Sep 2025

A Two-Part Phone Screen and a DIY Attention Algorithm on the Virtual Onsite

A premium story — unlock it to read the full loop.

RejectedOnsitePremium0
AnthropicSoftware EngineerSenior+
Aug 2025

An Extra LRU Cache Round After Admitting I'd Seen the First One Before

Overall the questions weren't hard, but there was a lot of code to write. The phone screen was one coding round — they asked the file deduplication problem (Q2), done in Replit. The onsite ended up being 5 rounds total; it was originally supposed to be 4, and they added one more later: Round 1 (Coding): asked about the web crawler problem (Q1). The interviewer asked if I'd seen a similar question…

OfferOnsite0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP