How to move from developer to start-up founder FAST COMPANY CONTRIBUTOR
I ALWAYS knew I wanted to start my own company some day, and many developers have the same aspiration. Developers tend to have countless product ideas that turn into side projects, and some of those projects can turn into the real deal. But transitioning from developer to founder is likely the hardest thing you’ll ever do – and it isn’t the right move for everyone. I’m a believer in offering more senior technical opportunities for developers, because stellar technologists shouldn’t be thoughtlessly promoted into management roles that don’t make sense for them. One of the first projects I worked on as head of engineering at Salesforce was creating and elevating the technical track within engineering alongside the management track to convey the value and equal importance of the technical individual contributor route. That said, the journey to founder can be rewarding – and if you decide the entrepreneurial path is for you, look to others who have done it and learns. Here are some of my top lessons.
DON’T UNDERESTIMATE THE VALUE OF TIME IN A TECHNICAL ROLE Spending more time in a technical role can give you a unique perspective as a chief executive. Earlier in my career at PeopleSoft, I wanted to move into a management position much sooner than I did. My manager at the time persuaded me to spend more time as an engineer in the trenches. It ended up being a blessing – the identity projects I worked on at PeopleSoft informed my vision for Okta and gave me the time I needed to hone my engineering skill set. Technical experience will also set you up to create and execute the right R&D culture and rhythm. Innovation and investment is nonlinear – and as a founder, you’ll need to convince your board and non-technical teammates of that. KNOW THAT YOU’RE NOT JUST BUILDING FOR DEVS In the show Silicon Valley, a group of engineers create a platform called Pied Piper. It’s portrayed as revolutionary, winning
first prize at TechCrunch Disrupt and receiving rave reviews from fellow developers. But the early product ended up being a bust – the interface was far too complex for the average user. This is all too relatable for many engineers. When you’re living and breathing code, it can be hard to remember that most people don’t have the same technical expertise. You have to build for a broader audience, and this even applies to developer-focused companies. One way is to seek out partners and a founding team with different experiences than you.. PREP FOR A DAY-TO-DAY THAT LOOKS DIFFERENT I can remember thinking when I was an engineer, “why would anyone need a calendar?” I had to get accustomed to relying on a calendar when I moved into management and juggled meeting after meeting along with other new responsibilities. Another change: you have the final say on higher-stakes decisions in the chief executive role, so your decisionmaking process slows down.
