Live data from Hacker News

Why Google's hiring process is broken

blog.teambox.com

1–10 of 177 posts

Re: Why Google's hiring process is broken

#4
This "Google can't do design" meme is really getting old, imho. At best, this is a story about one recruiter in a giant company not doing his job well in matching the requirements with the skill set of the candidate.

It is easy to conclude preconceived notions.

Re: Why Google's hiring process is broken

#5
It doesn't take a designer or user experience expert to note that google products lack consistency and don't interopt with each other very well. I think this stems from larger issues that are much harder to fix, or through 20% projects and acquisitions that were developed independently of a common set of standards. I doubt they are ignoring it.

Perhaps the lack of a "Google standard" enables eager developers to create amazing new products, like Gmail.

Re: Why Google's hiring process is broken

#7

This "Google can't do design" meme is really getting old, imho. At best, this is a story about one recruiter in a giant company not doing his job well in matching the requirements with the skill set of the candidate. It is easy to conclude preconceived notions.

It's not that, it's that Google's candidate referral or search is really poorly targeted when they contact a candidate. They've talked me twice, about the same job that's really not a good fit for me. They talked to him, and totally missed the designer thing and went straight into CS101.

Re: Why Google's hiring process is broken

#9
I recently talked to a colleague who was hired as a developer by Google.

He went through 3 rounds of "hiring committees".

3 different committees to make a developer hire is obviously broken. The ability to evaluate culture and skill fit should be possible with a hiring manager and a few prospective peers.

Post reply on HN