Follow-up to “The dystopian world of software engineering interviews”
I got to the last thread too late for a comment to make a difference, but I&#x27;m exactly the person most of you want to talk to or hate.<p>I&#x27;m an interviewer at a FAANG company with &gt;500 interviews in the last 5 years, I teach multiple internal courses on interviewing, and I think the system makes a lot of sense for companies at our scale.<p>Ask Me Anything :)<p>I currently have a toddler on my lap, but I&#x27;ll edit this post later today to address some common criticisms and misunderstandings, but also point out which concerns I think are valid and where we should do better.<p>edit:<p>Okay, let&#x27;s go through the most important points<p>1) I&#x27;m a Software Developer. I interview other SDEs. I ask them problem solving coding questions, algorithmic coding questions, data structure questions, and whiteboard architectural design (not at the same time, but it could be any of these)<p>2) Our process is REQUIRED for a company of my size. You would not believe the amount of candidates we get. We have a high bar for hiring, but fundamentally we have to be efficient with our time. That completely removes as an option superior interviewing techniques like &quot;spend a day with the dev team working on a small real task&quot; or &quot;do this take home test over the weekend and then the interviewing team will review it with you&quot;.  Both of these are better at uncovering good candidates than a whiteboard coding interview, but don&#x27;t scale, and are themselves controversial in the industry from candidates who are unhappy of the time they require.<p>3) A common criticism of &quot;algorithmic&quot; questions (leetcode) is that they don&#x27;t reflect the reality of day to day work. If a lot of people even at FAANG are working on typical 3-tier front-end-back-end-database systems, utilizing the tools and systems other employees built before, why bother evaluating if the candidates could build the next generation of such systems if asked.<p>Because once these people are inside the company, we&#x27;d like to think that everyone passed a similar tech bar. That means that if a new database or distributed system does need to be purpose built for a high scale system, and someone applies internally, you can be flexible with the kind of interviewing process you put an internal transfer through - you already know they passed a high technical bar, and are likely qualified to work on the hard stuff.<p>4) another common misconception is people underestimate the complexity of &quot;typical&quot; systems inside the FAANGs of the world - compared to their prior job experiences. A payment processing integration at Amazon scale is not a payment processing integration at your company&#x27;s scale. An internal CRM build at Google scale is not an internal CRM build at your company&#x27;s scale.<p>The 10,000 foot view is similar, but the expectation would be that the system would be 1&#x2F; built out faster, 2&#x2F; built out better, and 3&#x2F; scale better than a comparable project on a less technically strong company.<p>5) Coming back to the interview process. What that means, is that when we ask a candidate to solve a hard algorithmic problem on a whiteboard in 20 minutes, or deep dive into the inner workings of a complex data structure, or show how they could combine multiple data structures to solve one problem, we are not validating &quot;Can this candidate write an algorithm in 20 minutes on the job at their desk&quot;<p>What we&#x27;re checking is &quot;Can this candidate do something really hard, ambiguous, and time-sensitive in the Computer Science domain, when prompted to.&quot;  The real life challenges will be different, but if they CAN do the first one, they&#x27;ll likely be able to do the second one.<p>Of course we miss out on candidates who are terrible at these skills, or can&#x27;t code on a whiteboard, or are overwhemled by the interview stress and can&#x27;t perform. But we are willing to do that because of Point (2) above. We&#x27;d rather say no to a &quot;maybe&quot; candidate than hire someone who can&#x27;t perform.<p>Despite what people state that ability with algorithmic performance on a whiteboard does not translate to on the job success, that is not my experience. Remember - I&#x27;m not looking to see if a person can spit out A* search algo on a whiteboard from memory.<p>I&#x27;m looking to see how they approach a problem they haven&#x27;t seen before, how they break it down, what kind of assumptions they make, what ways they simplify it, how they consider ideas and tradeoffs, and finally how their ideas translate to code (fluently or not)<p>6) The majority of people I see cannot execute that last paragraph well enough to join a team at my company and be productive. Sorry, hackernews readers, but that&#x27;s just the case. This isn&#x27;t a &quot;can&#x27;t solve fizzbuzz&quot; level of incompetence - these are good engineers who are likely stars at their smaller companies, and who can be relied upon to get the job done. But they would not thrive at a FAANG-level company because they lack some ability - either clarity&#x2F;coherence of thought, or ability to understand their techncial domain in depth enough, or because they just aren&#x27;t fluent at translating ideas into code.<p>edit2:<p>7) All this to say...if you&#x27;re not FAANG++(Dropbox, Salesforce, etc I don&#x27;t know)....stop copying us. You don&#x27;t need this process.<p>Your company has fewer candidates, and you both can&#x27;t afford to be as picky as us, and you don&#x27;t NEED to.<p>Each of my previous companies (in the 200-500 person range) had a process of a simple coding question onsite, followed by a take home test that a decent candidate (and I don&#x27;t mean decent for FAANG, I mean decent across the SDE community) could complete a reasonable solution in ~2-3 hours. We set expectations as &quot;you could do it in a weekend&quot; because certainly some people took closer to 8 and got hired.