[BillBohan]

If a company wants me to write code, they need to pay me for it.

I came across a similar situation where a prospective employer sent me the requirements for a complex routine and gave me 7 days to return functioning and commented code. My estimate was that it would take me 2 days to do it, so it would probably have taken 6 days.

I can envision an unscrupulous business model whereby you do the top level design and break it into routines, advertise for a programing position, and send the specifications for a routine to each applicant. You reject each applicant after they have submitted their code, take the best implementation of each routine, pack it all together and now you have a product.

I don't know that that's what they were doing but nobody will do it to me. I hope that's not what happened to you.

You may call me cynical but I've been around enough that I come by it honestly.

[gravypod]

This is only a practice because people are being tricked into doing it. Also, I'm not too sure you're being cynical. This is the obvious next step to an interview puzzel, isn't it?

   * I need to test my employee so I give them a test
   * A test isn't code so I give them a coding HW
   * The coding HW isn't representative of our work, so...
   * I give them a small chunk of my real work. 

This is pretty stupid. I've just barely started in the working market and I think my resume is solid enough that I won't mess around with any BS like this and if no one else does then they will finally stop.

There is one proviso (as usual). I'm completely fine with coming in and doing a pair exercise with people if the job requires pair work. I mean, that's not really about the programming at that point (maybe just write a simple web scraper) together with someone you'll actually be working with to see if you can all get along. Crack a few jokes, get some work done, leave with a better understanding of the enviroment. I'd be fine with that but nothing that would take more then 1-2 hr.