Build Like Esper: How to Bridge the Gap Between Technical Expertise and Category Creation

The path from technical expert to startup CEO isn’t just about learning new skills – it’s about fundamentally reimagining your relationship with expertise itself. In a recent episode of Category Visionaries, Esper CEO Yadhu Gopalan shared how his journey from Microsoft and Amazon engineering leader to founder required him to unlearn as much as he needed to learn.

The Engineering Mindset Challenge

As a self-described “introvert by design” and someone who started coding in fifth grade, Yadhu’s technical identity ran deep. “I’m really comfortable if you put me in a bunch of people who know my domain,” he shares, “but outside of the domain, I was always very uncomfortable.”

This comfort with technical depth but discomfort with breadth is a common challenge for technical founders. At Microsoft and Amazon, Yadhu’s success came from deep technical understanding. “As an engineer, I went deep all the time because I had to understand every aspect,” he explains. “Even as an engineering manager, I had to understand every aspect of what we were trying to build.”

The Amazon Turning Point

A pivotal moment came during Yadhu’s time at Amazon, leading device infrastructure for Amazon Go stores. When first approached about the role, his immediate reaction was “I don’t know anything about retail.” But Amazon’s culture encouraged this kind of stretch: “You know how to build things. You’re going to learn how to build something completely outside your domain space and kind of pick that up.”

This experience became a template for his later transition to CEO. “That’s something that I’ve taken away when I’ve started Esper,” he notes. “I’m no longer just engineering. How do I learn about marketing and how do I learn about sales?”

Redefining Expertise as CEO

The biggest challenge wasn’t learning new skills – it was learning a new way of being expert. “It’s the breadth of trying to know how to go deep just exactly in places because it’s not your space,” Yadhu explains. “So you have to kind of let the experts tell you what to do and then be able to kind of hone in on the questions you need to ask to make sure that you understand, rather than try to understand everything about it.”

This shift required developing confidence in a different kind of leadership. Instead of technical mastery, success meant “understanding in a general sense, what they are trying to accomplish and then trying to correlate and then make sure everything is attached and everything is flowing in the same strategic direction.”

Building Category Expertise

This new approach to expertise proved crucial in creating the “DevOps for devices” category. Rather than getting caught in technical details, Yadhu and his team focused on the broader transformation they could enable. They recognized that while cloud software deployment had evolved significantly, device software deployment remained stuck in the past.

The technical foundation helped them understand the problem deeply, but creating the category required looking beyond technical solutions to market education and customer success. “Early on, we were kind of playing with, this is security, this is this, et cetera,” Yadhu shares. It took time to find their true north.

The Learning Never Stops

Today, with millions of devices under management and “five of the top ten restaurant chains using Esper,” the company’s success validates this evolution in leadership style. But Yadhu emphasizes that the learning continues. “What lands now will not be what lands in about six months to a year,” he notes, highlighting the constant need to evolve and adapt.

For technical founders making a similar transition, Yadhu’s journey offers a crucial lesson: success doesn’t come from abandoning your technical expertise, but from learning to apply it in a new way. It’s about knowing when to go deep, when to rely on others, and how to use your technical understanding to guide rather than control.