I had a disastrous phone interview this week throughout which I remained calm and focused but immediately after putting the phone down I emailed the recruiter to say I wasn&#x27;t interested.<p>The &quot;Technical&quot; part was just trivia. Never-mind that I was sat in front of a computer and could have googled everything asked, I chose not to do that.<p>So yes, I stumbled when asked &quot;what does the using keyword do&quot;.  I explained how it relates to IDisposable, disposeing the object at the end of the block scope and avoids needing try&#x2F;finally blocks.<p>But clearly that wasn&#x27;t the script, because they kept asking &quot;Are you sure it doesn&#x27;t do anything else? Are you sure isn&#x27;t used anywhere else?&quot;.<p>Eventually I realised they were talking about &quot;using System.Linq&quot; etc, and all they wanted to hear was the word &quot;namespaces&quot;.<p>Talk about interviewing by numbers, had I wanted to I could have googled every question and given them perfect descriptions.<p>What could they possibly have learned from that interaction? I learned I didn&#x27;t want to work there, so it helped me I guess.<p>But I find implementation things more helpful (in person, not by phone!), because it&#x27;s not about whipping out the right answer, it&#x27;s about watching how the candidate thinks and approaches problems. It&#x27;s about how they work not the end result.<p>I like the &quot;write a function to multiply&quot; because it can be extended to any level. If someone aces the positive numbers case you point out negative numbers, if they ace that you can talk about efficiency, or bounds checks, exception handling, efficiency or whatever else you think they&#x27;d like to talk about.