About

What I do

I’ve built and governed platforms in environments where reliability, compliance, and capital discipline are non-negotiable. My work spans enterprise data strategy, engineering leadership, and AI-enabled operating models.

Founder perspective

Founding and scaling companies taught me that technology decisions are balance-sheet decisions. Architecture affects cost structure. Delivery cadence affects trust. Governance affects valuation. These lessons continue to inform how I design teams and systems.

How I lead

• Improve cycle time and reduce friction across teams and functions
• Break large initiatives into smaller, faster loops with clear ownership
• Use metrics (cycle time, deployment frequency, incident trends) to guide decisions
• Prioritise written clarity and async alignment for distributed execution
• Mentor through regular 1:1s, direct feedback, and consistent expectations
• Coordinate incidents calmly and systematically, with clear follow-through
• Hire for ownership, autonomy, and long-term team resilience

Operating principles

• Governance and security are product requirements
• Reliability compounds; heroics do not
• Capital discipline sharpens engineering decisions
• Small, fast experiments beat prolonged alignment
• Teams scale through context, not control
• Data literacy is a cultural transformation

Outside of work

I have an amazing wife and am a hands-on father to a two-year-old daughter. Family time includes petting farms, swimming, and foodie exploration.

I reset with 10min daily meditations, drives through country B-roads in 3.6L flat-six automobile while singing along to my favourite music.