37signals Job Board or visit the Gig Board

Wanted: Rails developers who care about quality work and best practices. Somebody who knows when to use nginx v. Apache or Ferret v. Sphinx, and can explain why.

We have some in-flight projects and some new projects, and need Rails devs who can offer consistent part-time architecture and development help. Have five hours a week? We’ll take it. Twenty hours a week? We can keep you busy. Forty hours a week? Easy there, pardner. But let’s talk.

What will you be working on? Immediately, a batch of improvements to http://currentenergy.com. In the future, all sorts of interesting web apps. We build whatever the client needs, so you could be writing a RESTful interface for an online store one day, building a custom CMS the next, or tweaking a Rails app for performance yet another day.

You absolutely must:

1. Know Rails well: You needn’t be a core contributor, but we’re not looking for "I watched the Flickr demo and now I know Rails!" types. Our apps are developed with Rails best practices in mind, so you should be able to quickly orient yourself and keep others oriented as well.
2. Operate within the Rails ecosystem: We manage source with Subversion, deploy with Capistrano, and serve with nginx + mongrel: you must be comfortable with these tools. Bonus points for being able to pick the best tool available for future development decisions.
3. Play well with others: You don’t need to be the Fonz, but if you’re not likable and communicative, it’ll be hard to work in our collaborative atmosphere (read: multiple people working part-time on the same projects).