Recruiters and companies love the term devOps, and now DevSecOps, because it enables them to keep job descriptions generalized. This way you can be a software d

Recruiters and companies love the term devOps, and now DevSecOps, because it enables them to keep job descriptions generalized. This way you can be a software developer that is fluent in Python or PHP, but they can also pressure you to do everything from writing proposals to setting up and securing app infrastructure in the cloud (because it's all called devOps now!), that way they can reduce the number of overall jobs for projects and make sure apps have massive gaps in configuration and implementation... It's also the reason why many apps and sites fail regularly, because you can only squeeze so much juice out of a lemon, and less eyes on a project mean testing is often deprioritized and even skipped due to the cost of doing it. By combining roles and spreading them across multiple disciplines it can also cover bigger salary demands of the most talented developers, but it also drives burnout and toxic work culture. For example; A traditional development team of 4 people (e.g. 1 front end dev, 1 back-end dev, a System Admin, and a tester) is now cut down to 2 people. 4x 60k salaries now cover 2x $120k salaries for people that do everything under the flag of devOps... The company bills hourly now rather than per employee, but saves money by only having to cover costs like health care for 2 employees now instead of 4... Classic "corporate shell-game" move. :/ The system is broken, and mostly driven by marketing and profit-driven results. Don't fall victim to the hype, get them to fully detail your line of work prior to joining a team despite it being no consolation on what your actual role will involve. :P