20+ Years of Leading Engineering Organizations Through the Hard Parts.

Situation

Siemens was launching a mission-critical Customer Experience Portal but had no senior engineering leader to own the platform, the team, or the vendor relationships.

What I Led

• •Built and hired a 28-person engineering organization from the ground up — structure, roles, delivery cadence, on-call model.
• •Owned architecture decisions for a multi-region AWS platform serving global customers.
• •Established the security and release-engineering practices that made 99.99% uptime possible.

Business Outcomes

• •99.99% uptime on a mission-critical global platform
• •75% faster deployment cycles
• •30% infrastructure cost reduction through FinOps discipline

What I Left Behind

A self-sufficient engineering org, documented architecture, and a successor ready to step into the permanent role.

Situation

Atlas Air was executing a large-scale AWS migration with multiple vendors in flight and tight executive oversight, while also preparing the organization for responsible AI/GenAI adoption. They needed senior engineering leadership to own architecture, governance, and vendor coordination end-to-end.

What I Led

• •Architecture and delivery oversight for the migration of 1,000+ servers to AWS across a multi-vendor delivery model.
• •The AI/GenAI governance posture — cost, risk, data access, and readiness — so adoption could scale without surprises.
• •Executive-level reporting on progress, risk, and vendor performance throughout the program.

Business Outcomes

• •1,000+ servers migrated to AWS under tight executive oversight
• •Multi-vendor delivery kept aligned to a single architectural direction
• •An AI/GenAI adoption path that was governed and de-risked before scale

What I Left Behind

A production-ready AWS footprint, a documented AI governance framework with least-privilege IAM and cost controls in place, and an internal team aligned on the next phase of adoption — with my responsibilities cleanly handed off across multiple individuals.

Situation

Carrier was launching a new global IoT SaaS platform to manage millions of connected devices, but needed a senior engineering leader to set the serverless architecture and replace legacy on-premise systems that couldn't support the new business.

What I Led

• •Architecture for an event-driven, serverless AWS platform designed to scale from day one to millions of connected devices.
• •Coordination of engineering, platform, and product teams through the build and launch.
• •The cost, security, and release-engineering practices the platform runs on today.

Business Outcomes

• •Successful launch of a new, high-growth IoT SaaS platform in the global climate and energy solutions market
• •Serverless architecture that eliminated server-management overhead and scaled dynamically with demand
• •A foundation capable of securely managing and processing data from millions of connected devices globally

What I Left Behind

A production IoT SaaS platform, documented serverless architecture, and an internal team equipped to run and evolve it.

Situation

Kubota was constrained by expensive, inflexible legacy IBM on-premise systems that couldn't support their digital transformation goals or respond quickly to market demands — a widening competitive disadvantage.

What I Led

• •The AWS migration strategy away from legacy IBM infrastructure — prioritization and sequencing across business units.
• •The DevOps foundation and delivery cadence that modernized how engineering shipped software.
• •Target architecture and FinOps guardrails to make the cost reduction durable, not one-time.

Business Outcomes

• •100% performance improvement on modernized applications
• •30% reduction in infrastructure costs
• •Modern DevOps foundation that accelerated software delivery velocity

What I Left Behind

A modernized AWS footprint, a DevOps practice the internal team could sustain, and a clear roadmap for the remaining legacy decommissioning.