Earlier quoted context omitted.
If I were asked that question, my answer would be that obviously P != NP because the former doesn't have an N at the front. The pain of being tossed out onto the pavement would totally be worth it.
might get you bonus points. It's a clever answer.
Google's “Director of Engineering” Hiring Test
941–950 of 969 posts
Re: Google's “Director of Engineering” Hiring Test
#942Earlier quoted context omitted.
I can expand beyond 140 characters if you like. The OP claimed that in the past ten years, as a result of their hiring practices, Google's product output quality has noticeably declined, presumably as compared to the search product on which their name was made, and gmail, which they launched in 2004. And it's easy and fashionable to knock Google because maps is not as good as you remember it used to be, or because th…
It's still the case that other than search and ads, most of Google's biggest hits were acquired rather than the result of in-house initiatives (even Google Analytics, which is probably one of their more heavily-relied-on products, was acquired). Google doesn't hire people who will create stuff like Android; they hire people who can pass their interview process, and get new product and service lines mostly through acq…
Google (vs Alphabet) often acquires companies that have a seed of a useful product. Android for example was apparently not in a usable state when it was acquired. 99% of the creative work is making the thing actually work, not in having the prototype.
To say Google's own engineers didn't create Android because they didn't commit the very first line of code is doing them a disservice.
Re: Google's “Director of Engineering” Hiring Test
#943I am doing neither of those things. I said it was tempting, because it puts things I've read about G-WAN into perspective (the claims I saw some time back when I was shown a heads-up versus nginx were questionable, and it's an interesting data point). That's why it's an unrelated addendum, and it's completely unrelated to the blog post at all. I have no desire to discredit someone I have never met and whose name I do…
Please don't take any more HN threads into tangents of drama. I know it's annoying to be accused of something you don't feel you did, but this subthread is the kind of noise we all need to avoid here.
Re: Google's “Director of Engineering” Hiring Test
#944Re: Google's “Director of Engineering” Hiring Test
#945Re: Google's “Director of Engineering” Hiring Test
#946Earlier quoted context omitted.
> Why the hell would you ask someone at that level basic questions like fizz buzz? Because there are people applying for software engineering jobs that still can't answer those questions.
If you have a CS degree and cannot answer this type of question in your language of choice, you simply aren't ready for even a junior position in my opinion. This type of coding exercise can potentially answer more questions about the candidate in two minutes than 30 minutes of softball questions about the candidate's past experiences. I think that people who disagree simply haven't done much interviewing or haven't…
Absolutely. Last time I went through trying to hire people was about a year ago. Easily 90% of the applicants we saw were completely unqualified. You have to have a way to weed them out.
Re: Google's “Director of Engineering” Hiring Test
#947Earlier quoted context omitted.
I gather you didn't run this by your PR folks: > Particularly, when one side presents something that makes the other side look like a blithering idiot, the likelihood it's 100% accurate is, historically, "not great". I get that you are happy at Google, that you want to defend your employer. But implying the guy's a liar or a fool does not help. If anything, it makes me more likely to believe that Google has something…
Well, I mean, he's right: any time a story seems outrageous and unbelievable, it's often because it has been embellished at least somewhat. That doesn't mean it's completely false either, though.
Even if you're correct and he's merely saying something generically true about almost any concerning story, him saying it in the context of the post reads to me as a veiled accusation.
For example, suppose you posted an open-source project of yours here. If I were to comment, "Open-source projects are often half-finished, buggy messes," how would that seem? It is factually true; randomly looking at GitHub projects is enough to show that. But in context, it's an unkind thing to say because encourages people to look at your project as one of them.
Re: Google's “Director of Engineering” Hiring Test
#948Earlier quoted context omitted.
Sorry, I only saw your comment now. They were asking stuff like finding patterns (like in IQ tests). Then they also had ones where you had to read text and then say what you would do with it based on certain requirements. You couldn't skip questions so I spent way too much time on the number ones. I cannot obviously tell you the exact specifics because of the NDA.
I am curious what your opinion is of these? I personally find this practice loathsome. Was this something that happened after speaking to a human or was this the initial screening?
Maybe I dodged a bullet there and Amazon would have been a bad place to end up anyway.
Re: Google's “Director of Engineering” Hiring Test
#949Re: Google's “Director of Engineering” Hiring Test
#950Earlier quoted context omitted.
I am curious what your opinion is of these? I personally find this practice loathsome. Was this something that happened after speaking to a human or was this the initial screening?
It was the initial screening and I was very upset that they rejected me since I did (very) well on the coding part but poorly on that reasoning test. If I have a good GPA at a Uni with a degree in Computer Science, then they can certainly assume that I can reason and there is no need to put me through a very strictly timed "IQ test." Maybe I dodged a bullet there and Amazon would have been a bad place to end up anywa…