The three-dimensional engineer

Hiring scrappy, creative people who bring their whole selves to work.

I’m hiring for a few engineers right now: five Ruby on Rails positions (most of them senior), two JS positions, and a quality engineer. More than a few people I’ve spoken to for these roles have apologized to me for coming from different backgrounds and not having been the product of a conventional CS track.

There’s no need to apologize for this. At all. In fact, I really like working with people who come from non-traditional backgrounds and/or small startups. Conversely, I’m not at all swayed by whether people went to top CS schools (or did CS at all) or are an an alumnus of a Fortune 500 tech company. Perhaps it’s worth exploring why; it seems obvious to me, but maybe isn’t to everyone.

The short answer is: it’s about priorities and values. Big companies and well-established CS tracks tend to (but don’t always!) lead to a certain kind of templated thinking that doesn’t necessarily translate to a smaller startup environment. People from more creative backgrounds or who have worked on smaller startups tend to be focused on making an outsized impact on a real, human problem using a broader set of skills, rather than developing a niche skill and working their way up the corporate ladder.