Rubric and a mock interview plan

Self-review rubric

Score each from 1 (needs work) to 4 (strong) after a practice session.

Signal	Strong looks like
Understanding	Read the code and ran the tests before generating; asked clarifying questions
Decomposition	Small steps, each verified before the next
Prompting	Specific prompts with location, behavior, constraints and tests
Verification	Reviewed every diff, wrote or read tests that would fail if the feature broke
Ownership	Could explain every line kept; rewrote parts the assistant got wrong
Communication	Narrated decisions and trade-offs; summarized the change at the end

Practice plan

1. Pick a small open-source project in a language you know, or one of your own.
2. Write a feature request and a bug report for it, or reuse the two exercises in this guide.
3. Run a 60-minute session with a timer and screen recording, using the assistant your target company provides if you know it.
4. Watch the recording and score yourself with the rubric. Note every point where you accepted code you had not read.
5. Repeat with a different codebase; the reading skill improves fastest with variety.

Keep practicing classic problems in the workspace as well. They remain part of most loops, and they train the judgement you use to review generated code.