What parameters to choose to evaluate a candidate’s technical skills

The task of technically evaluating a candidate is not simple. Each company has its own criteria and variants, which makes it difficult to have a homogeneous view of the candidate.

For this reason, we have launched a new feature in Rviewer that will bring clarity and light to our technical tests for companies: a candidate skills report, in which multiple variables are analyzed to measure the candidate's real level.

This allows us to have a pool of candidates with their skills validated according to a common scale, thus facilitating the rapid selection and evaluation of the candidate by the company.

Let's see what parts this report is composed of.

The candidate card on the outside

This is the outside view of the brand new candidate report:

In this initial card we see the main characteristics of the candidate summarized. On the one hand, an overall score is assigned. On the other, their skills and salary requirements are shown.

In the center, in the radial graphic, their main skills are detailed:

  • Maintainability: degree to which an application is understood, repaired, or enhanced, and the ability to make the solution testable.
  • Code quality: we measure code quality based on design patterns and clean code.
  • Testing: we measure the candidate's ability to test solutions with the maximum number of logical variants.

Candidates report from the inside

Inside each card we will find a link to the full report, where we will find more metrics to help us understand the skills and shortcomings of each developer when performing the technical test.

On the one hand, we see the radial diagram that was shown in the card, and on the other a level rank graph that compares the overall quality of the developer with the rest of developers who have performed the same test.

Within the testing section, we discover two metrics: 

  • Code Coverage
  • Test Quality: Based in how many paths cover the test but also in what is the Mutation Metric Score.

Within the maintainability section, two other metrics:

  • Readability: easy with which the solution is read and understood.
  • Testability: degree to which the solution supports testing, and how many tests needs to cover the full logic. The higher, the better.

Finally, the code quality section is extended with two metrics:

  • Design Patterns: Based on how well the candidate has applied some design patterns to improve the code.
  • Clean code: Based on how good is the solution of the candidate in terms of readability, extensibility, maintainability and complexities (both cognitive and cyclomatic).

How can I access the reports of already validated candidates?

You can also access to the new Rviewer functionality by clicking directly here, where you will have to choose the programming language you are interested in to see the candidates.

Advantages of visual reporting and unified technical testing

Because our developers perform the same technical test, we can compare their performance on the basis of the same exercise. Then, our experts analyze the work done and elaborate the scores as a letter of introduction to the companies.

So, if you are a company interested in hiring a developer for a certain position, you will have a lot of data and evaluations of the candidates. And all from the metrics extracted from the correction of the technical test.

This speeds up the selection process, saves time on ineffective technical tests and allows you to better match the candidate you need at any given moment.

Related articles

Stay tuned: receive the latest product updates

Subscribe to our newsletter to keep up with the latest trends!