Well, maybe not everything. Look, being a goalie is objectively ridiculous. You strap on forty pounds of equipment designed to protect you from frozen rubber traveling at speeds that would make physicists frown. Then you stand in front of a net and dare people to shoot at you. It’s a strange job. But here’s the thing: being a goalie is basically the same job as running ops, or security, or honestly, any part of software development where you’re the one who has to keep the thing from breaking.

Starting fresh with a new team—whether it’s stepping into the net as a goalie or joining a company as a Site Reliability Engineer—comes with a rush of excitement, uncertainty, and the need to quickly adapt. In both worlds, you’re expected to understand the system, earn trust fast, and make the right decisions under pressure. This piece explores the parallels between guarding the crease in ice hockey and taking on infrastructure responsibilities in a new engineering org: the importance of communication, learning team dynamics, managing risk, and building confidence through early wins.

I remember the moment vividly—a hard shot struck the lower side of my mask. The impact was sharp, a bolt of pain radiating through my face. I dropped my head to the ice, letting the sting settle before pushing myself up onto my knees. It wasn’t until I stretched my neck, looking around, that the blood started flowing. When I glanced down, the realization hit—red pooling rapidly beneath me. Instinct took over.