Creating a Front-end, Back-end or Full-stack Question

NOTE: Please go here if you are looking for teams management.

HackerRank for Work allows you to create Role-based questions to assess candidates. This facilitates the hiring of programmers who are familiar with each layer of software technology and are adept at front-end programming, back-end programming or both. Role-based questions can also be custom made to suit roles such as DevOps, Database Engineer and more. Below we elucidate the steps to create a role-based question.

To learn more about "Role-based Assessments", read our blog.

Prerequisites

• You must be logged in to your HackerRank for Work account.

Steps

1. Click the Library tab on the home page and then click Create Question. The HackerRank Library page
2. In the Select Question Type dialog box, select the role according to which you want to tailor the assessment, under the Role-based section, as shown below. You can choose one of the following roles: 
   
   1. Front-end Developer 
   2. Back-end Developer 
   3. Full-stack Developer
   4. Database Engineer
   5. DevOps
   6. Android Developer  Selecting the 'Role-based' Question type
3. Once you choose the role, you will be proceeding to the stage where the question can be designed. 

 Note: The following steps elucidate how to set up a Front-end Developer question. These steps are also applicable to the Back-end Developer and Full-stack Developer type questions. You can view the detailed steps in creating questions for other roles in the Question Creation section.

Consider you are framing a question that is part of a Front-end developer assessment.

1. For a Front-end developer question, in the Select framework tab, select the desired framework and hit Proceed. Selecting the framework for a Front-end project
2. The Setup Project tab will already be initialized with a sample project for the selected stack.
   • The sample project has the necessary hackerrank.yml config file that is required for configuring necessary project parameters like scoring command and IDE menu config.
   • You can use this sample config file as a reference when creating your own question. To know more about various parameters of the config file, see Writing the configuration file for projects in Front-end, Back-end, and Full-stack developer questions. 
   • You can use the already present sample project to proceed to step 7 if you quickly want to set up a question. 
   • Do not use sample projects in a test. These projects are designed to only serve as sample projects, they are not designed for evaluating candidate skill.
3. For setting up the project:
   1. You can import your own project from a public git URL or by uploading a zip Setting up the project

       Note: Beta version of this step had a restriction that top-level directory must be named 'project'. That restriction isn't valid anymore.

   2. As soon as the project is imported, validation will start automatically. A Front-end, Back-end or Full-stack developer question cannot be created before the successful validation of the project.
      Validating the project
   3. Refer to How to create a valid project for a Role-based question to learn more about the validation process.
   4. If the validation fails, use the information provided by validation result to fix the project.
      Failed project validation
   5. You can use the in-page file editor to update and save files or update project on your local and re-import.
   6. If you are making changes using the in-page file editor, hit the Validate button when you are ready. It will start the validation process again.
   7. Once validation succeeds, you can Save & proceed to the next tab. 
      1. Note 1: If the validation fails at a step that is run after a server has been created (scoring command validations for example), you will get an additional link called 'open debug console'. You can open the server and debug scoring command in the live environment. The debug console is available to you for 30 minutes and changes made here are not saved to the original project.
      2. Note 2: If you were editing a Full Stack question, on modifying existing files, you have an option to 'reset to last saved project structure' which will reset the file structure to the last valid state. Similarly, you have an option to 'Download last saved project structure'.
5. In the Define Question tab, specify the following:
1. Problem Name
   Ensure that the problem name does not hint at the solution to the problem. 
2. Score
   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.
   

   Score	Question Type
   50 points	For an easy question that can be solved in 15 minutes
   75 points	For a medium question that can be solved in 30 minutes
   100 points	For a hard question that can be solved in 45 to 60 minutes

3. Tags
   Tags are words or phrases that help in searching and organizing questions. You can add existing tags or create new tags. 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.

   a. Click the Tags drop-down, and type a keyword. Example, Easy.

   b. Click Add, 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 Setting the Difficulty Level for Questions for more information.

4. Problem Description
   While describing the problem statement, ensure that the question is clear and detailed. You can also use tables, graphs, or attachments to enhance the clarity. Defining the Question and the problem statement
5. Internal notes
   Internal notes 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. They are only visible to your team and you; however, candidates cannot view these notes. This step is optional.
6. 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 for more information.
7. Click Save & Proceed.

The Questions you create are stored in the HackerRank Library under the “My Company questions” section. 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.