Interpreting Your Candidate's Completed Assessments

In this article, we’ll look at some specific steps you can take when reviewing and interpreting the results of a developer assessment. We’ll provide details on how you can look from a top-down perspective to funnel in on the best candidates, without spending too much time on poor candidates.

We’ll look at:

Comparing Across Candidates

Within Qualified, we provide a very high-level overview of your candidates in the form of the Assessment score. This score is calculated off the tests for each challenge within the assessment, and should mostly be used as a quick filter, and in some cases, as a relative comparison between candidates.

Eliminating Very Poor Performers

Digging into the Assessment Results

Once you have eliminated the lowest performers, you can start to analyze the results of each candidate to look for stand out skills.

Candidate Feedback

Every candidate is given the opportunity to provide feedback at the end of an assessment. This can provide insight into their experience with the test.

Assessment Summary

Besides the score, one important detail included in the assessment summary is the overall time taken. This number can help guide your expectations for the challenge solutions.

If a candidate took a long time, but didn’t solve every challenge — or solved them poorly — you should look into that further, and maybe discuss with them what happened.

Challenge Summary

The assessment results includes a quick overview of each challenge. You should look out for:

Challenge Details

At this point, you can be confident that it’s worth looking through the code solutions.

Solution Code

Look over the final solution for the following:

Output

You should open up the Solution Details to see more details, including the run output, where you can look for:

Example Test Cases

Qualified provides example test cases on most of our challenges. These can be used by the candidate to run their code before running it against the full test suite.

Code Playback

Our advanced code playback makes it possible to look into the programming style and thought process of your candidate.

Quick Usage Summary: You can simply use the play button to run the code, or you can click the bar at any point to see the code at that point. You can also check Key Events Only to focus on major events (ignoring most keystrokes).

The code playback can give you further insight in the following ways:

Solution Review Examples

These are contrived just to highlight some common issues.

Fantastic Solution

var solution = {  
    /**
     * Squares the input number.
     * @param {number} num The number to square
     * @returns num squared
     */
    square: function(num) {
        validateNumber(num);
        return Math.pow(num, 2);
    },
    /**
     * Cubes the input number.
     * @param {number} num The number to cube
     * @returns num cubed
     */
    cube: function(num) {
        validateNumber(num);
        return Math.pow(num, 3);
    }
};
/**
 * Ensures the input value is a number
 * @param {number} num The number to check
 */
function validateNumber(num) {  
    if(typeof num !== 'number') {
        throw new Error('Not a number: "' + number + '"');
    }
}

Decent Solution

var solution = {
    square: function(num) {
        return num * num;
    },
    cube: function(num) {
        return Math.pow(num, 3);
    }
};

Poor Solution

solution = {  
"square": function(n) { return n * n },
cube: function(myNumber) {  
  console.log(myNumber)
        return myNumber * myNumber * myNumber
  }
};

Technically valid, but…

No Effort Solution

var solution = {  
    square: function(num) {
        if(num === 1) return 1;
        if(num === 2) return 4;
        if(num === 3) return 9;
        if(num === 4) return 16;
    },
    cube: function(num) {
        if(num === 1) return 1;
        if(num === 2) return 8;
        if(num === 3) return 27;
        if(num === 4) return 64;
    }
};