Product Engineer
One partner for roadmap, architecture, and delivery.
Over the years, I've learned that the strongest product decisions happen when someone in the room can both shape how the product is built and deliver the code.
Product & roadmap clarity 🗺️
I work with you to turn product goals and stakeholder expectations into a clear, sequenced plan. Priorities are explicit, dependencies are mapped, and the technical roadmap is aligned with what the business needs to ship.
Outcomes: A technical roadmap tied to product milestones; backlog structured by impact and dependency; shared language between product and engineering on scope and success criteria.
Solves: Chaotic or politically-driven roadmaps; misalignment on what "done" or "next" means; no clear way to say "not yet."
Architecture & system design 🏗️
I define or clarify how your system is structured: boundaries between services or modules, APIs and contracts, and how the stack can evolve. The goal is an architecture that supports the product today and can scale—not accidental complexity.
Outcomes: Documented architecture and clear API contracts; justified build-vs-buy and platform decisions; a shared mental model so new work fits the system.
Solves: "Nobody knows how it all fits together"; sprawl and ad-hoc integrations; big rewrites with no clear path; headless or multi-site decisions that feel like guesswork.
Technical debt reduction 🔧
Technical debt is treated as a product and risk concern. I help you prioritise paydown in a way that supports delivery instead of blocking it—the right debt in the right order, with clear criteria for "good enough."
Outcomes: A prioritised debt backlog aligned with product and risk; incremental improvement without "stop the world" rewrites; fewer incidents and rework from neglected debt.
Solves: Debt ignored or triggering panic rewrites; team fighting the codebase instead of building; hidden dependencies and recurring security or performance issues.
Delivery & execution supervision ⚡
I provide senior oversight of how work gets done: quality bar, release discipline, and whether what's built matches the architecture and roadmap. When I write code, it's on the highest-leverage items; the rest of the time I ensure the process supports sustainable delivery.
Outcomes: Consistent quality and alignment; clear "done" criteria; CI/CD and release practices that support safe deployments; one accountable voice for "how we build."
Solves: Inconsistent quality and "we'll clean it up later"; risky or manual releases; gap between what was decided and what was built; no senior technical reference for standards.
Ready to align strategy and execution? Schedule a conversation
In short
What is a Product Engineer?
A Product Engineer helps you decide what to build and why, designs how the system should work, and builds it—or has the team build it. They don't just take tickets: they shape the plan, the technical choices, and the delivery. One person who can take you from "we're not sure what we need" or "our tech is a mess" to a clear plan and a product that works. With AI everywhere, this profile decides where it fits, where the guardrails are, and what ships—no handoff, no black box. In 2026 that's the profile that wins.
Developer, Tech Lead, Product Manager, Product Engineer—same words, different scope. Below: where each role sits on focus, ownership, depth, and delivery.
| Dimension | Developer | Tech Lead | Product Manager | Product Engineer |
|---|---|---|---|---|
| Focus | Features and bugs, within a given scope. | Team delivery, tech decisions, people. | What to build, for whom, in what order. | What to build and how; product and tech in one role. |
| Owns | Tasks and tickets. | Team output, quality, tech direction. | Roadmap, priorities, alignment. | Outcomes, architecture, delivery; the how and part of the what. |
| Depth | Code, tests, what's assigned. | Broad and deep; guides stack and design. | Often light; relies on eng for how. | Deep: codes, systems, APIs, scale. |
| Business | Via specs and priorities. | Trade-offs and resourcing. | Roadmap, metrics, users. | Tech choices tied to product and business. |
| Architecture | Follows patterns; may improve locally. | Defines or refines for team/product. | Rarely owns; works with eng. | Owns or co-owns structure, boundaries, debt. |
| Ships | Their work. | Enables the team. | Defines what; doesn't build. | Ships and shapes what and how. |
AI & execution
How a senior Product Engineer uses AI responsibly
AI can speed up execution—but it doesn't replace judgment, architecture, or experience. Here's how I use it: with guardrails, CI/CD rules and process, clear boundaries, and senior oversight so it amplifies delivery instead of creating chaos.
AI accelerates execution
I use it for boilerplate, refactors, tests, and documentation when it saves time without compromising quality. The gain is in throughput on well-defined work, not in replacing design or decision-making.
AI requires guardrails
Output is reviewed, tested, run through CI/CD rules and process, and aligned with your architecture and standards. Nothing ships without human verification. No blind copy-paste into production.
AI does not replace architecture thinking
System design, API contracts, technical debt prioritisation, and build-vs-buy decisions stay with the engineer. Tools suggest; people decide.
Experience matters more than tools
Knowing what "good" looks like, when to push back on a spec, and how systems fail in production comes from years of shipping—not from a model.
Senior supervision prevents AI-driven chaos
Unsupervised AI output leads to inconsistent patterns, hidden debt, and rework. A senior Product Engineer keeps the bar high and the system coherent.
So: AI as leverage, not identity. Clear boundaries, human ownership, and no hype.
How we work
Strategic technical partnership.
I work with one or a few clients over time, not one-off projects. Recurring collaboration so I stay in the loop: aligned with your roadmap, architecture and team. I can join your dailies and weekly ceremonies so the work stays coherent.
Ongoing partnership
Recurring rhythm, long-term
A clear technical partner who keeps the plan, the architecture and the backlog aligned with where you want to go.
We review where things stand, make the key decisions, and I do hands-on work on what matters most. I can join your dailies and weekly rituals so nothing drifts.
Good fit: Teams that want one accountable technical voice without a full-time hire; product-led teams that need consistency over time.
Phased work, then optional ongoing
Clear phases with outcomes (e.g. clarify roadmap → build foundations → hand over)
You move from confusion or overload to a clear plan and solid base, then choose whether to continue with ongoing support.
Each phase has clear deliverables. After the main work is done, we can switch to a lighter ongoing rhythm if that helps.
Good fit: Teams about to do a rebuild or a big platform change; organisations that need to clean up before scaling.
A partner dedicated to one team
When the project needs regular presence and one clear technical owner.
One team gets a single technical partner in the loop on roadmap, architecture and delivery—present for dailies and key ceremonies so nothing drifts.
Useful when the stakes are high or the team benefits from having the same person fully in the loop. One accountable voice, continuity without a full-time hire.
Good fit: Teams that need a steady technical partner; projects that require closer alignment between direction and execution.
You get a Product Engineer who thinks in systems and outcomes, and who can both shape the plan and deliver. Not a freelancer dropping in for a few hours—someone who stays and owns the coherence over time.
I offer a few ways to work together, all built around recurring, long-term collaboration.
Ideal fit
Who I work best with
I'm most effective when the context fits how I work: strategy and execution in one place, clarity over buzzwords, and room to reduce complexity.
Product and engineering leaders
You want a senior partner to structure the roadmap, challenge the architecture, and deliver—not just execute tickets.
Teams with legacy or tangled systems
You want to reduce debt, clarify structure, and stabilize without a full rewrite.
WordPress / CMS-heavy organisations
You want to move towards headless, modernize Gutenberg, and structure clean APIs with a clear long-term vision.
Multi-brand or multi-market companies
You need to manage complexity, consistency, and performance without adding unnecessary layers.
Small teams (2–4 devs) under pressure
You need clear prioritization, solid technical standards, and a structured framework to ship cleanly.
Startups and scale-ups
You want a responsible technical voice, able to hold the line from strategy to delivery.
How I build
Technical foundations
One partner across the stack. The technologies I work with support product and architecture outcomes: clarity, scalability, and sustainable delivery. Tools serve the system—not the other way around.
Proof
Selected work
A few engagements where ownership of architecture, product impact, and delivery mattered. Outcomes over tasks.
Milesopedia 
Product Engineering and Platform Evolution
Architecture and Platform Modernization
- Multi-Market Expansion: I helped guide the transition toward a multi-market platform supporting Canada, France, and the United States, enabling the business to expand its reach while maintaining a unified technical foundation.
- Centralized API Architecture: I designed and scoped the foundation for a centralized API that will progressively distribute financial product data across the entire network of sites and partners, preparing the platform for a headless and scalable architecture.
Product Development and Editorial Infrastructure
- Modern Gutenberg Ecosystem: I developed and implemented a large set of custom Gutenberg blocks and editorial tools, enabling the content team to build complex layouts while keeping the editing experience simple and efficient.
- Legacy System Transition: I led the progressive migration away from legacy components toward a modern block-based architecture, improving maintainability, performance, and long-term flexibility.
Platform Operations and Continuous Improvement
- CI/CD rules and process: I defined and implemented CI/CD rules and pipelines (build, test, deploy) to keep plugins, themes, and platform components synchronized across the entire network of sites.
- Performance and Product Optimization: I continuously analyze platform performance and business requirements to prioritize improvements that strengthen user experience, editorial efficiency, and revenue generation.
Tech Stack
WordPress and custom plugins, PHP & JavaScript (ES6+), extensive Gutenberg block development, REST API architecture, centralized API design, advanced caching strategies, CI/CD pipelines and automated deployments, multi-site and multi-brand platform architecture, custom financial comparators, and integrations with external data sources and services.
Nesto 
Synergy and Technical Innovation
Definition and Implementation of a Centralized System Architecture
- Design of a Unified Architecture: I develop a centralized system architecture that serves as the foundation for all projects, ensuring consistency, efficiency, and ease of maintenance across various initiatives.
- Adaptable Grid: I implement an adaptable grid within the architecture, offering flexibility and customization according to the unique requirements of each project, while preserving a solid and consistent technical infrastructure.
Technical Leadership and Team Coordination
- Technical Direction and Supervision: I provide precise technical guidelines and support to teams to ensure alignment with the defined architecture and adoption of best practices.
- Recruitment and Talent Development: I actively engage in the recruitment process, aiming to hire highly qualified candidates who align with the company culture, and I design technical skill tests to efficiently evaluate candidates.
Monitoring, Maintenance, and Evolution of Systems
- Maintenance Process: I establish monitoring and maintenance procedures to ensure optimal performance of existing systems and their compliance with technological advancements or changing needs.
- Constant Updates and Optimization: I regularly analyze the current architecture's effectiveness to identify opportunities for improvement.
Tech Stack
Vanilla PHP & JavaScript (ES6+), 95 React blocks for the Gutenberg editor, extensive use of transients and advanced caching, sessions/local storage, REST routes, and external API integration. It also includes rewrite rules for a fully custom WordPress setup, advanced MySQL tables & queries, Salesforce integration for lead creation, complex Webpack configuration to build theme variations via the command line, and many more cool features!
Compare Mortgages 
Architecture, Innovation, and User Optimization
Strategic Planning and System Architecture
- Designing an Optimal System Structure: I establish an architecture that effectively supports the analysis and comparison of mortgage loans, thus ensuring optimal support.
- Detailed Project Planning: I define key stages and deliverables to structure the development and ensure timely delivery.
Team Leadership and Coordination
- Aligning Design to Development Stages: I effectively coordinate between the creation of functional mockups, design, as well as back-end and front-end developers.
- Planning and Integrating Phases: I clearly define priorities and timelines for each phase, ensuring a smooth progression towards the final delivery while maintaining high quality and an optimal user experience.
User Experience and Result Analysis
- User Interface Development: I work closely with designers to create prototypes and mockups that meet user expectations.
- Creation and Integration of Efficient Tools: I develop and integrate advanced tools dedicated to A/B testing and in-depth data analysis.
Tech Stack
Vanilla PHP & JavaScript (ES6+), REST routes and external API integration, rewrite rules for a fully custom WordPress setup, advanced MySQL tables & queries, Salesforce for lead creation, a complex Webpack configuration file to build theme variations via the command line, and many more cool features!
BrightWize 
Innovation, Planning, and Technical Oversight
Project Evaluation and Planning
- Feasibility Analysis: I comprehensively evaluate timelines, required resources, and the overall viability of the project.
- Development Strategy: I develop a detailed strategy to guide the project's execution, including the definition of work phases.
Architectural and Technological Design
- Architecture and Technology Selection: I design a project architecture and select appropriate technologies and tools to ensure effective and adaptable development.
- Technical Prerequisites: I define technical requirements to ensure a solid foundation for the deployment and future growth of the project.
Ongoing Technical Supervision and Support
- Progress Monitoring and Problem Solving: I regularly monitor development progress, paying particular attention to the proactive resolution of technical challenges.
- Compliance Assurance: I ensure that developments are aligned with the initial project vision and meet high quality standards.
Tech Stack
Laravel, complex MySQL tables & queries, React calculators for the mortgage industry, web scraping, project scoping, estimation, and code reviews, ...
Who I am
About
Creative director and design for several years, then programmer, now product and technical leadership—that path gives me a perspective that’s rare. I’ve been on both sides of the brief: from pixels and UX to systems, APIs, and roadmap. I know what gets lost when “design” and “engineering” talk past each other, and how to keep things aligned.
I care about clarity over buzzwords, reducing complexity instead of adding layers, and one person owning the thread from strategy to delivery. That’s why I work as a Product Engineer: not a consultant who leaves a deck, not a dev who only takes tickets—someone who structures, challenges, and ships.
Based in Quebec, I work with product and engineering leaders who want one accountable partner for the full stack: strategy, architecture, and execution.