If your team hires in Ashby, you can now send an EasyEnv interview to a candidate straight from the interview plan, and watch the result come back onto the candidate's profile. No second tab, no copy and paste, no "did anyone send the test?" in Slack.
This post covers what changes for recruiters and hiring managers, what Ashby shows at each step, and how to switch it on in about ten minutes.
The problem it removes
A hands-on interview is the best signal you can get on an engineer. It is also, too often, the step where the pipeline stalls.
The recruiter moves the candidate to "Technical assessment" in the ATS. Then someone has to open another tool, find the right role, paste the candidate's email, send the invite, and later come back to copy the outcome into the ATS. Every one of those steps is a place for a candidate to sit for two days because the person who usually does it was on holiday. We wrote about how much those gaps cost you in why your best candidates drop out of the funnel.
With the integration, Ashby does the sending and EasyEnv does the reporting. Your team only does the part that needs a human: reviewing the work and deciding.
How it works, in one minute
- Your EasyEnv roles appear in Ashby as assessments. Any active role in your EasyEnv account can be picked.
- A recruiter adds EasyEnv to a stage of a job's interview plan and chooses the role.
- The candidate reaches that stage and the assessment is started from Ashby. EasyEnv emails the candidate their invitation right away.
- The candidate works in a real environment: a real server, a real terminal, a real codebase. Not a puzzle in a browser box.
- Every step shows up in Ashby as it happens, with a link to the full interview in EasyEnv.
- Your reviewer decides in EasyEnv, and that decision becomes the result in Ashby.
The interview also appears in EasyEnv under the role, exactly like one you sent by hand, so nothing about how your team reviews changes.
What Ashby shows on the candidate
| Status in Ashby |
What it means |
| Invited |
The candidate has the email and has not started. Ashby also shows when the invitation expires. |
| Started |
The candidate is working on it now. |
| Submitted |
The candidate finished. It is waiting for your team to review. |
| Completed |
Someone on your team accepted or rejected the candidate. Accepted shows as passed, rejected as failed. |
| Cancelled: Expired |
The candidate never started and the window closed. |
| Cancelled: Not completed |
The candidate started but the interview closed before they finished. |
Next to the status, Ashby shows the time the candidate spent, the score on automatically graded questions, a summary of the AI review, and a link to the full session.
The result is your decision, not a robot's
This is the design choice we care most about. EasyEnv grades what it can automatically and runs an AI review on the answers, and both show up in Ashby as supporting detail. But the result Ashby records is only ever the decision of a person on your team. Until someone accepts or rejects, the assessment stays at Submitted.
An auto score can tell you a candidate's service started. It cannot tell you they found the bug by reading the logs instead of guessing. That is what the session recording and your reviewer are for, and that is the signal we do not want an ATS rule to skip past. If you want a structure for that review, see how to write a technical interview rubric.
Small things that save real time
- Cancel from Ashby. Cancelling the assessment in Ashby closes the invitation in EasyEnv. If the candidate is mid-way, the session stops and their work so far stays available for review.
- No double invites. Starting the same role for the same application again before the candidate begins returns the interview that is already open.
- Your interviewers come along. Members of the Ashby hiring team who are also in your EasyEnv account are added to the interview as interviewers.
- Your invite window. Candidates have 7 days to start by default. You can change that on the Ashby card in EasyEnv.
Set it up in four steps
You need to be an owner or admin in EasyEnv, an admin in Ashby, and have an active interview plan in EasyEnv. Each assessment sent from Ashby counts as one interview, the same as one you send from EasyEnv.
- In EasyEnv, go to your account, Integrations, open the Ashby card and click Generate EasyEnv key. Copy it, it is shown once.
- In Ashby, go to Admin, Integrations, API Keys, and create a new key with Easyenv as the Integration Partner and write access to Candidates.
- Back in EasyEnv, paste that Ashby key into the Ashby card and save.
- In Ashby, go to Admin, Integrations, find Easyenv, click Enable Easyenv, paste your EasyEnv key, pick the Ashby key you just created, and leave Staging Base URL empty.
That is it. The full walkthrough, with troubleshooting, is in the Ashby setup guide.
Where it is not the right fit
To be straight about the edges: the integration sends take-home assignments, the kind a candidate completes on their own schedule. Live, paired sessions with an interviewer on the call are still scheduled from EasyEnv. And an email that belongs to a member of your EasyEnv account cannot be used as a candidate, so test with a second inbox, not your own.
Try it on your next role
If you already use EasyEnv and Ashby, the setup takes less time than the coffee break it replaces. Pick one open role, add EasyEnv to its interview plan, and let the next candidate who reaches that stage go through without anyone lifting a finger.
Not on EasyEnv yet? Start with one role and see what a candidate actually does in a real environment. That is usually the moment teams stop going back to take-home puzzles.