3 ms·
It's perspective. By the end of interviewing 6 or 7 people, YOU know those questions and all the paths to answers cold. You not only know the questions and answ
by Zigurd 11y ago
It's perspective. By the end of interviewing 6 or 7 people, YOU know those questions and all the paths to answers cold. You not only know the questions and answers, you know all the ways thinking about those problems is connected to other problems. So, WHO could possibly not know that? Possibly you, before you put together your list of interview tech questions.
- pjc50 11y ago.. but these two always come up as suggestions. So much so that anyone googling "what questions to expect during a programming interview" ought to be able to come up with canned answers to them. A priori you might expect to find that there were lots of candidates who could do string reversal and fizzbuzz but nothing else. This doesn't seem to be the case.
- Zigurd 11y agoThat's right. Mostly they test whether people have taken the time to prep for an interview. That has some value, but maybe not the value the interviewers intended. I like the kinds of interviews where you assign a coding problem before the interview and review the code, or where debugging is part of the tech interview.
- _Codemonkeyism 11y agoSo you think given the instructions in an interview: 'Write a program that prints the numbers from 1 to 100. But for multiples of three print “Fizz” instead of the number and for the multiples of five print “Buzz”. For numbers which are multiples of both three and five print “FizzBuzz”.' people should not be able to write the code? Just by hearing the answer 6 to 7 times ("By the end of interviewing 6 or 7 people") someone knows the answer? "Possibly you, before you put together your list of interview tech questions." No actually given the instructions I could write the code in one go. So I'm mystified as why someone applying to a developer position could not do this in your opinion.