The story
I grew up on the internet.
Where it started
Around the year 2000, a kid found IRC. And then found Graal Online. And figured out you could write scripts that made things happen. Made other people's things happen. That was it. That was the bug.
Not the programming bug, the this is what I want to do with my life bug. The internet was wide open and anything was possible if you were willing to figure it out. Nobody was gatekeeping. There were no prerequisites. You just built things.
I learned to code the way most of my generation did: breaking things, reading source, asking questions in forums at 2 AM, and building small tools that solved small problems. By the time I had my first professional job, I'd already been coding on my own for nearly a decade, long before the Canada or Accuro chapter.
The Canada chapter
In 2011 I moved to Canada, Kelowna, BC. In 2013 I joined QHR Technologies. Accuro EMR is QHR's product. I shipped on it across two stints: nine years at QHR Technologies on Accuro (through 2021), then one year on Accuro after the parent changed (2022), so 2013–2022 on that platform, with 2017–2018 at Kronos (UKG) in Kelowna in between, not one uninterrupted run. National-scale deployment; I went from engineer to Technical Lead, managed 35+ rotating developers, led architecture decisions, and shipped features into clinical workflows.
Healthcare software taught me something you can't learn anywhere else: bugs aren't bugs. They're patient safety incidents. That weight changed how I think about code. About quality. About what "done" means. It never left me.
Between those two QHR stints, I spent a year at Kronos Canadian Systems, the Canadian dba of Kronos, now UKG, still in Kelowna, different product. Enterprise workforce software at a different scale than EMR. Same city, different world.
The return
In 2022 I came back to the US. I had enough saved to be deliberate about what I built next, and a clear belief about what kind of technology was worth betting on: systems that serve people, not extract from them.
I landed at Chewy, then Outcomes Inc, where I was hired at Staff level and designed a pharmacy data platform for a 10,000+ pharmacy footprint, supporting existing products like Rx30 and PrescribeWellness. We launched to production during my tenure and proved the architecture was scale-ready, but Rx30 and PrescribeWellness did not adopt the changes as planned and the effort was eventually cut during broader team reductions. That stretch confirmed what I already knew: I'm best when I'm building systems that have real stakes and real people on the other end.
Now I'm at WEX, architecting agentic AI infrastructure and feature stores for fraud detection and credit decisioning. The scale is different. The stakes are still real.
The tension
I love technology. I hate how technology is used against people.
That's not a contradiction; it's a compass. I've watched the internet become something I barely recognize: surveillance infrastructure dressed up as social media, engagement optimization that's really addiction engineering, platforms that extract value from everyone who uses them and return nothing.
I still believe in the early promise of the internet: that one person building the right thing can matter. My drive is to build systems that actually serve people, in an industry that keeps finding new ways to extract from them instead. I'm not here to burn anything down. I'm here to build the better version.
'Cause love's such an old-fashioned word
And love dares you to care for
The people on the edge of the night
And love dares you to change our way of
Caring about ourselves
How I lead
I set direction and I bring people with me. I care about outcomes, but outcomes without impact on real people mean nothing to me.
I've managed 35+ engineers at a time. I've mentored people across every career stage. I've focused on mentoring people with the hardest path, especially women in engineering, because talent is everywhere and opportunity isn't, and that gap is worth doing something about.
I give direct feedback. I expect it back. I don't let people fail when I can help them succeed. And I believe the best thing a senior engineer can do is make a room full of more junior engineers feel like they can build anything.
How I work
Direct. Results-oriented. Persuasive when I need to be. I don't hedge my technical opinions; I make a call, explain it clearly, and change my mind when new information shows up.
I move fast and make calls, but I build feedback loops in before anything is locked. Quick prototypes over long specs. Decisions made in the open so people can say "that's wrong" early, not after. I want to know what you actually think, not what you think I want to hear.
I'll stop someone if I'm genuinely convinced they're heading the wrong direction. But I don't pull rank. If I'm the most senior person in the room, that shows up in the questions I ask, not in who wins the argument. I've been wrong in ways that mattered. I want you to tell me when I am.
I think out loud. I prefer a working thing over a perfect spec. I hire for curiosity and work ethic before I hire for credentials. And I've never once regretted over-communicating with a team.
Off the clock
Terraria. Kingdom Hearts. Pokémon. Games that reward curiosity, building, and doing one more thing before bed. I've probably restarted Terraria three times this year. No regrets.
I sing. I make music. Same impulse as programming: making something that wasn't there before.
I care about the people around me. My ESFP comes through in meeting rooms, on calls, and in code review. I want to know how people are doing. I want work to be a place that's actually good to be in.
