Debugging and testing code you didn't write
The AI rounds put you in someone else's repo far more often than classic rounds did — a bug-fix phase, a repo of failing tests in an online assessment, a pull request to review, a module to explain. This lesson gives you a five-minute orientation, a triage method for failing tests, and a way to review AI-written code without trusting the AI's summary of it.
What you'll be able to do
- Orient yourself in an unfamiliar repo in five minutes, in a fixed order
- Triage a set of failing tests by cause before changing any code
- Use the assistant to locate code, then confirm every claim by reading or running it
- Review an AI-written pull request and deliver a severity-ranked verdict
Before this: working-with-the-ai
Log in to read the rest of this lesson
The AI rounds put you in someone else's repo far more often than classic rounds did — a bug-fix phase, a repo of failing tests in an online assessment, a pull request to review, a module to explain. This lesson gives you a five-minute orientation, a triage method for failing tests, and a way to review AI-written code without trusting the AI's summary of it. This walkthrough runs about 16 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.
Log in to continueThe first module of every track is free to read on the web: see what's open in AI interviews.