Selected Work
What I built, the decisions behind it, and what changed
A few recent things I built and shipped. Written as short case studies, not resume bullets.
Alberta Motor Association — POS, Billing, and Micro-Frontend Platform
AMA agents service memberships in an internal POS and billing platform: enrollment, coverage changes, cancellations, reinstatements. I rebuilt core servicing flows as a React micro-frontend and worked on the reliability layer underneath, while years of legacy records were consolidated into the new platform.
- What I built: enrollment, cancellation and refund, coverage-change, and reinstatement flows, with invoice previews so staff see the outcome before committing.
- Reliability layer: event-driven workflows with idempotency, retries, duplicate suppression, and a failure queue, so changes stay safe while records are mid-migration.
- Migration compatibility: legacy-identifier lookup and preserved membership-number lineage kept old records searchable and correct.
- Scale: the platform supports ~80K completed transactions/month across 600+ active agents.
- Platform: this MFE lives inside AMA's internal POS platform, where I also work on the shell, shared tooling, and delivery.
Case studies: Membership rebuild → Micro-frontend platform →
findnaseeb — In-Person Matchmaking
Most dating apps are built around swiping. We wanted to start somewhere else: getting people into the same room. findnaseeb is built around real events instead of swipe-style matching. I co-founded it with two other people (one engineer, one product/UX designer) and built the app.
- What I built: the web app, the APIs, the data model, and the invite workflow we use for each event.
- Invite list: software uses profile and event context to draft a guest list. We always review it by hand before anything goes out.
- A tradeoff I'd defend: small team, boring stack. Next.js and SQLite on a single box is easy to run and reason about. We'll move off SQLite when concurrency forces us to.
- Where it's at: launched early 2026. 200+ members in Calgary, all from organic Instagram and TikTok. Waitlists open in Toronto, Vancouver, and Chicago.
Liveworks — Hospitality Marketplace
An early backend project for a hospitality staffing marketplace, and my first substantial exposure to marketplace logic beyond CRUD: job routing, payment flows, and internal tools for messy operational edge cases.
- What I built: backend features for job routing, Stripe payment flows, and admin tooling.
- The hard part: marketplace payments. Money moving between two sides means edge cases everywhere: refunds, no-shows, disputes. Most of the useful learning was in the unhappy paths.
- Stack: Node.js, PostgreSQL, AWS, Stripe.