We are constantly updating HackerRank for Work with new improvements and fixes. Here is a summary of the updates we have made from April 1, 2019 to July 1, 2019.

CodeScreen Updates

Quality Review for Coding Questions

The Quality Review page analyzes your Coding Question and provides best practices for making high-quality questions.

Improved Report for Sentence Completion Questions

Customers are able to easily see candidates’ correct and incorrect answers to Sentence Completion questions.

CodePair Updates

CodeScreen - CodePair Integration

We have integrated our CodeScreen and CodePair solutions to give more insights on candidate skills using code submitted in the screening stage. We have enabled teams to create a connected interview experience from initial screening to the technical interview.

Advantages

• Hiring managers and interviewers can import questions and candidate code from the CodeScreen stage into a live CodePair session with a single click.
• Interviewers can review the code with the candidate, build upon the pre-screen challenge, and test code together in real-time.
• Candidates and interviewers can experience a truly interactive pair programming session.
• Improves efficiency and saves time of the hiring process by allowing hiring managers and interviewers to conduct effective first tech screenings remotely via video, evaluate candidates further and reserve onsite for the best candidates.

Learn More

Add Candidates to ATS from Public Link

HackerRank has supported inviting candidates to an assessment from a public link for years, but candidate information remained in HackerRank unless the recruiter manually added users into the ATS. With this launch, any candidates taking an assessment from a public link will be automatically created within the ATS for Lever and Greenhouse users (more ATS support coming soon).

Starting the recruiting funnel with a public link eliminates manual work. Rather than creating candidate profiles, public links handle the profile creation and recruiters can focus on identifying those relevant candidates that they want to move forward. This will make the recruiting process simpler and more efficient.

Learn More

Approved Questions in CodePair

It allows our compliance-conscious Enterprise customers to create a CodePair specific question bank. Company admins can tag questions and filter the interviewing experience to allow just custom questions with these tags.

Note that multiple tags can be added, each one restricting the search. (AND between tags)

Option to disable CodePair Self Signup for Interviewers

HackerRank supports a way for Interviewers who do not have an account to signup on the fly before an interviewer. This signup is restricted to only email addresses that match the company domain. 

Based on customer feedback, we have added a way to disable this sign up link. Although some customers appreciate the reduced friction at the time of an interview, others want to prevent signp for employees who have not done training and should not be provisioned.

Role-Based Assessment Updates

New IDE is now available to all customers

This was previously available as an opt-in and customers had to choose if they wanted to use this IDE over the older IDE available for front-end/back-end/full-stack developer question. This update upgrades everyone to the new IDE.

This IDE significantly changes the candidate experience for candidates attempting to solve front-end/back-end/full-stack developer questions. Candidates will be able to leverage better and more insightful autocomplete and linting, and debug Java code inside the browser. We have also significantly improved the offline working experience for candidates who still prefer working on their local IDE.

To know more about additional features available as part of this update, please refer to Q1 Release Notes

PDF Reports for attempts now have data for role-based questions

Platform Updates

SSO Auto Provisioning Users with Okta

HackerRank now supports creating users and teams from Okta through SCIM Provisioning. The following capabilities are supported:

• Push new Users
• New users created through Okta and assigned to HackerRank for Work will be created within the application.
• De-provisioning is not supported. This action needs to be done through Hacker for Work.
• Push Profile Updates
• Updates made to a user’s profile within Okta will update the user’s profile in HackerRank for Work.
• Import New Users
• Users who were created within HackerRank for Work can be download and turned into a User object in Okta.
• Import Profile Updates
• Updates on a provisioned user’s profile within HackRank for Work can be downloaded and synced in Okta.
• Push Groups
• Groups will be provisioned as Teams and members within those groups will be mapped into the team on HackerRank for Work.
• Only Add Users to Group is supported.
• Silent Provisioning
• Users are silently provisioned through Okta, meaning new users will not receive Welcome or Activation emails.

Learn More 

Integration Updates

IBM Kenexa BrassRing CodeScreen Integration

HackerRank now integrates with the IBM Kenexa BrassRing Applicant Tracking System.

Functionality:

• Send Test invitations to HackerRank assessments from within BrassRing
  • Optionally specify Time Accomodation % to extend assessment for certain candidates
• Receive Test Results in a BrassRing form when a candidate completes an assessment.
• Support for Candidates on Multiple Reqs
  • If a Candidate applies to multiple reqs, they only need to take the HackerRank assessment once, the results will be sent to all reqs that requested the test.
  • If a candidate has taken the test in the past, the historical result will be sent back to BrassRing.
• Preserve HackerRank role based access and permissions when taking actions in BrassRing

The integration uses a standardized Candidate Export XML API and Form Import XML API. If you have experience with these APIs and are a BrassRing Workbench administrator, you should be able to configure the BrassRing side of the integration yourself. If you are not familiar with these APIs, it is recommended that you work with IBM Kenexa professional services who can make the changes on your behalf.

Learn More

Fixed Issues

The following customer impacting issues were fixed within the last quarter.

• THD data issue due to the inconsistent time frame between mail tracking data and invites data is fixed. Now THD funnel shows accurate data for test started & test attempted.
• ModuleNotFoundError was seen when importing yaml for Python 3
• Intermittent issues where Monaco editor doesn’t allow candidate to type or edit code
• Candidates cannot run code if the head part of the code stub is empty
• Unable to edit candidate reports without first refreshing the page
• Company and Test Insights tab does not match actual company usage
• Unable to purchase subscription from trial for Luxemburg addresses
• Unable to list tests from Lever integration
• User is able to save Test Duration with `0` on Settings page
• Evaluator field does not get updated when inviting candidate via API
• Unable to import approximate solution into CodePair
• Scrolling the bar backwards does not update time when "All Code" toggle is on
• Some candidates were seeing Server Error: Unauthorized request after login
• Fixed checkbox to ignore row with error in bulk candidate invite
• Handle duplicate emails when capitalization is different
• Locked users not showing in user data download
• Cloned test was still using the duration from the original test
• Questions opened on the right side by default during some Library searches

Changes or Regressions

Role Based Assessments

1. The tools menu at the top of the IDE was updated.
   1. The “View IDE Tutorial” Link is now removed as we have the pre-login tutorial now
   2. There is a new “Reboot IDE” button for the rare scenario when the IDE is unresponsive. It happens when candidates run a command that takes up all the memory available in the container
   3. The “Reset Project” and “Reboot IDE” links are now under the “More” button on the top right corner.
      

2. "Select Framework" is now called "Select Environment" in step 1 when you start creating a Front-end/Back-end/Full-stack Developer question.