Getting a job at Return Path is harder than getting into a good college. We have 400 employees, but we got there by identifying 30,000 potential hires, vetting them, negotiating a deal with the ones we liked, implementing a rigorous, 90-day onboarding process, and capping it off with a 90-day review to make sure that they'll make it over the long haul. All the while, our competitors were trying to do the exact same thing—as were hundreds of other companies drawing from the same pool of talent. It's no wonder that hiring is one of the many full-time jobs you take on when you become a startup CEO.
Retaining good people has always been at the top of my list, even in the dark days. But hiring presents some real challenges. Many of these aren't unique to startups—it's always tough to find A players—but there are three things I've observed that are uniquely tough about hiring in an entrepreneurial environment:
Hiring Friends and Family
Hiring friends or family members can be great for you and for the organization. You want people around who you trust. You want people around who you've seen work before, who you've already gone through a war or two with. If you're going to work a million hours a week on a startup, doing it with friends can make it much more worthwhile and fun.
That said, if you don't handle it correctly, hiring friends or family members can be a disaster for you and for the organization.
When you bring friends and family members into your organization, you need to be up front and transparent with other employees about it. You need to let them help you make the decision about who to hire—even more so than usual in this case. And you need to let them know up front that your intent is to treat these people just like any other employee, and that you want everyone else's input if they feel like you're not doing just that.
Before you hire friends or family members, you have to tell them that there won't be any difference between how you manage them and how you manage everybody else at the company. They are going to be held to the same standards as everyone else, and you are their boss just like everyone else, and they shouldn't join in the first place if they're uncomfortable with those realities. Even if you have this “prenup” conversation, firing a friend or family member is an agonizing process. You need to prepare extra for these conversations; make damn sure you're making the right call; but also be wary of taking too long to make the call, because your credibility as CEO hinges on it, 10 times as much as if the person weren't a friend or family member.
I've never hired a family member other than having my brother Michael intern for us for a semester while he was in college and having Mariquita do a little bit of highly specialized consulting for us. I don't think I ever will ever do more than that. It's difficult enough for other employees to come to you as the CEO and criticize your friend, let alone your wife or sibling.
Most of the managers on your team are making tactical decisions that can be forecasted and planned for in advance. This includes hiring: if you're planning to roll out a mobile app in the following year, you need to start recruiting mobile developers 6 to 12 months ahead of time. CEOs, by contrast, focus on long-term, strategic planning. When those plans change or go into a new phase, you'll find yourself needing an entirely new set of talent on very short notice. You can either scramble to find those people at the last minute, or you can go back to a contact you made years ago—just in case.
Return Path Head of Recruiting Jen Goldman on the CEO's Role in Recruitment
Jen Goldman is Return Path's long-time lead recruiter extraordinaire. Given how much of a CEO's time is devoted to recruitment, it's no exaggeration to say that she's played a significant role in any success I've had. Here, she discusses how CEOs can help recruiters succeed in their roles.
At all companies, of all sizes, recruiting is the responsibility of every employee. A key attribute of recruiting success is having everyone in the company understand their role in finding, attracting, and selecting great talent. The CEO's role is particularly important, and very unique. There are three areas in particular that CEOs should focus their efforts.
Recruiting, sourcing, interviewing, and checking references are all a part of the hiring process that a CEO can make a big impact on at any time, and especially as a company is in growth mode.”
Jen Goldman, Head of Recruiting, Return Path
For the most part, your managers can focus their recruitment efforts around specific needs: your chief financial officer (CFO) needs a new controller, your chief technology officer (CTO) a database specialist, your head of sales needs two new reps. CEOs have to be engaged in general recruiting all the time.
This is a subset of being “in-market,” and it's just as important as keep tabs on your customers and your competition. If a friend, board member, or colleague recommends somebody, meet with them—even if you don't need someone with their skill set at the moment. If you don't have the time, send one of your senior people. You never know when you'll find a great executive that you want to hire now and find a home for later. This is the same philosophy as Jim Collins's “Get the right people on the bus” theory from Built to Last.
There's nothing disingenuous about taking these meetings even if you're not hiring: when a need arises that this person might fill, you will get in touch. (It's important to be up front about this: don't give people the impression that they're interviewing for an active position if that's not the case.) You're just being honest when you say that you don't know when that will be. We've been able to fill more than a few key senior roles over time very quickly, and without having to use expensive recruiters, by being actively in-market all the time.
In addition to reference from trusted colleagues and friends, there are five major areas you should focus on when thinking about recruitment:
The recruiting process usually focuses on the skills and requirements listed in your job listing. Is this person a good developer? A high-performing salesperson? A talented marketer? Ask a potential hire, and they'll certainly say yes. If you want the real answer, you have to depend on two things: references (both on and off the list provided by your recruit) and domain experts. As Opsware co-founder and technology VC Ben Horowitz once pointed out, you can't determine whether someone is going to be an effective head of Japanese sales if you don't speak Japanese. Find a domain expert, and let them answer that question.
As a CEO, your goal should be to look for cultural fit and engagement—the X factors. The best way to do so is by interviewing candidates yourself.
The Cleveland Airport Test
Most years, we have a board/management offsite for a full 24 hours. It's a great time, and the conversation is always a nice blend of business and personal.
It was during one of those offsites that I realized just how much I genuinely enjoy the company of the people I work with. Whether it's my senior staff, our board, or anyone else at Return Path, we are not all the same personality type, but we can manage to have fun together as well as productively thinking about and discussing work.
With generic assumptions of eight hours of sleep a night and eight hours of work a day (neither one being true of course, but canceling each other out somewhat), we spend half our waking hours on the job. So we might as well choose to work with people that we get along with! That doesn't mean everyone we hire at Return Path has to be like-minded or have the same sense of humor. But it does mean that we look for people who have that spark in their eye that says “I get it”; it means we want to find people who are articulate, have strong convictions and aren't afraid to speak their mind; and it means we screen for people who can be lighthearted and don't take themselves too seriously when we recruit, interview, and hire.
Think about that “half your waking hours” thing the next time you're hiring someone. Which candidate would you rather spend your day with? In my former career in management consulting, we used to call this the “Cleveland Airport test”: if you were stuck in the Cleveland Airport with this candidate, would you be happy about it or miserable?
There's a phrase I'm going to repeat a couple of times in this book, a favorite of our head of sales, Anita Absey: “You have two ears and one mouth for a reason.” You should always listen more than you speak, especially when you're interviewing somebody. Lots of senior people spend all their time talking when they're interviewing a candidate for a job. Maybe they love selling, maybe they just love hearing their own voice. Either way, it's a mistake.
Perhaps the most important interview question you can ask is “What do you think of our business?” If the interviewee doesn't have a cogent response by the time they get to you, you don't want them. And it doesn't matter what job the person is applying for. Why should you hire an accountant who didn't take the time to read your web site or learn more about your company throughout the interview process and develop a point of view on your business? Find the candidate who cares enough to do that. With that question, you're still leading the conversation. For at least half the time you spend with someone, you should let them lead it instead. What are their questions? Are they focusing on the right areas or sniffing after red herrings? Did they show up prepared for 15 or 30 minutes' worth of questions or just a handful of generic concerns? Spend most of the interview listening, and you'll quickly find out.
Three Key Interview Questions
Most of the conversations you'll have with potential candidates are going to be specific to the position you're interviewing for. There are some things you want to know about every candidate, whether they're applying to be a sales intern or a chief marketing officer (CMO). These are three questions I always ask:
I interview a lot of people: I probably interviewed 60 people last year and will interview at least that many this year. Until the year we hired over 100 people for the first time (which brought our team to about 275), I interviewed everybody. Not just direct reports—or even reports of reports—but every last intern.
Usually, these were on the phone or Skype. In most cases, they lasted for only 15 to 30 minutes. For the most part, I only wanted to meet what were almost certain to be new employees and validate my managers' decisions. It was only in extremely rare cases that I overrode a hiring manager's decision and dinged a recruit. In those cases, it was clear that the manager was rushing the process to fill a seat—which didn't happen often and needed to be stopped when it did.
These short interviews have been great mechanisms for collecting data about the organization, for making a personal impression on the culture, and for continuing to get to know all employees, at least a little bit. Moreover, it was a great recruiting tool: good candidates really appreciate the fact that the CEO is interested in them, even if you give them only 15 minutes of your time.
It was a bittersweet moment when I stopped interviewing everyone: while it was great to be growing fast, I immediately started missing the personal connections with everyone, and it's harder to remember names as I walk through the hallways now.
Topgrading Your Team
One of the best business books I've read in recent years is Topgrading by Brad Smart. The book is all about how to build an organization of A players and only A players, and it presents a great interviewing methodology. It's very long for a business book, but also very valuable. Buy a copy for anyone in your company who's doing a lot of hiring, not just for yourself or for your HR person.
There's been much talk lately about “the importance of B players” in the Harvard Business Review and other places. I share the Topgrading perspective, which is that you should always hire A players—the definition of which is “one of the top 10 percent of the available people in the talent pool, for the job you have defined today, at the comp range you have specified.” The Topgrading methodology, though, splits out A1 players (future executive material) from A2 players (promotable) to A3 players (great at the role, could do it forever). Why would you ever settle for less than an A player in every role?
The hiring process doesn't end on an employee's first day. It ends 90 days later.
Perhaps the single most important part of the recruiting process is onboarding. Nothing has a greater impact on a hire's viability. Sure, you have to get the right people in the door. But if you don't onboard them properly, they may never work out. This is where all companies, big and small, fail most consistently.
Remember your first day of work? Did you (or anyone at the company) know where you were supposed to sit? Did you (or anyone at the company) know if your computer was set up? Did you (or anyone at the company) have a project ready for you to start on? Did you (or anyone at the company) know when you'd be able to meet your manager? Probably not.
Take onboarding much more seriously, and you'll be astounded by the results. We have a manager of onboarding whose only job is to manage the first 90 days of every employee's experience. You don't need to go that far (and won't be able to until you've scaled well past 100 employees), but here are some things you can, and must, do to ensure a successful onboarding process:
With that, the hiring process is done. Now, repeat.
Management Moment
Exercise the Courtesy of Notification
In most startups, there's something in between asking for permission (in advance) and begging for forgiveness (after the fact). I call it the “courtesy of notification.”
It comes down to practicality. A healthy organization is one where most of the players know the rules and framework and mission and are empowered to make things happen. Most importantly, people understand what they're in charge of. There are lots of circumstances where “just doing it” makes sense. Making sure that the relevant people at least know “it” is happening will save a lot of heartache down the road—and probably create a safety valve to make sure there are no radically adverse unintended consequences.
Teach your team to think about who in your organization is affected by the things they do. When they have to charge forward on their own, they should at least give their colleagues the courtesy of notification.
3.149.235.63