3 ms·

I'm convinced that the best interview is to give someone an app (react or node app for example) and do exactly what occurs all the time in the real world. Give

I'm convinced that the best interview is to give someone an app (react or node app for example) and do exactly what occurs all the time in the real world. Give vague indication that a feature appears to sometimes not work correctly. In the app code there should be one or two very obvious bugs and easy optimizations to make, and then put more subtle and challenging to fix issues there as well. And ideally make it something where a really sharp and experienced developer would identify some high-level architectural flaw and they would know how to rearchitect it. Everyone knows that the leetcode-style questions are contrived and don't usually reflect real world work but we continue to do it anyways.

JohnBooty 5y ago
I've done a variation of this exercise with some folks I helped to interview. We showed them our website and asked how they'd investigate/troubleshoot a complaint that the site was "slow." Then we kind of role-played the troubleshooting process. Ideally I wanted them to determine if the site was slow for everybody, vs. just the person that reported the issue. If it was only slow for a single person, was it their account, or many just their internet connection? How would they determine that? If we determined the issue was happening for everybody, how would you determine which part of the stack was slow? Etc.