Coding Problems from Programming Job Interviews
A take from someone who asks these types of questions in interviews on a regular basis:<p>1) Don&#x27;t just memorize this list. The fact that this list is publicly available means that we know not to ask these specific questions.<p>2) This is a very good way to practice the types of problems that are often asked in interviews, so if you can tackle these then you should be good to go.<p>A lot of people on HN and in real life (I&#x27;ve had people get angry for asking them to write code in an interview) hate these types of interviews. There&#x27;s a lot of research done on this topic and so far, it&#x27;s kinda like democracy. A crappy system, except for all the others. For all the complaints about this, I have never seen anybody propose something that satisfies the long list of requirements for interview questions.<p>Here&#x27;s the list, pasted from an HN comment I made a few years back on a similar discussion:<p>Objective - the process avoids human bias (this guy was in my frat, therefore is awesome).<p>Inclusive - someone doesn&#x27;t need extensive past knowledge in a particular area of coding to do well in the interview.<p>Risk Averse - Avoids false positives.<p>Relevant - it properly tests the abilities needed for a coding job, and not irrelevant ones (like the ability to write an impressive resume).<p>Scales - this will be used for tens of thousands of interviews.<p>Easy-to-do - this will need to be done by hundreds&#x2F;thousands of engineers, who would probably rather be coding.