false |

DevSkills Documentation

Building your challenges

Our mission is to make developer hiring sensible rather than a university exam. That's why we specialize in real-world challenges that tackle problems developers face at work (e.g. we don't do Algo/DS-based tasks or CS quizzes). 

Here are a couple of examples of such tasks:


There are three basic scenarios of how hiring teams use coding challenges:

  1. Screen their candidates with quick take-home tasks (<1h) before the main tech interview (this one only has framework-agnostic auto-tests to score candidates submissions)
  2. Run full tech evaluation with elaborate take-home tasks (2-3h) and a follow-up tech discussion over the results (this one comes with both framework-agnostic auto-tests and a code-review scorecard)
  3. Run live-coding interviews using adapted coding challenges from Category 2 where the candidate needs to implement some parts of the task and answer the interviewer's questions they found in the challenge's code review scorecard (this one comes with both auto-tests and a code-review scorecard).

Getting started

To save you time, we've created this elaborate blog post that describes how we design challenges.

To save your time, feel free to stick to the challenge structure described in one of the challenges above. Such structure has been tested on over 2000 interviews so we know it works, that's why we stick with it.

Increasing the probability of someone using your challenges

Increase the number of use-cases where your coding challenges can use:

  1. Ask us at authors@devskills.co if there is any uncovered use-case that some team(s) could benefit already now.
  2. Have several variations of the same task that:
    1. evaluates developers of different experience levels (see how TMF - Lvl 1, TMF - Lvl 2, and TMF - Lvl 3 differ in scope)
    2. covers different interview types (e.g. screening, full take-home, life-coding interview).

Did this article help?

Thank you for your feedback