21–30 of 683 posts
Interviewing is stressful and all, but if the guy's reaction to not getting hired is to flame on twitter, not hiring might've been the right call.
I think everyone knows that this is not a problem exclusive to Google.
FWIW, I find Facebook turning down Jan Koum in 2009 and then spending $19B to acquire his company even more ironic.
Humorous answer: Maybe I can't invert a tree, but watch me flip this table. Serious answer: Companies that pull this crap deserve to starve and die.
What specifically are you objecting to? That specific question? Writing code on a whiteboard? How would you interview software engineering candidates?
Interviewing seems broken to me too. I have spent the last few months trying to get a job out of college and everyone seems to be interested in how well you can regurgitate CS fundamentals. They are seemingly less interested in seeing how you solve problems and work through the process of software. I would be more than happy to see this process change, I am just not sure what it entails.
Humorous answer: Maybe I can't invert a tree, but watch me flip this table. Serious answer: Companies that pull this crap deserve to starve and die.
What specifically are you objecting to? That specific question? Writing code on a whiteboard? How would you interview software engineering candidates?
The main problem with interviews [imo] is it grabs stuff the interviewer is familiar with and throws it at the person in the more stressful position of being the interviewee. Its also [often] a very non-standard way of communicating. I don't know about you but all of my communication is via text or graphic, not whiteboard.
And, honestly, do you care more about the fact they can invert a binary tree from memory? Or that they can learn to in the next hour and implement it?
My guess is for 90% of jobs, its the second.
Humorous answer: Maybe I can't invert a tree, but watch me flip this table. Serious answer: Companies that pull this crap deserve to starve and die.
What specifically are you objecting to? That specific question? Writing code on a whiteboard? How would you interview software engineering candidates?
Would love to hear people's thoughts and feedback!
Was it really because he couldn't do the problem, or was it that he didn't handle himself well in the interview? At two different interviews I was given logic puzzles just so they could watch how I went about trying to solve them.
> At two different interviews I was given logic puzzles just so they could watch how I went about trying to solve them. That's usually what they say, but I've found that if you don't solve the puzzles, you don't get hired ever.
Interviewing is stressful and all, but if the guy's reaction to not getting hired is to flame on twitter, not hiring might've been the right call.
On the other hand, if it was a complex and reasoned decision that he's summarizing badly, then yeah, good call on their part.
Context is king here, and we have little.