&gt; A lot of people are pissed because they didn&#x27;t get in and feel it&#x27;s google&#x27;s fault for having a &#x27;broken interview process&#x27;. But reality is that google is one of the most profitable&#x2F;successful companies in the world and gets voted &quot;top employer&quot; year after year. A lot of people want to work for them, so they can afford to be picky in the interview process; but that doesn&#x27;t mean anything is broken. Quite the opposite actually.<p>I&#x27;m not convinced of this argument at all. Many of the people I know who either work there or have work there complained about the process as well. I didn&#x27;t get in which was fine (I certainly wasn&#x27;t pissed) but I was very frustrated with the interviewer being 15 minutes late and when he asked me to implement an object he cut me off when I was almost finished to optimize a method (I protested; premature optimization and all). Then, since we had a truncated time table, I just finished optimizing and he ended the interview. I explained to him what code was left in my object implementation and it didn&#x27;t seem to be a big deal. Then when I didn&#x27;t progress a few friends I have at Google looked into it and found out I didn&#x27;t get to progress because I didn&#x27;t get to finish my implementation.<p>I&#x27;ve been in a variety of different types of interviewing. The more academic, white boarding of issues that you never even see on the job just suck in my opinion. I like it a hell of a lot more when I get to work with whoever I&#x27;m interviewing with and we&#x27;re working on a real problem. Or hell even homework. Anything to show how I solve problems and code versus simply remembering different algorithms or data structures from college.