Connecting Greenhouse

#Why in-house teams ask for this

Greenhouse sits mostly with internal talent acquisition teams rather than staffing agencies, and that changes what a formatting integration is for. You are not packaging a candidate to win a client — you are handing a shortlist to a hiring manager and an interview panel who have to compare four people fairly, often in a rush, often on a phone between meetings. CVs that arrive in four different layouts make that harder than it needs to be. One house format puts the same information in the same place every time, and it carries your employer brand into a document the candidate's own work is being judged on. That is the value here: internal comparability first, presentation second.

#How the integration is set up

1. 1

   Tell us Greenhouse is where your hiring runs

   Email support@remakecv.com with your organisation name and a short picture of the current path — who prepares candidate CVs, and how they reach the hiring manager today.

2. 2

   Arrange API access on your Greenhouse account

   Your Greenhouse administrator, or their support team, decides what credentials can be issued and under what terms. Their answer defines what we have to build against.

3. 3

   Send the credentials over securely

   We will point you to a safe channel. Anything that touches applicant records deserves the same handling as a password — not plain email, and not left in a shared inbox.

4. 4

   We build the connection and enable it

   Our team implements it against Greenhouse's API and switches it on for your company. The relevant controls then appear in your RemakeCV dashboard, with nothing for individual recruiters or coordinators to install.

#What the workflow looks like

With the connection in place, producing a panel-ready CV becomes part of moving the candidate along rather than a separate errand:

1. Your recruiters and coordinators keep progressing candidates in Greenhouse as they do today.
2. The CV is rendered into your organisation's branded template — same template, same editor, same options as any other RemakeCV job.
3. The finished document returns to the candidate record, where the hiring manager and the interview panel find it.

The middle step is untouched, so anything your team already knows about RemakeCV still holds. See uploading a CV and reviewing and editing.

One thing worth raising early: whether the connection is held once centrally or made by each user individually. In-house teams often have strong opinions here, because it affects how permissions and audit trails line up on the ATS side. We settle it with you rather than choosing for you.

#Does the integration change the formatting?

No. Templates, editing, anonymisation, summaries and downloads behave the same whether a CV arrives over a connection or is dragged into the browser. An integration only governs the journey the file takes, which means adopting one never forces a review of your output.

Auto-anonymisation matters more to in-house teams than most — it is what lets you run a blind first sift without maintaining two versions of every CV by hand. It carries over untouched, as do candidate summaries. If your branded template does not exist yet, our team builds it to your design alongside the connection: see requesting a custom template.

#Building it yourself

Where you have internal engineering capacity and would rather own the connection, the public REST API exposes the processing, retrieval and template endpoints directly. See connecting RemakeCV to any ATS or internal system for what they cover.

#Which plan includes it?

It is included whichever plan you are on. See plans and pricing.

#Start the conversation

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