PACE scores how you actually drive a coding agent, across four disciplines drawn from how the best operators work. Each guide below explains what the discipline means, what good looks like in practice, and includes a released sample question with the reasoning behind the answer.
Telling the agent what to build — and what done means
VCatching confident-but-wrong before it ships
CFeeding the window what it needs — and nothing that poisons it
LGetting more than one keyboard’s worth of work done
Read the discipline you are weakest in first — most people over-index on Direction and under-invest in Verification. Then sit the exam: 40 questions, 10 per discipline, drawn at random from a 420-question bank. Your certificate shows a per-discipline breakdown, so the guide doubles as your retake plan.
Sit the beta exam →