The (Real) 11 Reasons I Don’t Hire You

(With 🙏 to Joe Beda, whose brilliant idea for a blog post this was.  Thanks for letting me borrow it!)

Interviewing is hard and it sucks.

IMG_8461In theory, it really shouldn’t be.  You’re a highly paid professional and your skills are in high demand.  This ought to be a meeting between equals to mutually explore what a longer-term relationship might look like.  Why take the outcome personally?  There are at least as many reasons for you to decide not to join a company as for the company to decide not to hire you, right?

In reality, of course, all the situational cues and incentives line up to make you feel like the whole thing is a referendum on whether or not you personally are Good Enough (smart enough, senior enough, skilled enough, cool enough) to join their fancy club.

People stay at shitty jobs far, far longer than they ought to, just because interviews can be so genuinely crushing to your spirit and sense of self.  Even when they aren’t the worst, it can leave a lasting sting when they decline to hire you.

But there is an important asymmetry here.  By not hiring someone, I very rarely mean it as a rejection of that person.  (Not unless they were, like, mean to the office manager, or directed all their technical questions to the male interviewers.)  On the contrary, I generally hold the people we decline to hire — or have had to let go! — in extremely high opinion.

So if someone interviews at Honeycomb, I do not want them to walk away feeling stung, hurt, or bad about themselves.  I would like them to walk away feeling good about themselves and our interactions, even if one or both of us are disappointed by the outcome.  I want them to feel the same way about themselves as I feel about them, especially since there’s a high likelihood that I may want to work with them in the future.

So here are the real, honest-to-god most common reasons why I don’t hire someone.

1. Scarcity

IMG_7488If you’ve worked at a Google or Facebook before, you may have a certain mental model of how hiring works.  You ask the candidate a bunch of questions, and if they do well enough, you hire them.  This could not be more different from early stage startup hiring, which is defined in every way by scarcity.

I only have a few precious slots to fill this year, and every single one of them is tied to one or more key company initiatives or goals, without which we may fail as a company.  Emily and I spend hours obsessively discussing what the profile we are looking for is, what the smallest possible set of key strengths and skills that this hire must have, inter-team and intra-team dynamics and what elements are missing or need to be bolstered from the team as it stands.  And at the end of the day, there are not nearly as many slots to fill as there are awesome people we’d like to hire.  Not even close.  Having to choose between several differently wonderful people can be *excruciating*.

2.  Diversity.

No, not that kind.  (Yes, we care about cultivating a diverse team and support that goal through our recruiting and hiring processes, but it’s not a factor in our hiring decisions.)  I mean your level, stage in your career, educational background, professional background, trajectory, areas of focus and strengths.  We are trying to build radical new tools for sociotechnical systems; tools that are friendly, intuitive, and accessible to every engineer (and engineering-adjacent profession) in the world.

How well do you think we’re going to do at our goal if the people building it are all ex-Facebook, ex-MIT senior engineers?  If everyone has the exact same reference points and professional training, we will all have the same blind spots.  Even if our team looks like a fucking Benetton ad.

3.  We are assembling a team, not hiring individuals.

We spend at least as much time hashing out what the subtle needs of the team are right IMG_5072now as talking about the individual candidate.  Maybe what we need is a senior candidate who loves mentoring with her whole heart, or a language polyglot who can help unify the look and feel of our integrations across ten different languages and platforms.  Or maybe we have plenty of accomplished mentors, but the team is really lacking someone with expertise in query profiling and db tuning, and we expect this to be a big source of pain in the coming year.  Maybe we realize we have nobody on the team who is interested in management, and we are definitely going to need someone to grow into or be hired on as a manager a year or two from now.

There is no value judgment or hierarchy attached to any of these skills or particulars.  We simply need what we need, and you are who you are.

4.  I am not confident that we can make you successful in this role at this time.

We rarely turn people down for purely technical reasons, because technical skills can be learned.  But there can be some combination of your skills, past experience, geographical location, time zone, experience with working remotely, etc — that just gives us pause.  If we cast forward a year, do we think you are going to be joyfully humming along and enjoying yourself, working more-or-less independently and collaboratively?  If we can’t convince ourselves this is true, for whatever reasons, we are unlikely to hire you.  (But we would love to talk with you again someday.)

