Live data from Hacker News

Max Howell's take on getting rejected by Google

quora.com

71–73 of 73 posts

Re: Max Howell's take on getting rejected by Google

#71
post #33
post #25

Earlier quoted context omitted.

I would have written the same. I have no idea what Google understands by "inverting a binary tree", but to me it looks this. "Recursively swap left with right." Now just convert that to an inferior language, like java or python, so they can understand it.

If you are faced with a question like this in a Google interview, and you simply state the answer above right away, you are only solving part of the problem. A Google interviewer expects you to ask questions and clarify any simplifying assumptions you may have made. For eg: Are you assuming right at the beginning that the entire tree fits in memory? If so, Google interviewers expect you to clarify that at the beginni…

No, this is not what happened at my google interview. Some poor HR guy, without any tech background read questions from his screen, and tried to match my answers with his answers. When I gave a too good answer on something he said "no wrong, next question". Ridiculous interviews. Twice. That's why I can relate to Max Howell.

Re: Max Howell's take on getting rejected by Google

#72
post #46

Earlier quoted context omitted.

Be careful with binary assessments of whether someone ‘is a dick or is not a dick.’ The linked article draws more differences than similarities as far as I can tell. Max Howell readily admits weakness before pride. He brags outwardly at the end of his message, which was a little distasteful, but it was after he widely incriminated the project he is bragging about. The linked article describes a very different type of…

I'm not assessing anything, just quoting himself.

Well, you did say, in your own words: "No, Google shouldn't have hired him, and he made it very clear why..."

That seems like a pretty clear assessment to me.

Re: Max Howell's take on getting rejected by Google

#73
post #71
post #33

Earlier quoted context omitted.

If you are faced with a question like this in a Google interview, and you simply state the answer above right away, you are only solving part of the problem. A Google interviewer expects you to ask questions and clarify any simplifying assumptions you may have made. For eg: Are you assuming right at the beginning that the entire tree fits in memory? If so, Google interviewers expect you to clarify that at the beginni…

No, this is not what happened at my google interview. Some poor HR guy, without any tech background read questions from his screen, and tried to match my answers with his answers. When I gave a too good answer on something he said "no wrong, next question". Ridiculous interviews. Twice. That's why I can relate to Max Howell.

That's just the HR screen. The actual interviews are not like that.
Post reply on HN