Practice → evidence → application

Practice the work. Carry the proof into hiring.

Debug services, review code, change repositories, design systems, and solve focused problems in a real workspace. Keep the work private, then share selected evidence with an application.

Repository debugging · attempt 04Checkpoint saved
settle.ts+8 −3
42  const receipt = await ledger.claim({
43    settlementId,
44    idempotencyKey,
45  });
46  if (receipt.replayed) return receipt.result;
47  return settleAuthorized(receipt);
Focused checks✓ retry preserves one settlement✓ duplicate webhook is idempotent1 integration check unavailable · retry when service returns
Evidence privateAI assistance: disclosed Resume from checkpoint

The work sequence

Practice the same way good engineering happens.

No score spectacle. The useful artifact is the work, the checks, the reasoning, and the recovery path.

  1. 01Understand the brief
  2. 02Inspect the real system
  3. 03Change the smallest correct owner
  4. 04Verify focused checks
  5. 05Explain the decision
  6. 06Retain evidence privately

Candidate control

Evidence moves only when you move it.

Completed attemptVerified work + provenance
Private PortfolioYou decide what to retain
One application grantExact claim, exact hiring process
Employer packetOnly permitted evidence
Future accessRevocable by the candidate

Real recovery states

A workbench is only credible when failure is designed too.

  • Failed checkKeep the exact failure and retry after a material change.
  • Interrupted attemptResume from the durable checkpoint instead of replaying completed work.
  • Tool unavailableShow the blocked dependency and keep independent work usable.
  • Private / revokedEmployer access follows the current evidence grant, not a stale copy.

Build proof before the interview asks for it.