Re:Google Tech Dev Guide
by dbt00 on Wednesday December 19, 2018 @12:22AM
(#18713248)
As someone who's done a ton of tech interviewing for a blue chip silicon valley firm, viewing this as a homework problem to which there is one correct answer is exactly not what I'm looking for. I want to see your problem solving skills and I'm curious about your knowledge base, but if you don't know any of the specific techniques and/or don't get to the specific optimal solution I'm looking for I really don't give a shit.
[ Parent
| on HN ]
Re:Google Tech Dev Guide
by SmirkingRevenge on Wednesday December 19, 2018 @01:11AM
(#18713479)
This is the reassuring story every interviewer has to tell themselves to feel good about their decisions... and its the story every interview consultant tells the tech firm. But I tend to think its probably a just-so story, most of the time. All this work is done in the tech world to eliminate the subjectivity from interviews - this is how the subjectivity is re-introduced through the back door.
> this is how the subjectivity is re-introduced through the back door.
Exactly. You'd think that the large tech companies would insert "mystery shopper" candidates into the pipeline to uncover and measure the objectivity/subjectivity/bias of the interview process.
Re:Google Tech Dev Guide
by jakebasile on Wednesday December 19, 2018 @12:39AM
(#18713327)
Everyone says "it's not about the solution but how you go about solving it", but it's never been my experience as an interviewee. Every time I've been interviewed with one of these godawful trivia questions I've been denied even though I do my best to work with the interviewer to solve it. On the rare occasion I get feedback it has been because I didn't solve the problem optimally or some other nonsense.