Live data from Hacker News

How to Hire

blog.samaltman.com

21–30 of 82 posts

Re: How to Hire

#21
Just re-read and saw this: ".... if I were going to jump into....recruiting startups, I would try to make it look as much like personal network hiring as possible..."

Funny about that: I started exactly that with a friend at a Startup Weekend a while ago... we didn't go anywhere with it: http://www.findexpert.co/

We also found that these guys did the same thing: https://ooomf.com/

Re: How to Hire

#22
> Whenever possible (and it’s almost always possible), have someone do a day or two of work with you before you hire her; you can do this at night or on the weekends.

No. Absolutely not.

If a candidate really is as good as you think he/she is, they already likely has a full time job that they're perfectly happy with (as you already well know):

> Often, to get great people, you have to poach. They’re never looking for jobs, so don’t limit your recruiting to people that are looking for jobs.

They might have other compelling offers, and they'll certainly have personal projects, hobbies, and people that are more worthy of their time than this insulting little game. The developers who know what they're worth won't put up with this. Why are you trying to hire the ones who will?

Hire fast / fire fast is fine, but seeing a founder do this is a big red flag for me. It screams indecisiveness, lack of confidence, and mediocrity. Does he try to pull this stunt with everyone he hires? What am I supposed to think of the rest of the team? Can I get behind someone whose hiring process is so driven by fear that he's willing to miss out on the best candidates?

This tactic might help you hire a decent candidate over a mediocre or a terrible one, but you'll be missing out on (or even creating ill will toward) the great candidates. It's already hard enough to get them on board -- why would you make this harder on yourself?

Re: How to Hire

#23

Great thoughts in this one, but missing what I think is the biggest key to hiring correctly in the startups I've been part of is what Paul DePodesta said in Moneyball - ""What gets me really excited about a guy is when he has warts... and the warts just don't matter." I've always thought that hiring in a startup is really like what the A's had to do in Moneyball - you don't have the advantages in terms of money, faci…

This is great insight. Really like the moneyball quote.

Re: How to Hire

#24

And why does Stripe need top developers? To make a REST API for payments? What am I missing?

Nope, you nailed it. There is nothing in payments that requires more dev work than could fit in an Excel function. Patrick admitted as much with this screenshot of the complete Stripe codebase earlier this week: https://twitter.com/patrickc/status/381779690567913472

That said, the pingpong tables aren't going to play themselves...

Re: How to Hire

#25
So much interesting stuff here. For the past couple years, this has been most of my (non-billable) role at Matasano, and we've gotten steadily better at this stuff. So, my thoughts:

›››››› Spend more time

›››››› Have a mission

›››››› Always be recruiting

These three are of a kind for me.

I recommend that you think about hiring the way Patrick McKenzie things about conversion optimization: as a form of marketing that is amenable to engineering. In particular: start tracking it as soon as you possibly can, so you'll have data to pull trends out of. Every effective hiring organization I've talked to has a process for this.

"Have a mission" sounds fuzzy but I don't think that it is. What we've learned is to think a lot about what's good for the candidate about the roles we hire for. We've gotten good enough at this that people on our team can write snappy job descriptions for us: https://news.ycombinator.com/item?id=5640441 --- Sean's a good writer, which helps, but there's also a notion across the team of what we think is great about the work. Having this "through line" for all your recruiting conversations makes it easier not just to sell the job to candidates but also, like any serious sales effort, to qualify prospects.

Being serious about qualifying also gives you another piece of data to track: how well your qualifiers predict how far people get into the funnel. That's been helpful for us too.

›››››› Don't hire

›››››› Get your hands dirty

This times 1000; I think this is the most important piece of advice he has. Jason Fried has been talking about this for years with "The Importance of Hiring Late"; the 37signals motto was "don't hire until you've done the job yourself".

›››››› Focus on the right way to source candidates

I agree in general with the idea here.

I think in particular that "blind" job ads of any sort do poorly. Every venue for ads that has significant visibility is both oversold and also low signal/noise ratio. We don't take job ads seriously anymore.

There's a lot to think about w/r/t poaching employees, particularly from peers. It's important to remember that the ethics of poaching from another company have to be weighed against the best interests of candidates; refusing to talk to someone because they work for a friend's company is probably a fraught decision. On the other hand, remember that you're likely to be at a different company in 2 years, and your long-term relationships with people are important; I wouldn't use inside information I have from peers to poach employees.

I wouldn't work with a recruiter. They also irritate candidates and set up weird incentives.

›››››› Don't compromise

›››››› Look for red flags

This is some of the oldest hiring advice in the industry, for a reason.

Be careful with the "default-to-no" posture if your hiring signals come from employee-driven interviews. Your whole team is rarely on the same exact page about what you're hiring for.

I take specific issue with the "red flag" of people being title-conscious, because there are good reasons some people think about titles: they are (sensibly) concerned about their own career trajectory. The absolute cheapest benefit you can offer an employee is their title, and if they have a rational reason for wanting a better title, why on earth would you refuse to give up some title to get a good candidate on board?

›››››› Have a set of cultural values you hire for

This scares me because I think people don't have a good idea of what a "cultural value" really is, or have aspirational cultural values, like "we'll work as hard as it takes to make our milestones!".

You discover real cultural values bottom-up, by observing what is good and effective about your team. You don't have the value until you've established it in your existing team.

