&gt;Technical interviews became 10x easier when I realized that most companies aren&#x27;t necessarily looking for the right answer as much as they are trying to look into your mind.<p>This is a great, great point.<p>I&#x27;d like to add one more: Admitting when you don&#x27;t know the answer. I&#x27;ve been in a number of recent phonescreens where we&#x27;d ask a technical question of a simple &quot;good&#x2F;bad&quot; sort. My advise to those reading: If you don&#x27;t know, just say so. &quot;I&#x27;m really not sure.&quot; or &quot;I knew at one point, but I&#x27;d have to go look it up again.&quot; Perfectly acceptable. No one&#x27;s a walking encyclopedia, and to say you don&#x27;t know show&#x27;s humility. I&#x27;m much more comfortable with someone who says they don&#x27;t know and will go look for the correct answer than someone who might stand in front of the customer and try to poker face.<p>To those reading this and taking notes for an interview, I&#x27;d say instances like these are a good opportunity to discuss. If you don&#x27;t know, ask what the correct answer was. Ask why. See if you can build off the answer, sometimes you might get asked a question you couldn&#x27;t recall the answer for, but once given, you can expand upon and demonstrate your knowledge in other ways.