Re:An inside look at Google’s data-driven job interview process
by victor9000 on Wednesday September 04, 2013 @10:03PM
(#6331769)
I'd much rather have someone on my team who knows how to get shit done. optimizing in a vacuum is easy.
Re:An inside look at Google’s data-driven job interview process
by tomkarlo on Thursday September 05, 2013 @02:00AM
(#6332431)
When you're trying to build services for hundreds of millions of people, optimizing gets pretty key, and it's often the harder part than building a MVP or "getting shit done". Ask Twitter.
Re:An inside look at Google’s data-driven job interview process
by AznHisoka on Thursday September 05, 2013 @09:45AM
(#6334116)
That's true. It's often the hardest part if your service isn't really anything technically groundbreaking (ie Twitter, Facebook as opposed to Google)
Re:An inside look at Google’s data-driven job interview process
by Arelius on Thursday September 05, 2013 @03:03AM
(#6332623)
I'd never be able to be a Googler either, for nearly the opposite reason: I left College a long time ago for a job. I have since spent 8+ years working on tough problems that are highly algorithmic, and tons of optimization work. Yet the lack of college is a deal breaker AFAICT.
Re:An inside look at Google’s data-driven job interview process
by rlu on Thursday September 05, 2013 @12:55AM
(#6332263)
Maybe you're right and maybe you're wrong - but I certainly hope that this thought hasn't prevented you from applying.
Can't win if you don't play :)
Re:An inside look at Google’s data-driven job interview process
by enraged_camel on Thursday September 05, 2013 @01:29AM
(#6332343)
>>Can't win if you don't play :)
Actually, considering the horror stories we have heard about Google's hiring process, it might be more appropriate to say: "the only winning move is not to play."
1) I graduated from college long time ago, and have worked in a BigCorp for 6+ years, where the toughest technical problem all center around CRUD, nothing that requires any deep algorithmic, machine learning, or NLP techniques (ala building a search engine).
2) During my free time, I hack on my startup, and although the problems are more challenging, I tend not to spend too much time trying to optimize things, or come up with the most efficient, elegant solutions because of time constraints. I just ask myself: is this good enough and move on. Because of this, I develop bad habits that would never be allowed in Google.