DEV Community

Discussion on: 💡 How to waste less time for interviews at hiring

Collapse
catriel profile image
Catriel Lopez

The situation is worsened by the fact that CVs often do not contain enough information to compare candidates with each other without performing a time-consuming interview. For example, if I see “PostgreSQL” in CV, I cannot understand the actual level of the candidate's skills with Postgres: may he write simple SELECT queries or he may write complex queries with functional indexes. It is a common situation when good developers have very bad CVs.

I may be or may not be guilty of this. Do you have any recommendations on how to avoid this issue? I feel like expanding each skill into a detailed explanation would make my CV too long for a recruiter to read..

Collapse
roadmaps profile image
Roadmaps master Author

Recruter may see aggregated data, like matched for 84%. And it's enough to invite for interview