4 ms·

Great implementation for a bad practice, idea. This tool IMHO encourages the worst interviewing practices. I'd prefer to hire like this: 1. Collect resumes

Great implementation for a bad practice, idea. This tool IMHO encourages the worst interviewing practices. I'd prefer to hire like this: 1. Collect resumes/recommendations 2. Ask candidates to implement a simple project (~8 hours) 3. Ask remaining candidates with reasonable/better solutions to come on-site. 4. See how behave during code review of their project 5. Give them a small simple problem to solve 6. Ask them to tell you their solutions time and space complexity 7. Ask them to write a unit test for their solution 8. Ask them to code review your solution to the same simple problem and contrast it to theirs 9. Ask them 1 or 2 simple theory questions that demonstrate their understanding depth. Maybe "How does virtual memory work and why was it invented". 10. Buy them lunch/supper. This focus of this is 1. Can they produce 2. Can the work on a team 3. Do they grok computer, with 1 and 2 being weighted more.

Forplax 13y ago
> 2. Ask candidates to implement a simple project (~8 hours) I've never understood why employers seem to think asking for 8+ hours free work before even possibly getting an interview is fair to the applicant.
- voidlogic 13y ago
  Its more fair then the "what can I make you code under pressure, without references, while I stare at you" tests, and its more like what you are hiring them to do. Its also good for figuring out who you don't want to fly across the country to interview with you. It also lets people self select and go- I don't know how to do this- maybe this isn't the right job for me. I'm assuming these tasks are toy tasks and the company isn't getting IP value from them- I'd let your candidates open-source what they build, so long as they don't say why they (really) built it.
asadlionpk 13y ago
Asking people to implement projects seems very less scalable (considering you get 100+ resumes). It is good for small hire... This reminds me of Aaron Swartz's essay about this.

Forplax 13y ago

> 2. Ask candidates to implement a simple project (~8 hours) I've never understood why employers seem to think asking for 8+ hours free work before even possibly getting an interview is fair to the applicant.

voidlogic 13y ago
Its more fair then the "what can I make you code under pressure, without references, while I stare at you" tests, and its more like what you are hiring them to do. Its also good for figuring out who you don't want to fly across the country to interview with you. It also lets people self select and go- I don't know how to do this- maybe this isn't the right job for me. I'm assuming these tasks are toy tasks and the company isn't getting IP value from them- I'd let your candidates open-source what they build, so long as they don't say why they (really) built it.

asadlionpk 13y ago

Asking people to implement projects seems very less scalable (considering you get 100+ resumes). It is good for small hire... This reminds me of Aaron Swartz's essay about this.