Here's something I've been wanting to write down for a while.

I run ML system design and behavioral rounds at one of the FAANG companies. Been doing it for about two years. Before that I was at another major tech firm. I'm not a recruiter, I'm an engineer who sits on hiring committees and conducts a lot of interviews. So this is one staff engineer's view, not my employer's official position, but I talk to enough peers at the other FAANG companies and AI labs to know my read isn't unusual.

Last month I rejected a candidate who solved every coding question cleanly. The medium in 8 minutes, the hard in 20. The kind of candidate who would've gotten an automatic hire rec in 2022. He didn't get the offer.

The round that sank him was system design. I gave him a problem that's now pretty standard in our loop: a recommender that started producing biased outputs overnight, hundreds of millions of users impacted, what do you do. He started drawing boxes. He talked about rebuilding the ranking pipeline. I asked him "what do you do first?" and he gave me more architecture. I asked again. More architecture. By the third time I was pretty sure I was writing a no-hire, and I did.

I don't think he was a bad engineer. I think he was prepping for a loop that doesn't exist anymore.

If you're a student or early-career engineer trying to break into FAANG ML, this is the part most prep guides aren't telling you yet.

What changed

By late 2024, GPT-class models could solve about 80% of LeetCode mediums on the first try. By mid-2025 every engineer I work with was using AI in their daily flow. The signal "writes correct fast code under pressure" stopped predicting anything useful about how someone performs on the job. So companies adapted. They started weighting the rounds where AI can't fake it for you. System design. Behavioral. The deep dive into your past work.

Nobody put out a press release. There's no official blog post saying "behavioral now matters 3x more than coding." But every interviewer doing this for two years has felt it. The debriefs sound different than 2023. The reasons we say no are different. The reasons we say strong-hire are different.

Coding round: still there, but not where you win

You still need to be solid. But it's now a "don't fail" round, not a "show off" round. After about 80 well-chosen LeetCode mediums you have very steep diminishing returns. The 200th problem gives you almost nothing the 80th didn't. If you're at problem 250 in grinding mode right now, you're optimizing the wrong thing.

I know that's hard to hear because LeetCode feels like the "real" prep. It's been the cultural center of FAANG prep for like a decade. But it's not where the loop is won now.

System design: where the loop is actually won

The question used to be "design a recommender system" with whiteboard freedom and a friendly interviewer who'd let you pick your favorite architecture. Now it's something like "your main feed ranking system is showing a 3% engagement drop in the last 24 hours, walk me through what you'd do, latency budget is 100ms, you can't change the ranking model this quarter." Real constraints. Real production decision. We're not testing whether you can recite a recsys architecture. We're testing whether you can hold the constraints of an actual system in your head while reasoning about a problem.

The thing that flips this round is reasoning out loud. And I don't mean narrating, like "first I'll do this, then I'll do that." I mean actual reasoning. Like "I think we should start by checking whether this is data quality, because the symptoms look like bias, but bias and feedback loops at this scale can look identical from the metrics alone, so the way I'd disambiguate is..." Visible thinking. You're telling me how your brain is working through the problem.

Every interviewer I work with grades for this and it's the single biggest thing that separates a hire from a no-hire. School trains you to give clean right answers. The interview rewards showing your work, especially when you don't have the right answer yet.

Behavioral: the most under-discussed change

Behavioral used to be a vibe check with a STAR-method shell. Now it's closer to "tell me about a decision you made that you later thought was wrong, and what you did about it." The questions probe judgment, not accomplishments. STAR recitations get spotted instantly and read as canned.

If you're a student you might think you don't have huge stories to tell. That's fine. We know your level. What we're looking for is whether you can talk honestly about your judgment and your mistakes. A student who tells a real specific story about a class project where they made a hard call and partly got it wrong is in way better shape than someone with a polished "I led the team to a 10% improvement" story. We see a lot of polished stories. They all blur together.

ML depth: about what you've built, not what you've read

Not textbook theory. Not "explain backprop." If you have one real ML project (even a strong internship, even a class project you took seriously) you should be able to talk about every decision: why that model, what you tried first, what surprised you, what you'd do differently.

If you don't have a project like that yet, this is the highest-leverage thing you can do. Forget the next 100 LeetCode problems. Build one ML system end-to-end (data pipeline, model, eval, deployment if you can) and write up what you learned. That's a better use of three months than any amount of grinding.

The new thing nobody's talking about: AI-collaboration literacy

This is new in the last 12 months. Interviewers, especially at the frontier AI labs and increasingly at the bigger tech companies, are watching whether you treat AI tools as a peer or as an oracle. Can you tell when a model's suggestion is plausible but wrong? Do you verify or trust? When you describe how you'd build something, are you describing how you'd build it with AI in the loop, or thinking like it's 2022?

This is becoming an explicit scoring dimension at the AI-first companies and it's going to keep mattering more. Practice using AI while reasoning out loud. Practice the moments where you catch the AI being wrong and say out loud how you caught it. It's a separable, learnable skill and most candidates aren't training it.

