<p>There is a nice hands-on path into the DevOps world:</p>

<ul>
<li>Read books to set the mental direction. Starting out with "The Phoenix Project" is not the worst bet. We can discuss the literary qualities of the story, but it gives a very sound idea on what are common pitfalls during software development (or in the larger IT world), and how to avoid. It is not too specific about a method (yes, it does use Kanban as a basic scheme, but Kanban itself is quite unspecific, compared to others like Scrum). If that book is too cheesy for you, take "The Devops Handbook" from the same authors.</li>
<li>Learn basic tools. Build a basic DevOps toolset. You can start with Git, Gitlab, Docker, Ansible, Vagrant, to name a few concrete choices (except for Git, there are plenty of alternatives, but those are nice). This gives you Code Control, Pipelines, Containers, Configuration Management, VM Management.</li>
<li>For your next application, setup a very basic CI/CD pipeline using Gitlab.</li>
<li>Read more practical things like the "12-Factor Apps" article, and try to understand what all of the 12 factors are about.</li>
<li>Learn orchestration. Install MiniShift on your own PC, use it to develop/locally deploy a few small applications. Try to apply the concepts from 12-Factor Apps to MiniShift. Learn more about OpenShift, play around with their free online demo area. Dive into Kubernetes.</li>
<li>Get your CI/CD pipeline running in MiniShift/OpenShift. Think about how you would do certain things (e.g. what happens if you scale the Pod containing your database... etc.).</li>
<li>Get an AWS demo/cheap account and play around with their offering. Look into all their parts that are not trivial VMs - play with Lambdas, etc.</li>
</ul>

<p>All of this is easy and fun - each single step is more or less self contained, and if you understand what you are doing along the way, then you <em>are</em> a DevOps guy.</p>

<p>If you let it be known in the working environment that you have all this know-how, then DevOpsy work should come your way. If it doesn't, find a new employer and strongly emphasize your toolbox and pay attention during your interviews, whether they have CI/CD etc. in their process. No need to look for specific "DevOps Engineer" jobs.</p>

CC BY-SA 3.0
2018-04-15T19:04:48.483Z
2018-04-15T19:04:48.483Z
AnoE
<p><strong>DevOps</strong> is not a role and in words of <strong>@Tensibai</strong> <a href="https://devops.stackexchange.com/a/160/15">here</a>:</p>

<blockquote>
  <p>DevOps is roughly an organization pattern aiming at breaking the silo between developers and sysadmins.</p>
</blockquote>

<p>So, you could already be on the DevOps moto and if you don't think you are, you can probably just try to implement the DevOps pattern on your organization or move to another organization with that pattern already implemented.</p>

<p>You may want to become an Infrastructure Engineer, a SysAdmin Engineer, an Automation Engineer, a Site Reliability Engineer, a Performance Engineer... but surely you can not become a DevOps Engineer.</p>

<p>You can get a good sense of your path by reading some questions and answers on this site. Here are a few ones:</p>

<p><a href="https://devops.stackexchange.com/questions/2892/what-is-devops">What is DevOps?</a></p>

<p><a href="https://devops.stackexchange.com/questions/1894/what-is-the-difference-between-devops-engineer-vs-devops-consultant-vs-devops-ar">What is the difference between DevOps engineer Vs DevOps consultant Vs DevOps architect?</a></p>

<p><a href="https://devops.stackexchange.com/questions/86/what-is-the-difference-between-sre-and-devops">What is the difference between SRE and DevOps?</a></p>

<p><a href="https://devops.stackexchange.com/questions/788/what-could-be-a-valid-definition-of-devops-to-introduce-it-to-a-novice/1407#1407">What could be a valid definition of DevOps to introduce it to a novice?</a></p>

<p><a href="https://devops.stackexchange.com/questions/911/what-is-the-difference-between-the-traditional-development-and-operations-model">What is the difference between the traditional Development and Operations 
Model and Site Reliability Engineering?</a></p>

<p><a href="https://devops.stackexchange.com/questions/157/what-is-the-difference-between-sysadmin-and-devops-engineer">What is the difference between Sysadmin and DevOps Engineer?</a></p>

CC BY-SA 3.0
2018-04-19T10:47:29.043Z
if so , what is this aws DevOps certification all about ?
Abhi Ravi
CC BY-SA 3.0
2018-04-19T16:45:38.967Z
They are just taking advantage of the trendy name, that specific certification should be named "CI/CD Certification" or something like that (which is  still a team, not exactly a single role).
Gepser Hoil
CC BY-SA 3.0
2018-04-15T16:16:22.647Z
2018-04-15T16:23:21.173Z
2018-04-15T16:23:21.173Z
Gepser Hoil
<p>Please suggest me a right path to this DevOps career. From blogs Im not getting a well defined path. 
What all courses I have to take.</p>

