I started running Product and Engineering at Change.org late this past April. One of the things that attracted me to the company was how successful they had been with such a small, focused staff. For example, my colleague Mark Dimas had single-handedly built the entire web site. As an engineer, Mark’s expertise is both broad and deep, yet amazingly, he seems to have almost no ego.
After assessing things within the organization in my first few weeks there, I realized that not only was there some technical debt (as can be expected when only one person works on a codebase), but in addition, there was quite a bit of organizational debt. Not only had Mark built the whole web site, but he was also doing network and system operations, technical support, and a whole array of other things to keep the web site running smoothly. I feared what might happen if he ever got “hit by a bus”.
I am an entrepreneur. My favorite part of entrepreneurialism is team-building. And my favorite part of team-building is the beginning stages. People who have built early-stage teams before will most likely either smile or cringe at that statement … they’ll smile because they know that the early-stage team are the foundation for the whole future. They’ll cringe because they know how detrimental it can be to hire the wrong people. The early-stage team members are the metaphorical Atlas upon whose shoulders the world rests. Hiring the right people at the beginning will go a long way toward making a team successful. Hiring the wrong people … well, I’ve done it, and let me tell you: it isn’t pretty.
I can best illustrate my point with data I’ve collected about hiring engineers here at Change.org. I’ve looked at 127 resumes. From those 127 resumes, I’ve set up 72 phone screen interviews. Of those 72 phone screens, I’ve invited 9 engineers on-site for in-person interviews. Of those 9 engineers, just 3 made it past all of the rounds of in-person interviews and received offers. And of those 3 offers, just 1 engineer accepted. For those of you not good at math, that’s about a 0.08% success rate on resumes received. 127 –> 72 –> 9 –> 3 –> 1 == 0.08%!
Some of you may be saying to yourselves, “That’s impossible — certainly there must have been more than just 3 viable candidates from a pool of 127!” To which my response is, “No, there weren’t.” When we are evaluating candidates, we consider mission-alignment (we are Change.org, after all), team fit, and skills and experience (in that order). We have met with a few candidates who had deep skills and expertise, but were not a team fit. Other folks seemed like they’d be great to work with, but didn’t quite have the depth of experience we need from them at this stage. With such a small team, we need folks who can hit the ground running, folks who aren’t intimidated by a large codebase, a large data set, or intense uptime requirements. We’re rapidly approaching 2 million users and get about 100 thousand new signups every month. We are profitable and need to stay that way. We need hardcore hackers, not hobbyists.
We are, right now, feeling the burdens of being understaffed. Still, .
Are you a Ruby / Rails hacker? Do you want to use your skills to make the world a better place? Would you like to work for someone who has (in the past) made hiring mistakes and understands that understaffed beats wrongstaffed? Drop me a line. We’d love to meet you.