It's obviously important that you build your team out of people who will work well with your team. But it's equally important not to cast too small a net. Among other reasons: it can make you especially susceptible to drama, in a monocultural kind of way.

›››››› Hire people you like

Don't try to do this.

You will be surprised by what you end up liking about people who didn't seem like an immediate "hang out on weekends" fit with your social culture.

When you hire, try to make sure you're hiring on objectively important criteria. Don't kid yourself about how much it matters that a candidate wants to go bar hopping with you after work.

›››››› Fire fast

This is so hard to do. If you haven't actually run a "fire-fast" culture at size yet, I recommend you not assume you'll have this capability. Hire as if it's the life-or-death decision it probably is.

›››››› Put a little bit of rigor around the hiring process.

Put a lot of rigor around the hiring process.

We've steadily standardized every part of our recruiting process and to date we've never looked back at something we standardized or measured and said "you know, this wasn't worth the effort or the cost in flexibility".

We have a funnel with specific objectives at each stage of the funnel. For instance, in 2013, I think it's impossible to interview with us without knowing what our whole hiring process is, and without having the phone number of a company principal to call with questions. It is remarkable how often we hear how much better our process is than the typical company's process, because the things that make us outwardly easier to talk to are so easy. And yet, until a couple years ago, we weren't doing them either.

›››››› Have people audition for roles instead of interviewing for them.

There's nothing I can say about this that hasn't already been said a million times, but I'll make the simplest point against it that I can: the best candidates generally aren't available to "audition" for you, because they're already working full time jobs.

Re: How to Hire

#26
post #15
post #5

“Experienced” people often have higher personal burn rates and sometimes you’ll need to pay them more, but remember that great companies are not usually created by experienced people (with the exception of a few roles where it really matters a lot.) Scary statement for me to read. I'm getting older and worry that the above thinking will eventually cut off cool and even just new opportunities for me. Also hard to audi…

Experience itself is usually a good thing; the problem for startups comes when that experience brings with it things that cause issues with the startup--for example, much higher salary requirements.

"Experienced" employees are also more likely to need/want that cliched work-life balance. They may not want more money, but they may not be willing to work incredibly long hours indefinitely.

Re: How to Hire

#27
post #22

> Whenever possible (and it’s almost always possible), have someone do a day or two of work with you before you hire her; you can do this at night or on the weekends. No. Absolutely not. If a candidate really is as good as you think he/she is, they already likely has a full time job that they're perfectly happy with (as you already well know): > Often, to get great people, you have to poach. They’re never looking for…

The co-working trial is a two way street. Wouldn't a good developer want to make sure the new co-workers are also good?

Re: How to Hire

#28
Overall, I thought this was a great post, but. . .I've always been kind of hesitant about the "hire someone you'd want to hang out with on Sunday" bit. Well, not when I first heard it. . .but over the years, I've come to believe that so many people hire or want to hire people just like them that it weeds out a lot of otherwise qualified people. Yes, I know you want people who share your company's cultural values. . .and that in a small group it's important that people like each other or least don't dislike each other. I guess it depends on how tightly you draw your box. . .and how "boxy" your box is. . .and the alignment between your comapany's values and your personal values.

Re: How to Hire

#29
post #27
post #22

> Whenever possible (and it’s almost always possible), have someone do a day or two of work with you before you hire her; you can do this at night or on the weekends. No. Absolutely not. If a candidate really is as good as you think he/she is, they already likely has a full time job that they're perfectly happy with (as you already well know): > Often, to get great people, you have to poach. They’re never looking for…

The co-working trial is a two way street. Wouldn't a good developer want to make sure the new co-workers are also good?

Hiring has always been a two way street, but in technology the scales are usually tipped against the hiring company. It's simply a numbers game -- there are far more mediocre and poor developers than good ones, and in the current environment, the good ones can basically get hired to work wherever they want.

The co-working trial is an attempt to make the scale more favorable for the company. I can understand the desire for this, but in the current environment, it's almost guaranteed to backfire, as the best developers simply won't put up with it. No amount of wishful thinking on the part of the company is going to change this.

Re: How to Hire

#30
post #25

So much interesting stuff here. For the past couple years, this has been most of my (non-billable) role at Matasano, and we've gotten steadily better at this stuff. So, my thoughts: ›››››› Spend more time ›››››› Have a mission ›››››› Always be recruiting These three are of a kind for me. I recommend that you think about hiring the way Patrick McKenzie things about conversion optimization: as a form of marketing that…

"The absolute cheapest benefit you can offer an employee is their title, and if they have a rational reason for wanting a better title, why on earth would you refuse to give up some title to get a good candidate on board?"

Well one reason [1] might be that by giving the a "big" title it will enhance their resume in the eyes of another company that is looking to poach. Doesn't matter if it works out or not at the new company. You've still lost out.

[1] This is simply pointing out a downside. It doesn't mean what you are saying "cheapest benefit" is not correct.

In all honesty though what stopped me cold was this which appeared at the start:

"Keith Rabois believes the CEO/founders should interview every candidate until the company is at least 500 employees."

And then:

"*In the beginning, get your hands dirty.

Speaking of spending time, you should spend the time to learn a role before you hire for it. If you don’t understand it, it’s very hard to get the right person. The classic example of this is a hacker-CEO deciding to hire a VP of Sales because he doesn’t want to get his hands dirty. "

How much time is proposed to spend on learning the job of a company where you are supposed to hire (he agrees with the statement) "the first 500 people".

Post reply on HN