At Robin, our mission is to provide you with quick access to all candidates. In this article, we explain how we do this for Indeed, what the limitations are, and what data you can expect!

How many candidates are available?
≈ 1.2 million

How quickly do we load new CVs?
≈ 9 seconds

What data do we have available?

We have 2 labels: new candidate and updated information. A candidate labeled as new has never been seen on that platform before. A candidate with the label updated has been seen before, but one of the following points on their CV/profile has changed:

Results may differ when you run two seemingly identical searches (Robin vs Indeed). This can be attributed to several factors explained below:

Radius
Indeed uses a different central point for locations, which means that a candidate may appear to be twenty-one kilometers from location X in Robin, while Indeed shows them as nineteen kilometers away.

Search Method
Indeed uses standard "keywords" to search for candidates.

For example, searching for "baker" will yield candidates who have worked as pastry chefs, delivery people for a bakery, and even someone named Mirjam Baker who has never baked a bread roll.

If you are looking for a "technician," you may get maintenance technicians as well as candidates who have worked in customer service at KPN because they indicated in the job description that they managed technicians.

If you prefer this search method, leave the job title field blank in Robin and use the "keywords/skills" field instead.

CV Parsing
Sometimes, candidates do not appear in Robin because their CV parsing has failed. This usually happens if the candidate uploads an image in the CV field, making it impossible for us to read their work history, and therefore, we do not load the candidate in.