Here at 99designs we're what you'd call a polygot shop – we've got a mix of PHP, Ruby, Python, and Go in production. When we say production, we mean at serious scale. Our mission is to connect the world with great graphics designers wherever they are, something which we do quite a bit of.
Right now we're on a hunt for a developer who can Help Us Out™. Usually we advertise for a generalist "web developer" and then find the right place for them internally based on their strengths. This time we're trying to hire a very specific skill set for a very specific project. The skills are Ruby and Rails, and the project is building out our new payments service.
Company wide we're transitioning to having small, decentralised teams with their own product lines and the attendant SOA/Platform to support that goal. Last year we had great success with creating our single sign-on system in Go, and this year we're rounding out the platform with a shared payments system in Rails*.
This new service will enable us to spin up new product lines or move into new international markets quickly. Between the iterative approach we're taking to replace our old payments system and the UX for both the customers using the service and the developers integrating it there are some exciting and interesting problems to solve on this project.
The existing team on project are very strong developers with good knowledge of the problem space but not a lot of Rails experience. We need a mid to senior developer to come in and help "set the tone" of the codebase. That role had been filled within the team by me (John Barton, internet famous as "angry webscale ruby guy"), but I've since been promoted to manage the engineering team as a whole and between all the meetings and spreadsheets it's hard to keep up the pace of contribution that this project deserves.
You'll need to be the diesel engine of the team: churn through the backlog turning features into idiomatic and reliable Rails code at a steady cadence. There are opportunities to coach within the team, but even just creating a sizeable body of code to be an example of "this is how we do it" (cue Montell Jordan) will keep this project on track.
The quality of the codebase after 3 months of progress is high. We don't believe in magic make-believe numbers here, but right now we're sitting on a code climate GPA of 4.0. If you're a fan of Sandi Metz's Practical Object Oriented Design in Ruby or Avdi Grimm's Objects on Rails you will feel right at home in this codebase.
If this is something you're interested in and think you can help us out with, check out the job ad
*You may be wondering "why not go?" for this system. The short answer is that there's enough complexity in the business rules that the expressiveness of Ruby is very useful, and being a financial project moving numbers around in a database is very important and ActiveRecord is more mature that any of the ORMs available in Go right now. I'm happy to elaborate on our line of thinking during your interview 😉