Discover talent experience with hard skills in a second
Every tech job description declares minimal experience with certain skill(s), that would be necessary to take a position.
Looking for a Python developer with 3 years of experience with Django.
Opportunity for a Node developer who has worked with NestJs and React for 2 years.
In order to check it, for each particular resume, recruiters have to calculate the years of work spent in each relevant job position. It’s boring, time-consuming and error-prone as skills can be forgotten or don’t match reality in different ways.
Would you like to know candidates YOE (Years-Of-Experience) with hard skills in less than a second?
New feature: skill heatmaps
When searching for talent on DevScanr, recruiters can immediately see how many years the candidate has worked with the required technologies. We call it the Skill Heatmap (after the chart category).
For example, you are looking for:
- Python developer with 5 years of experience (with the language)
- Minimum 3 years with Django framework
- Knowledgeable with PostgreSQL, FastAPI and Asyncio
- Docker and Tornado technologies are good to have.
The screenshot below is from a search on DevScanr. On the left you can see the defined filters, and on the right – a list of search results.
The heatmap (purple rectangles, standing for half of a year) demonstrates that Betty has been working with Python and Django since 2021. For our requirements, she may not be the best fit as we are looking for someone with 5+ years and it’s currently 2024.
Talent Search on DevScanr: showing years of experience with matching skills.
The next profile in the list is Vivian. She has been working with Python and Django for over 5 years. Besides, Vivian looks to be familiar with Docker, PostgreSQL, and FastAPI. Nice catch!
Talent Search on DevScanr: showing years of experience with matching skills.
New feature: not found skills
To help recruiters evaluate candidates faster, we added one more section to the profile card – “Not found skills”. A vacancy may have multiple requirements, and, in such cases, it’s normal to evaluate talent that match most of the criteria, but not necessarily 100% of them. Seeing a concise list of what is missing helps to make quicker decisions about profiles.
In the previous example, Tornado is not part of Vivian’s hard skills known to the platform. Per our job description, Tornado is a good-to-have skill, so we should still consider her profile.