|
|
|
|
|
by ravenstine
2771 days ago
|
|
As an interviewee, I'm not interested in only answering questions that are easily answered by my resume so you can tick boxes. If I can't get a sense on the company spirit and you aren't going to treat me like a human being over the phone, why would I want to work for you when there are better companies looking for culture fits? The sentiment is mutual. |
|
We can talk about how much we hate doing anything over a voice call, but it’s ludicrous to think that interviewers should never ask a question that could be answered by reading the résumé.
For example, we have some Scala code in our analytics stack at my work. I have worked with it, but I avoid touching it and honestly, I am not a Scala programmer.
I have been at this company for 3 1/2 years, on this team for one year. Some people in such a situation will say that they have 3 1/2 years of Scala, an outright fabrication.
Others will say that they have 1 year of Scala, which is kinda-sorta true on some bad-faith, you-can’t-call-me-a-liar planet.
If I put Scala on a résumé, I would totally expect someone to drill down and find out if I was using it every day, whether I was writing big chunks of code or just fixing the odd bug and so on.
I wouldn’t highlight Scala, personally, but what if I put JavaScript down? Given how tenuous Scala might be, wouldn’t an interviewer want to know if my JavaScript experience is “real” or not? I know that I use JS almost every day and Scala almost never, but my interviewer doesn’t know that I have such scruples, so they are supposed to ask me questions about JavaScript that my résumé answers, then drill down and corroborate.