| I apologize if I mischaracterized your company's hiring process -- there was no disparagement intended. On the contrary I believe it is intriguing, and given your company's excellent reputation it appears to work well. It also appears that we're definitely at a communications impasse. By "project work" I was referring to steps 3, 4 and 5 from the career page you referenced: 3. Web app challenge 4. Custom protocol challenge 5. Write a fuzzer (including automated testing) I'm open to any other descriptor for those steps that you care to use. I most sincerely apologize if "project" implies too heavy a meaning. And by length of time I was referring to the answer to question #1 directly below those steps "This looks complicated. How long does it take? Not that long! We work hard to minimize the amount of time we demand from candidates. We'll be 80% of the way through before you're ever asked to come on-site. We can usually wrap things up inside a few weeks. " I personally think it sounds like your process is designed to optimize around keeping the technical screening as short as possible while still maximizing the information you retrieve -- which I think is great. It's certainly a much better use of everybody's time than say, Google's multiple all-day committee interview/quiz show extravaganzas are. If I misunderstood the FAQ and the process does not, in fact, take a few weeks, I apologize. I'm not sure if it's you or I that's going out of our way to be obtuse regarding best hiring practices, but I apologize if I brought any offense or disparagement to you or your company. It wasn't intended. |