Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / Why You Should Hire People Smarter Than You
Transcript
- Lucas: There's a line I keep coming back to from Steve Jobs when he was recruiting John Sculley away from Pepsi in 1983. He looked at Sculley and said, 'Do you want to sell sugar water for the rest of your life, or do you want to come with me and change the world?' Luna: That's one of the most famous recruiting pitches in business history. But what's the hiring lesson underneath it? Lucas: Jobs was explicitly hiring someone smarter than him in certain domains. Sculley knew marketing and operations at a scale Apple desperately needed. Jobs was a visionary, but he didn't have the discipline to run a growing company. He went after someone who could fill his gaps, and who outshone him in those areas. Luna: Right, but we all know how that ended. Sculley eventually pushed Jobs out. So is hiring someone smarter than you actually a good idea, or is it just a romantic story? Lucas: Good question. The story definitely has a cautionary tail. But the principle still holds up in a lot of research. There's a study from Cornell that looked at teams doing complex problem-solving. They found that teams where at least one member was objectively smarter than the manager outperformed other teams by about 17 percent on those tasks. The key was that the manager had to be willing to actually listen to that person. Luna: Seventeen percent is significant. But I imagine a lot of managers feel threatened by that kind of hire. Isn't the instinct to protect your own position? Lucas: Absolutely. And that's the biggest barrier. Insecurity. I've seen hiring managers reject a perfectly qualified candidate because they were 'too strong' or 'wouldn't fit the team.' What they really mean is, 'I'm afraid this person will make me look bad.' But the reality is, if you hire people who are only 80 percent as good as you, your team's ceiling is your own ability. If you hire people who are 120 percent, your ceiling rises with them. Luna: So it's a mindset shift from being the expert to being the talent magnet. But does that work at every level? Or is it mostly a leadership principle? Lucas: It works at any level where you are responsible for building a team. A senior engineer hiring a junior engineer? Sure, you want someone who could eventually become a senior engineer themselves. A marketing manager hiring a coordinator? You want someone who might automate half your job in two years. The principle scales. The question is whether your ego can handle it. Luna: But there's also a practical risk. If you hire someone much smarter than you, they might get bored and leave, or they might try to take your job. How do you mitigate that? Lucas: Two things. First, you need to give them real ownership and autonomy. If you hire someone brilliant and then micromanage them, they will leave within six months. Second, you have to be secure enough to let them take credit for their ideas. If you're constantly stealing the spotlight, they'll resent you. But if you make it clear that their success is your success, they're more likely to stay. Luna: That makes sense. I think of the way Lorne Michaels built Saturday Night Live. He famously hired dozens of writers and performers who were funnier than him, and he gave them the stage. He's not a comedian, but he built a comedy empire. Lucas: Exactly. Lorne Michaels is a perfect example. He didn't have to be the funniest person in the room. He had to be the best judge of funny. And that's the real skill — identifying talent and creating an environment where it can flourish. That's a different kind of intelligence. Luna: So when you're interviewing, what should you look for? How do you know if someone is genuinely smarter than you, or just good at interviewing? Lucas: The best signal is curiosity. Ask them about a problem they solved that you don't understand. If they can explain it to you clearly and enthusiastically, that's a good sign. Also, look for people who ask you hard questions. If a candidate asks you something that makes you pause and think, that's someone who will push your team forward. Luna: But what about cultural fit? If someone is much smarter but also abrasive, doesn't that hurt the team? Lucas: That's a fair concern. But I think we often conflate 'cultural fit' with 'people who are like us.' If someone is abrasive in a way that damages collaboration, that's a problem regardless of IQ. But if they're just intense or direct, that might be a style difference you can manage. The question is whether their intelligence adds more value than their style subtracts. And often, the answer is yes. Luna: I've also seen cases where a manager hires someone smarter, but then the new hire ends up leaving because the organization can't keep up. So it's not just the manager's ego — it's the whole system. Lucas: That's true. If you hire a rocket scientist into a team that operates at a snail's pace, they're going to be frustrated. So you need to be honest about your organization's capacity for change. If you're a slow-moving company, hiring a brilliant disruptor might just lead to mutual frustration. But if you're in a growth phase or a turnaround, that's exactly when you need them. Luna: Let's talk about the actual hiring process. How do you structure an interview to identify candidates who could potentially be smarter than you? Lucas: One technique is to give them a real problem your team is facing and ask them how they would approach it. Don't look for the 'right' answer — look for the depth of their thinking. Do they ask clarifying questions? Do they challenge your assumptions? Do they bring up perspectives you hadn't considered? That's a sign of someone who could add value beyond your own thinking. Luna: Another thing I've seen work is to include a panel interview with people from different functions. If the candidate can engage with a non-expert and make their ideas accessible, that's a strong signal of both intelligence and communication skills. Lucas: Great point. And you can also use reference checks differently. When you call references, ask: 'In what areas was this person clearly more knowledgeable than their manager?' If the reference can point to specific domains, that's a good sign that the candidate is comfortable being the smartest person in the room on certain topics. Luna: But what about the risk of insubordination? If you hire someone smarter, they might not respect your authority. How do you handle that? Lucas: Respect isn't automatic based on title. You earn it by being a good manager — by giving them resources, protecting them from politics, and clearing obstacles. If you do that, most high performers will respect you even if you're not the technical expert. They want a leader who enables them, not one who competes with them. Luna: I want to come back to the Jobs-Sculley story. Jobs later said that hiring Sculley was one of the biggest mistakes of his career. But do you think that's because the principle is flawed, or because the execution was? Lucas: I think it was execution. Jobs was young and inexperienced as a manager. He didn't have the political skills to manage someone as powerful as Sculley. Plus, Apple's board at the time sided with Sculley. So the dynamic was doomed. But Jobs learned from it. When he came back to Apple in 1997, he hired Tim Cook — someone who was clearly better at operations than Jobs was. And that worked brilliantly. Luna: So the lesson is: hire people smarter than you, but also build the organizational structure to support them. Give them room to operate, and make sure your board or leadership team is aligned. Lucas: Exactly. And also, be clear about your own role. When Jobs hired Cook, he didn't try to micromanage the supply chain. He focused on product vision and design, and let Cook run operations. That division of labor is key. You have to know what you're good at and what you're not. Luna: So if someone is listening and thinking about their next hire, what should they do differently starting tomorrow? Lucas: First, review your current job descriptions. Are they written to attract people who could challenge you, or people who fit a mold? If they're too narrow, rewrite them. Second, in your next interview, ask yourself: 'Could this person teach me something?' If the answer is no, think twice. Third, if you're the smartest person in every room, you're not building a strong team — you're building a fan club. Luna: I think that's a great practical framework. And it ties back to something we've talked about on the show before: hiring for potential over experience. Hiring smarter people is a form of betting on potential. Lucas: Yeah, it's connected. But it's also about humility. The best leaders I've seen are the ones who are secure enough to surround themselves with people who are better than them in specific areas. They don't see it as a threat. They see it as leverage. Luna: And that's a hard skill to learn. It requires constant self-awareness. But it's worth the effort. Lucas: You know, this kind of conversation is exactly why we keep doing this show ad-free. We want to dig into real hiring challenges without any sponsor telling us to wrap it up or steer it toward their product. If these conversations have moved your work forward in even a small way, and you want to support that choice, the link is buy me a coffee dot com slash fexingo. No pressure, just a way to keep it independent. Luna: Yeah, it's a small gesture that goes a long way in keeping the show focused on what matters. And speaking of what matters, let's get back to hiring smarter than yourself. Lucas: So one more concrete tactic. I've seen companies use what they call a 'challenge interview' — where the last round includes a meeting with a prospective peer who is known to be the smartest person on the team. If the candidate holds their own in that conversation, it's a strong signal. Luna: That's a great idea. It tests both the candidate's intellectual horsepower and their ability to engage with people who might outshine them. And it also gives the existing star employee a sense of ownership in the hire. Lucas: Exactly. And it works both ways — the star employee also gets to vet whether the new person is someone they want to work with. It's a mutual selection process, which is healthier than a top-down decision. Luna: Alright, so let's wrap up with a takeaway. If you're a manager, the next time you have a hiring decision, ask yourself: 'Am I willing to hire someone who could eventually replace me?' If the answer is no, that's a red flag. Lucas: I'd add one more: 'Is this hire going to raise the average IQ of the team?' If not, you're probably settling. And in a competitive market, settling is a slow death. Aim for people who make you look good, not people who make you feel comfortable. Luna: That's a good note to end on. Thanks, Lucas. Lucas: Thanks, Luna. Talk to you next time.