Connecting Firefish

#The CV is the last mile of your candidate marketing

Firefish tends to be chosen by small and mid-sized UK agencies that take attraction seriously — the ones running their own careers site, their own campaigns and their own tone of voice rather than leaving a job board to speak for them. If that describes your agency, you have already accepted the argument this page rests on: how something is presented changes how it is received.

The client-facing CV is where that argument gets its final test. Everything upstream is aimed at the candidate. The formatted CV is aimed at the person deciding whether to interview, and it is often the only artefact of yours they open all week. An agency that has spent real money looking deliberate everywhere else has an obvious reason not to send that document out in whatever shape the candidate happened to write it in.

#What it looks like on the desk

Agencies of this size rarely have a spare person for admin, so what a connection buys you is that formatting stops being a separate errand:

1. A consultant works the candidate in Firefish as they always have.
2. The CV passes through RemakeCV and comes back in your house design, with the same editor and the same options your team already uses in the browser.
3. The branded version is filed against the candidate, ready for the client.

The middle step is simply the product — see uploading a CV and reviewing and editing. What goes away is the manual handling either side of it.

#Getting it built for your agency

1. 1

   Tell us how your desk runs

   Email support@remakecv.com with your agency name and a few lines on where CVs sit today, who formats them, and where the branded copy has to end up.

2. 2

   Ask Firefish for API access on your account

   Their support team decides what credentials your account can be issued and on what terms. Their answer is what we build against.

3. 3

   Hand the credentials over on a channel that is safe

   We will point you at one. Anything that reaches candidate data deserves the care you would give a password — not plain email, and not left in a thread someone forwards on months later.

4. 4

   We build it, then turn it on

   Our team writes the implementation and enables it for your company, after which the relevant controls appear in your RemakeCV dashboard. Nobody installs anything and there is no plug-in to keep current, which matters when there is no in-house IT to look after it.

We will ask early whether the connection should be held once for the whole agency or made by each consultant individually. Small teams usually prefer the former, but it is your call rather than our default. Security and sub-processors covers how credentials and candidate data are held.

#Formatting is unaffected

Nothing about the output shifts because a CV arrived over a connection instead of by drag and drop. The template, the editor, auto-anonymisation, candidate summaries and template variants all behave as they do now. A connection settles how the file travels and has no say in what it looks like, so taking one on never means reopening a design your clients already recognise.

If that design does not exist yet, our team builds it to your brand — see requesting a custom template. Agencies with strong attraction branding usually want the CV to sit alongside the rest of it rather than merely near it, and this is the point at which to say so.

#Or wire it up yourself

Where you have a developer — in-house, or the freelancer who looks after your website — the public REST API hands them the processing, retrieval and template endpoints directly. Connecting RemakeCV to any ATS or internal system sets out what those cover.

#Plans, and what happens next

Business and Enterprise subscriptions both include integrations, so nothing here is held back for the larger plan — see plans and pricing. Email support@remakecv.com with Firefish and your agency name, and we will come back to you on what the connection can do on your account, what we need from you, and how it will feel to the consultants using it.