1 min lesson
Self-scorecard & gap plan
Put this idea into your own words: "Treat the rubric as a gap finder, not a score to admire."
Step 1 of 3
You've now run every stage against yourself. The last move is to turn that into an honest number and a plan that fixes your two weakest stages, not the ones you already enjoy practicing.
Treat the rubric as a gap finder, not a score to admire. Mark the weakest proof, turn it into one practice rep and keep the artifact you would show an interviewer.
Score each loop stage 1–5 against the rubrics from modules 2 through 6. Be the harsh grader - the loop is reputationally tough and a generous self-score is the most expensive mistake you can make this week.
Learn more
Full explanation
Full explanation
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Weight your prep here - these are the signals Anysphere is actually grading.
Learn more
Advanced table
Score the loop
Score the loop1 = shaky, 5 = ready
- Loop stage
- Recruiter / HM screen
- What a 5 looks like
- Crisp why-Cursor, why-support, logistics handled, no rambling
- Your score (1–5)
- __
- Loop stage
- Technical screen (live debug)
- What a 5 looks like
- Environment first, method in order, symptom vs cause named
- Your score (1–5)
- __
- Loop stage
- Written / async exercise
- What a 5 looks like
- Reply and report both pass their self-checks, done fast
- Your score (1–5)
- __
- Loop stage
- Automation / tooling round
- What a 5 looks like
- Four-beat pitch, named trade-offs, tied to scaling support
- Your score (1–5)
- __
- Loop stage
- Cross-functional / product
- What a 5 looks like
- Escalation path clear, customer-voice framing, authentic usage
- Your score (1–5)
- __
- Loop stage
- Values / behavioral
- What a 5 looks like
- Two cold STAR stories, truth-seeking under push-back
- Your score (1–5)
- __
| Loop stage | What a 5 looks like | Your score (1–5) |
|---|---|---|
| Recruiter / HM screen | Crisp why-Cursor, why-support, logistics handled, no rambling | __ |
| Technical screen (live debug) | Environment first, method in order, symptom vs cause named | __ |
| Written / async exercise | Reply and report both pass their self-checks, done fast | __ |
| Automation / tooling round | Four-beat pitch, named trade-offs, tied to scaling support | __ |
| Cross-functional / product | Escalation path clear, customer-voice framing, authentic usage | __ |
| Values / behavioral | Two cold STAR stories, truth-seeking under push-back | __ |
Anything below a 4 is a target. Two-plus below 4 means you're not done.
Target your two weakest stagesSpecific drills, not vibes
- Live debug is weak
- Run two more recorded 20-min scenarios; force environment-first and out-loud root-cause every time.
- Written round is weak
- Do three messy-ticket drills at 15 min each; check both artifacts against the module 5 rubric.
- Automation pitch is weak
- Rehearse one pitch to three minutes flat, then have someone push on the failure modes.
- Product takes are weak
- Do a real side-by-side with one competitor on one task this week; write the verdict in two sentences.
- Behavioral is weak
- Write and time two STAR stories; deliver them cold to a friend who'll interrupt.