3 ms·
Although this is welcome to hear, it's not something a candidate can count on reliably nor something they can really control. After all, a candidate can come of
by decafninja 6y ago
Although this is welcome to hear, it's not something a candidate can count on reliably nor something they can really control. After all, a candidate can come off as likeable to one interviewer and unlikeable to another.
Versus just being able ace through leetcode problems - that's a more objective criteria a candidate has more control over.
Personal anecdote. I interviewed at a FAANG, got rejected. They actually offered feedback, and one of the key reasons I apparently got rejected was that "I asked too many (clarifying) questions" about the leetcode problem.
Fast forward a year, I retry. I take the above feedback to heart, and refrain from asking too many questions. I get rejected again, and given feedback. One of the reasons given? "I asked too few questions".
- alboy 6y agoClearly they want you to demonstrate a working knowledge of binary search.
- Rapzid 6y agoYeah, but you gotta sort your shit out first.
- KwisatzHaderack 6y ago> candidate can come off as likeable to one interviewer and unlikeable to another. > I apparently got rejected was that "I asked too many (clarifying) questions" about the leetcode problem. > I get rejected again, and given feedback. One of the reasons given? "I asked too few questions". It sounds like they didn't like you _personally_. If the rejection reason wasn't due to technical or behavioral mismatch but a fake reason like the ones above, it's the often the problematic "Airport test" (ie. They don't want to be stuck in an airport with you"reason). And to be clear, I think it's wrong to reject candidates because you personally can't think of "being friends" with them. It's unfair to both the candidate, but also the company as it misses out on great engineers.