Mischa van den Burg

Devs who want a DevOps job, read this:

You're failing because you're doing the same thing that everybody else does.

Even though you have 2-8 years of experience, you're still just a junior in the CV pile.

What does everybody else do?

1. Watch random free video tutorials without a plan
2. Learn two cloud providers at once
3. Going straight for containers & Kubernetes
4. Consuming instead of building.

I've helped hundreds of people land DevOps jobs within months.

I went from nurse to Senior DevOps in 4 years and created a system to repeat these results in others.

Here's what you should do:

First, be intentional. Create a clear plan for yourself and study accordingly.

Having a clear plan starts with having a clear goal.

The main tech stack you should focus on:
- Linux - Containers
- Kubernetes
- Automation (CI/CD)

Stick to one cloud provider.

Research the market you wish to work in. Find which one has the most jobs.

Master that one.

Everything becomes easier when you master the fundamentals.

For DevOps, Linux is the root of everything.

If you don't understand Linux on a deep level, everything else becomes extremely difficult.

Don't skip the foundations if you want to build a strong building.

Instead of consuming video tutorials, you should start building.

Start with a desired outcome. Identify what you need to learn for that outcome.

Learn ONLY what you need to achieve that outcome.

Create a new desired outcome.

This is how you should learn.

Literally all of my students land their jobs because I teach them to build a Kubernetes homelab.

The interviewing process changes from a technical interrogation to a conversation about what you've built.

If you take away only one thing from this post, it should be this: Build a home lab.

If you are serious about landing a DevOps job, you can apply for my mentorship.

Go here:


kubecraft.click/04cd04

5 days ago (edited) | [YT] | 121

Mischa van den Burg

Another job landed in just two weeks!

This is a record for KubeCraft.

If you want to see the system in action, read Lennard's post.


We only work with serious people who are ready to follow a proven system, so if that’s you,

book your qualification call here → kubecraft.click/4gr

1 week ago (edited) | [YT] | 78

Mischa van den Burg

Two more DevOps jobs landed last week 🚀

Inside the KubeCraft Career Accelerator, we just celebrated two members starting new roles one as a Junior DevOps Engineer, another in their dream company.

In 2025, the market is competitive because most engineers still learn in isolation, follow random YouTube tutorials, and never build real production skills. That’s why they stay invisible to recruiters.

Our members take a different path. They focus on:
• Learning the exact technologies the market wants right now
• Building production-grade projects that act as proof of skill
• Positioning themselves so companies come to them

📅 This means slots have opened up. We only work with serious people who are ready to follow a proven system, so if that’s you, book your qualification call here → kubecraft.click/4gr

2 weeks ago | [YT] | 90

Mischa van den Burg

Many of you requested a tour of my Arch Linux setup, as well as a video in my older style: long, valuable screen-sharing. Here you have both!
Enjoy https://youtu.be/-dfq1blmVB8 - The Arch Linux Setup for 6-figure DevOps Engineers

2 weeks ago (edited) | [YT] | 83

Mischa van den Burg

Looks like I finally made it as a tech YouTuber!

And no, I’m not taking the sponsorship.

I prefer to keep providing you with quality content that lands you jobs instead of shilling products I don’t even use.

3 weeks ago | [YT] | 176

Mischa van den Burg

𝗧𝗵𝗲 𝗲𝗮𝘀𝗶𝗲𝘀𝘁 𝘄𝗮𝘆 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝗵𝗼𝗺𝗲 𝗹𝗮𝗯 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗯𝗿𝗲𝗮𝗸𝗶𝗻𝗴 𝘁𝗵𝗲 𝗯𝗮𝗻𝗸.

Here’s exactly how I run mine for daily learning and real-world practice.

🖥️ 𝗦𝘁𝗲𝗽 𝟭: 𝗛𝗮𝗿𝗱𝘄𝗮𝗿𝗲
Start with an old laptop. 4 GB of RAM minimum.
Add nodes later if you need them.
💡 Used thin clients work great for extra nodes and cost around 200$.
Avoid surprise cloud bills by running everything local.

⚙️ 𝗦𝘁𝗲𝗽 𝟮: 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺
Begin with k3s. It is lightweight and simple.
Move to full Kubernetes when you are ready.
Add GitOps with Flux or Argo.
Set up basic monitoring from day one.

📦 𝗦𝘁𝗲𝗽 𝟯: 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀
Deploy one important service first.
Document everything in Git.
Focus on security basics.
Automate small tasks one by one.

📈 𝗦𝘁𝗲𝗽 𝟰: 𝗦𝗰𝗮𝗹𝗶𝗻𝗴
Keep your control plane separate from your worker nodes.
Add redundancy when you need it.
Take proper backups.
Monitor your resource usage closely.

🧠 𝗦𝘁𝗲𝗽 𝟱: 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴
Break things on purpose.
Practice troubleshooting until it feels natural.
Try new tools and see what works.
Share what you learn, it sticks better.

The key is to start small and expand based on real needs.
Most important of all: use it every day.

4 weeks ago | [YT] | 209

Mischa van den Burg

This is a video you’ll only need to watch once, but the insight stays with you forever.
Here’s how the timing of your job search can be the difference between landing interviews… and hearing nothing back.

Watch or Save for later: The Hidden DevOps Hiring Calendar → https://youtu.be/4yzHp_5Ky0o

4 weeks ago (edited) | [YT] | 18

Mischa van den Burg

Got questions about DevOps, Kubernetes, or landing your next role? THIS Sunday 27/7 at 4 PM (CEST) I'll be hosting a live Q&A for DevOps engineers.

No fluff. Just real answers. Free to enter.

I'll be hosting this from my Free community, you can join here:
www.skool.com/mischa

See you there!

1 month ago (edited) | [YT] | 33

Mischa van den Burg

Why I ditched Go after 12 months (Python won)

I spent a year learning Go, but I switched back to Python.
Why? It made it easier to get a job.
In my early DevOps years, I used Python every day. But I wanted to learn Go because so much modern DevOps runs on it.

WHAT I FOUND LEARNING GO

Kubernetes and many cloud tools are built in Go. Most projects are huge and hard to fully understand if you don't write code full time.
Now I use AI to help me read Go when I need it.
Learning Go was still worth it:

Strict typing
Memory control
Fast single binaries

Why I came back to Python:

More jobs here in the Netherlands need Python
Easy to learn but has depth
Huge community and libraries
AI and ML run on Python with PyTorch and NumPy

In daily DevOps I write scripts, APIs and small tools. Python does all of this well.
It keeps me flexible and ready for the AI side too.

WHY BOTH LANGUAGES MATTER

Both languages matter:

Go runs so much infrastructure
Python keeps me productive and open to more work
Here's what I actually build with Python in my daily DevOps work:
Automation scripts
APIs for internal tools
Small utilities and tools
AI/ML integrations when needed

WHAT I LEARNED FROM THIS EXPERIENCE

Both languages matter, but in different ways:
Go runs so much infrastructure we depend on
Python keeps me productive and employable

I still use my Go knowledge when I need to understand Kubernetes source code or debug cloud-native tools. But for building solutions day-to-day? Python wins.

Ready to level up your Python & DevOps skills? Join the KubeCraft community where we share practical projects and land people jobs every week

skool.com/kubecraft
​
Cheers,
Mischa

1 month ago | [YT] | 95

Mischa van den Burg

How do you feel about Linux for DevOps Engineers. Is it required to become a DevOps Engineer?

1 month ago | [YT] | 39