/Interview

AI interview rounds · Lesson 1 of 8 · 10 min

The new interview map

Study with AI

Part 1Basics

Until recently, a software interview meant algorithms, system design and behavioural questions, with AI strictly banned. Now two things have changed.

First, some companies put AI in the room and score how you use it. Second, teams building AI products added rounds of their own: retrieval, agents, evals, and sometimes a role-play with a customer.

Details change quickly and many companies don't publish them, so this page labels who said what. A company's own post is strong evidence. A prep vendor's guide based on candidate reports is useful, but it could be out of date. Your recruiter's answer beats all of them.

Words you need

AI-enabled round
A live coding round where an assistant is provided or allowed. You're scored on your judgment in using it.
Code comprehension round
You work on code you've never seen: reading, debugging, improving.
Applied AI engineer
An engineer who builds products on top of models, rather than training them.
Loop
The full set of interviews for one job.

A worked example

Meera emails her recruiter and learns the loop: an LLM screen, an AI-allowed coding round, a RAG design round and an evals round. Knowing the list reshapes the next 21 days, and she drops the graph problems she'd been grinding.

Part 2The question

What rounds will you actually face now, and who says so?

By the end of this lesson, you should be able to:

  • Name the rounds you might face
  • Weigh a claim by its source
  • Ask your recruiter the right questions

Part 3In detail

Step by step

  1. Find your loop. Ask the recruiter for each round's name, length and tools.
  2. Match each round to a lesson. The next seven lessons cover one round each.
  3. Score yourself on each. This feeds the study plan in the next path.
  4. Check for updates. Formats change. Re-check what you read here against what you're told.

What's been reported

Checked in November 2026. Only Canva's row comes from the company itself. Treat the rest as reports, and confirm them with your recruiter.

WhoRoundWhat's reportedSource
CanvaAI-assisted codingCandidates are expected to use tools such as Copilot, Cursor or Claude. It uses realistic, ambiguous problems. Scored on using AI well, breaking down requirements, technical decisions, fixing AI code, and production standards.The company, June 2025
MetaAI-enabled coding60 minutes in CoderPad with an AI chat, replacing one coding round. Described as stages: fix a bug, build a feature, then optimise. Reported to be scored on problem solving, code quality, verification and communication.Prep vendors. Not confirmed by Meta.
GoogleCode comprehensionA pilot using Gemini for select US teams hiring early and mid-career engineers, planned for the second half of 2026. Scored on AI fluency, including prompting, validating output and debugging.Press, citing an internal document. Sources disagree on the start date.
Shopify, RipplingLive codingCandidates may bring their own AI copilots.One press mention, no detail.
Applied AI rolesMixedOften 4 or 5 rounds: screen, LLM phone screen, take-home or live coding, system design, sometimes a customer conversation.Prep blogs. Varies widely.
Eval-focused rolesEvalsA 2 to 4 hour take-home to build a small harness, plus eval system design and eval data rounds.One blog, no sources given.

Prompts to copy

Ask your recruiter about the rounds

This is the best source you'll get.

Could you share the rounds in my loop, with each one's length and format? For any coding rounds: what tools are allowed, which languages, and will I work in an existing codebase or start from scratch? For any design rounds: is there a particular product area I should expect?

What can go wrong

Trusting a prep site's rubric as official
Vendors report what candidates told them. It's often right, but it isn't a promise.
Preparing for yesterday's loop
A guide from a year ago may describe a round that's changed. Ask.

Part 4Questions and answers

Answer out loud first, then open each one.

Why might a Meta guide be wrong even when it's written carefully?
Meta hasn't published the details, so guides rest on candidate reports and can be out of date or differ by team.
What's the most reliable source on your own loop?
Your recruiter. Ask for each round's format and what tools are allowed.

Part 5Going further

Drill: Write your own loop (10 min)

  1. List the rounds you know about.
  2. Mark each with the source of what you know.
  3. Score yourself from 1 to 5 on each.
  4. Send the recruiter any open questions.

Keep the fundamentals fresh with the critical basics.

Who says so

Checked in November 2026. Vendors and individuals often report what candidates told them, so treat their details as reports.

Next: the round that's changed the most. Coding with an AI assistant beside you.

Next: AI-enabled coding →
AI Engineer · AI interview rounds