Lev Goncharov

Infrastructure simplifying engineer

View My GitHub Profile

Devops Roadmap

Date: 2024-10-14

About industry

One who wants to become a devops engineer should learn a lot in this journey. Before sharing the materials let me put things from A to Z and clarify who is who and why. I don’t want to touch salary topics because it’s quite well described in the The Trimodal Nature of Software Engineering Salaries in the Netherlands and Europe.

Seniority

Learning journey: hard & soft skills

bg contain

Usually before the senior level there is nothing interesting - you just learn, get practice & increase expertise. However at some point of time you should decide which track to choose. More technical or more people related. Soft skills (time management, mentoring, knowledge sharing, etc.) are also crucial and it is not possible to continue without them.

Learning journey: skillset

Learn deeply

Usually devops is a person with the combination of different skills. An those knowledge should be gotten in more less defined order. It’s doesn’t make sens to learn IaC without understanding underlaying principles of clouds, OS and networks.

Learning journey: learn deeply

Learn deeply and be T-shaped

In that journey you should learn deeply instead of technologies on the TOP. If you have fundomental knowledge it will you ability to troubleshoot complex problems.

Seniority levels

Some times it’s tricky to understand current seniority level, so you can estimate your level according the table. It’s not precise defenition but you can use it as a lighthouse in the journey. But please keep in mind that seniority it’s not about the title.

Role Planning Timeframe Complexity Risk Management Domain Expertise Big Picture Understanding Influence on People Experience (Years)
Junior 1-3 days Simple tasks Escalate Learning domain Not expected Self 0-2
Middle 1-2 weeks Tasks Report issues Competent domain Understand strategy Self 2-5
Senior 2 months Problems Tasks risks Expert domain Propose solutions Team (2-5) 5+
Staff 6 months Complex problems Project risks Company leader Evaluate strategy Teams (10+) 10+
Principal 1 year Reduce complexity Company risks Company leader Support strategy Organization (50+) 12+
Distinguished 1-2 years Coordinate problems Industry risks Industry leader Lead strategy Company (1000+) 14+
Fellow 3-5 years Pioneer areas Existential risks Industry leader Define big picture Industry (10000+) 15+

Problem solving

Senior!=title

It’s quite tricky to understand the current level. However, if you create a new complex problem from the existing problem then it might be possible that you are junior and just gaining the expirience. And it’s ok. But in case of senior people expect that he provides the most optimal and efficient sollution. It can be used as a marker.

A journey of a thousand miles starts with a single step

But it is crucial to keep in mind that our brain is too crucial. If you think that you know everything usually you know too litle. Becaus if you learn you understand that world is much more complicated that you can expect

Lessons learned

Materials

Intro

Intro: books

Intro: courses

Intro: articles

Intro: videos

Network

Network: books

Network: courses

Network: articles

Network: videos

OS

OS: books

OS: courses

OS: articles

OS: videos

OS: practices

OS: certifications

Docker

Docker: books

Docker: courses

Docker: articles

Docker: videos

Docker: certifications

CI/CD

CI/CD: courses

CI/CD: articles

CI/CD: videos

Cloud

Cloud: books

AWS: courses

Cloud: articles

Cloud: videos

IaC

books

courses

articles

videos

practices

certifications

k8s

k8s: books

k8s: articles

k8s: videos

k8s: practices

Monitoring

Monitoring: books

Monitoring: courses

Monitoring: articles

Monitoring: videos

Monitoring: certifications

Soft-skills

Soft-skills: courses

Soft-skills: articles

Development

Development: books

Development: courses

Development: articles

Development: videos

Development: practices

Development: certifications