I build for
what comes next.

CTO, Software Architecture and Builder. I’ve engineered distributed systems and led the teams behind them.
I treat coding as craft: built to hold, made to last.


Founder of Pixelbot, in Toronto.

01 // ENGINEERING

I build for scale before it's needed.

System Design & Scalability

A system shouldn't need to be redesigned every time the business grows. I design distributed architectures, platforms, and services that can evolve with the organizations they support, all while balancing performance, reliability, and long-term maintainability.

AI-Native Platforms

Most software has AI bolted on after the fact. AI-native platforms are built the other way around, with intelligence woven into the architecture so the system reasons, adapts, and improves as it runs. I build them from the ground up, because retrofitting intelligence is never as capable as designing for it.

Infrastructure Transformation

Most legacy systems aren't broken. They've simply outgrown the environment they were built for. I modernize infrastructure without disrupting what works. Performance, reliability, and operational efficiency improve in the process.

02 // TEAMS

I build teams around ownership and creative technical thinking.

Engineering Culture

I establish best practices, code review standards, and technical excellence frameworks, building cultures where ownership, curiosity, and good judgment are the default.

High-Performance Teams

I've built and scaled my own engineering team, embedded in client organizations, and worked across existing structures, from individual contributors to CTOs. What matters isn't just the team, but how it connects to the rest of the business: product, marketing, design, and operations.

Engineering at AI Speed

I bring modern AI tooling into how teams build. It shortens the path from idea to working software, and the gains compound: faster iteration, better products, sharper tooling across the company.

40+
engineers led & mentored
10×
team velocity increase
Ownership
the cultural default
Creativity
creative technical thinking

03 // HOW I WORK

Grew up in Silicon Valley. Been building ever since.

STEP 01 / 03 — UNDERSTAND
queries.graphql resolver.ts
main · UTF-8
~/projects/pipeline — zsh
80×24
PIPELINE / OVERVIEW
LIVE 00:00:00 UTC
Lines of code written this year
0
+12.4% vs 2025 78% to goal
Project success rate
0%
42 of 44 shipped on time
Coffee consumed
0cups
~3.4 / day · cold brew season
Deployments / week
0
p95 build 4m 12s · 0 failed last 30d

                        
01 — UNDERSTAND

Every project starts by understanding the system, the constraints, and the people relying on it.

02 — BUILD

Build what needs to last. Software should be reliable, maintainable, and capable of supporting future growth.

03 — DEPLOY

Connect engineering to outcomes. Technical decisions matter most when they improve how an organization operates and performs.

04 // CLIENTS

Over a decade of building across healthcare, enterprise, startups, and public sector organizations.

I've worked with 0+ clients

Always interested in difficult problems worth solving.