> The very first two things you do with a resume are match up the list of technical skills with the list of tech in your position requirements, and check the education requirement. That's why those two go at the top.
That is what you do. The very first thing I check is where they worked before and how they describe what they did there.
In the case of juniors, that’s replaced with looking at basically anything they did and how they describe it.
By the time the CV gets to my desk the keyword matching is already done.
While the resume isn’t necessarily bad, it screams to me that the candidate didn’t even bother to look at, or didn’t care how a CV is normally structured/laid out before handing theirs in.
It’s not necessarily bad, but when looking through a bunch of them you don’t really want to adjust your mental parsing model for every resume, so barring anything else about it that stands out, you just mentally dismiss it.
To be fair, this is something I’ve seen more from people just leaving school.
That is what you do. The very first thing I check is where they worked before and how they describe what they did there.
In the case of juniors, that’s replaced with looking at basically anything they did and how they describe it.
By the time the CV gets to my desk the keyword matching is already done.
While the resume isn’t necessarily bad, it screams to me that the candidate didn’t even bother to look at, or didn’t care how a CV is normally structured/laid out before handing theirs in.
It’s not necessarily bad, but when looking through a bunch of them you don’t really want to adjust your mental parsing model for every resume, so barring anything else about it that stands out, you just mentally dismiss it.
To be fair, this is something I’ve seen more from people just leaving school.