Cracking the Coding Interview Tutorial
While there are many legitimate criticism of whiteboard-style coding interviews, I have yet to see a convincing alternative that scales well to the size of big companies. Google [1][2], Facebook et al. hire thousands of engineers per year, meaning they conduct at least 10-100k interviews per year. How do you design a process that is consistent, measurable and efficient at that scale?<p>[1] Google gets 2 <i>million</i> resumes a year <a href="https:&#x2F;&#x2F;www.fastcompany.com&#x2F;3044606&#x2F;hit-the-ground-running&#x2F;googles-head-of-hr-shares-his-hiring-secrets" rel="nofollow">https:&#x2F;&#x2F;www.fastcompany.com&#x2F;3044606&#x2F;hit-the-ground-running&#x2F;g...</a><p>[2] Headcount increased from 57,148 to 66,575 between Q2 15 and Q2 16: <a href="https:&#x2F;&#x2F;abc.xyz&#x2F;investor&#x2F;" rel="nofollow">https:&#x2F;&#x2F;abc.xyz&#x2F;investor&#x2F;</a>