Strategic Credibility
Engineering organizations earn influence through delivery, but they sustain it through operational maturity. I specialize in shifting engineering teams from reactive execution to strategic partnership—where platform leaders shape roadmaps, not just deliver them.
Most engineering leaders operate as service providers: the business defines requirements, engineering executes. That model breaks down in complex environments where technical constraints shape what’s possible and where platform decisions have long-term strategic consequences. I build engineering organizations that earn a seat at the strategy table—not through politics, but through consistent delivery, stakeholder fluency, and operational maturity that makes collaboration inevitable.
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—serving as the engineering voice in decisions that shape the platform, not just the roadmap.
Operational credibility: Predictable delivery, transparent communication, and mature release practices that build trust with non-technical leadership.
Roadmap influence: Moving from “we execute what you prioritize” to “we shape what gets prioritized”—because platform leaders understand the business constraints and technical landscape better than anyone else.
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 platform, a $9B+ loyalty and travel ecosystem. When I took ownership, 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 increase deployment frequency and release predictability, and established a supporting delivery cadence that moved us from monthly to biweekly mobile releases while maintaining full enterprise compliance.
That operational maturity shifted the dynamic. Our teams earned a seat at the roadmap table, moving from execution partner to strategic collaborator with Fortune 100 stakeholders. The work didn’t change—our credibility did.
Engineering as the business voice
At Quore, the product management function was eliminated, leaving engineering teams without roadmap direction or stakeholder translation. Rather than backfilling the role or waiting for a structural solution, I absorbed strategic planning across a platform serving 81K+ daily users in 50 countries and managed stakeholder relationships directly with Business, Marketing, and Support leadership.
This wasn’t gap-filling—it was organizational repositioning. I prioritized features based on customer lifetime value and operational impact, translated technical constraints into business trade-offs, and built credibility that enabled engineers to step into larger strategic roles. The organization didn’t just survive the transition—it established engineering as the strategic function that understood both the platform and the business better than any single department.
Reframing fraud as an executive problem
At Dayforce, the platform was losing revenue to fraud, but engineering couldn’t get traction on a fix because the losses were buried in operational noise. The technical solution was clear—rebuild payment validation and monitoring infrastructure—but it required pausing feature delivery, which meant engineering needed budget authority and executive air cover to execute.
The organizational problem wasn’t technical competence; it was that no one with decision-making power understood the exposure in terms they could act on. I reframed fraud losses as a margin problem, quantified the revenue impact, and built the financial case that earned executive sponsorship for a platform stability initiative.
Result: Engineering went from requesting resources to owning a strategic initiative. The 82% fraud reduction followed, but the real outcome was establishing engineering as the function that understood both platform risk and business economics—and could translate between them.
