Candidate Documentation

  1. Intro to TalentScore test
  2. Different types of tasks
  3. Programming task modes

Intro to TalentScore test

When you receive an invite to the test, click on the “View test details” button to see more details about your test, like the timing, task types, and the technologies used in our build environment. This is an example of the Welcome page you will see:

 

Please read the terms of the assessment in order to be fully prepared for your test. You should also check the versions of the technologies you will be working on within this test.

You may also verify the details of the test and check what each section contains. The different sections of your test are displayed in order, so you will be able to plan your test experience and better prepare yourself for the challenge!

 

Once you have done that, you can edit the display options that will be visible throughout the test. Switch between Dark and Light mode or High Contrast, to judge which is the best for you.

 

When you’re ready to take the test, please select the checkbox, confirming that you are prepared. Then, you can proceed to the test by clicking the “Start the test” button which will be highlighted in green.


Once you start the test, you will have to complete it within the given time. At every stage, you will see the total time remaining in the top bar. You will also see the suggested completion time for the page, based on how long the test authors think it should take you, to help you more easily manage your time.

 

When you are done with all the tasks on the page, select the "Next" button to move to the next page. NOTE: you may not be able to go back once you leave the page - if it isn’t possible, you will be notified with a pop-up window before moving onto the next step. TalentScore does not support Internet Explorer versions older than 11, or Safari versions older than 12.

If in the incredibly rare circumstance that you come across any errors while taking the test, please let us know by writing an email to support@devskiller.com. Please include some screenshots, logs, and generally more detailed information about the issue to get a faster response.

NOTE: If you have any questions about the test, please contact your recruiter as TalentScore is just the testing service provider.

 

Different types of tasks you might have

There are 7 types of tasks that you might face during the test. The list of the types of tasks is available on the Welcome page. You might also receive requests from the platform, such as being asked to provide a link to your LinkedIn profile, make a photo capture, or provide some other information. The information requested depends on your recruiter. Remember, that you are able to see which types of tasks you might encounter during the assessment, on the welcome page, before starting the test.

Let's take a closer look at all of these types of tasks:

1. Multiple Choice tasks

Single answer: Select the best option from the provided answers. 



Multiple answers: Select all the options that fulfill the requirements provided in the task description.


2. Essay tasks

Write the answer to the questions or question outlined in the task:



3. Code Gaps tasks

Here, you need to fill in the blanks with the correct code or text fragment. Note: Please be sure to use the specific syntax for the technology in which the task is written (e.g. C#, Java, Javascript, Ruby "true" and Python "True").



4. Code review tasks

Note: Before starting this task you will see a quick tutorial on how to complete it. If you would like to watch it again select the "Watch tour" button.

In this task, you will have to review a piece of code. Highlight a code fragment and press "c" to add a comment. All the comments you add will appear on the right-hand sidebar. If you would like to come back to the added comment, you just need to click on it and you will be able to edit it.



5. Database tasks

Write a SQL query to fulfill the requirements provided in the task description. At any point, while working on the query, press the "Run & Validate" button. You will then be able to see the results that your query returns and compare them to the expected results.

If your result does not match the required result, you can try to edit the query and press the "Run & Validate" button once again. Please note, there is a specific database engine specified. You can use all the native functions and syntax it provides.



6.  DevOps tasks

If you have received a DevOps task, your browser window might look like the picture below. Follow these steps to complete the task:

  1. Install/Open the SSH client. For example, this would be the PuTTy SSH client if you use Windows systems.
  2. Enter the URL, login, and password provided in the instructions, on how to connect.
  3. You might see a dialog asking for trusting the server while you are trying to connect to the server for the first time.
    a) In the case of PuTTY it looks like this:Candidate_Documentation_Update_1.png
    b) And for SSH:
    Candidate_Documentation_Update_2.png
  4. Complete all requirements described in the task description.
  5. Finish the test. NOTE: If you click on the button ‘Finish the test,’ you will lose the connection with the server within a few seconds and you won’t be able to make changes afterwards.


