About
Making transformation matter where it matters most: growth, value, and scale.
At Verizon, I lead the transformation of network systems — the platforms, the data, and increasingly the AI that determines whether a network at national scale behaves predictably. The portfolio runs into eight figures annually, delivered through a distributed engineering organization several hundred strong across regions.
The transformation work has translated into multi-million-dollar savings for the business — not a pilot, not a proof of concept parked in a lab. Platforms carrying tens of millions of customers, at telecom-grade transaction volume and sustained data throughput, modernized while they stayed live.
A smaller group of leaders can point to the harder version of this: in-house products built to displace high-licence COTS platforms, and large data lakes stood up on open-source foundations instead of licensed stacks. Both are usually framed as cost plays. They're really architecture decisions about who controls the roadmap — the savings follow from that, not the other way round.
Alongside the operating work, I've led technical due diligence and post-merger integrations, and hold an exited investment in a healthcare company. Capital allocation and delivery discipline turn out to be the same instinct, pointed in different directions.
At a glance
Trajectory
Verizon
Own the transformation agenda for network systems: global data platforms, AI-enabled operations, and the multi-agent model driving toward Level 3 network autonomy. Portfolio spans $30M+ annually with ~450+ engineers across regions.
Verizon Network Services
Led enterprise-level data transformations, integrating platforms across diverse business units and unlocking multi-million-dollar savings. Established large data lakes on open-source foundations rather than licensed stacks.
Enterprise Technology
Led technological due diligence, post-merger integrations, and synergistic platform consolidation, the unglamorous work that decides whether an acquisition thesis survives contact with the estate.
Private
Invested in a healthcare company and exited successfully after three years. Operating experience and capital allocation, informing each other.
Executive leadership lens
The questions a board asks do not arrive in technical language. These are the translations I work across.
Digital platforms and network monetization
Automation and platform consolidation
CapEx and OpEx portfolio optimization
Intelligent, predictive operations
Resilient, compliant, auditable architecture
Product-oriented engineering
An enterprise AI operating model, not a pilot
Technology due diligence and integration
Organizational leadership
Scale of organization is the part of a technology remit that does not transfer from a slide. It is built, and it is led.
~450+
Technology professionals
Multi-region
Distributed organization
$30M+
Annual portfolio under management
Organizational design against the shape of the work, not the org chart it inherited
Leadership development and succession, so the structure survives any one person leaving
Global delivery across regions and time zones, held to one definition of done
Engineering productivity treated as a managed outcome rather than a hope
Vendor and partner ecosystem governed as part of the operating model
Architecture governance that speeds decisions up rather than slowing them down
Executive stakeholder management across business units and functions
M&A, investment and enterprise partnerships
The unglamorous work that decides whether an acquisition thesis survives contact with the estate.
Technical evaluation of the target estate: architecture, obligations, technology risk and what the integration will actually cost.
Post-merger platform consolidation, sequenced so the combined business keeps operating through it.
Turning the diligence thesis into a tracked number rather than a slide that ages quietly.
Invested in a healthcare company and exited after three years. Operating experience and capital allocation informing each other.
Operating principles
These are positions, not platitudes. Each one has cost me an argument at some point.
Every programme carries a number it is accountable to. That value may be financial, operational, customer, risk or strategic, but it has to be measurable and someone has to own it.
High-licence COTS products are often paying for capability an enterprise already has the talent to build. Displacing them returns both margin and roadmap control.
The large data lakes established under my leadership stand on open-source products because they compose better. The savings are a consequence, not the thesis.
~450+ engineers do not follow a strategy deck. They follow someone who has been close enough to the work to know what it costs.
Education
University of South Florida
Tampa, Florida, USA
Indian Institute of Technology (IIT) Roorkee
Roorkee, India
Working together
Board-level conversations, CXO roles, advisory work, and speaking. If the problem involves large data, complex operations, and a number that has to move, it is worth a conversation.
Start a conversation