this post was submitted on 02 Aug 2023
10 points (100.0% liked)

CSCareerQuestions

988 readers
2 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Related Communities

Credits

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
10
Switching from DevOps to backend (self.cs_career_questions)
submitted 1 year ago* (last edited 1 year ago) by Citizen_12B to c/cs_career_questions
 

A a friend of mine said he could recommend me to a junior DevOps role at the company he works in, but I'm interested mostly in back-end development and DevOps is not really something I like. The question is: could I use experience as a DevOps to later switch to back-end? Edit: more detail

you are viewing a single comment's thread
view the rest of the comments
[–] Reader9 2 points 1 year ago* (last edited 1 year ago) (1 children)

Devops is not a position in itself. It’s supposed to be a software development and operations philosophy

This is the definition I know but unfortunately the term seems to have become a modern synonym for system admin/engineer.

Such a role might still provide valuable experience for a backend dev if there’s an opportunity to write production code for internal tools as well.

Developers at my company need to have a deep understanding of the environments they deploy onto (microservices, scheduled workflows, etc.) which can include configuring canary testing, rolling deployments, status probes, setting up and using monitoring, and very occasionally intervening to restart or redeploy running software. But these are secondary skills compared to writing code.

[–] [email protected] 2 points 1 year ago (1 children)

the term seems to have become a modern synonym for system admin/engineer.

True, but the distinction still holds value. If a company has a DevOps role defined, you can derive from that what kind of a company you are joining. For example, they hire based on marketing and not based on merits, which tells you something about the colleagues you can expect to be working with. It also tells you about how they structure work and that hierarchy and bureaucracy may play a bigger part in getting your work done than you might like.

[–] Reader9 1 points 1 year ago

Good point and an interesting take. As you said this could be a good signal, when taken in context with the other limited information we get as employment candidates, about internal development practices.