> Well, since you seem to know who I am, you
> probably know which challenge I was given.
> Do you really think its not an OO problem?
OO is indeed the most common strategy for solving the problem you received. However I'm sure you appreciate that you could use many different techniques. > Otherwise, you can probably have some of
> your other engineers review these tests if
> you are too busy to do it yourself. Not
> like this is rocket science. They can at
> least weed out clear failures like me :D
I know you're joking but I certainly realize that I reject many candidates who would actually have been great hires. It isn't possible for me to evaluate people 100% accurately, so I have to settle for conclusions drawn from an admittedly imperfect process. http://basecase.com/company/careers
http://basecase.com/platform/video/
Cheers,
1. New applicants receive an outline of the salary range, the working environment, our products, and the remaining recruitment process (our "FAQ").
2. "Software architecture" test (3.5hrs - 6hrs avg, 9hr max)
3. ~2 1hr interviews
4. Offer
The 'software architecture' test document has also been expanded, so that more information is provided on what we're looking for exactly.
Since everything is disclosed in step 1, people can make an informed decision on whether to proceed. This differs with the previous process in that one needed to pass a screening test before receiving this document.
Notes:
-) All applicants receive explicit accept / rejection emails (this has always been the case)
-) I will try to reduce the review time for the tests (I'm involving more people)
Regards,
Diarmuid / CTO of BaseCase