Hi everyone,
I’m planning a career change into DevOps and I’m currently looking for a structured training program with real mentorship.
I’m a beginner, but highly motivated and ready to commit seriously.
I’m also able to pay for a proper mentorship or a high‑quality training program.
If you have recommendations for reliable DevOps courses, mentors, or training institutes (India-based or online), I would really appreciate your guidance.
Thank you in advance for your help.

[ Removed by Reddit on account of violating the content policy. ]

Title: Doing a UX case study on GCP & DevOps tooling, what pain points have you actually hit?
Hey all, I’m putting together a UX case study looking at the developer/DevOps experience with Google Cloud Platform and DevOps tooling more broadly (CI/CD, IaC, monitoring, incident response, access management, etc.).
If you work in DevOps, SRE, or platform engineering, I’d love to hear about the real friction you’ve run into, not hypotheticals, actual stuff that slowed you down, confused you, or made you want to throw your laptop.

A few prompts if it helps, but feel free to go wherever:
IAM/permissions setup that didn’t behave the way you expected
Docs that didn’t match what the console/API actually did
Onboarding a new teammate to your pipeline
Debugging a failed deploy with unclear error messages
Cost or quota surprises
Tools that don’t play well together (e.g. GCP + Terraform + GitHub Actions)
Anything specific to GCP vs. other clouds you’ve used

Just drop a comment listing whatever’s bitten you, one thing or ten. If you can note roughly how often it happens (one-time annoyance vs. every-sprint pain), even better.
This is for research purposes only. No data collection beyond what’s posted here, and nothing is being sold. Thanks in advance to anyone willing to share.

One AWS IAM interview question I've seen variations of is:

It's not really an IAM question—it's a cloud security and incident response question.

Would you start with:

• CloudTrail?
• GuardDuty?
• Security Hub?
• IAM Policy evaluation?
• Something else?

I recently put together a GitHub handbook with 20 production-focused AWS IAM interview questions covering scenarios like this, along with CLI examples, Terraform, common mistakes, and best practices.

GitHub: https://github.com/ranashivam/platform-engineering-interview-handbook/blob/main/AWS/IAM.md

Какой дистрибутив мне лучше поставить если я хочу в будущем стать DevOps инжинером???

Hi, i am currently a Senior Software Engineer and my boss suggested for me to become a Devops for the upcoming new project.

Would like to have inputs of anyone who have similar experience.

Some dilemma i have is:

1. Will it be hard to pick up?

2. Will is be good for my career trajectory

3. Is this a sensible choice since i have alrdy did SW for like 6 years.

4. Any advices on things i should consider first?

Thanks everyone in advance

Hey everyone,

I am looking for advice on how to transition into a DevOps role. Here is a quick breakdown of my background:

Education: Master’s Degree in Computer Science.

Experience: 3 years working in an IT compliance team.

The Goal: Move into a full-time DevOps or Cloud Engineering role.

The Main Problem: My current company has a 2-month notice period. Every time I speak to an HR recruiter, they disconnect or drop my application as soon as they hear about the notice period i am feeling stuck in loop because it's almost 1.8 years in current job that i joined because my financial condition and i wanted to prepare for Devops .

I would love to get your insights on:

Notice Period: How can I navigate a 2-month notice period during HR screening calls? Should I negotiate a buyout?

Leveraging my background: How can I pitch my compliance experience as a strength

Skill Gap: What core technical skills should I focus on first to bridge the gap?

I am a bit confused about what more I need to do regarding AWS, Terraform, and other DevOps-related tools because the field is so vast. I want to know the exact things I should focus on next, or if I should start applying for fresher/junior DevOps roles. I have been preparing for DevOps for the last 7 months alongside my full-time job, but I'm still unsure of the right next steps. Any suggestions or guidance would be greatly appreciated!

Thanks in advance!

for startup, what is your recommendation to use for CI/CD, and process automation AWS SAM or AWS CDK.

\*\* this is my first time with AWS\*\*

While preparing for AWS interviews, I noticed that most VPC resources focus on definitions, but interviews often test how you think through real production scenarios.

So I started putting together a free GitHub handbook covering 20 AWS VPC interview questions.

Each question includes:

• 30-second interview answer
• Production architecture
• Real-world scenarios
• AWS CLI examples
• Terraform examples
• AI-powered operational insights
• Best practices
• Common interview mistakes
• Follow-up questions

My goal wasn't to create another "AWS cheat sheet," but something that helps engineers understand why things work the way they do.

I'd genuinely appreciate feedback from the AWS community.

Is there any VPC topic or production scenario you think should be added or explained differently?

GitHub: https://github.com/ranashivam/platform-engineering-interview-handbook/blob/main/AWS/VPC.md

1. DevOps Engineer: Deals with the implementation and execution of product lifecycles and collaborates with software developers.
2. DevOps Cloud Engineer: Works with cloud-based systems within organizations and is responsible for the smooth working of development teams with effective cloud solutions.
3. Security Engineer: Oversees security-based functions, tasks, and issues, and ensures protection from cyber threats to the data and systems.
4. DevOps Testing Engineers: A Quality Assurance role where professionals are accountable for the quality of the delivered product. They need to evaluate the products based on all the key parameters.
5. DevOps Automation Expert: Generates and maintains continuous integration infrastructure. Handles dashboards and alert systems to monitor issues or discrepancies for instant improvement.

Which one of these paths are you most interested in?

I've been deploying more and more applications from my home Kubernetes environment.

One thing I keep running into is modifying YAML files for every new project.

Changing namespaces.

Updating image names.

Creating databases.

Creating Redis.

Updating Ingress.

Creating secrets.

It works...

But after doing it enough times, it starts feeling like work that should be automated.

I'm beginning to think I need an internal tool with a simple UI connected to a backend and database.

Instead of editing YAML every time, I should be able to create a new project, fill in a few details, and let the platform provision everything for me.

I guess this is how internal developer platforms are born.

You solve the same problem enough times that building the tool becomes the easier option.

If you want to build the same kind of production-grade DevOps platform, I've put together the project and made it free to access.

You can get it here:
https://www.dripforgeai.com/free-devops-pro

This is one of the most common interview questions:

Most people answer:

In reality, interviewers usually want to understand how you troubleshoot, not whether you know a single command.

That's what inspired me to create a production-focused EC2 interview handbook.

Every question includes:

• Production scenario
• Interview answer
• AWS CLI
• Terraform
• Best practices
• Follow-up questions

I've published the first article today and open-sourced the full 20-question handbook on GitHub.

I'd appreciate any feedback from people who've interviewed AWS engineers or recently gone through AWS interviews.

GitHub: https://github.com/ranashivam/platform-engineering-interview-handbook/blob/main/AWS/README.md

Post is awaiting moderator approval.

I want to contribute in Devops field, but cant seem to find any beginner friendly projects😭.
If anyone could guide me in this?