2 min lesson
Readiness scorecard and final plan
Use "Readiness scorecard and final plan" to tell the cases apart, then choose a response for each one.
Step 1 of 2
You've run the whole loop on yourself. Now grade it honestly and turn every weak area into a dated task, because a score with no remediation is just anxiety with a number on it.
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.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Your 1-5 score tells you where you stand; this tells you where a gap costs most.
Learn more
Advanced table
Score each area 1-5
Score each area 1-5Be your own interviewer
- Area
- Coding / AI-authenticity
- What a 5 looks like
- Clean AI-assisted solve, every line defensible, idempotency reasoned
- Your score
- __ / 5
- Area
- Inference fundamentals
- What a 5 looks like
- Prefill/decode, KV/prefix cache, batching, TTFT/ITL answered cold
- Your score
- __ / 5
- Area
- Routing / failover / backpressure design
- What a 5 looks like
- Full path with numbers, failover ladder, blast-radius thinking
- Your score
- __ / 5
- Area
- Cost / latency reasoning
- What a 5 looks like
- Every lever names its latency or quality cost and how to measure it
- Your score
- __ / 5
- Area
- Behavioral / authentic usage
- What a 5 looks like
- Five quantified STAR stories, real critique, tight why-Cursor
- Your score
- __ / 5
| Area | What a 5 looks like | Your score |
|---|---|---|
| Coding / AI-authenticity | Clean AI-assisted solve, every line defensible, idempotency reasoned | __ / 5 |
| Inference fundamentals | Prefill/decode, KV/prefix cache, batching, TTFT/ITL answered cold | __ / 5 |
| Routing / failover / backpressure design | Full path with numbers, failover ladder, blast-radius thinking | __ / 5 |
| Cost / latency reasoning | Every lever names its latency or quality cost and how to measure it | __ / 5 |
| Behavioral / authentic usage | Five quantified STAR stories, real critique, tight why-Cursor | __ / 5 |
Score from your own recordings, not from how it felt.
Any area under 4 gets one concrete remediation task and a date before your loop. Not "study more" - a specific action: "re-solve the streaming-consumer problem from scratch Tuesday" or "rebuild the gateway take-home and inject a 503 mid-stream this weekend."