Understanding the Full Stack assessment report.

This article Covers:

Overview 

Understanding the Full Stack assessment report 

Conclusion

------------------------

• Overview: A comprehensive view of the full-stack assessment report with an explanation of each component and how each of it becomes instrumental in making hiring decisions. The platform currently supports questions for React, Angular, and Java Spring. 
• Understanding the assessment report: the report consists of eleven sections that delve deep into the test taker’s skills, namely:
• Absolute scorecard
• Summary card
• Performance insights 
• Detailed and expanded view of each solution
• Technologies used in submission
• Proctoring analysis
• Additional information 
• Social footprint

Let's begin  by seeing each one of them:

1. Absolute score: a quick snapshot on seven decisive parameters to base a high-level decision.  

• Time taken for completion: This indicates the total time taken by a candidate to complete the test.
• Overall score: 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 
• Test verdict: To check whether a candidate was able to pass by meeting the overall cut-off percentage. Use this to shortlist or filter out candidates quickly.
• Number of problems attempted: This will help you understand the number of problems attempted, against the total number of questions assigned in the test. 

2. Performance summary: Divides the solutions into three statuses. I .e ‘solution accepted’ when the solution fully meets the criteria. ‘Solution partially accepted’ when only part of it is right and lastly ‘Solution rejected’ if it fails to meet the solution criteria. 

Performance insights: This section will give an in-depth and a birds-eye view of a candidate’s skills, areas of strength, and weaknesses on three levels namely Beginner, Intermediate, and Expert. Having this data allows recruiters to make talent decisions more objectively, by structuring the interview and later process,  based on the insights gathered.   

Solutions: A listed view of candidates' solutions that will enable the recruiter to understand the score breakup per problem and the problem's status of acceptance. To check the actual submission, just click on any one of the problems.  

Live preview the solution by opening the IDE.

Review each test case of a solution .

 Technologies used in submission: Most tests that are created on DoSelect allow you to solve a problem in multiple programming languages. A candidate can choose from the assigned back-end programming languages.

6. Proctoring analysis: A deeper insight can be collected using DoSelect's proctoring engine about candidates' usage behavior during 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 hint at the possibility of malpractices.

7. Additional Information: Gather additional information/credentials about the candidate, essential for the later evaluation process.  

8. Social footprint: Assess the candidate's technology proficiency based on contributions made on Github, Stackoverflow & DoSelect.