1) Not a problem and very understandable. I don't require work-related samples, just code samples in general. 2) Also understandable, but it's really no differe

1) Not a problem and very understandable. I don't require work-related samples, just code samples in general. 2) Also understandable, but it's really no different than doing it on a whiteboard in my office. Might as well take 30 minutes to write some code in an environment where you're comfortable versus doing it on a whiteboard where you're under pressure, yes? A would rule you out as a candidate for me. Passion is almost always a requirement. B would be acceptable -- in general, language doesn't matter. It's the ability to write code and explain it that matters. C would be a tossup. If you write crap code for fun, then why would you write better code for real? But I get that. Sometimes I write code for fun just to see if something works, and I never refactor it to make it more efficient or whatever. That's understandable. Again, it's more about the ability to master the basics to begin with. I can teach you to be a better programmer, provided you understand the basics (which your code samples should demonstrate). I don't have time to teach you the basics (unless I'm specifically hiring an intern or something.) Also, consider that in my original post, I said this is my process and how I do things. It has worked very well for me so far. I may rule you out, but I'm willing to bet that there are others equally as good (or better) than you that are willing to do what I consider to be far less annoying than the way interviews are conducted now. I don't want to waste your time -- nor my own time. That's the end game here. By having code samples ready for me, you are eliminating a not insignificant amount of redundancy for both of us.