Live data from Hacker News

Why I Don’t Talk to Google Recruiters

yegor256.com

541–550 of 674 posts

Re: Why I Don’t Talk to Google Recruiters

#541
post #463

The other way to respond: thanks, I'm interested. Alternatively: no thanks, I'm not interested. Recruiters aren't monkeys or slaves. This post is arrogant and rude.

THANK YOU. I'm concerned I had to scroll down this far to find a comment that calls out the author on this point.

Re: Why I Don’t Talk to Google Recruiters

#542

There is no point in giving me binary-tree-traversing questions; I don't know those answers and will never be interested in learning them. Let's presume this is out of preference and not ability. It's a pretty basic concept. If your preference stops you from learning something as basic as this as a programmer, then it doesn't seem likely that you will be motivated to keep up with even more abstruse concepts. Nearly e…

> Nearly every programmer nowadays knows that naive string concatenation is inefficient, and so they should use a stream or something like that. You and I live in different worlds, or have vastly different definitions of 'programmer.'

Yeah, I think he meant scipter.

Re: Why I Don’t Talk to Google Recruiters

#544

The reason I won't work at Google is because Google is incapable of hiring the engineers I want to work with. It's not a matter of whether I could pass that interview; it is whether I want to work with the code of people who can pass that interview. Whether I want to get code reviews from people who can pass that interview. Whether I want to rely on the code of people who can pass the interview not to break down in i…

amen!

Re: Why I Don’t Talk to Google Recruiters

#546
post #356
post #172

Earlier quoted context omitted.

> I'd rather hire someone who knows exactly why it's O(n^2) "How do we satisfy unlimited wants with limited resources?" - economics to the rescue again. Everyone would love to hire Linus Torvalds for that matter, but there are plenty of programming jobs where you don't really need to, or don't want to, or can't spend that kind of money. There are plenty of useful, productive positions for people who aren't up on thei…

I would not hire Linus Torvalds. For all his technical capability (which I've followed as a linux and git user for some 25 years now) many of his externally visible statements are not acceptable for any modern workplace (this has been discussed a number of times, I know people have differing opinions, but if Torvalds worked at a modern corporation with a real HR department, his words would get him in trouble.)

[deleted]

Re: Why I Don’t Talk to Google Recruiters

#547
post #472

Earlier quoted context omitted.

I get between 30 and 50 a month and all I really did was setup a linked in profile.

Incredible--would you mind sending me your LI profile (privately of course, email in my HN profile)? I'd love to see an example of a profile that generates that much interest, even if it's mostly low signal.

It's honestly not that incredible.

Just follow all the guidelines that LinkedIn gives you, so that your profile is an "all-star" and make sure you have a bunch of connections (500+).

An email a day is fairly normal at least for SF engineers.

Re: Why I Don’t Talk to Google Recruiters

#548

I'm wondering what was Google interview for Guido van Rossum?

Exactly! I'm sure Rob Pike and Guido didn't go through the typical BS.

What's curious too is that I've never heard either of them comment on their individual interviews at Google. Maybe Google made them sign a gag order.

My hunch is Pike & Guido were approached directly by management at Google.

Re: Why I Don’t Talk to Google Recruiters

#549
post #141

> some programmers who didn't know a thing about my profile asked me to invent some algorithms on a white board for almost four hours. Yep. Did the phone interview after weeks of back-and-forth, told them what I was interested in, told them I was only interested in working on such-and-such, then they drop me in the standard "write memcpy for us" interview. The last interview was some dude with a weirdly confrontation…

> The last interview was some dude with a weirdly confrontational attitude who wrote some assembly on the board and said "Find the bug. It took us 3 months."

Not great, but there is a world of difference between, on the one hand: (1) there is a bug; (2) it's in these 30 lines of code, and on the other hand: something's wrong, and the problem might be somewhere in your two million lines of code.

Re: Why I Don’t Talk to Google Recruiters

#550
"I do realize that these are multi-billion-dollar companies, the best in the industry, and I'm nothing compared to them."

Making a lot of $ as a company does not automatically mean that every individual working for the company is "the best in the industry". And the more they hire, the more this will be true. I have worked with people who ended up working for Google and they were certainly not the best developers I have worked with. They were good but not great. Also, to make a lot of $ as a company you need to have a good business. You don't need top developers. Just good enough developers. With a few really good ones mixed in to take care of the core components. A great business idea with OK developers beats a bad business idea with top developers every time.

Post reply on HN