Greenhouse
Test Utopia is a Take-home Tests partner inside Greenhouse. Once connected, recruiters get a Send Test button on any candidate scorecard, and scores come back automatically. Available on Professional and above.
Setup takes about ten minutes and needs org-admin access here plus Site Admin in Greenhouse.
What you need first
At least one published assessment. Drafts and archived assessments do not appear in the Greenhouse dropdown.
1. Create an API key
Under Integrations → API keys, create a key with the greenhouse:integration scope only.
That scope is purpose-built and grants nothing else in the public API. Do not reuse a * key here: this key is handed to a third party, and its blast radius should be exactly one integration.
Copy the key when it is shown — it is displayed once. You need the same key in both of the next two steps.
2. Connect from Test Utopia
Integrations → Greenhouse → Connect, paste the key, and use Test connection. That checks the key is valid for your company and carries the right scope.
The key is not stored here; it is being verified. Score pushes back to Greenhouse are authenticated with our own partner credentials.
3. Configure Greenhouse
Assessment partner setup is not self-serve — Greenhouse's Partnerships team configures it on their side.
Send your Greenhouse Partnerships contact the four endpoint URLs shown on Integrations → Greenhouse after you connect, along with the same API key. Once they confirm it is configured, the take-home stage becomes available in your jobs' interview plans.
How it runs
- A recruiter opens a candidate scorecard and picks an assessment.
- We email the candidate their link.
- The candidate sits the assessment.
- The score returns to the Greenhouse scorecard with a link to the full results here.
What we send back — and what we deliberately do not
The payload carries the candidate's score, the maximum possible score, and your configured pass mark as a threshold.
It does not carry a pass/fail verdict, and that is deliberate. Sending a verdict would make the rejection rule ours; sending the measurement and your own threshold leaves the decision — and the accountability for it under GDPR Article 22 — with you as the employer. Apply the comparison on your side.
If you automate a rejection on that score in Greenhouse, that is an automated decision you are making about a person, with the obligations that follow.
Re-sending a test
Sending a test again to someone who already has one behaves differently depending on whether they have used it.
If they have not started, or are mid-test, nothing changes — the link already in their inbox keeps working, and they are not sent a second, different one. An accidental double-click is harmless.
If they have already completed it, they get a fresh link and can sit it again. The earlier attempt and score are kept; only their ability to start a new one is restored. That newest link is the one that works, so if they kept the original email, point them at the latest.
A retake uses another attempt from your monthly allowance, the same as re-inviting from the assessments page.
One candidate has exactly one invitation per assessment. Removing and re-adding them in Greenhouse does not create a second one — send the test again instead.
Troubleshooting
The candidate says their link is already used — they completed this assessment before. Send the test again from Greenhouse and they will get a fresh link; see Re-sending a test.
No assessments in the dropdown — none are published, or the key is connected to a different company.
Connection test fails — the key is revoked, belongs to another company, or is missing greenhouse:integration. Keys cannot be edited to add a scope; create a new one.
Scores are not arriving — check the candidate has actually submitted and been evaluated. Scores are pushed after evaluation completes, not at submission, so an assessment containing essays waits for someone to mark them.
If evaluation has completed, open Recent score pushes on the Greenhouse page. It lists every attempt with Greenhouse's own response, so a rejected push explains itself there. A push still marked Retrying is fine — the retry curve runs for about three days. Note that your API key is not involved in score pushes, so rotating or reconnecting it will not fix a failed one; once the cause is resolved, Retry failed pushes requeues them without any risk of double-posting a score that already landed.