Hiring
Review the take-home running, not just the diff.
A candidate sends a repository link. You open it in pyrovue and review the app running: click through it in the preview, run the tests in the terminal and see how the code is organised on the map. No setup on your laptop, and none of the candidate's scripts on it either.
How it works
From a submission to a running review.
- 01
Get the link
Candidates push to GitHub or gitlab.com. A private GitHub repo works when the candidate adds you as a collaborator and you open it from My Repos.
- 02
Open it
Paste the link. pyrovue installs and starts the project, and you can watch each command in the log.
- 03
Review it
Use the app in the preview, run
npm testorpytestin the terminal, read the files, and look at the Code Map for structure and import cycles. - 04
Share it
Send the panel the box's link so everyone looks at the same running app. On Pro and Team a box can stay private instead.
Why reviewers use it
Fair to candidates, quick for reviewers.
- The same setup for everyone
- Every submission gets a fresh box with the same resources, so a project that only fails on one reviewer's laptop doesn't cost the candidate.
- No candidate code on your laptop
- Install scripts run in the box, not where your company's credentials live.
- Minutes, not an afternoon
- Most projects are running in about a minute. When one fails, the log shows the command and the error, which is useful to see too.
- Structure at a glance
- The Code Map shows layers, hotspots and import cycles before you open a single file.
A tip
Tell candidates up front.
Say in the brief that submissions will be run on pyrovue, and point candidates at pyrovue.json for anything unusual, like a database migration before the first start. It's the same thing a good README does, and it saves both sides a round of email.
Questions
Asked often.
Run the repo you bookmarked and never tried.
Hobby is free and needs no card. Paste a link and your first box is up in about a minute.