3 ms·
I had a really bizarre interview recently where, after the initial recruiter phone screen, I was rejected based on an in-person half-hour very simplistic paired
by kbd 11y ago
I had a really bizarre interview recently where, after the initial recruiter phone screen, I was rejected based on an in-person half-hour very simplistic paired coding exercise, only met with one person, and wasn't asked about my (imo very strong) resume once. I must have said something foolish at some point, which is on me, but the point is: interviews can be hit or miss. Fortunately you only need one hit.
- kybernetikos 11y agoIt does sound like a bad interview experience, but I will say that I have very little interest in what a candidate writes on their resume. There are candidates with amazing resumes that can't do much and people without much that they can talk about publicly that are amazing. If the interview is low signal, the resume is even worse.
- kbd 11y ago> There are candidates with amazing resumes that can't do much... That's certainly true. I understand not taking resumes at face value; I've interviewed developers (and DBAs) and I'd always pour over their resumes to look for both padding and meat to ask about. It can be insightful to ask about a big accomplishment someone claims as their own only to find out that they only actually affected a small part of it. However, In this case I'm honestly not sure whether my interviewer even read my resume.
- fapjacks 11y agoInteresting. I wonder if we interviewed at the same place! I had a very similar experience over a year ago. At least I was told they only select one person from the group to move forward from the pair-programming task, which I thought was weird, but hey, it's their company.