Can anyone please tell me?🙏🏻

This is only for people in college, recent grads, or anyone trying to land their first DevOps role. I'll review your resume for free.

I prefer people who already have basic to some knowledge of DevOps (Linux, Git, Docker, a cloud, or a project or two). Please share your resume in a DM.

About me: I work as a DevOps engineer with 3 years of experience.

​

Need help

Quick disclosure: I work at Archer from hackajob, so this is our own platform data, based on 7,362 US DevOps and Cloud roles posted in 2026. Our client base skews finance, enterprise and defense.

Median across everything was around $150k. Some other highlights:

- The biggest single pay jump was the sysadmin to platform engineer move, about +$50k, and a lot of it builds on what sysadmins already do day to day.

- AI/automation experience (LLMs, ML, Copilot, general automation) was the best-paying skill signal, roughly +$16k over the median, and it showed up in about 1 in 4 postings.

- AWS was in ~35% of postings, roughly double Azure, with GCP a distant third.

If you’re a sysadmin, that platform engineering jump is probably the most reachable one on the list. A lot of it is scope and title, and you’re likely already doing part of the job.

Full breakdown by role, skill and city is here if you want it (it's not gated and there's no sign up/subscribtion needed): https://hackajob.com/talent/reports/us-devops-cloud-jobs-2026?utm_source=reddit&utm_medium=social&utm_campaign=jobs_report&utm_content=us_devops_cloud

Does this match what you’re seeing/what you are currently earning?

I'm a backend dev (Laravel/AWS mostly) and I kept noticing that system design resources stop at boxes and arrows. Nobody tells you what happens to your design at 3,000 RPS, or why your app can't reach your DB, or what a retry storm looks like. So I built something to see it.

It's called InfraSim. You design an architecture on a canvas, put traffic on it, and watch where it falls over. Nothing real gets deployed, no cloud account needed. Everything is simulated.

What it does right now:

- Canvas with services from AWS, GCP, Azure and OCI (about ~240 of them), plus custom ones you can add

- Every service has an editable average response time (p50/p95), capacity and mock responses, so you can say "this DB takes 40ms" and see the effect

- You can paste a JS handler, give it a test payload, and see logs, errors and which services it called. If your code crashes because a mock response is missing a field, it can auto-fill the mock

- Set RPS and a traffic pattern (ramp, spike, etc). Overloaded services get a red bar and shake, and a "Why?" panel explains the cause

- Estimated monthly cost from public price lists, per region

- Networking: it tells you why service A can't reach B (missing security group rule, no NAT, bad route) and offers a fix

- Terraform export, and import from a plan JSON

- A few challenges, like "survive an AZ outage" or "handle 5k RPS under $500/mo"

Honest limits: it's a learning tool, not a benchmark. The latency and quota numbers are editable defaults, not measured values, and cost is on-demand list price only.

Self-hosting: [docker compose up, one or two lines on how to run it]

Repo: https://github.com/MrNamra/InfraSim

I'd really like feedback from people who've run real systems. What failure would you want it to show? What's missing or just wrong? Happy to hear it's wrong, that's more useful than praise.

Some images:

​

Hi everyone,

I'm currently looking to start a career in cloud/DevOps. I'm looking for a program that starts from the basics.

What I'm looking for:

Hands-on training (labs, real projects), not just theory

Coverage of Azure, Linux, Git, CI/CD, Docker/Kubernetes, Terraform, and basic scripting

Resume and interview support, ideally with genuine placement help

Classroom

Which institutes or trainers in Hyderabad have you actually learned from? (Ameerpet, Hitech City, etc.)

Any you'd avoid, such as ones with fake placement promises?

Hi everyone,

I'm looking for some honest career advice from people working in DevOps, SRE, Platform Engineering, or related fields.

I'm currently working as a QA Automation Engineer (SDET) with around 2+ years of experience. My primary tech stack includes:

\- Python

\- Robot Framework

\- Selenium

\- API Testing (REST/Postman)

\- CI/CD (Atlassian Bamboo)

\- Git, GitHub, and Linux basics

\- Automation framework development and maintenance

Lately, I've been seriously considering transitioning from QA Automation to DevOps.

There are a few reasons behind this decision.

First, with the rapid advancement of AI, I feel traditional testing and even parts of automation engineering could undergo significant changes in the coming years. I'm concerned about how this might impact long-term opportunities in QA.

