Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Businesses Ruby IT Idle

One Company's Week-Long Interview Process 362

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."
This discussion has been archived. No new comments can be posted.

One Company's Week-Long Interview Process

Comments Filter:
  • I've done simular... (Score:5, Informative)

    by Kenja ( 541830 ) on Monday September 10, 2012 @01:01PM (#41289429)
    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.
  • Re:Probably illegal. (Score:2, Informative)

    by Anonymous Coward on Monday September 10, 2012 @01:03PM (#41289471)

    They probably just call it an "internship."

    Captcha: Pretend.

  • 6 Grueling Hours. (Score:4, Informative)

    by scorp1us ( 235526 ) on Monday September 10, 2012 @01:05PM (#41289491) Journal

    It wasn't enough that the position I was interviewing for was for someone who got promoted out of it. And I knew him (but not that I was interviewing for his job, until I got there) we of course hit it off, but his boss was the one that needed convincing. I get showed around, described the job, I take some tests, where I ace them, save for the questions that were either asked poorly or the answers wrong (2 out of 20) and we all agreed I was an exact match, and even slightly over-qualified. We got this feeling early on, but they continued to grill me through the full battery of people and tests. After 6 hours (We get a1/2hr for lunch)

    We finish up, call the recruiter it looks good... They elect not to make an offer because I would be too good for the job. never mind the pay was better, the location was better, the industry was better and it was a topic I was very interested in.

  • Re:Probably illegal. (Score:4, Informative)

    by Anonymous Coward on Monday September 10, 2012 @01:05PM (#41289499)

    This happens in restaurants every day. Cooks work a few shifts for free prior to being hired. The French term is stagiare. The difference is cooks work for free to get minimum wage jobs.

  • Re:6 Grueling Hours. (Score:2, Informative)

    by Anonymous Coward on Monday September 10, 2012 @01:14PM (#41289641)

    >> They elect not to make an offer because I would be too good for the job.

    Amazing that they could say that with a straight face. More amazing is that you actually believed them.

  • by Maximum Prophet ( 716608 ) on Monday September 10, 2012 @01:20PM (#41289739)
    but we pay them inflated contractor wages. For the most part, we don't hire anyone direct, but convert contractors to full-time.
  • by interval1066 ( 668936 ) on Monday September 10, 2012 @02:01PM (#41290463) Journal

    Yes, I recognize the language's many obvious (and many not-so-obvious) failings...

    You're underselling the problems with PHP. Seriously. PHP is a hideous, three-headed stepchild of a programming language and I know nothing about it that's fun, functional, or useful. Its not Fun, or Funny. http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/ [veekun.com].

"More software projects have gone awry for lack of calendar time than for all other causes combined." -- Fred Brooks, Jr., _The Mythical Man Month_

Working...