My path into product management wasn't a straight line — it started with architecture and urban planning, moved through UI and UX design, grew through eight years of AAA game production at Ubisoft, and landed in the automotive software world. Every step taught me something the next role needed.
What architecture gave me was systems thinking and a sensitivity to how people move through spaces — physical or digital. Design gave me a language for communicating intent clearly. Games gave me the operational muscle: how to run complex deliveries across large, distributed teams with high stakes and tight timelines. And automotive data gave me depth in a domain where precision isn't a preference — it's a safety requirement.
Today I work at the intersection of data, engineering, and product — owning end-to-end delivery of labeled datasets for ADAS systems at diconium, while also helping grow the applydata community through writing and events. I'm most effective when problems are genuinely complex, when the answer isn't obvious, and when getting it right requires aligning people who see the world differently.
Craft over shortcuts
I care about doing things properly — in the work, the writing, and the relationships.
Clarity as a skill
Making complex things understandable is one of the most useful things a PM can do.
Curiosity first
I ask questions before proposing solutions. The right framing matters more than the fast answer.
People over process
Good process serves the team. When it doesn't, I change the process.
Outside of work