Improved interview state management (CodePair)

We’ve rolled out a change to improve the state management of CodePair interviews. Before this change, if an interviewer did not click the “End” button at the end of an interview (see image below), that interview continued to be listed in the “In Progress” field of “Reports” and was accessible by the candidate, indefinitely.

Screen Shot 2015-07-30 at 11.45.24 am
Ending CodePair interviews

 

The change ensures that all “In Progress” interviews are ended, and moved to the “Completed” state automatically after 60 minutes of inactivity. An interview is considered inactive when all the participants (i.e. the interviewer(s) and the candidate) leave the CodePair session.

Screen Shot 2015-07-30 at 11.48.17 am

We’ve also cleaned up all the old interviews in “In Progress” state as a part of this change. Please note that an interview may be re-opened (and moved back to “In Progress”) at any time by the interviewer by logging back into the session (at which point the candidate may re-enter, as well). It cannot, however, be re-opened by the candidate.

 

Improved video chat in CodePair

CodePair helps you get the best out of technical phone interviews. Besides the ability to see the candidates code real-time, one of the things that makes phone interviews more effective is to see candidates while talking to them. We’re excited to share 2 significant improvements to the video chat experience on CodePair:

Video call notifications: When someone initiates a video chat, it will notify the other interview participant(s) to join. This prevents any confusion and overhead communication between the candidate and interviewer around having to start the video chat at the same time.

Screen Shot 2015-07-22 at 1.09.04 pm

Chat in full-screen: There’s an option to have an enlarged video chat so you can have a proper conversation looking at the candidate. The minimal video mode can continue to be useful when the interviewer wants to focus on reading the candidate’s code.

Screen Shot 2015-07-22 at 1.09.14 pm

We hope these changes will help you conduct more effective phone interviews. Feel free to share any comments/suggestions.

CodePair Editor Improvements

The code editor in CodePair has been improved to help the interviewees feel at home. We strongly believe that CodePair must let the candidates remain focused on the interview questions and they shouldn’t have to spend time adjusting to the platform. Two of our recent changes will help candidates significantly:

Auto-complete: Intellisense, or suggestions for code auto-completion, is one of the most important feature offered by IDEs. This feature is now enabled in CodePair for C, C++, Java, Python, Ruby and PHP. If needed, it can be turned off from the settings menu.Screen Shot 2015-07-08 at 7.13.46 pm

Vim/Emacs editor mode: Many programmers are used to their own editor. With CodePair, one can now select Vim or Emacs as the editor mode and use the relevant shortcut keys.

Screen Shot 2015-07-08 at 7.14.00 pm

We continuously strive to give the best possible experience to candidates so they are fully equipped to showcase their technical strengths in an interview. If you’ve feedback or suggestions wrt this, please comment in the section below.

Introducing Company Insights: Make hiring data-driven

We’re very excited to announce the beta release of Company Insights, one of HackerRank for Work’s most anticipated new features. With Insights, we’ll show you all the key data on your HackerRank for Work usage so that you can make your recruitment process truly data-driven. Here are just a few of the ways that Insights will quench your thirst for recruiting data:

  • Account summary: An aggregate measure of how much you’ve used HackerRank for your technical hiring, as well as the ability to drill down further by segmenting your data over time or by different teams within your organization.

Selection_016

  • ROI Calculators: Built-in ROI calculators will give you the power to to see exactly how much you’ve saved on tech hiring since your investment in HackerRank.

Selection_014

  • Industry benchmarks: Get an inside view of how your recruitment team is performing against other companies based on their size, industry, and location.

Selection_015

  • Recruiter Performance: Detailed stats for every recruiter on your team gives you direct insight into who is sourcing from the best channels and how their hiring funnels compare against each other. You also get to measure the effectiveness of the screening questions and the interviewers.

We’re rolling this out today as a limited beta so if you’re interested in enabling Insights for your account, please reach out to us at support@hackerrank.com. Feel free to share your comments/feedback in the section below.

SSL Cipher Change Notification

