Only consider candidates who can actually write a web application. You'll be
surprised at how effectively even the simplest of the challenge
asking candidates to actually write the code will filter non coding coders.
Candidates can choose any IDE, language, libraries or framework of their choice. No restrictions.
In fact, many-a-times what tools they choose tell a lot about them
Don't limit yourself only to 'algorithmic' questions. You can ask the candidate to solve real-world problems.
For example, 'scrape this webpage'. or 'Find the latest tweet of this person'
Here's how it works
Create a challenge by describing requests and expected responses
Get candidate Url and share it with candidates
You can publish the url on a Job board, your careers site or share it with candidate(s) in a 'coding sprint' across the room
Once a candidate successfully answers, we collect their resume and display it on the 'answers' page