On the other hand, DevOps interests me because it involves infrastructure, cloud computing, system reliability, deployments, automation, and problem-solving at a deeper engineering level.

I also feel that DevOps requires substantial practical experience and a strong understanding of systems, networking, infrastructure, and production environments. AI can certainly assist engineers, but I don't think it can completely replace the experience and judgment required to manage real-world infrastructure.

Another factor is the job market. From what I've observed, DevOps roles seem to offer good opportunities and compensation compared to QA Automation, although I'd like to hear whether this is actually true from people working in the industry.

I'm willing to put in the effort and dedicate to learning and gaining hands-on experience

Fortunately, my current organization also supports internal role transitions, so there's a possibility of moving into a DevOps-related role internally rather than having to start completely fresh at another company.

I'd particularly appreciate advice from people who have transitioned from QA to DevOps, hiring managers, and engineers with 3–5+ years of experience.

I'm not looking for motivational answers. I'd genuinely appreciate realistic opinions, including reasons why I shouldn't make this switch.

What would you do in my position?

Thanks!

I have 4 years of experience in DevOps, primarily working with AWS and ECS. Throughout these years, I've had the opportunity to work extensively on cloud infrastructure, infrastructure automation, and infrastructure-level CI/CD pipelines.

However, I haven't had much hands-on exposure to Kubernetes or application-level CI/CD pipelines yet.

My long-term goal is to transition into Platform Engineering, but I've been struggling to figure out where to start and how to structure my learning journey.

I have 2.5 years of support engineer experience at a MNC and want to switch roles and move to a different company. I have worked on production systems and worked on Oracle sql, batch scripts on Linux and I have fair knowledge on Python. Have basic knowledge of Javascript that had a couple of years back before I got placed on campus for my current company. What role should I study for in order to switch jobs and get out of support or similar roles? I am in Bangalore India. What roles have more opportunities and easy to crack given my experience and skills.

I am thinking of DevOps and similar roles like Cloud/Platform engineer.

Hi , I am currently in my 3rd semester of my university (tri semester). I have exposure on Java,Python,C++ and Unity. Is it the right time to start off as a DevOps developer?
Heard that risks of AI takeover is less here. Moreover, it can lead to cybersecurity.

I know that the path is not as easy as it sounds. But should I prepare myself as a DevOps developer from my undergrad life?

Thanks for your precious advice.

Hi everyone,
I’m currently working as a Manual Tester in the IT industry, and I’m seriously considering changing my career domain to DevOps.
I’ve been thinking about this transition for some time. I have some exposure to technologies like Java, Spring Boot, Angular, Git, Maven, AWS, Docker and Kubernetes, but my primary work experience has been in manual testing.
I’m interested in learning DevOps from the fundamentals and building strong practical knowledge.
Some of the areas I’m planning to focus on:
● Linux and Shell Scripting
● Git and GitHub
● Docker and Kubernetes
● CI/CD pipelines (Jenkins / Azure DevOps)
● Cloud platforms (Azure / AWS)
● Terraform and Infrastructure as Code
● Monitoring and Logging
I would really appreciate advice from people who have made a similar career transition or are currently working as DevOps Engineers.
A few questions I would like your suggestions on:

1. Is moving from Manual Testing to DevOps a good career decision?

2. How difficult is this transition for someone without hands-on development or DevOps experience?

3. Should I focus on Azure DevOps or AWS DevOps? Which offers better opportunities?

4. What is a realistic learning timeline to become job-ready?

5. Are certifications important, or do practical projects and hands-on experience matter more?

6. Is it possible to transition internally within an IT services company?

7. What challenges should I expect during my first DevOps role?
   Most importantly, I would appreciate some learning resources and practical guidance:
   ● Good YouTube channels, websites and structured courses to learn DevOps from scratch.
   ● Online platforms where I can practice Linux, Docker, Kubernetes, Jenkins and cloud technologies hands-on.
   ● Beginner-friendly labs, real-time scenarios and project ideas.
   ● Free or affordable platforms that provide practical exercises rather than just theoretical explanations.
   ● Any GitHub repositories, roadmaps or reference materials that helped you during your learning journey.
   I’m planning to dedicate 2–3 hours daily and want to follow a structured learning path rather than randomly learning different tools.
   I’m not expecting an overnight career change. I’m ready to put in consistent effort and build the necessary skills.
   I would genuinely appreciate your experiences, honest suggestions, learning references and any guidance that could help me make this transition successfully.
   Thank you!