CC BY-SA 3.0
2018-04-15T21:23:49.913Z
What did you understand from the resources on the internet, i.e. please add your research and impediments.
030
CC BY-SA 3.0
2018-04-16T16:24:11.173Z
You may wish to explore ruby-based configuration management toolsets like puppet, chef and Katello/Foreman.
James Shewey
<amazon-web-services><culture><learning>
How can I become a DevOps Engineer?
Abhi Ravi
# How can I become a DevOps Engineer?

(Asked by: username_0 on 2018-04-15)

Please suggest me a right path to this DevOps career. From blogs Im not getting a well defined path.
What all courses I have to take.

**Tags:** amazon-web-services, culture, learning

> **Comments:**
> **username_1**: What did you understand from the resources on the internet, i.e. please add your research and impediments.  
> **username_2**: You may wish to explore ruby-based configuration management toolsets like puppet, chef and Katello/Foreman.  

---

## 2 answers

### Answer by username_4 on 2018-04-15. Score: 5 | Accepted answer

**DevOps** is not a role and in words of **@Tensibai** [here](https://devops.stackexchange.com/a/160/15):

> DevOps is roughly an organization pattern aiming at breaking the silo between developers and sysadmins.

So, you could already be on the DevOps moto and if you don't think you are, you can probably just try to implement the DevOps pattern on your organization or move to another organization with that pattern already implemented.

You may want to become an Infrastructure Engineer, a SysAdmin Engineer, an Automation Engineer, a Site Reliability Engineer, a Performance Engineer... but surely you can not become a DevOps Engineer.

You can get a good sense of your path by reading some questions and answers on this site. Here are a few ones:

[What is DevOps?](https://devops.stackexchange.com/questions/2892/what-is-devops)

[What is the difference between DevOps engineer Vs DevOps consultant Vs DevOps architect?](https://devops.stackexchange.com/questions/1894/what-is-the-difference-between-devops-engineer-vs-devops-consultant-vs-devops-ar)

[What is the difference between SRE and DevOps?](https://devops.stackexchange.com/questions/86/what-is-the-difference-between-sre-and-devops)

[What could be a valid definition of DevOps to introduce it to a novice?](https://devops.stackexchange.com/questions/788/what-could-be-a-valid-definition-of-devops-to-introduce-it-to-a-novice/1407#1407)

[What is the difference between the traditional Development and Operations
Model and Site Reliability Engineering?](https://devops.stackexchange.com/questions/911/what-is-the-difference-between-the-traditional-development-and-operations-model)

[What is the difference between Sysadmin and DevOps Engineer?](https://devops.stackexchange.com/questions/157/what-is-the-difference-between-sysadmin-and-devops-engineer)

> **Comments:**
> **username_0**: if so , what is this aws DevOps certification all about ?  
> **username_4**: They are just taking advantage of the trendy name, that specific certification should be named "CI/CD Certification" or something like that (which is  still a team, not exactly a single role).  

---

### Answer by username_3 on 2018-04-15. Score: 5

There is a nice hands-on path into the DevOps world:

* Read books to set the mental direction. Starting out with "The Phoenix Project" is not the worst bet. We can discuss the literary qualities of the story, but it gives a very sound idea on what are common pitfalls during software development (or in the larger IT world), and how to avoid. It is not too specific about a method (yes, it does use Kanban as a basic scheme, but Kanban itself is quite unspecific, compared to others like Scrum). If that book is too cheesy for you, take "The Devops Handbook" from the same authors.
* Learn basic tools. Build a basic DevOps toolset. You can start with Git, Gitlab, Docker, Ansible, Vagrant, to name a few concrete choices (except for Git, there are plenty of alternatives, but those are nice). This gives you Code Control, Pipelines, Containers, Configuration Management, VM Management.
* For your next application, setup a very basic CI/CD pipeline using Gitlab.
* Read more practical things like the "12-Factor Apps" article, and try to understand what all of the 12 factors are about.
* Learn orchestration. Install MiniShift on your own PC, use it to develop/locally deploy a few small applications. Try to apply the concepts from 12-Factor Apps to MiniShift. Learn more about OpenShift, play around with their free online demo area. Dive into Kubernetes.
* Get your CI/CD pipeline running in MiniShift/OpenShift. Think about how you would do certain things (e.g. what happens if you scale the Pod containing your database... etc.).
* Get an AWS demo/cheap account and play around with their offering. Look into all their parts that are not trivial VMs - play with Lambdas, etc.

All of this is easy and fun - each single step is more or less self contained, and if you understand what you are doing along the way, then you *are* a DevOps guy.

If you let it be known in the working environment that you have all this know-how, then DevOpsy work should come your way. If it doesn't, find a new employer and strongly emphasize your toolbox and pay attention during your interviews, whether they have CI/CD etc. in their process. No need to look for specific "DevOps Engineer" jobs.


---

