Career Pages

Integration with career pages is a key functionality that you need to resolve when transitioning to a new ATS.

The ideal option is a solution via API, but this means an internal project on your side, which depending on the availability of your resources may take a relatively long time. Therefore, we also offer several integration options so that you can connect the pages as quickly as possible and complete the API integration project later.

Response Form

You replace the link on the "I am interested" button on your career pages with a link to the position response form.

Advantages:

• simple implementation
• you can have different forms for different positions

Disadvantages:

• does not solve the transfer of positions to career pages

You can also specify that the candidate should be recorded with a specific source and enforce the language of control elements in the response form (learn more in this article about response forms)

iframe

In the "Publication channels" settings, you will find data for the iframe (see image below), which your programmers just need to copy into the code for your career pages. In the settings, you can also configure the iframe (change filter display, add custom filters, add CSS file)

Due to its simplicity of implementation, but significant technical limitations, it is more suitable for quick page connection before a full integration, e.g. using API. From a long-term perspective, this is not a recommended connection principle.

Advantages:

• practically instant implementation without the need for any major additional programming
• also solves automatic transfer of positions to career pages and recording candidates into ATS Recruitis to the relevant positions

Disadvantages:

• does not solve more complex position filtering logic for listing
• has limited graphic processing options
• has limited navigation logic
• general disadvantages of iframe
  • content is on a different page than the one you are linking from
  • shortcomings for organic search and SEO

Example of iframe output without applied CSS on your side:

API

You can find the API integration documentation here.

For initial understanding of the basic logic, you will primarily need these endpoints:

• "jobs" (GET)
  • i.e. listing of open positions
  • this listing needs to be filtered by the selected publication channel you want to display on career pages
  • link to the relevant part of the API documentation

• "answers" (POST)
  • i.e. endpoint for recording candidate responses to specific positions
  • link to the relevant part of the API documentation

• "candidates" (POST)
  • i.e. endpoint for recording candidate responses without a position
  • link to the relevant part of the API documentation

Advantages:

• The final solution (appearance, logic, etc.) is entirely in your hands and is not limited by anything

Disadvantages:

• integration speed depends on the availability of your internal resources (mainly programmers)
• integration takes longer than the simple methods mentioned above

Combination of API with Response Form in iframe

From an implementation perspective, one of the most challenging areas is getting the response form working. If you do not have significant requirements for changing the appearance of the response form from ATS Recruitis, this can be achieved relatively easily by integrating the response form from ATS Recruitis embedded in an iframe and formatted using your own CSS file. The rest of the logic - e.g. loading positions, content of individual positions, etc. - is done via API.

Example syntax for adding CSS to the response form for iframe purposes: https://app.recruitis.io/answer/form/kQp4i4HQ8bXFR1SM5sJiU7hu7P6Kl5Eq/cs?css=https://test.recruitis.io/all.css

For proper functioning, we need to allow your domain where the CSS is stored in ATS Recruitis settings