Job Search API & Beta Testing Update

Job Search API

In this sprint we created the Job Search API. This is a huge step, enabling candidates to discover their next job opportunity by searching and filtering the available jobs on the platform.

In this release, the job API is headless, meaning that it doesn't have a user interface to consume the data and display it to the user. However, that user interface will be enabled by this work and it will be coming shortly.

Key features

The key features of this release include:

Job Search API: This is the backend API where candidates can search and explore available positions. The can filter the jobs across many features such as location, salary, type of work etc... and find an opportunity which is perfect for them.

Database: The database has been designed to enable candidates to efficiently filter positions across many criteria. This will also enable recruiters to annotate job requisitions with rich, detailed information when they create jobs, allowing them to find the most suitable candidates for the role.

Next steps

Naturally, the next stage of development is going to focus on making this API available to our users. So we will be focusing on the development of the user interface for the job board in our next sprint.

Feedback from the previous release

We would like to start by saying a massive thank you to everyone that took the time to review the launch of the website and provide us with some feedback. The feedback we received was super insightful and will help us develop the best version of our product. Some of the most valuable insights we received include:

Target audience clarity: The landing page was unclear about whether it was aimed at recruiters or candidates, causing some confusion.

Clickable elements: Certain elements on the page look like they should be clickable, however they were actually only for decoration! This made it unclear which parts were interactive and which were for display.

Call-to-Action on the homepage: The main CTA did not stand out as much as it could. In fact, a few of you didn't even notice it was there at all, in and amongst all the other decorative (and not clickable) element. This is a shame and we’ll focus on improving its visibility and effectiveness.

All of your feedback has been taken on board and we will be addressing some of these issues in a future release.