Software engineer. Fifteen years turning specific, real-world problems into systems that ship — and stay shipped.
I build production web systems end-to-end. Backend infrastructure, frontend interfaces, the operational glue between them, and the work that keeps those systems alive once they're in production. The kind of engineering that doesn't make headlines — until the day it has to.
My work has run at scale, inside regulated industries, and across the small, demanding domains where one engineer ships the whole thing — credentialing infrastructure, marketing automation, fleet operations, conference platforms, multi-tier hosting environments.
I prefer problems with constraints. Real users, real budgets, real legacy code. The work I'm most proud of is rarely the work that got the most attention.
Built at Walmart Canada. A content destination with a nightly ingest pipeline that pulled thousands of product records from internal APIs — store-aware and postal-aware — feeding a recipe portal with ingredient-to-cart deep-linking, and a unified analytics layer that fed multiple measurement systems at once.
Built at Thentia. The company's corporate website, plus the Salesforce and Pardot automation behind it — qualification flows, segmentation, and the operational pipework that turns a marketing site into a revenue system.
A driver-side mobile app for capturing maintenance issues in the field, an operations dashboard for dispatchers and mechanics, parts and inventory linkage, role-based permissions, and cross-entity invoicing that reconciles work across operators, shops, and accounting. The hard part of fleet software is rarely any single screen — it's modelling how five roles actually pass work to each other, and keeping the data honest as it moves between them.
Registration platforms, on-site check-in flows, and event-day operational tooling for several North American conferences. Repeat engagements across multiple years — the kind of work where the system has to run flawlessly during the eighteen hours that matter most.
Member management, certification cycles, continuing-education accreditation, exam administration, and the operational reporting around them. The unglamorous backbone that lets credentialing bodies actually credential.
A fifteen-year practice. Operational systems for specific real-world problems across faith communities, small businesses, manufacturing, and education — most of them still in production, several of them still being used a decade after the last commit.