30-Day Hands-On DevOps Engineering Cohort2 with Learnwithdevopsengineer

The 30-Day Hands-On DevOps Engineering Cohort is designed for people who already understand DevOps fundamentals but want experience actually doing the work.

Instead of following step-by-step tutorials, you'll work on an end-to-end application through a production-style engineering workflow.

You'll receive engineering requirements and tickets, investigate solutions, make technical decisions, implement changes, troubleshoot failures, and handle production-style incidents.

The goal is simple: by the end of 30 days, you should be able to explain what you built, why you built it, what broke, how you investigated it, and how you fixed it.

What you'll work with

Throughout the project, you'll encounter technologies including:

• Git & GitHub
• Docker & Docker Compose
• Terraform
• GitHub Actions
• Azure Container Apps
• Azure Container Registry (ACR)
• PostgreSQL
• Azure Networking
• Key Vault
• Managed Identity & RBAC
• Application Insights
• Azure Monitor & Alerts

These technologies aren't taught as isolated tools. They appear as the project requirements evolve and new engineering problems need to be solved.

How the cohort works

• Minimum 2 focused hours/day of independent hands-on project work
• 3 live engineering review sessions per week, up to 90 minutes each
• Direct technical feedback on your implementations and engineering decisions
• Guidance and targeted teaching during reviews when concepts, gaps, or blockers need deeper explanation
• Production-style incidents and troubleshooting exercises
• Dedicated communication channels for questions, blockers, discussions, and project updates
• Channels checked daily during a dedicated support window
• AI and documentation are allowed, but you must understand and be able to defend the work you submit
• Individual implementation — discussing approaches is encouraged, but exchanging completed solutions isn't
• No recorded step-by-step classes

Most of your time will be spent working on the project, not watching lectures.

You'll attempt the requirements first. During reviews, we'll inspect implementations, discuss different approaches, troubleshoot problems, challenge engineering decisions, and go deeper into concepts where necessary.

If you're already doing something well, the goal isn't to make you sit through material you already understand — it's to challenge you further.

Live sessions

We'll have 3 live engineering review sessions each week, up to 90 minutes per session.

These sessions are designed for active technical discussions, implementation reviews, troubleshooting, architecture decisions, and targeted explanations — not traditional lectures.

The sessions will not be recorded.

If you occasionally miss a session, you can continue working on the project and join the next review. Important project decisions and clarifications will be documented through the cohort communication channels.

Missed live sessions are not replaced with individual make-up sessions.

Who should join?

This cohort is a good fit if:

• You already understand the fundamentals of DevOps
• You want hands-on implementation rather than more tutorials
• You want to become better at troubleshooting
• You want experience making and defending engineering decisions
• You're comfortable researching and attempting problems independently
• You can consistently commit a minimum of 2 focused hours per day for 30 days

Who should NOT join?

This cohort is not designed for complete beginners.

It may not be the right fit if you're looking primarily for:

• Step-by-step recorded lessons
• Solutions before attempting problems yourself
• A traditional instructor-led course
• A certificate as the primary outcome
• Guaranteed job placement
• Someone to complete the project for you

The objective isn't to finish another course.

The objective is to spend 30 days working through an end-to-end DevOps project and becoming better at solving engineering problems yourself.

Using AI

AI tools and documentation are allowed.

However, AI should assist your engineering process, not replace your thinking.

You should investigate the requirement or problem yourself, develop an understanding of what's happening, and then use AI where it helps you research, troubleshoot, validate an approach, or work more efficiently.

Anything you implement or submit must be something you can understand and explain during review.

Azure subscription

Participants will use and pay for their own Azure subscription.

The project will be designed with cost awareness in mind, and we'll keep Azure usage and cloud costs as low as reasonably possible.

Actual Azure costs can vary depending on individual usage.

What should you walk away with?

By the end of the 30 days, the goal is for you to have:

• An end-to-end DevOps project you personally implemented
• Experience taking an unfamiliar application from source code toward cloud operations
• Hands-on experience with infrastructure, CI/CD, networking, security, identity, monitoring, and operations
• Production-style incidents you've investigated and documented
• Engineering and architecture decisions you can explain and defend
• Better stories for scenario-based DevOps interviews
• Stronger troubleshooting confidence because you actually did the work

Don't leave saying, “I completed another DevOps course.”

Leave being able to explain what you built, why you built it, what broke — and how you fixed it.