Connecting Teamtailor

#How the integration is set up

1. 1

   Describe your hiring process to us

   Email support@remakecv.com with your organisation name and a short picture of how candidates move today — who prepares a CV for review, and whose desk it lands on afterwards.

2. 2

   Arrange API access on your Teamtailor account

   Your own administrator, or Teamtailor's support team, decides what credentials can be issued and on what terms. Their answer sets the boundaries of what we build against.

3. 3

   Get the credentials to us safely

   We will tell you which channel to use. Anything with reach into applicant records deserves password-grade handling — not a plain email, and not a thread that half the department is copied on.

4. 4

   We build it and switch it on

   Our team writes the connection against Teamtailor's API and enables it for your organisation. The controls surface in your RemakeCV dashboard; recruiters and hiring managers install nothing.

#What the workflow looks like

With the connection running, the branded document is produced in the course of moving someone forward:

1. Your team screens and progresses candidates in Teamtailor as they already do.
2. The CV is built into your organisation's template — same template, same editor, same options as every other RemakeCV job.
3. The finished file returns to the candidate's record, where whoever is making the decision opens it.

See uploading a CV and reviewing and editing for what happens in the middle.

#Carrying the brand past the application

Teamtailor tends to be chosen by in-house talent teams who take how their organisation appears to candidates seriously — a careers page written in the company's own voice, an application that feels considered rather than transactional. Then the shortlist reaches the hiring manager as whatever the candidates happened to send: one PDF exported from a design tool, one document last saved in 2019, one file someone in the team retyped by hand at eleven at night.

Recruitment agencies solved that years ago, because a scruffy CV loses them the placement. The reasoning holds just as well inside a company. A house document keeps the same sections in the same order for every candidate, so an interview panel is weighing experience rather than layout, and it puts your organisation's mark on the page that the decision is actually made from. It also travels: a CV forwarded to a second interviewer, a board paper, an offer discussion. Consistency there is worth as much internally as polish is externally.

Where the connection is held — once for the whole organisation, or separately by each user — is decided with you rather than for you. It affects how permissions and audit trails line up on the Teamtailor side, and in-house teams usually have a view.

#Does the integration change the formatting?

No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over the connection or is dragged into a browser window. The integration governs transport only, so switching it on never obliges you to revisit your output.

Auto-anonymisation comes across unchanged, which matters if you run a blind first sift, as do candidate summaries. If the branded document itself does not exist yet, that is designed alongside the integration — our team builds the template to your brand, and the connection then delivers it. See requesting a custom template.

#Building it yourself

If you have engineers who would rather own this, the public REST API exposes the processing, retrieval and template endpoints directly, letting you wire RemakeCV into Teamtailor on your own timetable. Connecting RemakeCV to any ATS or internal system covers what those endpoints do.

#Which plan includes it?

Business and Enterprise both include integrations — see plans and pricing.

#Start the conversation

Email support@remakecv.com with Teamtailor and your organisation name. We will confirm what the integration can do on your account, what we need from you, and how it will sit in your talent team's week.