How scoring works

• Quizzes: the share of questions you got right. A question left blank counts as wrong.
• Code reviews: how many of the real problems you found, minus the share of the fine items you flagged. Ticking every box scores zero.
• Bug fixes and features: the share of tests that pass, counting both the tests you can run and hidden ones.
• Write-the-tests tasks: the share of hidden bugs your tests catch, scaled by the share of your tests that pass on the correct code.

An applicant record is built only from completed tasks. It never uses a resume, a name, a photo, demographic information or camera images.

• Skill match: for each skill a position asks for, the average score on tasks that exercise it, weighted by how much the position values the skill. Skills with no evidence are left out, and the record says what share of the asked-for skills it covers.
• Overall, improvement and consistency: the average of valid task scores, how the later half compares with the earlier half, and how steady the scores are. Improvement and consistency need at least two tasks, and consistency is not shown when every score is zero.
• Ranking: applicants are sorted by skill match, discounted by coverage (full coverage keeps the match, none halves it), so a strong score on one skill counts for less than the same score backed by work across all of them. It is a sorting aid; people decide.
• Tasks that do not count: a task handed in untouched is kept but not counted, and can be tried again. Applying needs 3 counted tasks.

• Scoring a task and sorting applicants are automatic.
• Nothing rejects, shortlists or reveals a candidate automatically. A person on the hiring team moves each application between stages. A rejection needs a reason chosen from a fixed list, and the candidate is told that reason.
• A candidate stays anonymous to the hiring team, shown as an id such as C-3F9A1B, until they are shortlisted.

Real tasks record how often you leave the tab, how active the keyboard and mouse are (counts only), pastes from outside the workspace, whether your camera was on, and whether the submitted code reaches outside the task (reading files or the environment). The camera check runs in your browser: no images or video are stored, only events such as “camera covered”.

These appear beside a record as something to ask about. They never change a score and never reject anyone automatically. Each has innocent explanations, and a person decides what, if anything, it means.

Candidates can download their data or delete it, with a seven-day window to change their mind. What we keep, and for how long, is in the privacy policy.