Live data from Hacker News

Why I Don’t Talk to Google Recruiters

yegor256.com

1–10 of 674 posts

Re: Why I Don’t Talk to Google Recruiters

#2
It's like this person was inside my head. I agree basically word for word and do the same thing, cannot be bothered anymore, like he suggests, if they are telling him his profile is so great and 'impressive' why must they schedule a regular interview and on a whim reject him. Waste of time.

Re: Why I Don’t Talk to Google Recruiters

#4
Its the London Cabbie(1) method. They're not looking to fill any particular role. They're just looking for smart people (for the value of smart that fits their biases).

They just need as many warm bodies as possible to ram through their test so that a few trickle out the bottom of the funnel to keep the ranks from shrinking. If too many started getting hired, they'd add competitive basket weaving to the skillset if that's what it took to balance it.

(1)http://news.nationalgeographic.com/news/special-features/201...

Re: Why I Don’t Talk to Google Recruiters

#5

I wonder how high up you have to get before the top-tier companies are willing to make an exception to their standard interview process. Director? VP?

I was exempted and moved all the way to the last round of interviews. The compensation was even negotiated before hand. I am a regular engineer with three years experience.

Re: Why I Don’t Talk to Google Recruiters

#6
Yeah it kind of sucks, but from Google's perspective it's absolutely necessary. So many people talk the talk, run a blog, have a neat looking resume/website/GitHub and just cannot perform. Unless you're an undisputed rockstar in a specific area and they're hiring exactly for your expertise you can't expect anything else. It's a huge waste of time to custom tailor to each candidate when 90% won't receive an offer.

> 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.

Take an afternoon and skim Cracking the Coding Interview before applying. There's no reason a competent engineer shouldn't be able to solve questions like that. You know exactly what's expected of you, show some initiative.

Re: Why I Don’t Talk to Google Recruiters

#7
The worst part for me is how long the process takes, and how much time is invested for an interview process where the success rate is so low.

My recent experience with AMZN was:

- get contacted by recruiter, schedule a call with recruiter a few days later

- take a take-home coding test a few days later

- talk to the recruiter again a few days later to tell me I did well on the coding test

- talk to another recruiter a few days after that, get scheduled for an all-day in person interview 4 weeks in the future

- cram cracking the coding interview for 4 weeks

- go to the interview all day, hear at the interview that I was close but didn't pass, they recommend I should try again in 6 months.

All in all thats a pretty big time & mindshare investment

Re: Why I Don’t Talk to Google Recruiters

#10
Places like google give you a guide on how to prepare. So it consists of stuff like algorithms and data structures. I do wonder sometimes how much it is tailored to getting people who are fresh out of college rather than more experienced. My take is that you basically have to spend time preparing and studying so as to get past those types of questions then finally you talk one on one with the people you likely would work with and then it's smooth sailing for experienced people. But the entry bar can be pretty tough to get past with zero prep.
Post reply on HN