Site Reliability Engineer

Site Reliability Engineer I began my career at Uplight as an Infrastructure Intern, where I built foundational skills in managing production systems and understanding how reliability engineering supports both business and customer outcomes. Over time, I advanced into SRE I and ultimately SRE II, taking on deeper technical ownership and broader responsibilities in shaping how infrastructure was designed, automated, and maintained. My work contributed directly to infrastructure powering energy efficiency programs that reached millions of customers. Day to day, I focused on building automation, infrastructure as code, CI/CD pipelines, and observability practices. These efforts reduced toil, standardized deployments, and enabled engineering teams to ship changes more confidently. In addition to delivering technical improvements, I emphasized enablement, creating paved paths, writing documentation, and designing workflows that allowed developers to operate more independently and rely less on centralized SRE/DevOps intervention. This work helped balance speed and stability, ensuring that products could evolve without introducing unnecessary risk. By combining hands-on system improvements with a culture of enablement, I helped Uplight scale its engineering practices and create a foundation that supported both developer autonomy and long-term platform resilience.

Experience

My professional journey began at Galvanize (Hack Reactor), where I completed an intensive software engineering program. That experience gave me a strong foundation in problem-solving, collaboration, and the discipline of writing code that balances clarity with performance.

From there, I joined Uplight as an Infrastructure Intern, stepping directly into a production environment where reliability and scale were critical. In that role, I built practical skills in cloud infrastructure and began shaping the workflows that keep complex systems running smoothly.

I advanced to Site Reliability Engineer I, and later to SRE II, expanding my impact on the team. My work centered on infrastructure as code, automation, CI/CD pipelines, and observability practices, always with the goal of reducing friction and enabling engineers to deliver software confidently. Beyond the technical scope, I focused on enablement, designing paved paths, building documentation, and empowering development teams to operate more independently.

This progression from software training through increasing levels of infrastructure ownership reflects not just technical growth, but also a focus on creating environments where reliability and developer autonomy go hand in hand.