3 ms·

Why not just give them different parts. The last guy you interview you give the task of putting together the different pieces, and then you have your finished a

• bokonist 18y ago
  Well, you are unlikely to get a finished application in two man weeks. You have everyone implement the same thing so you can compare apples to apples. Then you hire the best for the long term.
• tvon 18y ago
  Assuming you're not joking... Aside from that just being a very dishonest way to conduct business, you'd spend all your time organizing people who are working together who don't know they are working together. Even if you could manage that, you'd have no way of assembling the finished components into a working application, and there is just no way you could find someone capable of handling that task that was also foolish enough to think such a complex operation would be part of a job screening process conducted by a person incapable of knowing if it's done well or not. In fact, it's very unlikely you'd fool any experienced developers they'd quickly deduce that you don't know enough about the code to judge it's quality. The end result would be a pile of code that wouldn't work and you'd have no way of fixing it without hiring an even more exceptional programmer, who would probably tell you to throw out 90% of the work and start over.