As a standard part of our security review process, we will be changing the set of ciphers supported by our web servers in our AWS ELB cluster. The changes will go live on Thursday, 18 June 2015 at 12:00 Hrs UTC The following ciphers are being dropped:

  • DHE-RSA-AES128-SHA
  • DHE-DSS-AES128-SHA

With this change we are effectively enabling the “2015-05” pre-defined security policy available on Amazon’s Elastic Load Balancer. You can find more information about the security policy here.

Qn: What does it mean to disable an existing cipher? A client (such as a browser) typically supports multiple ssl ciphers. As part of the handshake the client and server agree on one specific cipher. If the server rejects a requested cipher (because it is no longer supported) the standard protocol is for the client to request another cipher from its list of supported ciphers. All standard browsers and most API SDKs work on these principles and the change should be completely transparent to end users.

Qn: Why is this change required? This is a standard part of keeping our security infrastructure up to date. It is security Best Practise to replace ciphers that have been shown to have theoretical vulnerabilities with more robust ones.

Qn: I am using a custom API integration with a highly bespoke SSL wrapper and I use one of the ciphers that are going to be disabled. What should I do? You can test your software by requesting one of the supported ciphers listed in the AWS page linked above. If any of them work, you can configure your wrapper to request that supported cipher instead of one of the disabled ones.

Qn: Will there be any disruption of service during this change? No. There will be absolutely no disruption if you are using a standard web browser to interact with our application, or if you are using any standard SSL SDK.

Qn: I need more help. What can I do? We are happy to help. Please leave a comment below or send us a note at support@hackerrank.com

Test Report Emails – Change of Source Email Address

When one of your candidates completes a test, some key details are sent over to you as an email. The email is sent to the recruiter who invited the candidate and any one else you have explicitly configured in the Test’s Advanced Settings.

The email used to be sent from reports@interviewstreet.com. As part of an ongoing email infrastructure revamp we are retiring that address. The report emails will come from reports@hackerrankforwork.com starting immediately.

If you have any email filters in place please make sure to update them.

SSL Cipher Change Notification

As a standard part of our security review process, we will be changing the set of ciphers supported by our web servers in our AWS ELB cluster. The changes will go live on Tuesday, 26 May 2015 at 12:00 Hrs UTC

The following ciphers are being dropped:

  • ECDHE-RSA-RC4-SHA
  • RC4-SHA

The following cipher is added:

  • DES-CBC3-SHA

With this change we are effectively enabling the “2015-03” pre-defined security policy available on Amazon’s Elastic Load Balancer. You can find more information about the security policy here.

Qn: What does it mean to disable an existing cipher?

A client (such as a browser) typically supports multiple ssl ciphers. As part of the handshake the client and server agree on one specific cipher. If the server rejects a requested cipher (because it is no longer supported) the standard protocol is for the client to request another cipher from its list of supported ciphers. All standard browsers and most API SDKs work on these principles and the change should be completely transparent to end users.

Qn: Why is this change required?

This is a standard part of keeping our security infrastructure up to date. It is security Best Practise to replace ciphers that have been shown to have theoretical vulnerabilities with more robust ones.

Qn: I am using a custom API integration with a highly bespoke SSL wrapper and I use one of the ciphers that are going to be disabled. What should I do?

You can test your software by requesting one of the supported ciphers listed in the AWS page linked above. If any of them work, you can configure your wrapper to request that supported cipher instead of one of the disabled ones.

Qn: Will there be any disruption of service during this change?

No. There will be absolutely no disruption if you are using a standard web browser to interact with our application, or if you are using any standard SSL SDK.

Qn: I need more help. What can I do?

We are happy to help. Please leave a comment below or send us a note at support@hackerrank.com

Introducing DbRank: Assessing SQL made easy

We’re very excited to announce the launch of DbRank, our latest automated platform for assessing SQL skills. It simplifies your hiring for a variety of database-related roles like Data Analysts, Business Analysts, Data Scientists, Application Developers and many more. The platform supports four of the most commonly used databases: Oracle, MS SQL server, DB2 and MySQL.

 

