Connecting Lever

#How the integration is set up

1. 1

   Tell us Lever is where your hiring lives

   Email support@remakecv.com with your organisation name and a short account of how your talent team works today — where candidate CVs sit, and who needs to read the branded version once it exists.

2. 2

   Ask Lever for API access on your account

   Lever's own support team decides what access they can grant and on what basis. Asking is ordinary account administration, and their answer tells us what we have to build against.

3. 3

   Send the credentials across securely

   We will point you to a safe channel. Anything that reaches candidate records deserves the care you would give a password — not plain email, and not a thread with half the department on it.

4. 4

   We build the connection and turn it on

   Our team implements it against Lever's API and enables it for your organisation. The relevant controls then appear in your RemakeCV dashboard, and there is nothing for individual recruiters or interviewers to install.

#What the workflow looks like

Once your integration is live, the branded CV arrives where your hiring team is already working:

1. Source, screen and progress the candidate in Lever as usual.
2. Their CV is rendered into your organisation's branded document — the same template, the same editor and the same options as any other RemakeCV job.
3. The finished file returns to the candidate's record, where everyone involved in the decision opens the same version.

The third point is where a talent team running a collaborative process gets most of the value. A CV that goes out to a client is sent once and read once. A CV inside your own hiring process is opened again and again by different people at different points in the week — whoever screened the candidate, the hiring manager drafting questions, an interviewer skimming it twenty minutes beforehand, someone writing up notes afterwards. All of them should be looking at the same file. Keeping the branded version on the candidate's record, rather than in one person's inbox, means nobody quotes a line the next interviewer cannot find, and nobody is left reading the raw original because the tidied copy was never circulated to them.

Teams that anonymise CVs for a first sift get the same behaviour through the integration as they do in the browser. See uploading a CV and reviewing and editing for what happens between steps one and three.

#Does the integration change the formatting?

No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over an integration or is dragged into the browser. All the connection does is carry the file in and out, so switching one on never means reopening any decision about your output — what your panel reads is the same before and after.

If your branded document has not been designed yet, that runs as its own piece of work alongside the integration: our team builds the template to your organisation's own brand, and the connection then delivers it. See requesting a custom template.

#Building it yourself

If your own engineers would rather own the connection, the public REST API exposes the processing, retrieval and template endpoints directly, so you can wire RemakeCV into Lever on your own schedule and to your own design. See connecting RemakeCV to any ATS or internal system for what the endpoints cover.

#Which plan includes it?

Integration work is part of both plans rather than an upgrade. See plans and pricing.

#Start the conversation

Email support@remakecv.com with Lever and your organisation name. We will confirm what the integration will do on your account, what we need from you, and how your recruiters and interviewers will use it day to day.