I'm a full-stack engineer who starts every project with a deep understanding of who I'm building for and what problems they actually care about. That principle is the through-line of everything I do.

I cut my career in education—licensed to teach K-12 in Quebec—but I was always the person building tools to make people's lives easier. By the time I left the classroom to join a startup in 2014, the transition was natural. I wasn't abandoning teaching; I was scaling my impact by applying a builder's mindset to software.

I'm a tinkerer, a hacker, a critical thinker at heart. When I encounter a tool, framework, or technology that doesn't quite fit the problem I'm trying to solve, I don't force it. I dig in until something clicks, then build what's actually needed. That relentless curiosity has taken me from malware forensics investigations to context engineering, from open-source contributions to DIY electronics labs. I dive deep. I dig where others don't. I don't stop when something is confusing—I start paying attention.

What I've learned across more than a decade of building software is that deep end-to-end ownership of a feature area, close to the product and the people using it, is where I operate at my best. Open source, accessibility, and genuinely improving the online experience aren't career keywords for me—they're the filter through which I decide what to work on.

What keeps me going is finding something deeply interesting—either a problem worth solving or a technology worth understanding, or ideally both—and then figuring out how to do something with it that no one else has done yet. The harder it is, the more unusual it seems, the more excited I get. The learning is the point. I'm happiest when I'm stretching beyond what I already know, pulling myself into unfamiliar territory, and figuring it out.