GL

Full-stack product engineer · Ottawa, ON

I build full-stack products for messy operational problems.

I’m a full-stack engineer with a finance and operations background. Most of my work sits where product, compliance, QA, and support all have opinions.

View resume
ReactNext.jsTypeScriptNode.jsMongoDBAWSDockerPlaywrightFintechRegulatory logicInternal toolsAutomation

Featured work

A few places where product work met real-world constraints.

Bitcoin Depot / Bitaccess

Production fintech engineering

Fintech product work that had to survive real kiosks, real regulations, and real rollout pressure.

  • Built state-based regulatory rules with json-rules-engine and production scripts.
  • Led pricing and fees work that touched customer-facing flows, rules, and production rollout details.
  • Became a go-to engineer for production rollouts, escalations, and cross-repo troubleshooting.
ReactNext.jsTypeScriptNode.jsMongoDBAWSDocker

Faceout

Founder / Developer

Visit site

My small Ottawa web studio for local businesses that need a useful site, not a brand manifesto.

  • Focuses on local search, clean pages, and obvious ways for customers to get in touch.
  • Uses reusable pieces so projects move quickly without all looking the same.
Next.jsReactTypeScriptTailwindVercelResendVitest

PermiPro

Founding Engineer

Visit site

Early SaaS work around municipal permits: forms, follow-ups, missing context, and admin drag.

  • Mapped where applicants, contractors, and municipalities lose the most time.
  • Kept the MVP pointed at one useful workflow instead of a giant platform.
SaaSWorkflow automationProduct discoveryMVP planning

Operating style

I’m useful when a feature has to survive the real world.

I like messy workflows.

The useful problems are usually half product, half operations, and only then code.

I care about rollout.

A feature is not done just because it works locally. Someone has to test it, ship it, support it, and explain it.

I stay close to production.

Logs, edge cases, customer impact, support noise, and weird constraints all belong in the engineering conversation.