Senior full-stack engineer. Six and a half years on a national automotive SaaS platform.

I put the quality bar in the pipeline, so the team never has to remember it.

Senior & staff roles
Vancouver, BC
Hybrid preferred, remote or on-site welcome
Canadian citizen, no sponsorship needed

TypeScript
React
Next.js
Node.js
Tailwind CSS
Zod
Vue.js
PHP
Python
MySQL
PostgreSQL
MongoDB
Redis
WordPress
AWS
Vercel
Docker
Cloudflare
GitHub Actions
Jest
Lighthouse
Claude

01Read

Five years on the platform thousands of Canadian dealerships run their inventory on. The work I’d point you to first is the caching, and the win was stability more than speed.

Vue
Node.js
PHP
MySQL
Redis
AWS

Custom in-house OOP PHP, no Laravel or Symfony
Object Cache Pro: ended 3 years of cache churn
Technical SEO, where getting inventory found is the product
Mentored engineers in code review and pairing

The AutoSync Motors demo dealer site, top to bottom

5 yrs

Jan 2020 – Jun 2025

Cache reverts & removals, 3 yrs on

02TadvantageCase study

The platform behind dealer websites, from Convertus through the acquisition into AutoSync. I was its top all-time contributor over six and a half years.

PHP
WordPress Multisite
Vue.js
Node.js
MySQL
Redis
WP-CLI
PHPUnit

The tadvantage.ca home page, top to bottom

Owned production releases, v3 through v12.7
Canada’s luxury tax on every price, rolled out dealer by dealer
Ended three years of object-cache churn; page caching fleet-wide
The SEO foundation: bilingual inventory sitemaps, VIN-keyed schema
IQ Badging: one Vue component, on every vehicle card

1,682

Commits, #1 of 100+ engineers

358

Merged pull requests

Counted from the private repository’s history, so you can’t click through and check. I’m happy to walk you through it.

05DriftPilot

I moved the quality bar out of code review and into the pipeline, where nobody can forget it or argue it down on a deadline.

The DriftPilot studio site, from the hero down through its services and delivery process

Performance: ≥ 95
Accessibility: ≥ 98
SEO: ≥ 95
Best practices: ≥ 90

It’s easy to call an architecture reusable. I built a second site on mine to find out, and I’ll show you what had to change.

The Riflessi Auto Care home page, from the 3D hero down through its services and the bay

5 weeks

First commit to first full build

Pull requests in that build

07History

Where I’ve worked since 2016, the tools I’ve used, and the principles I hold my work to.

Chapters, 2016–present

Practice principles

08How I use AIHow it works

Specialist AI roles

May write files

Documents in the standard

1,920

Lines, cross-project

09Open gapsAll four

No test runnerOn the roadmapNeither project has automated test coverage. The lead-capture path, the only one that brings in revenue, has no regression tests.
No error monitoringIn developmentOn DriftPilot, if the webhook fails twice the visitor still sees a thank-you page, and only the failure is logged, not the lead. Riflessi tells the visitor and logs the full lead, but neither site stores it anywhere durable.
No perf gate on the second siteIn developmentRiflessi ships without the Lighthouse budget that guards DriftPilot, so regressions can reach the live site unnoticed.
No CMS yetOn the roadmapContent lives in typed accessors in the repository, so a copy change ships as a pull request and a deploy.