&gt; <i>Google’s recruiting process is well documented online, and from this point my experience was pretty typical.The only difference is that I didn’t need to go through a technical phone screen since I had already demonstrated some proficiency with coding through the foo.bar exercises.</i><p>&gt; <i>For my interview, I spent a day at Google headquarters in Mountain View solving problems on a white board.</i><p>So what&#x27;s the point? A phone screen takes what, 30 minutes? This is a lot of time to put in only to have to do it all again on a whiteboard.<p>I guess it would be better than a phone screen for Google, but this seems like just another hoop for candidates to jump through.<p>One of my gripes with the tech industry is that companies keep adding more onto the funnel part of the hiring process, but once you get the interview none of it matters. You can contribute to open source, have substantial github projects, complete coding challenges, have years of experience: all of this just helps you <i>get</i> the interview. Once you are in the companies hiring pipeline everyone is put through the same process, none of the other stuff really matters after that point.<p>Maybe I&#x27;m just bitter that my team just hired one candidate over another because they did better in the whiteboard interviews (but had no side projects or real code to show us) while the other person had a lot of (good) code and pretty creative projects to look at.