Lever integration guide
Integrations are only available to CoderPad plans which support organizations. If you’re on a personal plan, please consider upgrading to access this feature.
CoderPad integrates with the Lever applicant tracking system to automatically create CoderPad interview sessions for candidates. Apply the
"coderpad" tag to jobs or candidates to tell us to automatically create pads for them.
When a matching candidate reaches the Phone Screen stage, CoderPad creates a pad and updates the Lever candidate profile with a link to the interview:
You then copy this link and send it to the candidate (and interviewer) in the interview invitation.
To enable this integration, you’ll need to provide us with Lever API credentials, and provide Lever with a CoderPad webhook URL.
These settings require a Professional or Enterprise Lever plan and a CoderPad organization plan (Small Team or higher). To configure them you must be a Lever Super Admin and CoderPad organization Admin.
Provide CoderPad with Lever credentials
To get started visit the CoderPad Organization Integrations page. You should see an unfilled form like this:
You will need two pieces of information from Lever: an API key and a Webhook signing token. The API key is needed so we can fetch candidate information from Lever and update the candidate profile with our pad link. We use the Webhook signing token to verify web requests sent from Lever.
Generate a Lever API key
To continue, you must be a Lever Super Admin and your organization must be on a Professional or Enterprise Lever plan.
Go to Lever and navigate to Settings: Integrations.
Under the heading Lever API credentials, press the blue Generate New Key button. For the integration name fill in “CoderPad”.
Copy the new API key because you will need it soon!
Grant these permissions by checking the corresponding check boxes:
- Read: Read stage
- Read: Read candidate
- Read: List stages
- Write: Add candidate link
Click the blue Done button then confirm that you Got it to persist the key in Lever.
Return to CoderPad and paste the API key into the text box Lever API key.
Retrieve webhook signing token
Lever pushes us data on candidates, and they sign their requests using a webhook signing token. CoderPad needs this token to verify that the requests actually came from Lever. (Curious how this works? See this StackExchange question on Hash-based message authentication codes.)
Back to Lever, navigate to Settings: Integrations: Webhooks tab. Look for the heading Webhook signing token.
Copy the Signature Token and return to CoderPad and paste it into the text box Lever Webhook signature token.
Choose a pad owner
Please choose the CoderPad user from your organization who will own the Pads created by this integration.
Save and test
The page should now look like this:
Press the Save button, and we’ll test and persist your credentials. If it worked it’ll look like this:
If it didn’t work, check Lever to confirm you pressed Done afer creating the API key. Try also to create a new key ensuring it has the correct permissions.
After you’ve setup CoderPad with the Lever details, you’ll need to choose candidate stages to act upon, then add a new webhook to Lever.
Choose candidate stages
Please choose Lever candidate stages CoderPad should check for before creating Pads. For example, “Phone Screen”. You can choose multiple stages by holding the Control or Command key and clicking. Press Save to confirm.
Provide Lever with a CoderPad webhook URL
After providing CoderPad with Lever details, the Organization Integrations page now shows a webhook URL:
Copy this URL.
In Lever, return to the Settings: Integrations: Webhooks tab. Under the heading Webhook configuration, enable the Candidate state change toggle switch. Next to it, click + Add webhook to add a new webhook and paste the CoderPad Webhook URL into the box.
Press Verify Connection and it should spin then show ✔ Verified.
API setup is now complete. Please proceed to select specific jobs or candidates for this integration.
Enable integration for specific jobs or candidates
Enable for a job
If you tag a job in Lever with “coderpad”, then CoderPad will check for candidates who’ve applied to this job, and when a matching candidate enters the Phone Screen stage, we’ll create a pad for them.
To enable this, view a job in Lever and apply the “coderpad” tag:
To disable this, simply remove the “coderpad” tag.
Enable for a candidate
You can also tag a specific candidate with “coderpad”. When this candidate enters the Phone Screen stage, CoderPad will create a pad for them.
Disable for a candidate
Do you have a candidate who’s applied to a coderpad-tagged job, for whom you don’t want a pad created? You can disable CoderPad for such a candidate by viewing their Lever candidate profile and removing the “coderpad” tag. When this candidate enters the Phone Screen stage, CoderPad will not create a pad for them.
Schedule a CoderPad Phone Screen
At this point, you’ve setup Lever and CoderPad and tagged specific jobs or candidates with “coderpad”.
To trigger the integration, move a matching candidate into the Phone Screen stage. (If your stage is not named “Phone Screen” or “Phone Interview”, please email email@example.com for additional assistance with setup.)
After a few moments, we’ll create a pad and add the link to the candidate profile:
Please note this consumes pad quota!
Ensure that you only move “coderpad” tagged candidates into Phone Screen when you really mean it. Remember also that you can disable this for a single candidate by removing their “coderpad” tag.
Right click the CoderPad link and copy it. When you schedule the interview, include the link in the invitation:
When the CoderPad interview is finished, you may wish to view the results from Lever. The same CoderPad link we added to the candidate page also serves as a record of the interview. You should be able to play back the history of the interview sessions from that same link. You may also find it helpful to copy code from the interview into a candidate note.