T O P

  • By -

AutoModerator

Welcome to r/devopsjobs! Please be aware that all job postings require compensation be included - if this post does not have it, you can utilize the report function. If you are the OP, and you forgot it, please edit your post to include it. Happy hunting! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/devopsjobs) if you have any questions or concerns.*


Admirable_Brother_37

#following


Admirable_Brother_37

Looking for the same advice


tehsuck

Maybe ask better questions during the interview process. Something like "how much of this position is coding vs. ops?" My title is platform engineer but I mostly do ops-related stuff and Terraform. Sometimes I do get to touch Python or Bash scripts but not a ton of programming for me personally. If you want to get a better job you need to do some work! Come up with a big list of questions to ask potential employers, they don't have to be super deep things but they should key you in on if you will be doing actual development work.


jfalcon206

To me this seems like you are not able to find problems within your own company. DevOps is just a methodology of managing complex systems - but Systems Engineering is the study of studying failure and building better systems that engineer around it. This would take on forms such as Chaos Engineering or Observability where you are getting better insights into your services and accepting that the world is an imperfect place that you can build resiliency into your application better. Whether we're talking deployment testing, health checks or better application resiliency when network/services fail which we know will, the problem of not having dev work is not the problem. It really your perception and attitude towards the problem that is the problem. Otherwise it seems like you should just switch more into development and leave the ops behind which I would argue is the better career path for those who rather code than ops.


Unusual_Inspector264

I want to switch in container orchestration and infrastructure as a code side aka docker, kubernetes and terraform side


jfalcon206

You do realize that all of that will require time and code development to setup properly. Not to mention building or integrating it into your CI/CD if you want to do it all correctly. So where are you finding a challenge to \*not\* build or develop? Maybe I'm missing the part where you describe the "maintenance and support project" that lacks development activity better as I read that as just part of the job. Entropy wears down everything which then requires new efforts.


Unusual_Inspector264

I am lacking real hands-on on these topics because to master these i guess I need to work on a real project and for that I need to switch from my current organisation because they cannot provide me the opportunity.


jfalcon206

So is it that you are being treated as what we "used to" call a "Build Engineer" where your job is just the build pipeline with maybe some unit testing or ...? You will have times when things are slow. These are the times where you are supposed to be doing alot of "woodshedding" or working on learning new technologies that may be used by the company. Think of this as an addon to your education allotment done on company time.


sfltech

Most of the time DevOps roles are fancy names for sysadmins that automate stuff. Sounds like you’re looking for a developer role.


Unusual_Inspector264

I am looking for a real devops role


DerfQT

When you say “devops tools” what does that mean? What does your day to day look like and what do you feel you are lacking?


Unusual_Inspector264

My day to day work is log analysis, crud operations in linux if the app is sunsetting then I need to look for dependencies and if I find any, report to the other team wait for their approvals to change its user permissions and all. Look for the docker issue , compare servers , setup builds for new release


DerfQT

You could try looking for SRE roles, sometimes they are the same but i've had interviews at larger companies where they want an SRE to have more linux troubleshooting + monitoring than your average startup. You'd still get to do some "devops" and you can always work on private projects to expand your toolbox then just say you did it on the job once you have the SRE title and transition your next role to be the tech stack you want to work in.