Google's “Director of Engineering” Hiring Test (2016)
This was posted previously, in October 2016:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12701272" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12701272</a><p>An actual Google director of engineering pointed out that these are individual-contributor SWE&#x2F;SRE questions (and I can attest I got very similar questions as a new college grad).<p>As I commented previously: &quot;Reading more closely, it sounds like they are not interviewing him for a director of engineering position; it just sounds like he thinks his current role, CEO-who-writes-code of a very small software company (<a href="http:&#x2F;&#x2F;www.gwan.com&#x2F;about" rel="nofollow">http:&#x2F;&#x2F;www.gwan.com&#x2F;about</a>), qualifies him for a director-of-engineering-level position. He&#x27;s probably being interviewed for an SRE team lead or thereabouts.&quot;<p>Also, a ton of this conversation makes a lot more sense if you make the assumption that the interviewee is misremembering the questions: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12702726" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=12702726</a> (Which is a very gentle assumption, if the interviewee also mistakenly thought they were being interviewed to be a director of engineering.)<p>In which case, screening out someone with an inflated sense of their own experience and overconfidence that the stupid person on the other end of the phone is stupid is <i>exactly what this process is supposed to do.</i>