Why I Don’t Talk to Google Recruiters
yegor256.com
Why I Don’t Talk to Google Recruiters
1–10 of 674 posts
Re: Why I Don’t Talk to Google Recruiters
#2Re: Why I Don’t Talk to Google Recruiters
#3Re: Why I Don’t Talk to Google Recruiters
#4They 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
#5I 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?
Re: Why I Don’t Talk to Google Recruiters
#6> 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
#7My 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
#8Interview process: complete success.
Re: Why I Don’t Talk to Google Recruiters
#9I get that things can be fluid, but its such a meat machine.