Another job: mostly Rails
Sam Livingston-Gray
I started a new job last year, and the place where I work is looking to hire another Rails developer.
[If the previous sentence and subject line sound familiar to you, it's because I posted something similar to this list on September 30 of last year. We hired one of the people who replied to that, so I'm trying it again.]
The development group is profitable and [obviously] continues to grow. Position is hourly [as in paid overtime] and includes benefits after 60 days.
We have no carefully-curated list of bullet points. I've probably got the highest standards of any of the people you'd interview with -- so send me a code sample. Bonus points for TDD/BDD experience[1], for having generated PDFs from a Rails app, or for having decent CSS skills and an eye for design.
As you'll see from our product lineup,[2] the domain matter is fairly standard. The shop has been using Rails since the pre-1.0 days, and in fact, some of our apps are still running Rails 1.1.6. [Most new apps get forked from a standard codebase running Rails 2.3.x, but they tend to quickly develop their own inertia.]
Toolset: New apps are on github, some of the older ones are still in Subversion. It's a Mac shop; most of us use TextMate, but one person uses RadRails and another uses MacVim.
Cheers,
-Sam
[1] Caveat: while I personally place a strong value on testing, the team as a whole does not. I'd love to stack the deck, but changing overall practices will take years.
[2] http://www.ctisolutionsgroup.com/