My path into cloud engineering began with the fundamentals. A bachelor’s in Physics at Union Christian College taught me to break systems down to first principles, and a postgraduate program in Wireless Networking at Lambton College sharpened that thinking around real infrastructure.
Before that, I worked in frontline tech support at Apple, which taught me how to listen to people, diagnose problems quickly, and stay calm under pressure. My actual IT career started with an internship as a Junior IT Consultant, where I got my first real exposure to supporting hybrid environments, a mix of on premises and cloud systems.
From there I joined Hatch as an Azure Administrator, taking ownership of production infrastructure for the Canadian side of a global team and managing it end to end. That role pushed me from identity and endpoint work into deeper platform ownership, modernizing how we managed infrastructure as code, and building automation that turned slow, manual processes into things that ran in minutes instead of hours.
Today I’m a Cloud Solutions Engineer at Extendicare, where I design cloud environments for secure migrations and acquisitions and build the governance that keeps a growing environment secure, well organized, and cost aware. My work has also stretched into newer territory; AI infrastructure, modern data platforms, identity across a mixed set of systems — which tends to be where I land: the newest, least defined problems, before anyone’s figured out how they should work.
Governance and cost control are the parts of the job I keep gravitating toward, and it’s the direction I want to take my career next moving from managing cost as one piece of governance to specializing in FinOps directly.
I care about the fundamentals: clear architecture, honest documentation, and governance that actually holds up. I’m most useful on teams that want to move fast without cutting corners on reliability or cost.