Candidate Work Index Submitted With the Application

Submit a one-page index naming each work artefact, the part of it that is the candidate's and the direct path to it, and open that index in the first minutes of the live screen.

Intervention I-012 Actor: candidate action Scope: individual Cost: low Evidence: supported

On the canonical path

Assessed on the work, against a rubric that is shared — One timeboxed exercise that resembles the job. The candidate is given the criteria before starting, the timebox is enforced against the evaluator as well, and the same rubric scores everyone.

This entry is one of the things that holds that commitment up.

What it looks like when this intervention is in place

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

The one-page index, submitted with the application reconstruction

Title: Work index — backend: storage and ingest

Ingest library, upstream project under a different organisation. Mine: the storage layer rewrite — 40 commits, March to November. The link goes to the commit range, not to the account.

Internal service, not public. What can be shown: the design note with the employer's name removed, and a walkthrough on request.

Five-minute read path: the migration note in /docs, then the fourth commit in the range.

The CV line reads 'storage layer rewrite, upstream ingest library, contributor', so the claim and the path to it sit in one sentence.

What to notice: The surface a screener opens is a choice, and the default is a profile page in date order. The index makes that choice, and names which part of each artefact is the candidate's.

What this targets

Expected effects

M-023 loses its default: the surface opened is the one the candidate named, with the part that is theirs stated on it
A contribution held under another organisation arrives as a commit range rather than as something to be discovered
The index travels with the application, so B-003 and B-005 open the same named artefacts instead of whatever a profile page shows first

What to measure

work_index_attachment_rate
named_artifact_citation_rate
technical_screen_advance_rate

From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

Candidate

What reaches them: The surface an application opens on by default — a profile page, a list of repositories in date order — and their own work spread across it in a shape that page does not show.
What it means from there: Which surface is opened is decided by what the application carries, and the index is the part of that the candidate writes.
What happens next: Names each artefact, the part of it that is theirs and the direct path to it, and opens the index in the first minutes of the live screen instead of leaving the choice of surface to the hour.

Recruiter

What reaches them: An index in the application with named artefacts and direct links, alongside the profile link.
What it means from there: The minutes available per application go to something already located, and a line in the CV has a path attached that opens in one click.
What happens next: Records the note from the named artefact where the index points to one, and from the profile page where the application carries no index.

Hiring manager

What reaches them: The index in the material the panel receives, with the ownership line and the read path in it.
What it means from there: The exercise hour and the evidence of past work stop competing for the same minutes: what to open is stated, so the round is spent on the exercise.
What happens next: Reads the named artefact before the session where it is short enough, and asks about that work in the round rather than about the profile.

Share card png This page as markdown json