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, then route the low ones
Score each competency, then route the low onesBe honest: a 3 you can defend beats a hopeful 5
- Competency
- FinOps / COGS
- Your 1-5
- __
- If low, reopen
- FinOps for AI & COGS Attribution, then rebuild the s1 take-home
- Competency
- GPU / capacity
- Your 1-5
- __
- If low, reopen
- GPU Economics & Capacity Planning, then the s2 whiteboard rep
- Competency
- Systems literacy
- Your 1-5
- __
- If low, reopen
- GPU Economics & Capacity Planning, for inference serving, batching and routing
- Competency
- Program execution
- Your 1-5
- __
- If low, reopen
- Program Execution & Driving Without Authority, then the s3 drill
- Competency
- Values / why-Cursor
- Your 1-5
- __
- If low, reopen
- Behavioral, Values & Why Cursor, then the s4 drill
| Competency | Your 1-5 | If low, reopen |
|---|---|---|
| FinOps / COGS | __ | FinOps for AI & COGS Attribution, then rebuild the s1 take-home |
| GPU / capacity | __ | GPU Economics & Capacity Planning, then the s2 whiteboard rep |
| Systems literacy | __ | GPU Economics & Capacity Planning, for inference serving, batching and routing |
| Program execution | __ | Program Execution & Driving Without Authority, then the s3 drill |
| Values / why-Cursor | __ | Behavioral, Values & Why Cursor, then the s4 drill |
Score before you study. Your two lowest numbers set the week.
Confirm the story bank and the product usageTwo cheap checks people skip
Each hits a different value: ownership, truth-seeking, action bias, influence without authority, every-altitude.
Each leads with a number, such as % COGS cut, GPUs saved or a quarter protected, rather than "massive impact."
If two stories prove the same value, replace one. If a value has no story, build it.
Log real sessions before the loop if your usage is thin: tab, agent mode, a multi-file change.
Carry one specific observation about cost or latency you can name in the values round.
"I've used it twice" reads as thin; a concrete observation reads as genuine.