Proof of Work

Changelog

Changes a candidate or a hiring team can see. A saved Result is never rewritten: it keeps what was recorded on the day it was saved.

1. November 4, 2026v1.14.0

   Results are easier to share

   • A Result can be shared to LinkedIn or added to a GitHub README as a badge.
   • The first screen now has a path for candidates to try a Challenge with no signup.

2. November 1, 2026v1.13.0

   A review-and-fix Challenge, and questions pinned to the code

   • New Challenge: review a teammate’s merge-intervals code, find what it gets wrong, and fix it.
   • Interview questions on a Result can point at a specific line of the submitted code.
   • The site states what a Result cannot prove.
   • Employers can resend a Challenge.

3. October 16, 2026v1.11.0

   A sample Result, interview questions and a product demo

   • A sample Result written by Portfolio Pro shows the format before you send a link.
   • Every Result lists questions to ask in the interview.
   • The home page has a 36-second demo with captions.
   • The Challenge editor keeps your code if you leave and come back, and says what Save did.
   • Emails carry a one-click unsubscribe link.

4. October 9, 2026v1.9.0

   Two async Challenges

   • New Challenges: Retry with backoff, and Run tasks with a concurrency limit.

5. September 30, 2026v1.8.0

   Results show how the code arrived

   • A Result states whether the first graded run passed and the largest addition between graded runs, both taken from what the server graded.
   • The hiring product became the home page.

6. August 30, 2026v1.5.0

   Server-counted iterations, and two more Challenges

   • Iterations on a Result are counted by the server, so the number is evidence and not a claim.
   • New Challenges: Implement throttle, and Implement an LRU cache.

7. August 29, 2026v1.4.0

   Proof of Work for hiring

   • First release of Challenges and Results, starting with Implement debounce.

See how grading works for where the numbers on a Result come from.