One Company's Week-Long Interview Process
jfruh writes "What's the longest tech interview you've had to sit through — two hours? Eight? Ruby on Rails devs who want to work for Hashrocket need to travel to Florida and do pair-programming on real projects for a week before they can be hired. The upside is that you'll be put up in a beachfront condo for the week with your significant other; the downside is that you'll be doing real work for a week for little or no pay and no guarantee of a job slot."
Is that you're programming in Ruby on Rails...
Where do I send my significant other's resume? I can use a vacation.
There is also the old Russian engineering philosophy, "never design a plane that can fly if you're in prisson".
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
With one-week sprints.
Bravo! You have made the beginning of my day!
The title of my next newsletter:
Ruby: A language designed by programmers for non-programmers
Then followed by these illustrious titles:
Ruby: Non-programming for Programmers
Ruby: Unprogramming what you've learned about Programming
Ruby: Lobotomy required
Ruby: Brainfuck for the masses
Because he read some place that African trolls are starving?
Seriously. I've been at companies that do all day interviews and those are pointless. Group after group of people come in and ask the people almost identical questions. If it takes you more than an hour or two to determine someone's skill and personality then you are probably doing it wrong. If someone asked me to spend a week working before they would even consider me I'd laugh and tell them to have a great day. If some company I never heard of asked me to book 5+ hours for an interview, I'd tell them no thanks as well, unless I was absolutely desperate. I have better things to do with my time.
But what if the benefits of employment were fantastic? Like hot blondes give you blowjobs while you code?