it’s all intimidating, i spend most my days at work researching / reading documentation / following other people’s guides / scratching my head / pulling my hair out / then finally having an ah ha moment and it still not work, all-in-all it’s actually pretty stressful sometimes, but also novel and exciting. i’ve never had a job where i wanted to keep working after my 8hrs because i was getting off on making progress and making things work.
if that all sounds cool to you, look for any jobs with devops engineer, site reliability engineer, cloud engineer, or platform engineer then carefully read the job description as every title / role is something different depending on the company. for example, an sre is a role that google coined a while back where you’re expected to solve infrastructure problems with software engineering solutions, so in a true sre role you should be doing about 50% operations (setting up monitoring alerts, building ci/cd pipelines, etc) and 50% development work (building internal tooling to automate / make your life and your devs’ lives easier). a lot of devops-esque jobs may have you doing all ops work or very little, just depends.
anyhoo, look into some blogs that talk about some of those roles (e.g. devops engineer, sre etc) and see if that’s something you’d fancy doing. g’luck!
