It's Not Rocket Science...
Shame, because all your best ruby developers would be trying to solve the problem if it was. Rather, it’s a series of critical little steps that need to be done well in order to get you the results you want.
Why? There are thousands of companies, big and small, all trying to cut the line and get in front of the best ruby developers. So how do you stand out? SHOUT LOUDER? Nope, you just have to work harder and be scientific. Here’s how.
The 3 Stages
- Scope the Job – “Does the role make sense?”
- Message for Impact – “Will Ruby on Rails developers read my post?"
- Source Candidates – “Where do they hang out?”
Whether you take on the hiring yourself, turn to a recruiter, or delegate it to your internal HR department, the quality of your developer will depend on these three steps. Make sure you’re approaching each optimally.
1: Does this Rails Job Make Sense?
Recruiters often talk about “white elephant” or “unicorn” searches in reference to searches that have limited to non-existent candidate flow.
This is critical to avoid because the first two steps are all about attracting as many quality candidates as you can. Before we get into how you should scope your job to be realistic, let’s look at a few common mistakes.
Example 1: The Linux and Windows Expert …
Situation: You are a SAAS company that sells analysis tools. The calculations were created by a long gone PhD who only wrote in C# which currently runs on a Window machine, and it’s connected to your Rails application — the primary point of interaction with your clients.
Usage is taking off and you want an expert in both Linux and Windows to ensure that both systems will scale securely and respond to alerts at 3am on a Sunday morning. Let’s write up a post for just that. We know what we want right? Well let’s look at the space of developers with those skill sets …
- Admins tend to gravitate to Linux OR Windows so that creates the limited overlap.
- As they get more experienced in one, they have less time to be familiar with the other.
- Prying this person away from their job would most likely be hard and prohibitively expensive.
- If you can afford it, consider creatings two positions and hiring for each.
- If you can only afford one, what’s more important: Linux or Windows? I’ll take a guess that Linux is the way that this company is going. You could train that person in the Windows systems with the help of a consultant as needed.
- How about getting rid of the Windows setup? Talk to your CTO and find out if there’s a roadmap for this. It might be as simple as having the C# code run under the Mono project.
Example 2: Expert Developer who Fixes Routers…
- Situation: “We need a Ruby on Rails developer in San Francisco with TDD and BDD experience, who understands MySQL and NoSQL databases and can solve general IT questions.”
- Problem: Does an awesome developer want to be resetting your router? Do you want the developer’s deep meditative programming state to be fragmented by IT questions?
- Resolution: Split the role. Solve the office infrastructure issues another way.
Example 3: No Money Seeks Unaffordable Developer…
- Situation: “We’re a self funded startup in NYC looking for a fulltime, on-site CTO to join our team. We have limited funds but are willing to offer some equity.”
- Problem: Anyone with a high level of Ruby on Rails experience has a huge opportunity cost if they’re based in NYC.
- Resolution: Explore telecommute candidates who you could fly in once a quarter. Costs go down and you’ll raise more interest from the community. You could also position the job as a CTO in training and expect the person to grow into the role.
Don’t Over Specify the Role
Scoping is about challenging what you want in a candidate to increase application flow-rate. Note that the big problem here is over specifying. Don’t let the Ruby on Rails developer you would love to hire filter themselves out at this stage. If you are getting limited responses, you need to cast a wider net.
Many smart and large organizations get this step wrong. Tragically, they often talk themselves into why the role needs to be just so, and yet they never realize that it causes their dearth of candidates. This step is key. If you keep asking for white elephant, Ruby on Rails developers, you might as well not bother asking.
Getting a handle on what makes sense from a scoping perspective takes tough love and discipline, but hopefully the pitfalls of over-specifying are clear. Now that you’re casting a wider net into the pool of ruby programmers, let’s talk about crafting your position in a way that appeals to candidates.
2: Messaging for Impact
Once you’ve got the scope of your job outlined, you need to work on how to message it for maximum impact. Remember that however much you might think this is an awesome opportunity, you need to see it from their side.
Let’s say you are RubyNow.com, looking for a new Ruby on Rails developer...
How do you Stand Out?
Posting on a niche jobs board is an important first step. Solely by doing this, you’re limiting the number of daily posts by a factor of 10 or 100. Still, you have to understand that they might only look at your job post for fractions of a second before making a decision whether to click and read more. Let’s first talk about what content you should include and then how you should structure it.
What does a Ruby on Rails Developer care about...
- What kind of cool tech will they use and learn? Haml, Sass, Coffeescript, Bootstrap.js, Ember.js?
- What kinds of cloud patforms and CMS software? AWS, Chef? Puppet? JRuby? JBoss?
- What kinds of databases? PostgreSQL? MongoDB?
- What projects will they have a chance to work on?
- What longer-term problems are you tackling that they might be excited about?
- What’s exciting about what you do and what they will do?
- Will they work on their own or in a team?
- Who’s on the team? How big is it? Do they like what they are doing?
- How will you treat them? Will you listen and/or want their opinion?
- Can they work from home? If so, to what extent? What’re the expected hours?
Building a Career
- Are you a name brand company that will improve their resume?
- Will you let them contribute to open source projects?
- What mentorship can you offer within the company?
If you’re a startup...
- How much are you going to be paying? (how explicit do you want to be?)
- How much equity will you be giving out? (how explicit do you want to be?)
- How well funded is the company? Justify why they should invest in the company with their time and experience.
If you’re an established company...
- How much are you going to be paying? (how explicit do you want to be?)
- Be clear about the risk reward profile and why that’s what a lot of people want.
- What’s a common career path at your company? What could the candidate expect?
- Talk about investing in them: training, conferences, sick days, work schedule,etc.
That’s just a non-exhaustive list of things you can comb through to get started, but really think about why someone might be excited to work with you.If you're not excited by the post or the position, why would they be?
How Should I Structure My Rails Job Post?
No two job posts should be the same, but they often are. Let’s talk about possible sections, their respective weightings and how you can make your post stand out in the crowd.
Ruby on Rails Job Post Section Ideas
- About You: Keep this short and snappy, don’t lose their attention
- What They Will Do: Tell a story about the kinds of projects they could work on
- Who's on the Team: Give them a picture of a day they can get excited about
- Cool Technologies: what technologies they will touch, use and learn
- Who Are You Looking For: what are your requirements for the position
- Who Should Apply: Rails Noobs, Rails programmers with 2 years of experience, developers looking for a career change, etc.
- Salary Expectations: Don’t leave a vacuum. Even if you don't give a concrete number, at least give some guidance
Thinking Fast and Slow
There's a lot of neuroscience out there that says that people think with a quick, emotional, intuitive "monkey brain" and a slow, analytic "human" brain. Your job post needs to satisfy the monkey brain long enough to engage the analytic brain. Here are a couple ways to accomplish that:
- Formatting is important to keep a good visual flow. Squint at the page see if it’s friendly.
- Use Bold to keep the eye scanning the page for goodies to read. Note your brain will wander around the page and then dig in. Think about a kid browsing a Christmas tree looking for the easy candy!
- Avoid using business speak. Use actual information vs. bland phrases.
3: Sourcing Candidates
Now that the content is written, it’s time to get the word out. Below is a table that brakes down the different methods based off effort and return. Top right is lowest effort with highest return. Let’s review...
Win the Fast-Cheap Points First
Post your job to a niche Ruby jobs board. It doesn’t cost much, but every Ruby on Rails developer that stops by will see your post. Certain Jobs Boards will also email individual jobs to their list of opt-in ruby programmers and tweet it to all of their followers. A loud megaphone is important, but RubyNow isn’t a magic developer-magnet that will tractor beam candidates into a terrible job post. If you didn’t get steps 1 and 2 right, it doesn’t matter how big the megaphone is, you’ll still not get what you’re looking for. That said, you can post multiple times to test different recruiting strategies and then adapt your post for other sourcing channels.
Email Your Friends and Tech Friends
Get the word out on your and your team's network. Ask them to email around and tweet to their friends about the position. It’s a smaller network, but the connection should result in higher impact.
Maximize your ROI
Work through the other squares to get the most impact from your valuable time and resources. This isn’t meant to be a complete list, but a guide for your thinking and your approach with regards to your Ruby on Rails developer search.
RubyNow is Here to Help
If you have questions, please reach out. I’ve recently taken over RubyNow and have a background as an active Rails developer, entrepreneur who’s hired many developers, and as a reluctant recruiter, asked by my many technology friends who need help building out the amazing technologies that we are so lucky to be surrounded by.