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.

01Role

Computer builder · hardware assembly

Technical / operations / systems role · Calgary, AB · [ period — to add ]

What bothered me

Most of the operational work was repetitive and manual. People spent their days entering serial numbers, updating the inventory system, printing labels, keeping spreadsheets in sync, checking emails by hand, and carrying the same information from one system to another. None of it was hard — that was exactly the problem. It was repetitive, error-prone, and quietly exhausting. Watching capable people lose hours to copy-paste work bothered me more than it probably should have.

What I built

So I started building small internal tools and workflows to take the manual weight off: semi-automated serial-number handling, label-generation flows, spreadsheet automation — anything that removed a step a human had to do by hand. Without really deciding to, I became the person who redesigned the workflow instead of just following it.

What it changed

Fewer repetitive steps, fewer mistakes, faster and more consistent processes. But the result that actually mattered was internal: I realised I think in systems by default. When I saw repetitive work, my instinct was never “work harder.” It was always the same question — why doesn't a system exist for this yet?

02Role

[ industry — to add ]

[ role — to add ] · [ location — to add ] · [ period — to add ]

What bothered me

A lot of the operation ran on manual coordination. The same actions repeated constantly — moving data between places, updating content, handling inventory tasks, tracking operations, running the same communication loops over and over. The pattern was familiar: a lot of human effort spent holding things together that a system could have held instead.

What I built

I built internal tools, automations, and scripts to cut down the repeated human actions — automating processes, simplifying workflows, removing duplicated work, and making operations easier to see and track.

What I learned

This is where it became undeniable: I enjoy building the infrastructure and the workflow far more than the repetitive execution itself. Give me a system to design and I'm fully in. Give me the same task fifty times and I start looking for the exit — usually by building something so I never have to do it a fifty-first.

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.