Full-Stack Cloud Engineer | Next.js, React, Python, Java, C++ | Docker, AWS, Azure | Architect of secure, reliable applications & bulletproof pipelines
I am a software engineer who looks at development through a wider lens. While I love building intuitive, high-performance interfaces with Next.js and React, I care deeply about what happens after the code is pushed. To me, a feature isn't complete unless it's running on secure, resilient, and fully automated cloud infrastructure.
Over my career, I’ve intentionally cultivated a stack that spans the entire lifecycle of a product. I use TypeScript/JavaScript for rapid web development, Python and Java for heavy-duty backend services, and Docker paired with AWS or Azure to ensure seamless cloud deployment.
Because of my background in project management, I don't just write code in a vacuum. I design architectures with business constraints, security compliance, and long-term reliability in mind. I specialize in building robust CI/CD pipelines that eliminate deployment anxiety and keep engineering teams moving fast.
DEPLOY PIPELINE
My primary production language; everything I ship runs on it, in strict mode, because I want the compiler catching my mistakes before a user does.
The foundation underneath the TypeScript, and still where I reach when I want something small and direct.
My go-to for scripting, automation, and anything data-shaped that does not need a front end.
Where I learned to think in objects and systems; two full terms of OOP plus Spring, a neural-net build, and an open-source contribution.
The library I build interfaces in, components, state, and hooks, and the one I am most fluent in.
The framework my production site runs on; App Router, server components, and static generation doing the heavy lifting.
A second framework in my toolkit, useful for understanding how the other half of the ecosystem thinks.
How I style without leaving the markup; a design-token layer that keeps a whole site visually consistent.
The runtime under my APIs and tooling, and the reason my front-end and back-end speak the same language.
How I design services to talk to each other: predictable endpoints, clear contracts, nothing clever for its own sake.
My default relational database; where I model data properly and let constraints do their job.
The enterprise database I rebuilt a five-office manual report on top of, turning 45-plus weekly hours into an automated pipeline.
My reach-for when the data is document-shaped and a rigid schema would only get in the way.
Every change I make is a small, reviewed commit on a short-lived branch; version control is a discipline, not an afterthought.
Where my work is public and my pipeline lives: Actions running tests, scans, and quality gates on every pull request.
My development environment; I learned the command line before the GUI and I have never really left it.
Where I am building a containerized microservice right now: a REST API on ECS, secured with Cognito and JWT.
The cloud I ran enterprise infrastructure on at OCAD, migrating 2,500 users with Entra ID and Intune.
Where my production site actually lives and ships, with preview, staging, and production deploys on every commit.
How I package services so they run the same on my machine, in CI, and in the cloud.
Enterprise delivery, a creative career, and a production engineering practice. Read across the panel.
Building software every day
Architecture Decision Records on this site
of ~20 and growing
STRIDE threat scenarios modeled
Mean time to rollback
Users served by the cloud print platform
Reduction in print-related support tickets
fewer tickets
Services brought under continuity planning
Licensing cost eliminated
Titles administered at Warner Chappell Music Publishing
Manual work removed per week
Enterprise rights & royalty operations
Professional services & project delivery
Multiple certified gold records
Multiple national radio singles
Juno nominations and a Canadian Radio Music Award
A Next.js and TypeScript application built and operated like production software: PR workflow, automated testing, security hardening, and staged delivery.
A companion system with architecture decisions, threat models, and operations evidence behind each implementation claim.
I'm looking for a full-stack role where engineering judgment and a track record of modernizing how work gets done both matter. If that sounds like your team, I'd like to hear from you.
Everything on this site is open source, so look as closely as you like.