How DbRank works?

DbRank is a new question type in HackerRank for Work, such that when you create a new question you’ll select “DbRank” as your question type.

Screen Shot 2015-05-08 at 9.22.15 pm

Step 1:

Write the problem description (just like you would for any other new question)

Step 2

Select a set of databases that the candidates will be allowed to leverage to write their queries. Next, create a set of tables which will be available to the candidates in their test database. This involves writing the SQL queries for table definitions and inserting data in these tables as needed. There’s also an option to generate the SQL automatically by uploading a CSV file.

Screen Shot 2015-05-08 at 9.22.26 pm

Step 3

Define the expected output which will be used to automatically grade the question by matching it against the output from candidates’ queries.

 

How will candidates solve DbRank questions?

Candidates will solve DbRank questions in the same way that they solve any other Coding question. They’ll choose the database they want to use from the available options and then write their SQL queries in our online editor (which also supports syntax highlighting). The queries are written on the tables which were created as a part of the question. They’ll run their queries to see if their output matches the expected output.

Screen Shot 2015-05-08 at 9.22.41 pm

 

DbRank now makes it very easy for you to assess database skills in an automated way without waiting for an in-person interview. We would love for you to try this new offering by HackerRank and share your comments and feedback with us.

Introducing Insights for Tests/Questions

Today, we’re beginning to roll out Insights for Tests/Questions on HackerRank for Work to help you understand how your tests and questions are performing.

 

Thousands of companies who’re looking for technical talent use HackerRank Tests to screen candidates effectively and make their recruitment process more streamlined and cost effective. Now for the first time you can gain insight into how your Tests and Questions are performing and how you can improve them over time.


Test Insights

Go to any HackerRank test and you’ll find a link to Test Insights in the left pane. Note that there’s also a link to Question Insights for each question added to the test.

Selection_220
Test page

The first thing you’ll notice is aggregate test statistics on the top right of the page. These include % invited candidates who end up attempting the test, median attempt time, median attempt time to full score and median score. Next, you’ll see a distribution of candidate scores. This gives a very good picture about the difficulty of the test.

2
Test Insights

Next, you go one step deeper and look at question-level statistics. This helps you understand

  • How candidates are dividing their time across questions and whether the time limit for the test is sufficient or not
  • Whether the score of the some questions is out of proportion to the time candidates take to solve them and you should adjust question scores

Last, you get to see the conversion funnel of candidates i.e. % of candidates who qualify the screening round.


Question Analytics

To check out the Insights for questions, you can open the question list of a test (as mentioned earlier) or go to Library.

4
Library

The aggregate statistics, similar to the Test Insights, give a good idea about the difficulty of the question and the score distribution further gives a breakdown by candidates scores.

For coding questions, you see a very interesting breakdown by programming language. This helps you understand

  • What languages are most commonly used by candidates to answer the question?
  • Is the question relatively easier to solve in some languages than others? Some languages might give candidates an unfair advantage to solve a question much easily, which you might not want to allow going forward
5
Question Insights

Next, you see the usage of question over time. This tells you how long the question has been out there and whether it’s time to stop using it as it might already be popularly known to candidates.

 

We believe this is just the tip of the iceberg when it comes to empowering you to make your recruitment process more data-driven. Providing more insights around your HackerRank account usage, quantified returns of using HackerRank, industry-wide stats (including comparison to peers) and many more related things are among our top priorities today. We would love to hear your feedback on the Test/Question Insights and more about what insights will help your organisation.

Candidate and Tests API v1 Sunset Notice

Two of our oldest APIs – The Recruit Candidate API and Recruit Test API – are being deprecated with immediate effect and they will be completely shutdown on 30 April 2015. The older APIs are replaced with a much improved v2 of the HackerRank for Work API, documented here: http://apidocs.hackerrank.com/hr4wv2

 

Most of the changes are backward compatible and many users will simply need to use the new v2 end points. You can read about all the changes in our Migration guide, and if you have any questions about this or need any assistance migrating to v2, please drop us a note at support@hackerrank.com