# DevOps Engineer Crash Course - Section 1

**URL:** <https://forum.devtalk.com/t/devops-engineer-crash-course-section-1/18078>\
**Category:** In The News\
**Tags:** devops, course\
**Created:** [19 August 2021 15:30 UTC](https://forum.devtalk.com/t/devops-engineer-crash-course-section-1/18078 "2021-08-19T15:30:45Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mantyjaska](https://forum.devtalk.com/user_avatar/forum.devtalk.com/mantyjaska/32/2137_2.png) [@mantyjaska](https://forum.devtalk.com/u/mantyjaska)\
**Post date:** [24 August 2021 05:41 UTC](https://forum.devtalk.com/t/devops-engineer-crash-course-section-1/18078/5 "2021-08-24T05:41:30Z")

</div>

I’ve read that before and it’s a good read too! Though I have few thoughts based on my own experience. Semantically I’d argue the DevOps interface mentioned in the article needs “engineering” in the organisation before developers can use it. It also needs maintaining, updating and planning. I guess “Consultant” or “Coach” would tick that box too, but I think it would give slightly wrong undertone about the level of involvement in the development of the processes used. So, I’d argue that DevOps Engineering can be, if not job title, at least job description.

As a side note, my own job title is not “DevOps” anything. The team I work in is not “DevOps”, it’s actually “infrastructure”. But when people ask what I do, I say “DevOps stuff”. So at least colloquially the meaning is clear to people in the industry.

---

_[View the full topic](https://forum.devtalk.com/t/devops-engineer-crash-course-section-1/18078)._