Not the typical path.
No CS degree. No startup origin story. Just years of solving real problems at every level of the stack.
Started at the help desk
First lesson: tech is about people. Nobody cares how clever your fix is—they want their problem gone. I learned to listen, explain without jargon, and stay calm when everything's on fire.
Became the translator
Business analyst. The bridge between 'what they want' and 'what's possible.' Got good at spotting when the stated problem isn't the real problem. That skill still pays off daily.
Built things myself
Finally got to code. Realised why developers hate vague requirements. Code is communication—you're writing for the next person who has to understand it.
Went senior
Architecture calls. Tech debt decisions. Mentoring. The realisation: senior doesn't mean knowing everything. It means asking better questions.
Owned outcomes
Stopped asking 'what should we build?' Started asking 'what problem are we solving?' Learned to kill good ideas that weren't right ideas.
Led teams
Hiring. Culture. Process. Technical leadership is 80% people, 20% tech. The best architecture means nothing if your team can't ship.
Why this matters
I can talk to your engineers, your executives, and your customers—because I've done all three jobs. I spot project disasters before they happen because I've been burned enough to know the patterns.
Most people specialise early. I wandered first. Turns out that's my edge.
Tools of the trade
Enterprise
Salesforce
Zendesk
Celigo
Shopify
Code
Node.js
React
TypeScript
APIs & Integration
Method
System Design
Process Automation
Technical Architecture
Team Building
Currently
MSt in Entrepreneurship at Cambridge. Not for the letters after my name—for the frameworks and the people.
Still chasing the same thing: hard problems, sharp people.
Questions? Just ask.