<p>What <em>you</em> should learn next is highly contextual, so I fear this question will be closed as opinion-based.
However, there are a few patterns which we tend to see, which may help you understand where you are on <em>your</em> journey <em>with respect to the average</em> DevOps figure's  career roadmap.</p>
<p>I propose as an answer to this question:</p>
<ol>
<li>Take a look at <a href="https://roadmap.sh/devops" rel="nofollow noreferrer">https://roadmap.sh/devops</a></li>
<li>Select the items you feel you've mastered</li>
<li><strong>Decide whether you want to specialise or generalise</strong></li>
</ol>
<p>If you want to specialise, spend time in the area where you have the most experience (maybe Design Patterns), else if you want to generalise, pick off topics that are outside of your current comfort zone.</p>
<p>As an example I attach a screenshot of what a a roadmap of a typical engineer might look like:</p>
<p><a href="https://i.sstatic.net/Wkweb.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Wkweb.png" alt="enter image description here" /></a></p>
<p>This person might decide to specialise in monitoring, or generalise by learning more in the CI/CD space.</p>

CC BY-SA 4.0
2023-07-10T16:08:49.667Z
should I follow some particular order or can start from anywhere? Would a college level course in operating systems help for devops?
zeeshanseikh
CC BY-SA 4.0
2023-07-10T15:19:42.677Z
2023-07-10T15:19:42.677Z
Bruce Becker
<p>I'm working as a devops engineer in a big tech company (local). The technologies used here are nginx, linux, sql, redis, docker, glassfish and payara, kubernetes, tomcat, gitlab, jenkins etc. I've learnt linux and sql till date. What should I learn next? I mean the order might be important. But the important thing to note is that for example for jenkins, mostly just building jenkins is done, there's not much of other tasks. So, will it even be worth it to learn all stuffs in detail?</p>
<p>They're planning to use kafka after few months as well.</p>

<docker><kubernetes><jenkins><nginx><tomcat>
What should I learn next as a devops beginner?
zeeshanseikh
# What should I learn next as a devops beginner?

(Asked by: username_0 on 2023-07-10)

I'm working as a devops engineer in a big tech company (local). The technologies used here are nginx, linux, sql, redis, docker, glassfish and payara, kubernetes, tomcat, gitlab, jenkins etc. I've learnt linux and sql till date. What should I learn next? I mean the order might be important. But the important thing to note is that for example for jenkins, mostly just building jenkins is done, there's not much of other tasks. So, will it even be worth it to learn all stuffs in detail?

They're planning to use kafka after few months as well.

**Tags:** docker, kubernetes, jenkins, nginx, tomcat


---

## 1 answers

### Answer by username_1 on 2023-07-10. Score: 1

What *you* should learn next is highly contextual, so I fear this question will be closed as opinion-based.
However, there are a few patterns which we tend to see, which may help you understand where you are on *your* journey *with respect to the average* DevOps figure's career roadmap.

I propose as an answer to this question:

1. Take a look at <https://roadmap.sh/devops>
2. Select the items you feel you've mastered
3. **Decide whether you want to specialise or generalise**

If you want to specialise, spend time in the area where you have the most experience (maybe Design Patterns), else if you want to generalise, pick off topics that are outside of your current comfort zone.

As an example I attach a screenshot of what a a roadmap of a typical engineer might look like:

[![enter image description here](https://i.sstatic.net/Wkweb.png)](https://i.sstatic.net/Wkweb.png)

This person might decide to specialise in monitoring, or generalise by learning more in the CI/CD space.

> **Comments:**
> **username_0**: should I follow some particular order or can start from anywhere? Would a college level course in operating systems help for devops?  

---

