The DevScreen platform uses use code-reviews, bug fixes, and short projects to find the best engineers in your pipeline. No Leetcode puzzles here! Test engineers using the types of problems they'll solve on the job.
Hello PH!
We’ve been iterating on DevScreen for over a year now with the goal of making the developer interview process for both candidates and the company that is hiring.
Many automated tools don’t assess relevant skills during an interview. This is a waste of time for the candidate and a missed opportunity for the company. At the extreme end of the scale, you have companies asking candidates to invert a binary search tree on a whiteboard. All that this assesses is the candidate’s ability to read ‘Cracking the Coding Interview’ and work well under the pressure of being watched. Neither are particularly important attributes of an engineer and result in companies often missing great candidates or hiring sub-par engineers.
Today, DevScreen supports three different test types: code reviews, bug fixes, and projects. To help prevent the challenges from being made public, we spin up a new private Github repository for each test and add the candidate. Once they’re finished, they are automatically removed from the Github repo and we review their submission (or the company reviews the submission themselves).
We have a library of tests in place for various different skillsets. There are short, open-ended tests that can be done in any language or framework, and there are very specific tests that assess a candidate’s abilities in, say, React and TypeScript only. We lean towards open-ended tests ourselves, but we’ve found that companies who are hiring contractors like to test very specific skills only.
DevScreen Recruit
DevScreen Recruit