Previously at and trusted inside
Services
I work best where architecture, infrastructure, delivery, and engineering leadership overlap. The work is hands-on enough to unblock the team and strategic enough to make the next decision easier.
For companies whose AWS bill is scary, deployments take hours, or “we’ll fix it later” became the architecture.
Architecture audits, migration roadmaps, infrastructure-as-code implementation, and pragmatic cost optimization.
Typical engagement: 4-8 week project or ongoing advisory retainer.
For companies that need CTO/VPE-level judgment before a full-time executive hire makes sense.
Technical strategy, team structure, hiring support, engineering process, incident response, and stakeholder communication.
Typical engagement: 10-20 hours/week, 3-6 month minimum.
For teams shipping slowly, fighting fires, or scaling faster than their development habits can handle.
CI/CD buildout, testing strategy, developer experience improvements, and onboarding that does not take weeks.
Typical engagement: 6-12 week intensive.
Results
Rebuilt healthcare RFP search so enterprise users could get near-instant results instead of waiting on slow queries.
Refactored the core messaging pipeline behind 4-5 million monthly messages, removing the bottleneck and restoring operating headroom.
Led the move from colocated infrastructure to AWS EKS with Terraform automation while keeping the customer experience stable.
About
Over the past 10+ years, I’ve led engineering through acquisitions, AWS and Kubernetes migrations, SOC2 audits, high-volume messaging systems, and team growth. I’m comfortable moving between architecture diagrams, Terraform, code review, executive tradeoffs, and the messy middle where most technical risk actually lives.
Contact
I respond within 24 hours. If it’s not a fit, I’ll tell you straight and likely point you toward a better option.
