Portfolio Pro
Loading page…
Loading page…
For managers hiring without a recruiter
Send one link. The candidate solves a small JavaScript Challenge in the browser, with no account, in 20 to 35 minutes. You get a Result page with the submitted code, which tests passed, and how the code arrived.
Open a real sample ResultWritten by Portfolio Pro to show the format, not by a candidate.
Free during early access. No checkout. JavaScript Challenges only.
Proof of work · Result
Illustration, not a candidate
Final state: all 5 required tests passed after 3 graded runs and 2 distinct versions.
Runs add up. Every graded run is counted.
How it works
No vendor score to decode. You get the code and the test results, so you know what to ask in the interview.
01
Choose a task from the library that matches the role.
02
The candidate solves it in the browser. Their work runs against a test suite in a sandbox.
03
When you send a hiring link, we email you when they save. The Result shows the submitted code, what passed, and how the code arrived.
How the code arrived
The server counts every graded run and records how much code each run added. A solution built over many runs looks different from one that appears whole and passes on the first run. Use that as a question in the interview. It does not show who wrote the code.
graded runs, left to right
one graded run
Illustration, not a real candidate. A Result shows the counted runs, versions, time from first run to save, and the largest jump for the actual Attempt. Neither shape proves who typed the code. It tells you what to ask about in the interview.
Why this beats a resume
Resume
Result
A story they (or an LLM) wrote.
The code they submitted, the tests it passed, and how long the tests took.
You guess from a job description.
You read their actual code and see which tests passed.
Claims you cannot check from a PDF.
Iterations, distinct graded versions, and the largest jump in code between runs, counted by the server. These do not show who typed the code.
The library
Choose a build and the record beside it lists that build's tests. Nothing here is a scored submission. Open the challenge when you want to write the code.
Send a link
Enter your work email and pick a Challenge. We email you a confirmation link that works for 2 hours. Open it to get the candidate URL, then send that URL to the candidate. The candidate URL works for 14 days.
Straight answers
A Result shows the submitted code, each test, and counts the server measured. A verified inbox is not a government ID and not proof of who typed.
Yes. Nothing stops it. The Result shows how the code arrived: Iterations, distinct graded versions, the time from first run to save, whether the first run already passed, and the largest single addition of code. Code that appears whole and passes on the first run reads differently from code built over twenty runs. Neither shows who typed it.
No. Hiring links are free during early access. An Early Access Request asks for a monthly budget so we know what a seat is worth to you. There is no checkout.
Each Challenge shows a suggested time, 20 to 35 minutes. The time is not enforced. The Result shows the real span from first run to save.
Anyone with its URL. It shows the code, the tests, and the counts. A Result can name the inboxes the server checked. It does not verify a legal identity.
Early access
Hiring links are free during early access. Tell us your monthly budget for candidate Challenges. It decides what we charge.