1 min lesson
Readiness scorecard & gaps
Put this idea into your own words: "Prep drifts toward what's comfortable unless a scorecard points it somewhere else."
Step 1 of 3
Prep drifts toward what's comfortable unless a scorecard points it somewhere else. Score each competency the loop tests, route every weak score to the module that fixes it, confirm your story bank is deep enough and build a one-week plan weighted to your lowest two scores.
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.
Learn more
Full explanation
What the Loop Weighs Hardest
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
The five competencies, ranked by how decisive they are across this loop. Your two lowest self-scores against the heaviest bars set the week.
Learn more
Advanced table
Score each competency against what the loop tests
Score each competency against what the loop testsBe honest - a 3 you can defend beats a hopeful 5
- Competency
- FinOps / COGS attribution
- Your 1-5
- __
- Competency
- GPU / capacity planning
- Your 1-5
- __
- Competency
- Program execution
- Your 1-5
- __
- Competency
- Systems literacy
- Your 1-5
- __
- Competency
- Values / why-Cursor
- Your 1-5
- __
| Competency | Your 1-5 |
|---|---|
| FinOps / COGS attribution | __ |
| GPU / capacity planning | __ |
| Program execution | __ |
| Systems literacy | __ |
| Values / why-Cursor | __ |
Score before you study - your two lowest numbers set the week.
Map each weak score back to its fixEvery gap has a home in the track
- FinOps / COGS
- Re-drill cost attribution, showback vs. chargeback and why traditional cloud FinOps breaks on dynamic AI workloads; rebuild the take-home cost model
- GPU / capacity
- Re-drill reserved-vs-burst, the 60–80% sustained-use breakeven, utilization targets and tying GPU demand to DAU growth
- Program execution
- Re-drill scoping, critical pathThe longest end-to-end chain of dependent work in a plan; it sets the realistic timeline no matter how parallel everything else looks. A slip on the critical path moves the date; a slip on a task with slack does not. Press Enter for the full definition., RAIDRisks, Assumptions, Issues, Dependencies. A living program-tracking log: Risks (might go wrong), Assumptions (treated as true but unverified), Issues (a risk that already materialized), Dependencies (work blocked on someone else) — each with a single named owner. Press Enter for the full definition./risk registers, operating cadence and the influence-without-authority moves
- Systems literacy
- Re-drill inference-serving fundamentals - latency distributions, batching/throughput, model routing, what drives $/request
- Values / why-Cursor
- Rehearse the three debate prompts, the update-vs-hold drill and the 90-second why-Cursor with a peer poking holes