Background - A career built around delivery and technical ownership
I've spent over 20 years building and delivering software in environments where delivery, scale, and technical decisions carry real consequences. My career spans startups, scale-ups, and large organizations, often working across mobile, web, and backend systems during periods of growth or change.
Much of my work has involved stepping into ambiguous situations, new product builds, platform recasts, or delivery under pressure, where ownership was unclear and decisions needed to be made. I've operated as a technical lead, architect, and embedded engineering leader, staying close to the work while remaining accountable for outcomes.
That experience has shaped a pragmatic approach: make trade-offs explicit, avoid unnecessary complexity, and focus on systems and teams that can sustain delivery over time.
How I operate
I operate close to the work, especially when delivery or architectural decisions carry long-term consequences. I don't lead from abstractions or frameworks, I stay involved enough to understand trade-offs, risks, and constraints.
When direction is unclear, I help teams surface decisions that need to be made, make those trade-offs explicit, and move forward deliberately. When delivery slows, I focus on restoring clarity and momentum rather than adding process.
My goal is simple: enable teams to ship reliable systems under real-world constraints, without accumulating unnecessary complexity.
Career context
Through my consulting work, I've taken on engineering leadership responsibilities across a wide range of industries, often embedded with teams during periods of change or growth. In these contexts, I operated with clear ownership of technical direction and delivery, regardless of formal role definitions.
Much of this work involved extended engagements where responsibility for technical decisions and delivery mattered more than formal titles. That experience has shaped a pragmatic approach focused on ownership, trade-offs, and long-term maintainability rather than idealized solutions.
I'm currently focused on full-time engineering leadership roles where I can take long-term ownership and drive sustained impact.
If delivery matters, let's talk.
I'm open to senior engineering leadership roles and conversations where ownership, judgment, and delivery matter. If you're navigating technical complexity, scaling teams, or delivery risk, I'm happy to connect.
- Montreal
Montreal, Quebec
Canada