Why did you decide to become a mentor?
I’ve spent most of my career operating in environments where the technical decisions carry long-term consequences.
Early architecture choices, hiring decisions, and product trade-offs either compound or quietly accumulate technical debt that slows everything down. I started mentoring because I kept seeing talented founders and engineers make avoidable mistakes at exactly these inflection points.
Mentorship, for me, isn’t about motivation or surface-level advice. It’s about clarity.
It’s about helping someone think a layer deeper before they commit to a path that will define their next 3-5 years. I enjoy working with people who are building something real and want to move with intention rather than noise.
It also sharpens me. Explaining systems thinking forces you to refine your own.
Good founders ask hard questions. I value that exchange.
How did you get your career start?
My career didn’t begin inside big tech. It started by building.
Early consulting work exposed me to product, engineering, and commercialisation simultaneously. That forced me to think beyond code and into systems: revenue models, distribution, infrastructure constraints, hiring, capital efficiency.
From there, I founded and scaled a product and engineering studio, then moved into CTO roles across healthcare, spatial data infrastructure, and AI-driven systems.
Each environment introduced higher stakes: regulated data, global deployment, sovereign infrastructure, IP strategy.
I didn’t have a single mentor who mapped everything out for me. Instead, I learned by operating close to consequence. Shipping, hiring, raising, failing, restructuring. That experience shaped how I guide others now: decisions compound. Most people underestimate that.
What do mentees usually come to you for?
Most of my mentees fall into three categories:
1. Early-stage founders navigating technical product decisions.
2. CTOs or senior engineers scaling teams and architecture.
3. Deep tech builders wrestling with infrastructure trade-offs.
They usually come to me when complexity increases. Fundraising pressure. Hiring uncertainty. Architecture starting to crack. Team performance slipping. Or simply the realisation that their early decisions need to scale further than expected.
My mentorship style is systems-based and execution-focused. We map decisions against long-term outcomes. We separate signal from noise. I challenge assumptions and prioritise leverage. Some sessions are highly tactical. Others are strategic recalibrations.
What mentees can expect:
- Direct feedback.
- Clear frameworks for decision-making.
- Honest conversations about risk, trade-offs, and focus.
- Accountability to execution.
If someone wants hand-holding or generic career advice, I’m probably not the right fit. If they want clarity and leverage, we work well together.
What's been your favourite mentorship success story so far?
One of my favourite mentorship journeys involved a founder with strong early traction who was over-engineering the product architecture far too soon.
The system was becoming complex before it had earned that complexity. We stepped back and restructured the roadmap around first principles. We simplified the core architecture, clarified what actually needed to scale versus what could wait, and reshaped the hiring plan around capability gaps rather than inflated titles.
That shift created operational breathing room.
Over the following quarters, the company stabilised execution, improved engineering velocity, and went on to successfully close a major funding round. Investor conversations became sharper because the technical narrative was coherent. The team operated with clearer ownership. Trade-offs were intentional rather than reactive.
What stood out most wasn’t the funding milestone. It was the shift in how the founder thought. They moved from reacting to surface complexity to designing systems deliberately. That kind of maturity compounds well beyond a single raise or product cycle.
What are you getting out of being a mentor?
Mentorship forces clarity. When you help others reason through uncertainty, you refine your own frameworks.
It has strengthened my ability to communicate complex systems simply. It sharpens my pattern recognition across industries.
It also reminds me that leadership is less about having answers and more about asking the right questions at the right time. Operating at founder and CTO level can be isolating.
Mentorship creates structured conversations around problems that matter. I value that.
