Lever integration
Move the candidate in Lever. Kendor sends the screen or the interview.
When a candidate enters the Lever stage you choose, Kendor emails them a coding screen, or a link to book a live coding interview within the hours you set. Each step comes back as a note on the Lever opportunity, with a link to the review, so recruiters can follow along without leaving Lever.
- Technical screenSenior Backend EngineerSenior Backend screenRemove
- On-site interviewany jobLive coding · Pairing sessionMon, Tue, Wed, Thu, Fri · 09:00–17:00 Europe/Berlin · next 14 daysRemove
- ada.okafor@example.comSenior Backend screen · Senior Backend EngineerCompleted
- liam.chen@example.comLive coding · Pairing session · Senior Backend EngineerScheduled
- noah.berg@example.comSenior Backend screen · Platform EngineerInvited
- 2026-10-06 10:14
Kendor: invited to Senior Backend screen. The candidate got an email with their link.
- 2026-10-07 16:40
Kendor: Senior Backend screen: submitted in 74 min, ready to review. Review: https://kendor.io/organization/12/attempts/4821
- 2026-10-08 09:12
Kendor: Senior Backend screen: Passed, score 84/100, took 74 min. Review: https://kendor.io/organization/12/attempts/4821
- 2026-10-08 09:15
Kendor: Senior Backend screen: Advanced by the reviewer.
01
A stage sends a screen or a live coding interview.
Pick a Lever posting and one of its stages, or a stage name on any posting, and choose what it sends. A coding screen goes out by email right away. A live coding interview comes with the weekly hours the candidate can book: days, times, time zone and how many days ahead.
- Lever postings share one pipeline, so every posting offers every stage
- Bookable times skip the panel's other Kendor sessions
- The roster and candidate profile show the Lever posting and stage, and what Lever last heard
02
A note on the opportunity at every step.
Kendor writes back as notes on the Lever opportunity, not into its fields. For a screen: invited, submitted with a review link, the result and your decision. For a live coding interview: invited, the booked time, held with a review link, and the panel's decision.
- Each step is noted once; a note Lever refuses is retried for a day
- Cancelled, declined, missed, or never booked in time? A note says so
- Screened from Lever, then invited to live coding? Those notes land on the same opportunity
- 2026-10-09 11:02
Kendor: invited to the live coding interview Pairing session. The candidate got an email to book a time.
- 2026-10-09 18:27
Kendor: live coding interview Pairing session booked for 2026-10-14 09:00 UTC.
- 2026-10-14 10:01
Kendor: live coding interview Pairing session held (58 min), ready to review. Review: https://kendor.io/organization/12/interviews/311/result
- 2026-10-14 15:30
Kendor: live coding interview Pairing session: Advanced by the panel. Review: https://kendor.io/organization/12/interviews/311/result
03
Set up with one API key, US or EU.
Create an API key in Lever and paste it into Kendor. Kendor finds whether your account is on Lever's US or EU host, checks what the key can read and adds the stage-change webhook if the key may. If it can't, add the webhook in Lever and paste its signing token.
- Every webhook is signed; Kendor rejects any that doesn't match
- Lever sends the same change twice? The candidate still gets one invite
- The key is stored encrypted; disconnecting removes it and your stage rules
Connected with the key ending R7xq (EU), since 2026-10-09.
- Key permissionsThe key can list postings and stages.
- WebhookKendor added the Candidate Stage Change webhook in Lever.
- Candidate Stage Change turned onLever tells Kendor when a candidate changes stage.
- NotesResults are written as notes on the opportunity.
How it works
Lever stays the system of record.
Connect with an API key
Kendor finds your region and adds the webhook where the key allows. A Super Admin turns Candidate Stage Change on in Lever.
Map stages to screens and interviews
For one posting, or a stage name on any posting, choose a coding screen or a live coding interview and the hours it offers.
Follow along in Lever
A note lands on the opportunity as the candidate is invited, books, submits or is interviewed, and is decided.
Questions
Which plan includes Lever?
Pro and Enterprise include it. An owner connects Lever from Integrations in your dashboard.
Does it work with Lever accounts in the EU?
Yes. Kendor tries the key on Lever's US and EU hosts and keeps the one your account is on, so there's no region to choose.
Why notes and not fields?
Lever's custom fields live in per-posting forms, so Kendor adds a note to the opportunity at each step instead, visible to everyone who can see the candidate. The code and the review stay in Kendor, one link away.
Does Kendor work with other ATSs?
Yes. Ashby and Greenhouse work the same way: a stage you choose sends a screen or a live coding interview, and Kendor reports back to the application. Without an ATS, you invite candidates directly.
More of Kendor
All features- Coding screensAsync take-homes in a real browser IDE, reviewed by your team.Read more
- Live codingOne link, one shared sandbox, a verdict from every interviewer.Read more
- InterviewsSelf-booking, invites that update in place, live review.Read more
- AI agentsClaude Code and Codex in the candidate's terminal, on your keys.Read more
- AI review summaryA first read of each attempt, with evidence. Never a score.Read more
- Real environmentsSeven pinned languages, PostgreSQL and Valkey, one kendor.yaml.Read more
- Repo importCloud or self-hosted Git, private repos too, one fixed snapshot.Read more
- Ashby integrationAshby stages send screens or book live coding; results come back as fields.Read more
- Greenhouse integrationGreenhouse stages send screens and live coding; notes come back.Read more
Run your next screen on Kendor. Read what the code says.
Create your workspace, import a repository or start from a template, and send your first screen today.
Hiring at scale? Talk to us