Table of Contents
- End to End Documentation
- Fetching Your Greenhouse API Key
The HackerRank-Greenhouse integration allows recruiters with accounts on both Greenhouse and HackerRank for Work to process candidates without breaking their workflow in Greenhouse (ATS). The integration supports both Tests and CodePair.
Greenhouse maintains the end user documentation for the end to end workflow.
End to End Documentation
You can access detailed documentation at the following links. You need to be a current Greenhouse customer for these links to work.
Fetching Your Greenhouse API Key
There is one Greenhouse API Key per company. You can find your company's key by Navigating to Settings -> API Access and scrolling down to the Greenhouse Integration section. Note that the ATS Integrations section will only be visible if you are a member of the Owners Team of your HackerRank for Work account.
You can copy this Key and paste it into the appropriate settings section of your Greenhouse account.
I am not able to see the API Keys in my HackerRank for Work account. Why?
It is only visible to users who are members of the company's Owners Team. If you are a normal recruiter and interested in using this integration, you can find out the members of the Owners Team Settings -> Teams Management and request one of them to give you the Key.
Who is treated as the Inviting Recruiter if I invite candidate through Greenhouse?
Greenhouse sends us metadata about the recruiter who initiated the action to invite a candidate. That information is used to determine the inviting recruiter.
After the Test result is initially synched, if I change score in HackerRank, will it be synched back to Greenhouse?
No. The updated scores will not be reflected in Greenhouse.
I am unable to invite candidates any more. I never had these problems till recently What do I do?
If you receive an error when trying to invite a candidate, and see something like the following message, then read on:
We started enforcing a lot of security and seat controls to the Greenhouse integration so that the product behavior is more consistent with what you can do directly on our interface. After the recent changes, a candidate invitation can fail for one of the following reasons:
The API Key you used in your account is not valid for your HackerRank for Work account.
- Recruiter's email address in Greenhouse is different from the email address in HackerRank for Work. For e.g. you could be using firstname.lastname@example.org in Greenhouse and email@example.com in your HRW accounts. It does not matter which one you fix; they just need to be the same.
Candidate email address is missing or invalid
Candidate with this email has already been invited.
Recruiter does not have a "Recruitment Seat" on HackerRank, and as such does not the privilege to invite candidates
Recruiter does not have permission to access that particular test
Recruiter's HackerRank Account is not activated.
Can't you display a more meaningful error message?
Yes, there really should be a better error message. We are working with Greenhouse to ensure the Greenhouse UI is improved in this regard.
We are using a generic email address for our HRW account. How can we invite candidates?
We only require that the email address associated with your Greenhouse account match at least one user in your Company's HRW account. As such you can either change your Greenhouse account HackeRank for Work account. If you wish to reconfigure your HRW account, please reach out to us at firstname.lastname@example.org
Can we use a custom template that is saved on HRW?
Yes, the recruiter will be able to select which template to be used when inviting through Greenhouse.
Alternatively, if the recruiter has configured a Default Template to be used (see screenshot below on how to do that), that will be applied.