After the question about job role boundaries of a DevOps engineer has been closed, I'd like to share that I feel a strong disagreement and disharmony about that.
Indeed, the question is not of a technical matter "what X do I need to do to make Y work after I've tried Z and got an F error".
Nevertheless, the facts of the real world are as far as I can relate:
- there are many "DevOps engineer" jobs out there (despite of the fact that this must be a misunderstanding)
- partly, as our new member confirms, there are organizations where a DevOps engineer is sort of an extended system administrator. This is also by the way imho a sad circumstance that we have more system- and ops- related questions than development related questions similar to "how do I prototype containers in my IDE" either "how do I automate virtual infrastructure prototyping in context X".
So then I think it's very legitimate to ask a question at the biggest Q&A site for DevOps, what are the boundaries in this job role.
Closing such questions will keep us away from focusing on the actual DevOps culture which is one of the main drivers why we have this community.
Therefore I can't understand how much is the question not having enough focus (this was the reason to close) also given that obviously some folks have found the accepted answer helpful, and there is one another good answer.