I’m currently working as a Senior Associate at a major Data and Analytics firm, supporting low-latency financial data products. My experience includes investigating production issues, troubleshooting Linux and Windows systems, and working with networking technologies such as TCP/IP, UDP, and multicast.
I’m looking to transition into Site Reliability Engineering, particularly roles involving Linux internals, distributed systems, performance engineering, observability, and cloud infrastructure.
My current plan is to build on my existing experience through three areas:

1. Reading and theory
   ● Google’s Site Reliability Engineering book.
   ● Brendan Gregg’s Systems Performance: Enterprise and the Cloud.

2. Refreshing my DevOps skills
   I completed a DevOps course around two years ago that covered Docker, Kubernetes, Infrastructure as Code, Terraform, Ansible, and GitHub Actions. I need to refresh these skills and get more practical experience using them together.

3. Building a hands-on project
   I’m planning to build a client-server application that exchanges messages, containerize it with Docker, and deploy it to AWS EKS using Terraform. I’ll generate traffic, simulate process and network failures, and use tools such as Prometheus and Grafana to monitor performance and reliability. I’ll also investigate failures using Linux performance tools, logs, and crash dumps, then implement recovery mechanisms and document the results.

My goal is to demonstrate that I can investigate system behaviour, identify root causes, improve reliability, and automate recovery, rather than simply deploy an application.
I’d appreciate advice on a few questions:

1. Would my current production support experience, combined with refreshed DevOps skills, these books, and a well-executed project, be enough to start applying for SRE roles?

2. How much do hiring managers value this type of project compared with direct SRE experience?

3. Which gaps should I prioritize: Linux internals, coding, Kubernetes, cloud infrastructure, observability, or distributed systems?

4. Should I start applying while building the project, or wait until it is complete?

5. Given my background in low-latency financial technology, would I be competitive for SRE roles focused on infrastructure, networking, and performance engineering?

I’m particularly interested in feedback from people who have hired SREs or transitioned from production support, application support, or systems engineering into SRE. I’d appreciate candid advice on what would actually make me a stronger candidate.

Hello everyone,

I’m currently writing my master’s thesis at FH Dortmund (in Germany) on generative AI in everyday work, focused in the IT branch, and how they’re actually changing daily work: productivity, collaboration and data protection. In both office and remote.

Since this sub is all about DevOps and Azure, I think the perspective of specialists with a professional background is especially VALUABLE, whether you use AI tools yourself or consciously choose not to.

I would kindly ask your permission to post a small survey to assist my academic research (it has no other porpouses but academic ones). It takes about 10 minutes, is completely anonymous and available in German and English:

👉 https://www.soscisurvey.de/genai-it-survey/

Thank you for your support!

Hi Everyone,

I have 4.3 years of overall experience in IT, currently looking for new opportunities as a DevOps Engineer. I have hands-on experience with Linux, Docker, Kubernetes, CI/CD pipelines, Jenkins, GitHub Actions, and AWS Cloud. I would appreciate it if anyone could refer me to relevant DevOps Engineer openings in their organization. Any leads or referrals would be highly appreciated.

Thank you!

Hello good people.

I work as a CI-CD/Cloud deployment engineer at the moment and I use Harness Terraform Git action etc.. but the thing is I was never really good at low level coding or remembering syntax or using like complex coding. But I knew what needs to be done at a high level and always got through with my work by using AI to let the scripts be created and I review it of course to check whether it suits my functional requirements or not.

Now I want to switch and I at the moment cannot write code or the scripts per say but I can do the job you know what you mean.

What should I learn or remember? What do you guys remember?

Do you understand and remember how to write CLi commands of so many CLI tools say helm,git kubernetes docker so and so. I have always been bad at creating cli commands to meet my expectations with like very short time I always keep a copy of the commands that I want on a. Notepad or something and use it on a regular basis so I didn't try to remember it.

How do you all do that ?? What did you do to learn such things there are soo many things how do you remember everything?

What should I learn now in this AI era to beat interviews and get into new DevOps jobs?

Is it still worthy to learn a scripting language like powershell per say from scratch or should I just keep leveraging AI to do it for me.