Past Work / History

The same pattern, in every job I've had.

This isn't a résumé. The companies and titles matter less than the pattern, which is the actual point: across very different jobs, the same behaviour kept showing up on its own. I'd arrive to do a role, notice how much of it was repetitive and manual, and — without being asked — start quietly rebuilding the workflow underneath it.

1Role

Memory Express

System Builder · Calgary, AB · Jan 2026 – Present

What I did

Executed system assembly, testing, and validation workflows for desktop and laptop deployments. Maintained accurate operational and inventory records using Microsoft Dynamics 365 Finance & Operations.

What bothered me

Operational records moved through Microsoft Dynamics manually — the same information entered, verified, and cross-checked by hand, repeatedly. Nothing was broken. Everything was slower than it needed to be.

What I noticed

The same instinct showed up here: repetitive processes invite automation. Each standardised workflow I followed was quietly a blueprint for a system that could run itself. I followed the procedures — and kept a running mental list of the steps that didn't need a human.

2Role

Miss Kwan's House Limited

IT Administrator · Remote · 2018 – 2022

What I built

Built a JavaScript + Google Sheets ERP system handling inventory, customer management, invoicing, delivery notes, quotations, and automated PDF generation — end-to-end, without any off-the-shelf software.

Why it existed

The company ran its operations manually: spreadsheets, printed forms, hand-tracked inventory. Every invoice was a copy-paste exercise. Every quotation was assembled by hand. I built a system to make those things happen automatically — not because anyone asked, but because the repetition was obvious and the solution wasn't complicated.

What I learned

This is where it became clear that my instinct is always to build the thing that replaces the manual version. Maintaining a website and hardware infrastructure is straightforward. Building a system that makes a small business run without paper is the part that actually interested me.

The thread

The pattern, not the résumé.

The company names aren't the point. The point is that the same behaviour showed up everywhere I went, without anyone asking for it. I noticed inefficiency fast. Repetitive work bothered me at a level that's hard to describe. And I started building systems almost reflexively — always preferring to redesign a workflow over manually sustaining it.

This is the part worth saying clearly: the mindset didn't start with my AI and automation projects. It's been there the whole time, in every job, under every title. The tools have gotten more sophisticated. The instinct hasn't changed.