The key to a good test is the right number of quality questions with appropriate difficulty levels and enough time to answer these questions. While selecting questions, choose topics based on the candidates’ experience, especially for advanced topics such as Java project and Diagram-based questions.
Important: The examples in this section are based on the requirements described in
Best practices: Getting the basic details right.
Matching the questions to the requirements
This section is about adding the right questions for specific profiles.
Analyzing the job description
Divide the requirements into the following three sections:
- Section 1: Requirements that the candidate must have to qualify for the position. In this case, the candidate must have strong Java skills.
- Section 2: Set of requirements for which basic knowledge is enough. In this case, the candidate should know how to create diagrams to explain the architecture
- Section 3: Good-to-have requirements. In this case, knowledge about Spring and Hibernate will be considered.
Selecting the right type of questions
Selecting questions for the primary skill
Scan through the various question types available in the HackerEarth library to find a programming question to test that skill. In this case, Java. We recommend that you select a Java Project question, which will allow you to assess the candidate’s Java skills.
The secondary skill requirement is creating diagrams and implementing the design. Add a diagram-based question to support that.
You have covered the primary skills. Let’s move on to the secondary skills.
Selecting questions for the secondary skills
Select MCQs to assess secondary skills. The sample requirement mentions three skills:
Start with creating three sections, one for each topic, and not more than 5 questions per topic. Sections help you understand how the candidate has fared in each of the sections that you have created.
Selecting the right difficulty level
On a broad level, our difficulty levels are mapped to the experience level. The recommended mapping of the difficulty levels with the experience is as follows:
|Difficulty level||Experience (in years)|
Note: This is applicable to generic topics like Java which are used across all experience ranges.
Selecting the right number of coding questions
|Difficulty level||Average time required per question (in min.)|
Note: This is also applicable for Front end, SQL, and Java Project questions.
Diagram-based questions require a similar duration of time.
The ideal duration of a good screening test is not more than 90 minutes. Keeping this in mind, you should ensure that you do not add more than two programming questions in a test, which already has either:
- One diagram-based question
- Multiple choice questions
Note: The number of MCQs is based on the years of experience.
If you do not want to add a diagram-based question or MCQs, it is recommended that you decrease the test duration instead of increasing the number of programming questions.
This ensures that the candidate does not get exhausted while taking the test and remains engaged through the assessment process.
Selecting the right structure for your test
We recommend that you use the following experience-based structure to create your test.
|Experience (in years)||Test duration (in min.)||No. of MCQs||No. of programming questions||No. of diagram-based questions||No. of subjective questions|
|0-2||90 (max.)||10||2 (SQL and Front end)||0||0|
|2-4||60 (max.)||5||1 (SQL, Front end, or Java project)||1 (flowchart or UML)||0|
|4-6||45 (max.)||0||1 (SQL, Front end, or Java project)||1 (system design)||1|