One great piece of advice an informal mentor gave me long ago is that there is no information in a rejection . That is to say that you cannot draw any conclusions about yourself or your interviewing technique or your skills or anything from the single accept==0 bit that you typically get back. There are so many reasons that a candidate might get rejected that have nothing to do with one's individual performance in th…
> there is no information in a rejection. The most helpful job interview I had was when the interviewer broke script and just leveled with me about how I wasn't presenting myself well. There was a shared connection (our alma mater) that must have convinced him to be straight with me instead of hiding how poorly I was doing behind a mask. The HR handbooks say that you should never let a candidate know why they were no…
Slightly odd question but: what if it's the opposite of this?
Interviews are almost never an issue.
I would like to think (and have been told so too) that I'm both technically sharp and knowledgeable enough, and can communicate well enough. I have a firm handshake, and thanks to the ability to happily dive into topics I read up on, I can speak confidently - both on hard facts, as well as my understanding or opinion of any technical matter in my field - for hours maybe, if not longer.
But getting the interview... is.. legitimately hard. Multiple people have said my resume is quite solid, but I rarely get through beyond the base round.
Would you have any tips for just the act of getting a foot in the door, so to say? I'm reasonably optimistic I can take it from there.
(Two things I can probably change - using customized CVs (and a cover letter, where applicable), and reaching out to employees/HR at the places I'm applying at. Though that honestly seems exhausting with so many applications...)