
Strategic Credibility
Technical risk becomes a business decision when someone can price it. That translation is what moves engineering from a function that requests resources to one that owns them.
Most engineering leaders operate as service providers: the business defines requirements, engineering executes. That breaks down where technical constraints shape what’s possible and platform decisions carry years of consequence. I build organizations that do the pricing before the commitment, so the position is already settled when the pressure arrives.
What this looks like
Strategic translation: Reframing technical debt, platform risk, and architectural trade-offs in business terms that create budget authority and executive alignment.
Stakeholder partnership: Direct engagement with Product, Business, Marketing, Support, and Finance leadership, as the engineering voice in decisions that shape the platform, not just the roadmap.
Operational credibility: Release practices disciplined enough that technical constraints are accepted as facts rather than negotiated as preferences.
Roadmap influence: Engineering shapes what gets prioritized, not only what gets built, because the people closest to the platform can see which commitments it will actually carry.
How I’ve done it
From embedded delivery to strategic partner
As Senior Engineering Manager at iSeatz, I lead mobile teams embedded within American Express on the Amex Travel app, built on a $10.7B+ travel and loyalty platform. The mobile engineering organization operated in a delivery-execution posture with limited influence over product direction.
I redesigned the operating model around cross-functional pods with clear domain ownership, introduced architectural decoupling to raise deployment frequency and release predictability, and set a delivery cadence that gave enterprise stakeholders demonstrable progress.
The leadership operating model, capacity model, and delivery governance I designed were adopted across the wider mobile product-engineering program, defining decision rights, investment allocation, and role boundaries for teams beyond my own. The scope didn’t change first. The operating model did, and the scope followed.
Engineering as the business voice
At Quore, the product function was eliminated, leaving engineering without roadmap direction or stakeholder translation. Rather than backfilling the role or waiting for a structural solution, I took it on: I set roadmap direction with the CEO and decided what engineering would fund against sales, support, and customer demand, across a platform serving 81K+ daily users in 35 countries.
I prioritized against customer lifetime value and operational impact, translated technical constraints into business trade-offs, and worked directly with Business, Marketing, and Support leadership. Engineers on the team moved into larger strategic roles as that credibility held.
The function was never backfilled. Engineering kept it.
Reframing fraud as an executive problem
At Dayforce, the platform was losing money to fraud, but the losses sat in operational noise and nobody with budget authority could see the exposure in terms they could act on. Engineering had the technical answer and no standing to fund it.
I put a number on the exposure, took it to finance and executive leadership as revenue leaving the business rather than an incident count, and built the case that funded a platform stability initiative.
The containment work followed and cut exposure 82%. The durable change was that the next platform risk got priced before anyone had to argue for it.





