Bobby Mawhinney
📍 New York, NY | LinkedIn
Architect. Engineer. Enabler. Occasional Product Manager. Always a builder.
Three decades. Three continents. A handful of industries. One consistent thread — get close to how people work, understand the friction, and fix it at scale.
Preface - The Spark · Tokyo
1989 – 1991
It started with a plane ticket from Ireland to Tokyo.
Fresh out of university, I landed a technical trainee placement with Marubeni Corporation — one of Japan's great trading houses — and spent two years trying to keep up. The language was hard. The culture shock was there. The work was fascinating. Large, complex organizations moving enormous things with enormous precision.
Tokyo in '89 was unlike anywhere else on earth. It left a mark. A curiosity about how big systems actually work — the people, the process, the politics behind the technology - that I've never quite shaken.
Chapter 1 - The Foundation · London
1991 – 2003
Twelve years. More clients than I can easily count. London was the classroom.
Consulting across financial services, insurance, energy and the public sector — Nomura, Accenture, Sumitomo, CAISO, the British Government — every engagement was a different domain with a different kind of complexity. The technology shifted constantly. The fundamentals didn't; understand the problem before you touch the solution.
The variety was the point. You can't spend a decade moving between trading floors, government departments, and energy services without developing an instinct for what good looks like - and a healthy tolerance for finding out it isn't there yet.
Chapter 2 - The Long Game · Goldman Sachs
2004 – 2021 · Tokyo → New York
Sixteen years. One firm. An arc that started back where everything began - Tokyo - and ended in New York; picking up a new title along the way.
Tokyo first. Then New York. From regional teams to global mandates, from hands-on architecture to engineering management, from platform building to data strategy. The problems got bigger. The teams got larger. Throughout it all, the work was the same kind of work: build things that make engineers better at their jobs.
The capstone was being named a Technology Fellow — one of roughly 60 across the entire firm. A recognition reserved for the people trusted to set technical direction. I'd spent 16 years earning it without ever quite intending to.
Chapter 3 - The Product Detour · Twitter
2021 – 2023 · New York
Most engineers who drift into product management do it gradually. Mine was deliberate.
Two years owning some of the hardest product problems inside Twitter — how the company builds software, how it moves to cloud, how thousands of engineers stay aligned while moving fast. It was the first time I sat fully on the product side of the table, and it changed how I think about everything upstream of it.
I didn't stay in product. But I took the lens with me.
Chapter 4 - The Enabler · JPMorgan Chase
2023 – Present · New York
The role I didn't know I was building towards for 30 years.
Engineering Enablement at scale — creating the conditions for a thousand plus engineers to do their best work. Less toil. Fewer blockers. More time on the problems that actually matter to customers. It pulls on everything; the consulting instinct, the platform thinking, the product lens, the long view.
The mission is deceptively simple. Make it easier to do the right thing than the wrong thing.
The Through-Line
Engineering is a craft. Platforms are products. People are the whole point.
Whether architecting a system, enabling a team, or owning a roadmap - the question has always been the same - what does progress look like for the person on the other end of this?