Some loops now let you use an AI assistant in a round, and some ask to see how you did. That changes what a senior engineer has to show. Writing code fast matters less. Planning, directing the tool, checking what comes back, and saying why you trust it matters more. This chapter explains the formats, with a dated fact for the one that is documented well, and shows a worked session. Treat every format fact as a snapshot: these rounds change often, and the only reliable source for your own round is the recruiter.
What the formats look like
One format has public detail. Hello Interview's write-up of Meta's AI-enabled coding interview (read 2026-10-16; the page shows no publication date, and says Meta began rolling the round out in October 2025) describes the following.
- A 60-minute round, with about 5 to 6 minutes of orientation and roughly 30 to 40 minutes for the main work.
- One multi-file problem in three phases: fix a bug, implement a core feature, then optimise.
- A chat assistant, with a choice of models, in a three-panel layout. The page says the assistant can see project files but replies only in chat, so you write or paste any code yourself.
- Graded on problem solving, code quality, verification and communication. The page says you are allowed to use AI, but you must show you understand the code you use. It also says finishing every phase is not required.
That is a description by a third party, not Meta's own policy. Other companies run their own versions, some in design rounds, some as take-homes, and some ask for the assistant's chat log. The author has not verified any of those, so treat them as possibilities to ask about.
Whatever the format, the same four things are likely being watched: how you break the problem down, how precisely you direct the tool, how you check its output, and how clearly you explain your choices. That is the author's reading of the Meta description above, and a sensible default for any AI-allowed round.
What to ask the recruiter
You cannot prepare well without knowing the rules. Ask these in writing, in your first call or the email after it.
- Is an AI assistant allowed in this round? Which tools or models?
- Is it used in coding only, or also in design discussions?
- Do I bring my own setup, or use theirs?
- Will my prompts or chat history be recorded or reviewed?
- Can I use my own editor and shortcuts?
- How is the round scored, in general terms, and what does a strong result look like?
Recruiters often have only a one-page brief. If they cannot answer, ask them to find out, and say you will prepare for both the allowed and not-allowed cases.