Skip to main content
All Collections
Studentjob
Studentjob
Updated over a week ago

At Robin, our mission is to provide you with access to all candidates as quickly as possible. In this article, we describe how we do this for Studentjob, what the limitations are, and what data you can expect!

🔢 [Jobboard] in Numbers

How many candidates are available?
≈ 19.5k

How quickly do we load new CVs?
≈ 9 seconds

What data do we have available?

  • Personal information

  • Experience

  • Education

  • Certifications

  • Skills

  • Languages

  • Driver’s license

  • Hobbies

  • References

🆕 Recently Updated

We have two labels: new candidate and updated information. For the "new candidate" label, we have never seen this candidate on that platform before. For the "updated information" label, we have seen the candidate before, but one of the following points on the CV/profile has changed:

  • Personal information

  • Experience

  • Education

  • Certifications

  • Skills

  • Languages

💡 Good to Know!

Results may differ when you create seemingly identical searches (Robin vs. Studentjob). This has several causes, which we explain here:

  • Radius
    Studentjob uses a different center point for a location, so a candidate might be 21 kilometers from location X according to Robin, while the same candidate is listed as 19 kilometers from location X on Studentjob.

  • Search Method
    Studentjob uses "keywords" by default to search for candidates.

    For example, if we use "baker," you may get results for candidates who have worked as pastry chefs, those who delivered for Leen Bakker, and even Mirjam Bakker, who has never baked a roll.

    If you’re looking for a "technician," you’ll get maintenance technicians, as well as candidates who worked in customer service at KPN because they indicated they managed technicians in their job description.

    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 may not show up in Robin because their CV parsing has failed. This usually happens when the candidate uploads an image in the CV field, preventing us from reading their work history, and thus we do not load the candidate.

Did this answer your question?