Time allocation if I were prepping right now:

• 30% system design (real-system reasoning under constraints, not whiteboarding)
• 25% behavioral (real story practice, not STAR memorization)
• 20% ML depth on systems you've actually built
• 15% coding (around 80 well-chosen mediums)
• 10% AI-collaboration practice

The biggest difference from standard internet advice is that 70% of your time should be on non-coding rounds. That feels wrong to most students. I get why. But it's where the loop is decided in 2026.

Bottom line

The interview isn't testing what you know. It's testing how you reason. LeetCode was pattern recognition. Modern ML loops aren't. They're about reasoning through new problems where the pattern doesn't exist. The candidates who get offers slow down when they don't know, ask clarifying questions, name assumptions, propose multiple approaches, pick one with explicit tradeoffs, and do all that out loud.

If you've been a strong student, you already have the reasoning ability the loop is testing. You just haven't practiced expressing it under pressure in a 45-minute window with someone watching. That's the actual skill. It's much shorter to learn than 500 LeetCode problems. Most candidates never practice it specifically.

Happy to answer questions in the comments.

If you want to dig deeper, I run gradientcast.com : deep, staff-level walkthroughs of every major ML system design pattern

Two years ago I helped a friend prep for a Meta ML engineer loop. We did 200 LeetCode problems together. He was sharp, fast, would solve mediums in under twelve minutes. He didn't get the offer.

When the recruiter walked him through the debrief, the feedback was strange. The coding round had been "fine". Not a red flag, not a strong signal. What sank him was the system design round. The interviewer had given him an ambiguous problem about a recommender producing biased outputs and asked what he'd do in the next thirty minutes. He defaulted to architecture. The interviewer kept pulling him back: "what would you do first?"

I've been on the other side of that table for the past two years, running ML system design and behavioral rounds at Meta. What happened to my friend is happening to a lot of strong engineers, and most of them don't know why. They're prepping for a loop that doesn't exist anymore.

What changed: the algo round isn't dead, but its weight in hire/no-hire collapsed. The reason isn't that algorithms stopped mattering — it's that AI got too good at them. By 2025 GPT-class models could solve ~80% of LeetCode mediums first try. The skill "produce a clean implementation of two-sum in 12 minutes" stopped predicting anything useful. So companies shifted weight to what AI can't fake yet — judgment, system reasoning, AI-collaboration literacy, communication.

This shift wasn't announced. But anyone on a hiring committee in the past 18 months can tell you it happened. The debriefs sound different. The candidates who get strong-hire recs look different from the ones who got them in 2023.

What's actually being tested in 2026:

1. Reasoning under uncertainty. Deliberately ambiguous problems with no clean answer. The interviewer watches how you decompose, prioritize, name tradeoffs. Pattern-matching to a template = filtered out. Slowing down, asking questions, reasoning out loud = offer.
2. System design at production scale. Not "design Twitter" — "design Twitter with a 100ms latency budget, a degrading existing model, a downstream team you can't change, and a vendor you can't swap." Real constraints, real production decisions.
3. AI-collaboration literacy. New in the last 12 months. Can you tell when a model's output is plausible-but-wrong? Do you verify or trust? Becoming an explicit scoring dimension at Anthropic, OpenAI, increasingly Google/Meta.
4. Communication / thinking out loud. The candidates who get strong-hire reports almost always reason out loud constantly. Not narrating — *reasoning*. Making assumptions visible. Flagging uncertainty.

What an E5 Meta ML loop looks like now vs 2022:

2022: two LeetCode rounds, one broad system design, one ML theory round, one behavioral.

2026: one shorter coding round (pseudocode often fine for harder parts), one heavily-constrained system design round, one ML deep-dive on a system you've actually built, one meaningfully harder behavioral.

If I were prepping for a FAANG ML loop today, time allocation:

- 30% system design (real-system reasoning, not whiteboarding)
- 25% behavioral (real story practice, not STAR memorization)
- 20% ML depth on systems you've actually shipped
- 15% coding (~60–80 well-chosen mediums is enough; diminishing returns past that)
- 10% AI-collaboration practice (new — practice reasoning out loud while using AI tools)

The mindset shift: the interview is no longer testing what you know. It's testing how you reason.

LeetCode was about pattern recognition. Modern ML loops aren't. They're about reasoning through novel problems where the pattern doesn't exist. The candidates who get offers slow down when they don't know, ask clarifying questions, name assumptions, propose multiple approaches, pick one with explicit tradeoffs — out loud.

If you've been shipping production ML systems, you already have the skills. You just need to practice expressing them out loud, under pressure, in 45 minutes.

Grind less. Reason more. Talk out loud.

---

Full version with the worked example (Meta E5 round breakdown phase-by-phase) at gradientcast.com/insights/why-faang-killed-the-algo-round

---