Scheduled Maintenance on August 14th, 2016

HackerRank for Work will be down for scheduled maintenance on from 11:30pm PDT on Aug 14 – 01:30 AM PDT on Aug 15. We’ll be performing some system enhancements that’ll make your user experience even better (and faster) than it already is. During this time no one will be able to access the HackerRank platform.

Frequently Asked Questions

How does this impact test candidates?

The tests interface will not be available during the maintenance window. Candidates will see a notification to come back at a later time. We will also ensure that candidates are allowed to start their Test only if they can complete it before the start of the maintenance window.

How does this impact CodePair sessions?

New CodePair sessions cannot start during the maintenance window, and up to 90 minutes prior to the start of the window. For sessions that are live as we approach the window, we will show warnings to the participants so they can complete their interview. Interview data recorded before the maintenance window starts will be safe.

How does this impact my reports?

You will not be able to view reports or dashboards during the downtime.

As always, if you have any questions, please email us at support@hackerrank.com

Invite reminder emails

We added a new feature to HackerRank for Work: reminder emails. For each invite you send, you can opt to send one reminder email with customizable contents. This is a simple way to increase the number of candidates that attempt your tests.

Using the reminder emails feature is simple. Turn it on, select the timing of the reminder, and set the contents.

Screen Shot 2016-07-25 at 10.35.29 AM

 

You can enable reminder emails for a test from the miscellaneous section of its advanced settings. You can also set a default value for all invites you send in your personal user settings.

Do some spring cleaning with archived tests!

Your tests page just got a little tidier. Until now, all of your tests lived in one big list with no indication of whether or not the test was actively being used. To help communicate whether a test is in use or not, we’re introducing a separate listing of Archived Tests.

archived

You can archive a test from your main test list by checking the box left of the name and clicking the archive button.

Screen Shot 2016-05-09 at 3.50.12 PM

All of your test’s data is retained, and you can restore it back to the main list at any time. Invites cannot be sent for an archived test, but any outstanding invites or in-progress candidates will not be affected.

We see the archived tests list as a way to declutter and focus your test list. By storing your old tests out of view, you can focus on the tests you’re actually using without worrying about losing any data.

New Feature: Dynamic Tests

Our customers tell us that they often wish each Candidate being assessed is given a different Test. The idea is to have a pool of questions of a similar kind, and have the system select a subset of questions to present to each Candidate.

HackerRank for Work has long supported shuffling of Questions in a Test. In this model all candidates will see the same set of questions, but the order in which the questions are presented is different for each candidate. Today we are very excited to launch a new feature – “Dynamic Tests” that helps users automatically build an entirely different Test for every candidate based on specific rules.

The first thing you would do to start using the Dynamic Tests feature is to add tags to the questions you are interested in using in your Test. Make sure similar questions are tagged with the same labels. For e.g. add the ‘Easy’ tag to all questions you consider easy, or ‘Polymorphism’ to all questions related to object oriented inheritance concepts, and so on. Note that questions in the HackerRank for Work library are already extensively tagged.

Once you have your questions tagged, you can enable this feature by going to the Tests’ Advanced Settings page, Miscellaneous section. Once this feature is enabled, you will be able to add one or more rules, with each rule specifying the Tags to be matched and the count of questions to be picked with those tags.

Pasted_Image_21_04_16__7_57_PM

Note: You can specify multiple tags in a rule. For e.g. you can choose 1 question that has both ‘Easy’ and ‘Algorithms’ tags. You can also specify a second rule to select 2 questions for Logic or Data Interpretation, etc.

Take this feature for a spin, and let us know what you think!

Unified login across CodePair and HackerRank for Work

As a HackerRank for Work user, if you start a CodePair interview while already logged in to your HackerRank for Work account, it is reasonable for you to expect that you don’t have to log in a second time. Unfortunately that is not how it was. With a change that we are releasing today your HackerRank for Work and CodePair sessions share information so that you have to only log in once.

Here is what you would see if you visited a CodePair link while being logged in to your HackerRank for Work account from another browser tab.

CodePair sharing cookies

 

This login sharing works in the opposite direction too. If you start a CodePair session, and then visit you HackerRank for Work account you will not be prompted for a password.