5.  The team needs someone operating at a different level.

IMG_4749Don’t assume this always means “you aren’t senior enough”.  We have had to turn down people at least as often for being too senior as not senior enough.  An organization can only absorb so many principal and senior engineers; there just isn’t enough high-level strategic work to go around.  I believe happy, healthy teams are comprised of a range of levels — you need more junior folks asking naive questions that give senior folks the opportunity to explain themselves and catch their dumb mistakes.  You need there to be at least one sweet child who is just so completely stoked to build their very first login page.

A team staffed with nothing but extremely senior developers will be a dysfunctional, bored and contentious team where no one is really growing up or being challenged as they should.

6.  We don’t have the kind of work you need or want.

The first time we tried hiring junior developers, we ran into this problem hardcore.  We simply didn’t have enough entry-level work for them to do.   Everything was frustratingly complex and hard for them, so they weren’t able to operate independently, and we couldn’t spare an engineer to pair with them full time.

This also manifests in other ways.  Like, lots of SREs and data engineers would LOVE to work at honeycomb.  But we don’t have enough ops engineering work or data problems to keep them busy full time.  (Well — that’s not precisely true.  They could probably keep busy.  But it wouldn’t be aligned with our core needs as a business, which makes them premature optimizations we cannot afford.)

7.  Communication skills.

IMG_6114We select highly for communication skills.  The core of our technical interview involves improving and extending a piece of code, then bringing it in the next day to discuss it with your peers.  We believe that if you can explain what you did and why, you can definitely do the work, and the reverse is not necessarily true.  We also believe that communication skills are at the foundation of a team’s ability to learn from its mistakes and improve as a unit.  We value high-performing teams, therefore we select for those skills.

There are many excellent engineers who are not good communicators, or who do not value communication the way we do, and while we may respect you very much, it’s not a great fit for our team.

8.  You don’t actually want to work at a startup.

“I really want to work at a startup.  Also the things that are really important to me are: work/life balance, predictability, high salary, gold benefits, stability, working from 10 to 5 on the dot, knowing what i’ll be working on for the next month, not having things change unexpectedly, never being on call, never needing to think or care about work out of hours …”

To be clear, it is not a red flag if you care about work/life balance.  We care about that too — who the hell doesn’t?  But startups are inherently more chaotic and unpredictable, and roles are more fluid and dynamic, and I want to make sure your expectations are aligned with reality.

9.  You just want to work for women.

I hate it when I’m interviewing someone and I ask why they’re interested in Honeycomb, IMG_3865and they enthusiastically say “Because it was founded by women!”, and I wait for the rest of it, but that’s all there is.  That’s it?  Nothing interests you about the problem, the competitive space, the people, the customers … nothing??  It’s fine if the leadership team is what first caught your eye.  But it’s kind of insulting to just stop there.  Just imagine if somebody asked you out on a date “because you’re a woman”.  Low. Fucking. Bar.

10.   I truly want you to be happy.

I have no interest in making a hard sell to people who are dubious about Honeycomb.  I don’t want to hire people who can capably do the job, but whose hearts are really elsewhere doing other things, or who barely tolerate going to work every day.  I want to join with people who see their labor as an extension of themselves, who see work as an important part of their life’s project.  I only want you to work here if it’s what’s best for you.

11.   I’m not perfect.

IMG_5224We have made the wrong decision before, and will do so again.  >_<

In conclusion…

As a candidate, it is tempting to feel like you will get the job if you are awesome enough, therefore if you do not get the job it must be because you were insufficiently awesome.  But that is not how hiring works — not for highly constrained startups, anyway.

If we brought you in for an interview, we already think you’re awesome.  Period.  Now we’re just trying to figure out if you narrowly intersect the skill sets we are lacking that we need to succeed this year.

If you could be a fly on the wall, listening to us talk about you, the phrase you would hear over and over is not “how good are they?”, but “what will they need to be successful?  can we provide the support they need?”  We know this is as much of a referendum on us as it is on you.  And we are not perfect.

