4 ms·

DevOps I had the same issues for many years, but the past 2 positions have been official "DevOps" positions and they more often than not have me doing so many

DevOps I had the same issues for many years, but the past 2 positions have been official "DevOps" positions and they more often than not have me doing so many random things that require all sorts of skills. I love it. It keeps things interesting, and it makes me very valuable to the company because I can do whatever they need. Sure, some places have a very narrow definition of DevOps, but that's usually the large companies/teams. If you can find something a bit smaller, then you'll have more of a jack-of-all-trades role. At least in my opinion.

ProZsolt 7y ago
Agree, but a lot of companies use this title as a CloudOps so basically Ops but on AWS/GCP At my previous company, I work as one and really enjoyed it. I was a software engineer, but I was also responsible for infrastructure, tests, CD/CI. Now, I'm looking for a job like this, but most of the companies just want ops people who can code a little bit for automation and support other developers work "thrown over the fence"
hanoz 7y ago
Whenever I see DevOps roles advertised they seem to consist of a wall of product names under "must have x years commercial experience of", which is not at all conducive to attracting a true turn-hand-to-anything generalist.
- autotune 7y ago
  Yeah but when it's "must have x years of experience of $CLOUD_PROVIDER" that's a whole ecosystem of tools to become proficient at. As someone who does DevOps I've learned to take any hard requirements in job descriptions with a grain of salt; companies are desperate for good DevOps talent, most suck at hiring for it, and some are aware of both of those facts and as a result are more flexible on some things than they would like you to believe.
  - shepardrtc 7y ago
    This has been my experience as well. Some companies are strict about requirements, such as the FAANG companies, but many other smaller companies just need someone who has a wide range of experience and can jump on new stuff without any problems. Obviously you have to know basic DevOps terminology, but after that everything is gravy.
- twblalock 7y ago
  Most of the time, those job requirements are flexible.

ProZsolt 7y ago

Agree, but a lot of companies use this title as a CloudOps so basically Ops but on AWS/GCP At my previous company, I work as one and really enjoyed it. I was a software engineer, but I was also responsible for infrastructure, tests, CD/CI. Now, I'm looking for a job like this, but most of the companies just want ops people who can code a little bit for automation and support other developers work "thrown over the fence"

hanoz 7y ago

Whenever I see DevOps roles advertised they seem to consist of a wall of product names under "must have x years commercial experience of", which is not at all conducive to attracting a true turn-hand-to-anything generalist.

autotune 7y ago
Yeah but when it's "must have x years of experience of $CLOUD_PROVIDER" that's a whole ecosystem of tools to become proficient at. As someone who does DevOps I've learned to take any hard requirements in job descriptions with a grain of salt; companies are desperate for good DevOps talent, most suck at hiring for it, and some are aware of both of those facts and as a result are more flexible on some things than they would like you to believe.
- shepardrtc 7y ago
  This has been my experience as well. Some companies are strict about requirements, such as the FAANG companies, but many other smaller companies just need someone who has a wide range of experience and can jump on new stuff without any problems. Obviously you have to know basic DevOps terminology, but after that everything is gravy.
twblalock 7y ago
Most of the time, those job requirements are flexible.