Finally, it is important to remember that if you log out of your HRW session while a CodePair is going on, you will be logged out from both places. Don’t worry that does not mean your data will be lost, it only means you will have to log in again to access your pad.

Any questions or comments? You can leave a note below, or write to us at support@hackerrank.com

Customize phone interview experience

As part of a series of changes to improve the phone interview experience, our latest update allows you to choose the font size of the code written by you or the candidate during a CodePair interview. This option is available from the settings menu just like the other customization options of selecting the editor mode, turning on/off intellisense. 

Screen Shot 2015-11-19 at 6.23.31 pm

Upgraded CodePair availability

Earlier today, we rolled out an upgraded failover feature for CodePair. This allows a CodePair interview to continue on a secondary server if for some reason the primary server goes down. Even though our data center already guarantees 99.95% uptime, we believe it’s important to get that value as close to 100% as we possibly can, which is why we’re upgrading our failover system.

The way this feature will work is simple: if the primary server experiences downtime during a CodePair interview, both the interviewer and candidate see this pop up:

Screen Shot 2015-11-05 at 4.42.21 pm

When the user presses “Continue”, their CodePair interview session restarts on a secondary server with all of the session’s previous details and code completely intact. The interview will continue with minimal interruption and no data loss.

If you have any questions about this failover functionality, please write to us at support@hackerrank.com.

Scheduled Maintenance on Oct 21, 2015

HackerRank for Work will be down for scheduled maintenance on Oct 21 from 01:30 AM – 04.30 AM PDT. We’ll be performing some system enhancements that’ll make your user experience even better (and faster) than it already is. During this time no one will be able to access the HackerRank platform.

Frequently Asked Questions

How does this impact Test Candidates

The Tests interface will not be available during the maintenance window. Candidates will see a notification to come back at a later time. Further we will ensure that candidates are allowed to start their Test only if they can complete it before the start of the maintenance window. For e.g. if candidate Tom tries to start the “HackerRank Java Test” that is of 90 minutes duration after midnight on that day, he will be prevented from doing so as the scheduled end of the test will overlap with the maintenance window.

How does this impact CodePair Sessions

New CodePair sessions cannot start during the maintenance window, and upto 90 minutes prior to the start of the window. For sessions that are live as we approach the window, we will show warnings to the participants so they can wind up their interview. Please be assured that interview data recorded before the maintenance window starts will be safe.

How does this impact my Reports

You will not be able to view reports or dashboards during the downtime.

As always, if you have any questions, please give us a call at +1 415 900 4023 or e-mail us at support@hackerrank.com

Internal Notes comes to all Question Types

Earlier this year we implemented a feature that allowed Coding challenge creators to add internal notes. The feature has been a hit with our customers, and many requested us to extend it to other question types. So here it is. From now on you will be able write internal Notes for all questions, just below the Problem Statement.

Just to recap – Internal Notes appear in the Question view in your HackerRank for Work account, and candidate test reports. Candidates cannot see them. So go ahead and use them to document what a reviewer should watch out for while manually grading a question, or to note down why a particular question is worthy of being included in your library, etc.

Internal Notes

 

Authenticated test links in invitation emails

The test invitation email has been improved to provide a better experience to the candidates. The email will contain a “Start Test” button (see image below) instead of candidate email and password. Clicking on this button will take the candidate to a test login page which will be authenticated for that specific candidate and they will not be required to enter their email and password. Candidate will have to enter other fields, like “Univ/College Name”, “Full Name” etc (as applicable to the test) before starting.

Screen Shot 2015-07-30 at 10.56.06 am
Test invitation email
Screen Shot 2015-07-30 at 10.56.12 am
Test login page

Note

  1. This change doesn’t apply to cases when a candidate uses a short test URL or public test URL (one where password is not needed) e.g. http://hr.gs/arpit. These links will behave exactly as they do today.
  2. This change doesn’t apply to cases when the core email template is modified. By core email template, we’re referring to the part of the email which is non-editable from the invite candidate interface. It can only be modified by HackerRank support team as of today. The invitation emails sent for these cases will continue to include a password.
  3. This change doesn’t impact CodePair.