60 min · multi-file project · reported at Meta
AI-enabled coding round
A small codebase, an AI chat that can read the files but not change them, and three phases checked by tests you can't see.
More interview loops now hand you a working repo, an AI assistant and one hour. Find the bug, build the feature, make it fast. Rehearse that round on original codebases with hidden tests, before it counts.
Rounds like this have been reported at Meta, Google (pilot) and Canva.
Solved. Phases 2 and 3, building the feature and making it fast, come with the full sessions.
Join the waitlistsrc/inventory.py
pytest
Assistant reads your files · can't edit them
I can see every file in this project. Ask about the code, but you write it. (This demo answers one question.)
You open a project you've never seen. Tests point at a failure. You find the cause, explain it and fix it, with or without the AI.
Extend the existing code to meet a new requirement. The AI can draft and explain. You decide what goes in and you type it.
Bigger hidden inputs arrive. Your phase 2 solution times out, so you rethink the approach while the clock runs.
LeetCode trains you to write an algorithm from a blank file. These rounds test something else: reading code you didn't write, finding what's wrong, and checking what the AI hands you before you trust it.
60 min · multi-file project · reported at Meta
A small codebase, an AI chat that can read the files but not change them, and three phases checked by tests you can't see.
60 min · a few hundred lines · Google pilot
Unfamiliar code you have to read, explain, debug and speed up, with an assistant beside you. Candidates report it focuses on how well you check its answers.
A chatbot can ask you questions. The round gives you a working multi-file project, tests you can't see, a clock, and an assistant that answers but won't write the code. The practice sessions are built to recreate that setup, not just the questions.
Not exactly, and nobody outside these companies can promise that. Sessions are modelled on public reports and on how candidates describe the round. We never use real interview questions.
An independent software engineer, not a company or a prep-course business. The name stays off the page for now. Questions or feedback: [email protected].
No. This is an independent practice tool. The companies are named only because their interview changes have been publicly reported.
Join with your email. After that, a few optional questions help us build the round you're facing first.
We store your email, your country (from your connection) and any answers you choose to give, only to email you about launch. Visits are counted with Cloudflare Web Analytics, which uses no cookies. To be removed, email [email protected].
You're on the waitlist.
Optional: a few answers help us build the round you're facing first. Skip anything.