Hi, I’m Josh Symonds

I blog about Ruby on Rails, coding, and servers

Why I’m Not Applying to 37Signals (but Why You Should)

Reading time 5 minutes

In case you haven’t heard…

Rails Programmer: 37Signals

Yes, it’s true: Willy Wonka is going to grant one lucky golden ticket holder a tour of the chocolate factory. And then you get to stay there until you somehow get tired of working at one of the coolest companies on planet Earth – which, to carry my analogy, would probably be as likely to happen as getting bored of eating chocolate. If you’re into Rails, you’d have to be stupid to not at least consider such an amazing opportunity.

So I did, and because I’m a programmer I carefully enumerated my thoughts. If you’re on the fence at all about taking the plunge, maybe my reasoning will help you. Or horrify you – either way, you’ll have an opinion!

Why You Should Apply

  1. They’ve literally written books about how great it is to work there.

    If you haven’t read Rework you probably should. 37signals is immune to typical corporate bullshit: you won’t find stupid meetings, outside investors, or anyone burning the midnight oil here. You’ll find work. Great, meaningful, empowering work. When you get right down to it, isn’t that what people actually want out of their jobs? And you know 37signals is 100% dedicated to keeping it that way, since, well, as I said, they literally wrote the book on their business practices. They’re committed not only to the customer experience, but the employee experience. And that counts for a lot.

  2. The Man Himself.

    For those who think that intellect is at least as sexy as looks, this man would be the January pinup for the Men of 37Signals wall calendar I’ve been lobbying so hard for them to make. He’s the inventor of Rails, he’s highly opinionated, and he even drives race cars! Assuming he takes a shine to you, what’s not to like? I imagine that, if you announced to a room of programmers, “I work with DHH,” there would be a brief hush and then everyone would be talking over each other. One would say, “That man is a crazy person!” And another, “He’s the greatest programmer to ever draw breath!” There’s not a lot of people in the world you can work with who are smart, polarizing, and have invented the application framework you use in your day-to-day job. (And drive race cars.) You should jump at the opportunity to work with DHH.

  3. Fame & fortune await.

    Or, well, at least fame does. I have no idea what 37signals would offer for this job, though I bet they aren’t stingy on the paychecks. But being part of 37signals (while once again polarizing) ensures you notoriety in the world of Rails in particular and programmers in general. Most people you’ll talk to will know where you work. Your title and position will be meaningful – and also note that your personal fame will skyrocket. If you wanted to suddenly gain a few thousand Twitter followers (without having to pay $5.00), getting this job would be a great way to do it. Keep in mind too that, when you’re a 37signals alum (unless you intend to be a lifer), having “Programmer at 37signals” on your resume will look even more stellar than all those follower numbers.

  4. Work with the best – and be the best.

    37signals’ programming team is the crème de la crème of the Rails world. You’ll be challenged constantly to be just as great as they are. Imagine an environment where you might be the weakest link – doesn’t that thought thrill you? To work with the smartest, most dedicated people in the business? People who are at the apex of their field? You’ll grow and change and learn in ways you probably never expected, all because 37signals is a team of the best. And you can also take secret joy in the thought that, since they accepted you, they must see some of the same greatness in you as well.

Why You Shouldn’t

  1. You’re not the best.

    But in a team of greats, even being great is not enough – or, to use a more colorful metaphor, in a constellation with stars as bright as 37signals, you have little hope of shining brighter. I hear Google engineers suffer from similar problems, and also University of Chicago undergraduates. Coming from places where you were the best, now you’ll be just another programmer. For some, the knowledge that they’re there is enough: but there are lots of places with amazing teams, and some where the teams have more room for you to stand out than in 37signals (or Google or the U of C). These places are waiting for you, though they don’t yet have the fame and reach of 37signals. It’s up to you to find them!

  2. While it’s a great company, it’s still a company.

    I love startups. In a startup I’m not just a programmer: I do lots and lots of work with computers, it’s true, and most of that is programming. But I’m also responsible for marketing, design, number crunching, tech support, user experience, and when you get right down to it a little bit of everything else too. In a small group you must be a talented polymath, and what you don’t know how to do you learn quickly. 37signals is 36 people big and they were founded in 1999. Personally speaking I like growing outside of my computer-walled comfort zone. How much of that would you get at 37signals? That’s not an easy question to answer, but I would bet not a whole lot – or, at least, less than you would somewhere else.

  3. Go do it yourself.

    While 37signals is a great company, there’s nothing inherently special about it. They make CRM software, and while that’s an interesting problem space, there’s tons of fascinating questions to answer out there – questions that can only be answered through excellent software! The point of Rework is that there’s no real magic in 37signals that people who are smart and dedicated can’t create themselves. In my heart, I feel like DHH would look down on you for joining a corporation instead of becoming an awesome entrepreneur yourself. Sure, you’d be joining his company, but ultimately, if you’re so great, why aren’t you out there making a name of your own, rather than riding on someone else’s coattails? Even if they’re his.

  4. Fame & fortune await!

    If you’re a gainfully employed Rails programmer, most likely you make a comparable amount to what 37signals could offer you, unless they’re dramatically out of line with what the market pays. And while they’re famous (and you would become more so, too, if you joined them), if you want to be a programming luminary in your own right, you can’t join stars that have already risen. Do you really want fame and fortune? Then you don’t want to join 37signals. They’ve already arrived there, and while there’s money to be made and people to impress, if you want to to make it big you need to take a risk and not join an established, successful company… regardless of how awesome they are.

In The End

At the point I’m at in my career, 37signals – while incredibly appealing – isn’t the right choice for me. I hope to conquer the world myself, rather than join victorious conquerers. But where I was at five years ago? I would have moved heaven and earth to swing an interview there. If you haven’t picked this up already, they’re my programming heroes: and they should be yours too, because they care about everything that’s important in this industry. So if you’re at all interested in being a programmer among programmers, then 37signals is calling you.

If not, I look forward to seeing what you create in the future, because I bet it’ll be stellar.