Tip: If you want to test candidates on a specific part of your technology stacks like Angular or jQuery, add a <script> tag to the HTML whose src attribute downloads the code you want. The candidates can then use that technology to answer.
- Click on the Library tab on the home page and then click on the Create Question button.
On the Problem Statement page, specify:
A. Problem Name
- The problem name should be short and topical. It should not give any hints to solve the problem.
- While you can assign any score you want for the questions you create, we use certain standards for assigning scores to the questions we create that you might find useful.
For an easy question that can be solved in 15 minutes
For a medium question that can be solved in 30 minutes
For a difficult question that can be solved in 45 to 60 minutes
- Tags are words or phrases that help with the searchability and organization of your questions. You can add the existing tags or create new tags and set the difficulty level for your Question by associating the tags as Easy, Medium, or Hard. Alternatively, associate custom Tags to identify your Question by its complexity or levels.
- Click on the Tags drop-down, and type a keyword. Example, Easy.
- Click on the Add option, the “Easy” tag is associated with the Question.
- When you view your Questions in the Library, the associated tags will be indicated for every Question. You can use these Tags to generate candidate reports and performance graphs. Refer, Associating the Tags for Questions for more information.
D. Problem Description
- A good problem statement should comprise a clear and detailed problem description. It should clearly state how elements should appear in the final output on the web page. Ideally, an image should be included to show the final output. Any elements that are supposed to behave dynamically must be stated as well.
E. Interviewer Guidelines
- Interviewer Guidelines are for later reference. You can include a rubric about scoring the questions or write solutions to the problems in this section. These can be used by your team while evaluating the test.
Note: Interviewer Guidelines are only visible to your team and you; however, candidates cannot view these notes.
You can support your problem statement and internal notes by attaching a relevant reference file in these sections. Refer to the How to Attach a File to a Problem Statement topic for more information.
- Click on the Save & Proceed button.
On the Design Stubs page, perform one of the following operations:
You can provide them with a code stub for any or all three languages, as required.
Note: Candidates can edit the provided code stub. If you do not want them to edit any particular part of the code, you can add it in the comments in the stub.
- Select the Enable multiple file support option to upload the folder structure for the front-end code project.
i. Click on the current structure option to download the default multiple files projects. You can make changes to this folder instead of creating the folder from scratch.
ii. Click on the Choose file button to upload the project folder.
- Click on the Save Question button to save the question and exit. Alternatively, click on the Save & Add another button to save this question and proceed to create another one.
- The Questions you create are stored in the HackerRank Library under the “My Company questions” tab. The Question type and the associated tags are indicated below every Question title as shown below.
While in the Library, you can proceed to create more questions or add Questions to your Tests.