But we are hiring.  ☺️



The (Real) 11 Reasons I Don’t Hire You

26 thoughts on “The (Real) 11 Reasons I Don’t Hire You

  1. Photographing yourself with ice cream is freaking brilliant. You always look happy and stoked. Of course you do! You’re holding ice cream!

  2. mwidlake says:

    Thank you for an interesting and thoughtful article on why “failing an interview” is not failing. Well, not usually 🙂 An interview should always be a two-way affair I believe, and both sides need to fit, so not getting the job is often the best outcome.

  3. Ibod Catooga says:

    But would you hire a DUNKEY to life a fish out of the Oceans? NO YOU WOULD NOT. Then how do you know not to hire a TURTLE to fly to SPACE the FINAL FRONTIERS?

    No there is no answer. I just like pachinko.

  4. virummagum says:

    I think it’s important to not hire someone who is centered on the spectrum of dis/agreeability. If they always agree or always disagree with management, I think it’s a major weakness.

    1. I think it’s important to demonstrate that you value and listen to people’s feedback, negative or positive, and create a safe space for them to express it. I don’t think people develop those characteristics in a vacuum, and I don’t think they are immutable, either.

  5. It was a pleasure to read your article and to look at the icecream. I was counting how many icecream you ate while I was thinking about not taking myself so seriously. Thank you for the article. These are kind and soothing words for anyone looking for a job 🙂

  6. I can certainly relate to this.

    As you can see from my profile pic, I’m your fairly average middle-aged (well, perhaps a bit beyond that) white guy with beard & glasses. I’ve been in testing for nearly 25 years, I don’t have any formal qualifications in the field because they hadn’t been invented when I was starting out, and (despite age discrimination being illegal in the UK) I’ve had difficulties getting work because of perceptions., (One rejection I had from a company said that I was a “poor cultural fit” for the office. It was the most monocultural office I’d set foot in for probably 20 years; but I would have been far and away the oldest person there if I’d got the job.)

    The company I now work for recruited me for that very same reason! They had a team of five testers, but they were all of a certain age, mainly brought up through the IT industry, and mainly on their first or second roles in systems development and testing. Whereas the major strength I could bring to the team was a lot of varied business experience in different industries. The three years I’ve been in this role have been just a daily process of me learning new awesome stuff from the other testers and me teaching them old awesome stuff from the University of Life.

    We keep being told that we are developing products for a world-wide market that consist of – well, everybody. So the team that produces those products has to be the widest imaginable cross-section of people so that those products can fit the needs of everybody. End of.

    Having said that, I can also relate to your fourth reason: “I am not confident that we can make you successful in this role at this time.” I certainly had that. I applied for a role with a major UK clothing manufacturer and retailer. They were offering a nine-month rolling contract as they were engaged on a five-year project to refresh their bricks-and-mortar store systems; the whole end-to-end process, upgrading and integrating EPOS, stock control, financials, employee reward, HR, facilities management and data comms. I was upfront in my interview over my non-standard skills set, but they were enthusiastic and said that they could accommodate a certain steepness of my learning curve. I left the interview feeling quite upbeat about it.

    Except that two days later, the company posted a major profits warning as the downturn in High Street sales as opposed to online began to take hold. All the company’s projects were reviewed; and it turned out that the nine-month rolling contract that was on offer was taken away and replaced with a six-month fixed term contract, extension being entirely dependent on high-level decisions over the progress or otherwise of the store refreshment project. on those grounds, they said, they couldn’t accommodate my learning curve under the new economic reality. What was an acceptable level of knowledge in a nine-month timeframe with the possibility of renewal wasn’t possible in a six-month timeframe with no idea whether anyone would get renewal at the end of it.

    I keep saying to people looking for work that sometimes, it’s not your fault. Sometimes, the moment just isn’t shaped that way. And eventually, the pieces will fall into the right place and you become the right candidate for the right job.

Leave a Reply to A Conversation About Tech Jobs, Mobile Development, and Blogging – Chelsea TroyCancel reply