You'll want to take note of several key components when reading a report. Here are some explanations of what each component consists of and how it is relevant to making decisions on candidates.
Fig. Candidate reports
The most noticeable component is the overall score that a candidate receives. This is usually the best indicator of how well a candidate performed on the given tasks. You should be able to gauge a candidate's performance over a certain cut-off.
One of the most interesting and important metrics in the overall report. It tells you - how well is the code written by a candidate. Read more about it here.
Number of problems attempted
This will help you understand the number of problems attempted by a candidate in a test.
Qualified or Not Qualified
Single point of reference to whether a candidate was able to meet your expectations from test or not. Use this to quickly shortlist a candidate.
Once you enable proctoring for your test, you can check the flag as insecure or secure in the report.
Total Time Taken
This indicates the total time taken by a candidate to complete the test.
DoSelect’s suite of assessments enables you to assess candidates on core concepts in a particular language. Vendors mostly assess these by the aid of algorithms and Data Structures whilst the role might or might not be big on algorithms. Simply put, a candidate you are considering to hire for a Java role should be assessed for concepts like Inheritance, Polymorphism, Method Overloading, Strings, Classes, Methods etc. and not mere algorithmic knowledge. Above is the overview of insights.
An all-in-one view about a candidate's solution that will enable you to understand of their score breakup per problem and the problem's correctness status. If you're more interested to check the actual code submission, just click on any one of the problems
Technologies used in submissions
Most tests that are created on DoSelect allows you to solve a problem in multiple programming languages. A candidate can choose any programming language while giving the test.
A deeper insight collected using DoSelect's proctoring engine about candidates usage behavior while giving the test. The metrics like the number of browsers used to give the test and the number of times a user was away from the test window will make sense if you care about test monitoring.
To make most out of DoSelect reports, you need to understand the above metrics carefully. The reports play an important role in your hiring process as it helps you make informed decisions.
If you are still looking for more information on reports, we would be happy to hear from you. Drop in at firstname.lastname@example.org