81–90 of 164 posts
Xoogler here: If you want to work for Google, my advice is to try again when you get a chance. IMHO, getting an offer is about 50% the luck of the draw as to what questions you get, and what interviewer you get. If you were close this time, you might get an offer next time. If it makes you feel any better, people who I knew were smarter and better coders than me got declined, yet somehow I got hired. BTW, I thought s…
As always, remember that even technical interviews like this one have an incredible amount of random chance built into the hiring process. This is especially true at a big company like Google (where I work and do interviews). Do they happen to have positions open right now? Did you happen to get asked questions that clicked with you? Was the hiring committee feeling grouchy that day? Did you get an especially harsh i…
> There's a decent amount that you can do to prepare for one of these things, but there's also an incredible amount you don't have control over. This is super important. Don't take it personally at all. They're using the randomness as a flow control. They are always attracting more talent than they actually need purposely to keep the reservoir full and just running the extra through the spill gates. Just taking a rid…
Of course "not getting a job" is a "signal regarding your quality as an engineer". We need to keep this toxic mindset out of tech and silicon valley. The idea that everyone is smart, special, and deserves a job at Google, is completely false. There are people here on HN that will never get a "top" software/machine learning/design job simply because they are bad at it. Telling them "it's not you, it's the company" will only doom their future even further as they will lose motivation to improve themselves because: "Hey, HN said I'm smart and a talented engineer."
To drive the point home to viewers reading this, some of you may have applied to Google via their website. You did not get a reply. After reading this original post and the GP, please do tell me how smart you are and why your 10x programmer skills didn't catch the eye of Google recruiters (or Facebook, Apple, or any hot startup).
As always, remember that even technical interviews like this one have an incredible amount of random chance built into the hiring process. This is especially true at a big company like Google (where I work and do interviews). Do they happen to have positions open right now? Did you happen to get asked questions that clicked with you? Was the hiring committee feeling grouchy that day? Did you get an especially harsh i…
The OP did get hired -- he mentioned that in his first paragraph.
As always, remember that even technical interviews like this one have an incredible amount of random chance built into the hiring process. This is especially true at a big company like Google (where I work and do interviews). Do they happen to have positions open right now? Did you happen to get asked questions that clicked with you? Was the hiring committee feeling grouchy that day? Did you get an especially harsh i…
"If we didn't get lucky enough to hire you, someone else will quite soon." The OP did get hired -- he mentioned that in his first paragraph.
The OP was hired by Amazon, "we" refers to Google in this case.
> The talent is then picked up by a recruiter
Am i the only one who trips over such terminology of calling a hired worker "talent" and finds that it feels like it's manipulative, PC or doublespeak?
What meaning does the word "talent" have in casual English?
Earlier quoted context omitted.
> There's a decent amount that you can do to prepare for one of these things, but there's also an incredible amount you don't have control over. This is super important. Don't take it personally at all. They're using the randomness as a flow control. They are always attracting more talent than they actually need purposely to keep the reservoir full and just running the extra through the spill gates. Just taking a rid…
> If you don't get the job, it's not a signal regarding your quality as an engineer and you shouldn't interpret it as such (however tempting it may be to do so). Of course "not getting a job" is a "signal regarding your quality as an engineer". We need to keep this toxic mindset out of tech and silicon valley. The idea that everyone is smart, special, and deserves a job at Google, is completely false. There are peopl…
Therefore it should not be a signal. Not getting a job because of an interview does not mean that you are not a qualified engineer.
It may mean that though. But it's not as if it's a 100m sprint where you can very easily measure results between Olympian and couch potato.
> https://www.amazon.com/The-Drunkards-Walk-Randomness-Rules/d...
Earlier quoted context omitted.
> There's a decent amount that you can do to prepare for one of these things, but there's also an incredible amount you don't have control over. This is super important. Don't take it personally at all. They're using the randomness as a flow control. They are always attracting more talent than they actually need purposely to keep the reservoir full and just running the extra through the spill gates. Just taking a rid…
> If you don't get the job, it's not a signal regarding your quality as an engineer and you shouldn't interpret it as such (however tempting it may be to do so). Of course "not getting a job" is a "signal regarding your quality as an engineer". We need to keep this toxic mindset out of tech and silicon valley. The idea that everyone is smart, special, and deserves a job at Google, is completely false. There are peopl…
Not that I'd want to work for Google anyway, I don't like them very much as a company.
Earlier quoted context omitted.
Reading people's accounts of interviewing at Google, I would never apply, and I won't cash in on the recommendations I could get from some ex/Googlers I know. Reading the submission, look how many times the candidate has to "ping" people just to keep the ball rolling. In my mind, I'd end up working with a bunch of sycophants who are willing to do that sort of thing, the same sort of people who got a thrill out of the…
> I would never apply I guess you'll never know what (if anything) you've missed. > I'd end up working with a bunch of sycophants who are willing to do that sort of thing You are implying bad intentions where none are likely to exist. Google is a very large company, and 0.001% of candidates are bound to have suboptimal interview experience by sheer bad luck (and it's likely that you see their horror stories more than…
Better than my interview experience. Sailed through the phone interview, went in person for the day long interview. Most were no problem except for one that took longer than it should have. And then... Nothing. Radio silence. No emails. No answered emails. I had ceased to exist. After that colossal waste of time, I decided to only work remote.
Earlier quoted context omitted.
> There's a decent amount that you can do to prepare for one of these things, but there's also an incredible amount you don't have control over. This is super important. Don't take it personally at all. They're using the randomness as a flow control. They are always attracting more talent than they actually need purposely to keep the reservoir full and just running the extra through the spill gates. Just taking a rid…
> If you don't get the job, it's not a signal regarding your quality as an engineer and you shouldn't interpret it as such (however tempting it may be to do so). Of course "not getting a job" is a "signal regarding your quality as an engineer". We need to keep this toxic mindset out of tech and silicon valley. The idea that everyone is smart, special, and deserves a job at Google, is completely false. There are peopl…