A Method I’ve Used to Eliminate Bad Tech Hires
This. 100% this.<p>As many others are saying, I find that this is the most comfortable way for me as an interviewee to demonstrate that I do in fact know what I&#x27;m talking about. Put me in front of a room full of people and a whiteboard and throw something at me, and I&#x27;ll freeze. Freezing in that situation and being a bad engineer are wholly separate things.<p>Anecdotally, when I get one of these problems, I spent 20 minutes reading the prompt, looking at resources and making an outline of my code. Then I step away for the afternoon and don&#x27;t think about it. Let the subconscious internalize the problem for a while and when I come back, I&#x27;ve got a much better mindset to approach it. Solving new problems on the spot is just a skill I don&#x27;t have. I prefer to think that this is what makes you valuable as an employee and engineer, solving a problem by the end of the day. Not while under scrutiny. Personally, my resume and experience don&#x27;t get me far interviewing by the big companies, but on the occasions that I get take home code assignments, I tend to get pleasantly surprised and pleased reviewers and it takes me to the final rounds (where I face the dreaded white board and actually-there-is-a-correct-answer situationals).<p>My two cents, this just really resonated with me. Does anybody else happen to solve problems this way?