From Engineer to CTO: A Non-Linear Career Path
Startup codebases, CUDA kernels, and a decade of saying yes to messy problems. What I’d tell engineers who are told there’s a ladder.
Careers get narrated backwards. From here, "startup engineer becomes Fortune 500 CTO" sounds like a plan executed. It wasn’t. It was a sequence of messy problems nobody else wanted, taken on because they were interesting, that only looks like a ladder in retrospect.
The startup years: bias for action as a personality trait
I learned to engineer in small rooms — Spotlight Data, AgentHub, agency work — building Node.js microservices and React applications by day and, when the problem demanded it, dropping to C++ and CUDA to make algorithms fast enough to matter. Startups teach two things no enterprise training programme can: a bias for action, because nobody else is coming, and comfort with extreme ambiguity, because the spec does not exist and the customer is discovering what they want in real time. Both turned out to be executive skills wearing an engineer’s hoodie.
The enterprise shift: from building to multiplying
The move into the Eli Lilly and then Elanco world came with a question that took me years to answer honestly: what is my output now? The startup answer — "the thing I built this week" — stops scaling embarrassingly early. The answer that unlocked everything since: my output is the platform that makes hundreds of other builders faster. The 2018 spinoff was the forge for that identity; ElancoGPT was its proof. I volunteered to run the initial proof-of-concept when generative AI was still a curiosity with legal questions attached — precisely because it was messy, high-risk, and unowned.
Every promotion I’ve had traces back to a problem that was unowned, ambiguous, and slightly too big for me at the time.
What I tell engineers who want this path
- Stop talking about code; start talking about business value. Nobody funds elegance — they fund outcomes elegance makes possible.
- Master storytelling and technical translation. The best architecture that cannot be explained to a CFO does not exist.
- Embrace the non-linear path. Seek the messy, high-risk, unowned problems; they are the only ones with headroom.
- Build autonomous, high-trust teams. Letting go of the keyboard hurts; a clear, compelling vision is what you hold instead.
The engineer-turned-CTO’s real advantage isn’t nostalgia for code. It’s calibration: when someone tells me a platform will take three years and forty people, I have hands-on scar tissue that says it can be done in weeks by six — and the credibility to sponsor the people who prove it.