I spent my first eight years in IT at a massive manufacturing company. The career path was neatly mapped out: junior admin to senior, then team lead, then systems architect. I ticked every box, got the certifications they asked for, and built a reputation within the four walls of our ERP ecosystem. I genuinely believed I was accelerating my career growth, and in some ways I was. But when I left at 32 to join a 40-person fintech startup, I discovered how narrow my growth had actually been.
Enterprise environments reward depth. You become the go-to person for a specific module, a particular compliance framework, or a niche integration. That expertise is real and valuable. The problem is that you rarely see the whole picture. In my old role, I could tell you every parameter in our warehouse management system, but I couldn't spin up a basic cloud instance without a separate infrastructure team handling it. The organization had carved the work into such fine slices that my skills had atrophied in everything except that one slice. The mentorship was excellent, but it was mentorship within a confined box.
The startup shattered my assumptions. Suddenly I wasn't just the ERP architect; I was also the DBA, the network troubleshooter, and the person who had to choose a phone system for the office. At first, I tried to impose the same structure I'd learned at the enterprise. I created detailed RACI matrices, set up rigid change management for even small config changes, and insisted on formal documentation for every decision. In my mind, I was bringing discipline to chaos. In reality, I was strangling a team that needed to move fast. I'll never forget the lead developer pulling me aside after a week and saying, "We hired you for your experience, not a replica of a big company's red tape." That stung, but he was right. I had confused the tools of the enterprise with the skills that actually mattered there.
That failure taught me something about career growth I'd never considered: it's not a linear accumulation of titles and scope. It's about expanding your range of motion. In an enterprise, you learn how to navigate politics, scale solutions, and build consensus across large teams. In a startup, you learn how to make decisions with incomplete information, take end-to-end ownership, and recover quickly from mistakes. Neither is inherently better. They're just different sets of muscles. The real growth happens when you recognize which muscles you lack and deliberately put yourself in situations that demand them.
For years I'd thought enterprise was the "serious" career path and startups were for reckless young people. Now I see that the best career moves are the ones that feel uncomfortable without being toxic. My most rapid growth came when I moved back to an enterprise after the startup, bringing the bias for action I'd picked up, and finding ways to cut through red tape without breaking critical safeguards. I wasn't the same architect who had left. I had a wider lens.
If you're early in your career and feel stuck, ask yourself: are you deep or wide? Chances are you need more of the other. And don't assume that a bigger company means more growth. Sometimes the biggest leap is sideways, into a place that forces you to be a beginner again.