vendor of recruitment software 2024 INTEGRATION & PLUG-IN

PLUG-­IN_ VACANCIES ON EVERY CUSTOMER SITE

A vendor of recruitment software kept running into the same thing: every customer wanted their vacancies on their own website, and every time that became bespoke work. We built one plug-in that solves it, using the shortcomings of the existing plug-ins as the requirements list.

PLUG-IN VACANCIES ON EVERY CUSTOMER SITE
Brief
PLUG-IN ON AN OWN API
Audience
THE VENDOR'S CUSTOMERS
Built on
EXISTING API
Lead time
3 MONTHS
<problem_/>

WHAT WAS STUCK.

The same problem per customer, solved from scratch every time.

The vacancies lived in the vendor's system; the customer's site lived somewhere else. Every integration was built separately, by varying parties, with varying results.

Plug-ins existed for comparable systems, so that is where we started: what can they do, and where do people get stuck. The answer was short. They install easily, but you cannot edit a vacancy's text or URL, there are no fields for search visibility and social sharing, and the filters do not count how many results sit behind them.

That last one looks like a detail. It is the difference between a filter someone uses and a filter someone tries once.

WHAT THE EXISTING PLUG-INS LACKED

  • Vacancy text and URL not editable
  • No fields for search visibility or social sharing
  • No counts per filter
  • No handling of caching plug-ins
<approach_/>

WHAT WE BUILT.

What the standard does, plus what the standard does not.

The plug-in pulls vacancies from the existing API and places them in the customer's site: an overview, a detail page, filters and a block for the home page. Setup is one key per domain, so a customer sees their own vacancies and not somebody else's.

On top of that sits what the other plug-ins did not have. A vacancy URL is editable, there are fields for the title and description in search results and for the social sharing card, and the filters show how many vacancies sit behind each one.

Vacancy URLs land in the sitemap automatically and are submitted to Google's job search. And because nearly every site runs a caching plug-in, we deliberately handled what happens when a page comes out of cache just after a vacancy has been withdrawn.

WHAT WAS DELIVERED

  • Overview, detail page and filters
  • Home page block through a short code
  • API key per domain
  • Editable URL, title and description per vacancy
  • Fields for social sharing
  • Counts per filter and per page
  • Sitemap entries and Google job search submission
  • Nightly resynchronisation when the link fails
<result_/>

WHAT IT DELIVERED.

Since the plug-in went into use at customers.

1
plug-in for every customer
0
bespoke work per site
4
gaps in the standard closed
3 mo
lead time

The brief was: at least as good as what already exists. It is that, and better on four points.

— Product manager, recruitment software vendor
<next_step/>

WANT SOMETHING SIMILAR_

Half an hour on the phone is enough for an honest estimate. You will hear what it costs and how long it takes — including if the answer is that you are better off doing something else.