5 ms·

Its a good primer on getting into DevOps, but in today's market you need a lot more experience than this book can give you, especially following all the layoffs

Its a good primer on getting into DevOps, but in today's market you need a lot more experience than this book can give you, especially following all the layoffs.

JohnMakin 2y ago
Definitely. At the same time, there's a weird dynamic in the market - because of the boom of AI (driven mostly by cloud spending) architecture, the demand for cloud engineers and even general devops has surged, but mostly in the more senior 5+ years experience market. I am getting asked a lot of questions by people messaging me about how to enter after college, and I don't really have a good answer for them. The honest truth is that it's always been a little tricky and you've gotta be a little odd to get into it in the first place, and what I usually tell people is I don't believe many senior people doing it now ever "chose" it, it usually just happens to people. Plus the fact that these AI coding assistants can almost do a passable job of a junior, to the point where most of their job is probably going to be just dumping crap into copilot or some gpt. I feel very very bad for anyone entering the market right now.
- nolongerthere 2y ago
  Yup, the path usually looks something like: Service desk job > L2 > L3 > company pays for a bunch of cloud training so they don't have to pay for another consultant > DevOps or CE/CS intern > tasked with implementing stuff in clouds > hired as Jr SWE, but still tasked with doing those devopsy things that the real devops team doesn't wanna do > jump a few times, each time still taking on devopsy stuff > Sr DevOps Admin
  - JohnMakin 2y ago
    > CE/CS intern > tasked with implementing stuff in clouds > hired as Jr SWE, but still tasked with doing those devopsy things that the real devops team doesn't wanna do > jump a few times, each time still taking on devopsy stuff > Sr DevOps Admin Yea this is mostly the path I took. I had a hybrid lead/swe role that ended up me picking up sysadm stuff due to a weak DevOps team, then my next role was DevOps. Anecdotally, I find there's a large difference in quality of the engineer depending on which of those particular paths they took that's not usually well represented by salary ranges (although if you possess a CS degree jobs are MUCH easier to get IME).

Its a good primer on getting into DevOps, but in today's market you need a lot more experience than this book can give you, especially following all the layoffs.

JohnMakin 2y ago

Definitely. At the same time, there's a weird dynamic in the market - because of the boom of AI (driven mostly by cloud spending) architecture, the demand for cloud engineers and even general devops has surged, but mostly in the more senior 5+ years experience market. I am getting asked a lot of questions by people messaging me about how to enter after college, and I don't really have a good answer for them. The honest truth is that it's always been a little tricky and you've gotta be a little odd to get into it in the first place, and what I usually tell people is I don't believe many senior people doing it now ever "chose" it, it usually just happens to people. Plus the fact that these AI coding assistants can almost do a passable job of a junior, to the point where most of their job is probably going to be just dumping crap into copilot or some gpt. I feel very very bad for anyone entering the market right now.

nolongerthere 2y ago
Yup, the path usually looks something like: Service desk job > L2 > L3 > company pays for a bunch of cloud training so they don't have to pay for another consultant > DevOps or CE/CS intern > tasked with implementing stuff in clouds > hired as Jr SWE, but still tasked with doing those devopsy things that the real devops team doesn't wanna do > jump a few times, each time still taking on devopsy stuff > Sr DevOps Admin
- JohnMakin 2y ago
  > CE/CS intern > tasked with implementing stuff in clouds > hired as Jr SWE, but still tasked with doing those devopsy things that the real devops team doesn't wanna do > jump a few times, each time still taking on devopsy stuff > Sr DevOps Admin Yea this is mostly the path I took. I had a hybrid lead/swe role that ended up me picking up sysadm stuff due to a weak DevOps team, then my next role was DevOps. Anecdotally, I find there's a large difference in quality of the engineer depending on which of those particular paths they took that's not usually well represented by salary ranges (although if you possess a CS degree jobs are MUCH easier to get IME).