The five plus years are the point, not the detour●

I was the person internal teams escalated to. Five years at Shopify in CX RnD technical services: Twilio platform ownership, Tier 2–3 incidents, identity and access, outage comms in the war-room Slack channel, log-diving in DevTools and Splunk until the actual cause fell out. Before that, Accenture — deploying and troubleshooting endpoints and enterprise platforms for clients who noticed instantly when something broke.

That work taught me the thing bootcamps can’t: what software looks like from the receiving end. I’ve read the ticket that says “it just stopped working.” I’ve written the SOP that stopped fifty of them. When I build a UI now, I’m thinking about the person who will file the bug.

So I’m building the other side. React, Next.js, and TypeScript on the front, Rails and GraphQL behind it — learning by shipping one genuinely huge product, brick by brick. I’m early, and I’m loud about being early. This site is the record of it; the work, the decisions, and the ones I had to undo.

What it taught me
20+
Twilio projects owned end to end, where I learned that shipping the config is the easy half; getting four teams to agree on the workflow is the work.
1
full-stack feature built and shipped (merchant bans), mentored by Shopify engineers. The reason I stopped reading about frontend and started doing it.
95%
SLA resolution across Tier 2–3 support. Five years of reading "it just stopped working" is why I now design for the person filing the bug.
50+
SOPs and KB articles written. Turns out documenting a system is how you find out you did not actually understand it.
Work
  1. Company
    Shopify
    Role
    Technician, CX R&D
    Dates
    2020 – 2025
  2. Company
    Accenture
    Role
    Technology Analyst
    Dates
    2018 – 2019