Constrained Delivery
From constraint to advantage—I turn regulatory complexity into delivery capability.
Regulated platforms don’t fail gracefully. A bad deploy in fintech isn’t just a rollback—it’s a compliance event, a revenue hit, and an erosion of trust. I lead engineering organizations where governance constraints enable safe velocity, not prevent it.
What this looks like
Compliance-aware delivery: Audit requirements shape release architecture from day one, not after an incident forces the conversation.
Risk as a first-class signal: Fraud patterns, error budgets, and incident data are prioritized alongside the product roadmap, not below it.
Zero-downtime operations: Bank migrations and platform transitions are executed live because fintech platforms don’t get maintenance windows—they’re judged on uptime.
Governance as enablement: API contracts and service boundaries are designed so teams ship faster because of enterprise constraints, not despite them.
How I’ve done it
Rebuilding trust at $7B scale
Dayforce Wallet was an on-demand pay platform processing over $7B in transactions and losing revenue to fraud. I led engineering across mobile, gateway, and internal support tooling. The technical fix was clear—rebuild payment validation and monitoring infrastructure—but it required pausing feature delivery, an organizationally expensive decision that needed executive air cover.
With sponsorship secured, we rebuilt the platform’s fraud controls: ML-assisted transaction scoring, real-time reconciliation workflows, and automated risk thresholds that replaced manual review bottlenecks. The work included a zero-downtime U.S. bank migration that moved millions in daily transactions without a single service interruption.
Result: 82% reduction in fraud exposure, restored platform integrity, and a compliance posture that supported continued growth rather than constraining it.
Trading features for resilience
A SaaS platform serving major hotel brands across 50 countries sounds impressive until reliability silently degrades beneath the feature roadmap. That was Quore when I took over mobile engineering. I shifted the team from feature expansion to reliability remediation: crash triage workflows, automated regression testing, and staged rollouts. This drove the platform to a 99.98% crash-free rate. The business got a product they could sell with confidence, rather than one they had to apologize for.
Autonomous releases inside enterprise governance
Regulated enterprise environments don’t lack process; they have too much of it, and deployment velocity pays the price. Leading distributed mobile teams at iSeatz within an enterprise travel and loyalty ecosystem, I redesigned the release architecture to decouple our delivery pipeline from enterprise approval cycles. This let the team move from monthly to biweekly mobile deploys while maintaining full compliance with governance requirements. The constraints stayed the same; our architecture changed.
