Fetch cohort stats for an assessment
null for cohortStats if no completed sessions exist for this assessment.
Percentile rankings for a specific candidate
Add?sessionId=xxx to compute percentile rankings for a specific candidate relative to the cohort:
percentiles object:
Percentile rankings require at least 2 completed sessions. With fewer than 2, the
percentiles field is omitted.Session-level cohort stats
You can also fetch cohort stats from a session’s perspective, without needing to know the assessment ID:Understanding the metrics
What higher percentiles mean
Percentile values range from 0.0 to 1.0. Higher is better for all metrics:What metrics matter most
The metrics that matter depend on the role and task, but these tend to be the strongest signals:Test pass rate
Test pass rate
The most objective metric. For assessments using the OSS issue library with verified test suites, this directly measures whether the candidate fixed the bug. A
testPassRate of 100 means all tests pass.Command fail rate
Command fail rate
A low
commandFailRate indicates the candidate writes commands carefully and catches errors. A very high rate may indicate trial-and-error debugging without understanding.Verify intensity
Verify intensity
Candidates who run tests and check their work frequently tend to produce higher-quality solutions. Low
verifyIntensity can indicate over-reliance on AI without validation.First change latency
First change latency
How long the candidate spends understanding the problem before making changes. Too fast can indicate rushing; too slow can indicate difficulty. Compare against the cohort average for context.
