Section III — A Note
On the slow drift from code to systems.
From engineering to growth systems.
I started out writing code.
For a while, I built Android applications and websites — spending long nights debugging systems, fixing edge cases, and thinking about code long after shutting the laptop. I enjoyed building things, but I realised fairly quickly that I didn't want to spend my life inside codebases.
What interested me more was the machinery around businesses: people, decision-making, systems, and growth.
So I moved into recruitment.
For two years, I worked as a headhunter for Fortune 500 companies in the United States — hiring across functions and industries for companies like NBCUniversal, Comcast, The World Bank, Freddie Mac, and GSK.
Eventually, startups pulled me in.
The work became less about filling roles and more about building infrastructure from scratch. I moved from talent acquisition into founder’s office and operational roles — helping early-stage companies build hiring systems, map organizations, structure teams, create processes, and scale internal operations.
Somewhere along the way, content and growth became part of the work too.
Over the last few years, I’ve worked closely with creators, founders, and brands across talent, social media, positioning, and operational strategy — combining systems thinking with audience growth and execution.
More recently, my focus has shifted toward AI.
Not in the abstract sense people like talking about online, but in practical ways: using AI to improve workflows, automate repetitive operations, accelerate research, build content systems, generate media, and create scalable internal tools for teams and creators.
That’s largely what I do now.
Coda
I work across talent, growth, systems, content, and AI — usually somewhere in the middle of messy scaling problems, helping structure things before they break.