I am not sure how to start or where to begin, but I thought during my course of education that I would end up becoming.
- Software Engineer
- Cyber Security Engineer / Consultant
- Application Engineer
- Platform Engineer
- Security Engineer
- System Administrator
- Site Reliability Engineer
So why go through all the hoops to end up becoming a Site Reliability Engineer? Because it was the best place, a person like me could fit in. If you ask a passionate kid who codes his way to school, with “What do you want to become?”. He will say a computer engineer, software engineer, or something in between the lines.
Today, companies have different names for systems engineers; rarely are they termed accurate “Systems engineers.” The naming changes as a production engineer (FB), DevOps Engineer (AZ), Core Engineer, Core Service Engineer, Site Reliability Engineer(GOOG), etc.
My decision to become an SRE was the heartbeat of all practices and cultures mixed into one. In my eyes, SRE touches every stack that entails software/systems but does not have to worry about the code. Instead, we worry about the underlying infrastructure and tech stack used to deploy and run that code. It can be frontend, backend, infrastructure, security, monitoring, etc. When you touch practically everything, you understand the nitty-gritty of how things work in a larger scheme of things.
Also, not many people know this, but the “culture” of SRE was forked from the space shuttle missions, which happens to be my greatest passion. I live and breathe space.
Yes, being a Security Engineer or a System Architect might sound more fabulous, but the heart wants what it wants. I am not a person who feels satisfied with just one thing, no matter how good I might be at it.