I’m a cloud & infrastructure engineer with 12+ years in mortgage and financial services. I started in Service Desk and Tier 2, and that early experience shaped how I design infrastructure, with an emphasis on reliability, observability, incident response, and building visibility that engineers actually rely on during outages.
Developers focus on delivering features; my focus is on helping them deliver not just quickly, but responsibly, and in a way that works for the Ops teams who support those systems in production.
My strongest areas are Microsoft infrastructure and observability. I’ve built end-to-end monitoring for loan application workflows, supported large data migrations, and worked with teams to reduce cloud waste through right-sizing and decommissioning.
Most of my infrastructure work spans Azure and AWS, often alongside hybrid and on-prem environments. I grew up in the Microsoft stack (Windows, IIS, .NET, monoliths) and Azure, but learned to appreciate AWS on a high-performing team that leaned more heavily into Linux, cloud-native architectures, containers/Kubernetes, and IaC. I’m more comfortable in the former, but there are plenty of cases where scalability and a *-as-code approach beat the simplicity of a monolith. Refactor and re-architect where it makes sense…not “just because” or to pad a résumé.
I see OpenTelemetry as a force for good. Standardization around OTLP, schemas, and semantics is a net positive, and it’s a great way to keep instrumentation portable and consistent across teams.
That said, portability is overrated. Observability is foremost a data problem; a top-tier presentation layer that helps humans reason about systems matters more than avoiding vendor lock-in. At the end of the day, our role in IT is to keep applications running reliably.