Some of the Security tasks might also involve working with an external server. You might receive the link to a web page built by us. Follow the task instructions to find problems in the site security. In this case, you will be asked to extract some data from the website and paste it into the answer field.



6.1.  Kubernetes DevOps tasks

In order to connect to the Kubernetes cluster that is provisioned for the exam, you need to have a Kubernetes client installed. The primary tool that is used for this task is kubectl that is available for download and installation on your workstation from the official Kubernetes page: https://kubernetes.io/docs/tasks/tools/#kubectl.

7. Programming tasks

To complete the programming task you will need to implement certain functionalities (described in the requirements and test documentation) in the assessment’s project. Tests with several units might be included to help you verify your solution, but remember that those tests do not cover all the requirements and edge cases.

Remember to upload your solution before the time is up.

Before starting the programming task, you will need to choose one of three possible options for completing the task. NOTE: You can change the selected option at any time during the test, but if you begin with the In-browser editor and switch to one of the other modes, your code may be lost, so please copy your code from the In-browser editor to your own, before changing modes. (remember about the time!).



GIT repository

If you have chosen the option to clone the GIT repository, you will see the window as shown below. 

 
These are the steps for this option: 
  1. Clone the GIT repository that contains the source code of this project by running the `git clone` command provided in the description.
  2. Open the project in your favorite editor or IDE and solve the task.
  3. Commit and push your changes. NOTE: only the master branch is supported.
  4. Build and run your project using either the ‘Run full build,’ or ‘Run quick build,’ buttons to see the result of your changes. This step is strongly suggested to make sure that your solution is correct. However, if you don’t manage to do it because you run out of time, it won’t affect the assessment. Using either one of the buttons will result in a popup asking if you would like to save changes. In case of using ‘Run quick build' option, the platform will attempt to run the tests for the task, without attempting to download all dependencies before running them.

NOTE: Some projects might have files which cannot be edited. You can find the list of these files in the instructions. The section is called Read-only files. If you push the code after changing these files, you will receive an error. It will tell you which files should remain unchanged. If you receive the error, please, correct the files and try to push your code again. In order to fix it, try restoring them to their original state and push your changes again. To do this, use the following commands:

git checkout origin/master -- File1 File2 File3
git commit -am 'Restoring forbidden files'
git push // success! 


In-browser editor 

If you have chosen the in-browser editor, you will be able to see the window as shown below.

  • Select "Run full build" or "Run quick build" to have your code built and tested. A prompt will appear asking you if you would like to save any changes to the project.
  • You will be able to view the build console and test results in the bottom window.

NOTE
: A quick build does not download dependencies without a prior full build!

 

Download/upload code

If you have chosen the option to download the code, you will be able to see the window shown below:



These are the steps for this option: 
  1. Download the project source code as a ZIP archive.
  2. Edit it locally using your favorite IDE. NOTE: Please remove any dependencies or artifacts prior to creating a ZIP file of your solution. Your ZIP file must be less than 5 MB in size.
  3. Upload a ZIP archive with your modified files. NOTE: Uploaded files will overwrite the previous edition.
  4. Build and run your project using either the ‘Run full build,’ or ‘Run quick build,’ buttons to see the result of your changes. This step is strongly suggested to make sure that your solution is correct. However, if you don’t manage to do it because you run out of time, it won’t affect the assessment. Using either one of the buttons will result in a popup asking if you would like to save changes. In case of using ‘Run quick build' option, the platform will attempt to run the tests for the task, without attempting to download all dependencies before running them.

NOTE: Some projects might have files that cannot be edited. You can find a list of these files in the instructions. The section is called Read-only files. If you push the code after changing these files, you will receive an error. It will tell you which of the files should remain unchanged. If you received this error, please, correct the files and try to push your code again. In order to fix it, try restoring them to their original state and upload your ZIP archive again.

 

 

 

Was this article helpful?
104 out of 109 found this helpful
Have more questions? Submit a request