4 ms·

These are all excellent suggestions. Potential interviewers please note that leaving the candidate in a conference room with blank paper and pencil potentially

• tonystubblebine 17y ago
  We used to call the code writing section of the interview a typing test. You could literally tell if the person was going to make it by listening to them type. Someone who is comfortable writing code types confidently and with long bursts. We saw plenty of applicants who talked a big game, but clearly couldn't put together even the simplest program without resorting to cut and paste.
  • Periodic 17y ago
    I still find it hard to believe that someone would apply for a programming job without being able to write fizzbuzz in the language of the position.
    • tonystubblebine 17y ago
      I found it hard to believe also, but it happened plenty. I think it's more common once you get outside of silicon valley startups. For the startups I worked at, we were almost always able to hire from within the community and most people we interviewed already had public demonstrations of code. They weren't all perfect candidates, but they could at least write fizzbuzz.
      • Quarrelsome 17y ago
        When I took the interview for my current place the first question I was asked is "what is the difference between the public and private keywords". After I responded with the obvious answer the interviewer sighed with relief and told me I was the first candidate that day (out of 5) that managed to answer the question correctly. Be VERY afraid. :D