Slashdot Mirror
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.
The longest for me is 5 hours but this is ridiculous. The only people that would be able to apply are people who are unemployed. As someone who has interviewed people for programming jobs, it really doesn't take more than 2 hours to figure out if someone is a good fit.
Violation of labor laws. This is illegal. They have people doing full time work for less than minimum wage. The fact that they call it an "interview" is hardly a reasonable distinction. I hope the idiots involved suck a nice 6 or 7 digit fine for this.
only to be told that I finished the project during the interview process and my services would no longer be needed. They then had the audacity to contact me months later to see if I wanted another go at working for them. Free labor is free labor, dont fall for it unless you REALLY need to.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
I've been involved in a fair few hires for my previous employer, and it struck me that we *sucked* at making a fair assessment of the applicants' abilities. My experience at other firms have been no different, even though most do manage to weed out the obvious knuckledraggers or spot the shining genius. In contrast, observing someone at actual work for a week should give a far better insight in their abilities and soft skills. This is obviously of benefit to the employer, but also to the prospective employee. The only thing I'd hope is that the company already did a short assessment of the candidate to spot any obvious reasons why he/she woulnd't be hired, before asking them to commit for a week.
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
With one-week sprints.
I had an interview for an out of city employer. It resulted in me being given a PAID two week contract to see if I'm worth hiring. I forget what it was I made, but I was paid $2000.
that $2000 was part of my moving expenses if I was hired, and if I was not, I still got $2000, because I signed a contract stating if I finished the work on time, I get $2000.
This seemed like a good way to do things and benefits both the company and myself. I get money, company gets proof I can not only code, but be professional (meetings on time, meeting deadlines, etc).
I'm god, but it's a bit of a drag really...
Guess I can't interview there. My contract has one of those wonderful 'all IP created during your time here belongs to the company' clauses. If I create it during my interview my current company still owns it. I've never worried about interview code before since it's all toy problems and junk code anyway, but if I was doing something commercial as part of an interview process there could be some nasty legal implications if they try to release it.
I do a lot of work in Ruby, too. I notice that lots of Ruby gems contain C code. Someone competent is writing that.
Language fascists aren't generally as good at programming as they think. They'd understand where interpretive languages make sense, if they were.
Bruce Perens.