Sunday, November 1, 2009

Tips for Hiring Ruby Developers

By Steve Woolfe

Hiring Rails full-time Rails developers is hard. Surging demand. You will likely fight other companies for every recruit. Freelance consulting rates are going through the roof.

If you plan to hire a local candidate do not use 37signals job board. I've used it twice, it's pricey, and I never got a single resume from a local candidate. Our office is in a major American city. On the other hand I got a great resume from monster which turned into us hiring a great programmer. To be fair, his was the only resume with rails experience, but we got a good number of decent resumes from monster of people that had a genuine interest in rails, but had not used it professionally.

Avoid brand-name superstars. They will command massive salaries, sport huge egos, and ultimately not fully commit to your company. Better they gain notoriety through your projects.

A university degree is not important. I hate to say it-I'm personally a graduate from Canada's highly-regarded Math/CS program at Waterloo-but several of the best Rails developers I know didn't study computer science at all. Hire perpetually. You'll find that I always have an open Rails developer position, because when demand outstrips supply, you should hire when you can.

Have a company Rails blog with useful, meaningful posts (like our Email Veracity post which made it to del.icio.us/popular) to spread awareness and goodwill.

Does someone have to become an expert in Rails before even having the opportunity to work with and learn from others? It reminds me of all the "junior developer posts" that asked for 6 months commercial experience in VB - like you can get that as a graduate. While I can see that for the ideal candidate I'd be interested in what you'd ask for for a junior developer.

About the Author:

No comments: