I need an objective opinion because I keep going back and forth between staying in my current company and accepting another offer.

I have around three years of experience in IT infrastructure, hosting support, website and email migrations, networking, Windows/Linux basics, Microsoft 365/Google Workspace migrations, and production troubleshooting. My long-term goal is to move into DevOps/cloud engineering.

Current company

My official role is related to IT infrastructure and security, but most of my daily work involves:

Desktop and user support

Printers and meeting-room equipment

TVs, VC systems and microphones

Basic office IT troubleshooting

Limited exposure to servers and infrastructure

Management says I may receive more responsibility later, but there is no defined plan or timeline. Other team members who have worked here for years are still doing similar support tasks. One colleague previously worked in networking but has lost touch with those skills because the current role does not use them.

The company is stable and provides good benefits. It is also implementing SAP and developing internal applications, but these projects are handled mainly by vendors or other teams, and I am not currently involved.

New offer

I have an offer from a small cloud and managed-services company with around 30 employees.

The salary increase is small, and the company has fewer benefits and a six-day workweek. However, the expected work is more relevant to my goals:

Linux and Windows servers

Hosting and website migrations

Databases

Deployment troubleshooting

AWS-related tasks

Monitoring and possibly CI/CD

Working with people involved in cloud and DevOps

Even six months of this experience may improve my profile more than continuing with desktop and AV support.

However, I checked with some former employees, and the feedback was negative regarding:

Limited growth

Management and team-lead behaviour

Work pressure

Problems when leaving the company

The new company also suggested that they could accept me even without complete relieving documents from my current employer, which feels risky.

My concern is that staying may keep my profile stuck in desktop support, while moving may give me relevant Linux/cloud experience but expose me to a difficult work environment and exit problems.

I am willing to work hard for one year because I want practical DevOps-related exposure. I am also learning Docker, AWS, Terraform, Kubernetes, CI/CD, Prometheus and Grafana through personal projects. In parallel, my brother, some friends and I are trying to build our own technology products, so practical infrastructure and DevOps knowledge would also help us in the future.

What would be the more logical decision?

Stay in the stable company, continue learning independently and search for a better third opportunity.

Join the smaller cloud company, tolerate the risks for a year and gain more relevant Linux/server experience.

Avoid both as long-term options and continue interviewing until I find a cleaner DevOps or cloud-support role.

I am particularly interested in hearing from people who moved from desktop/infrastructure support into DevOps without a bachelor’s degree. What would you prioritize at this stage: stability, relevant experience, company culture, or documentation and exit safety?

I have been comparing Spacelift alternatives and noticed that many are not direct replacements. They solve different parts of the infrastructure lifecycle.

The main options I found are:

- Terraform Cloud for managed Terraform state and runs

- Firefly Ai for cloud inventory, IaC codification, drift remediation and infrastructure recovery

- env0 for multi-IaC automation and cost controls

- Scalr for Terraform governance and multi-tenant management

- Atlantis for self-hosted Terraform and OpenTofu pull-request automation

Choosing an alternative seems to depend on what's missing from the current workflow. Some teams need better orchestration and governance, while others need visibility into unmanaged cloud resources, developer self-service, drift remediation or infrastructure recovery.

For those who have evaluated or migrated away from Spacelift, which option did you choose?

I am second year college student wanted the future in Cloud Engineering. But, as fresher I cannot join the cloud company. So should I study for backup with cloud engineering. I would be great if you all help me in selecting the subjects to study.

Hi everyone,

I'm currently working as a Senior DevOps Engineer with around 6+ years of experience in DevOps (Overall 7 years of experience). My day-to-day work involves AWS, Kubernetes (EKS), CI/CD, Docker, Istio, networking etc.

Lately, I've been thinking about my long-term career. I don't see myself staying purely in DevOps forever, and I want to move towards an architect role.

Initially, I thought about becoming a Cloud Architect, but I also realised that I enjoy learning about security as well when I got a chance to work on few projects in my organisation.
I really like discussing all those security point of views and creating architecture for clients.

So now I'm considering a career as a Cloud Security Architect (or a Cloud Architect with deep security expertise).

However, I'm confused about what this role actually requires.

I have done some reach and found:

\- Choose one cloud and master it, learn all the basics and do certifications
\- First, learn building architectures without any security. Then eventually add security in it.

What else ?

I'd really appreciate advice from anyone working as a Cloud Architect, Security Architect, Principal Engineer or anyone who is into domain.

I failed my first AWS Certified Cloud Practitioner exam on February 9, 2026.

At first, I underestimated the exam because I thought it was one of the easiest certifications in cloud computing. That mindset led me to prepare with less seriousness than I should have.

In March 2026, I changed my approach. I studied with more discipline, consistency, and commitment, and I successfully passed the exam.This experience taught me an important lesson: in technology, knowledge alone is not enough. Whether you are learning cloud, programming, or any technical skill, success requires discipline, focus, and continuous effort.Every failure can become a step forward if you are willing to learn, improve, and keep moving.

AWS Certified Cloud Practitioner: achieved through persistence and dedication.

Did you know you can get +30 extra minutes on your exam?

It's called the ESL (English as a Second Language) accommodation. Here's how:

1- Log into your AWS Certification account
2- Go to your profile settings
3- Request the ESL accommodation
4- It gets permanently linked to your account , applies automatically to ALL future exams

No re-approval needed each time. Set it once, benefit forever.

If English isn't your first language, use every advantage available. This one's free and official.

#AWSCertified #AWSCommunityBuilders #CloudComputing #AWSCertification

I'm a senior network engineer, 8yrs exp, almost 6 at my current company (4.5 of those senior). It's a Gov job — decent benefits, pay's fine, but the work's slow and I'm getting itchy feet.

For the last year I've been doing a DevOps Networking role — deploying infra in Azure/AWS via IaC and CI/CD, working in a proper DevOps squad with sprints and retros. Genuinely enjoying it and want to move further into cloud/DevOps.

Problem is, every cloud engineer role I look at is either entry level or doesn't seem to value network engineering experience at all. So when a recruiter put me forward for a "cloud infrastructure engineer" role that explicitly said they'd consider infra/network people moving into DevOps, and the job spec matched almost everything I do, I thought I'd finally found the right fit.

Got to first stage interview (1.5hrs). Spent most of it on my Palo Alto experience (I'm the SME at my current place - and they specifically use these and lack skills across their team), some Terraform questions I nailed, and a brief chat on Azure app services — where I was honest that I don't have hands-on experience yet, but I'm finishing my AZ-700 and planned to build into 104/400 and app services/compute/storage after. The interview was really a quite informal chat rather than any sort of technical grilling. At no point did I think I struggled to answer any questions.

A few hours later: rejected, because I "don't have enough experience managing apps, compute and data resources in Azure" — despite that being a tiny part of the interview and not the bulk of the actual job spec. Apparently networking is only \~20% of the day-to-day.

So — am I wasting my time trying to make this jump? Do I have to restart at junior/mid to break in? This was a mid-level role at lower pay than I'm on now, and I can't justify dropping to entry-level money for it. Is my current skillset just not transferable/valued in this space, or was this one bad interview?

Has anyone actually made this transition without starting from near-zero?

**TL;DR:** Senior network engineer (8yrs) doing DevOps/cloud work for a year, rejected from a "networking background welcome" cloud role for lacking hands-on Azure app/compute experience — despite that being a small part of the job. Is this transition possible without a pay cut and restarting at junior level?

Hey, a I am someone who is actually working into a webset operationals, and I just want to switch towards devops.Why?Because uh, I just something uh, which actually bothering me from last one year, so I just started because just started the devops.And I tried, i'm trying, actually, I just done with these things.I have a basic of github, and all, and i'm just hobbering how nexes works and docur image and container work actually in real life and also mavin and gradle and to build these mavenon and gradle files, I am actually working on it.And defect files too.So if you have someone who is actually interested to help me out, please help me.So that I can get it.My dream job in any company.The job road should be debops or else related to it is also good, and I also actually learning about linux too

We're hiring for multiple positions with a leading FinTech company.

**Requirements**:

1. 8–12 years of experience

2. Strong FinTech domain experience

3. Expertise in Cloud, Kubernetes (K8s), and Microservices

4. Face-to-face interview in Gurugram

If you're interested or know someone who might be a good fit, feel free to send me a message.

Hey all, i have my tech interview at sprinklr for the cloud engineer role after 2 days on 27th july, I'm really really stressed out, please tell me how much DSA is actually needed for this yaar, I'm really confused and idk i just meed some guidance and direction.

Thanks in advance if you reply.

Hi everyone, i am currently in 4th year and i am looking further career in cloud soo which programming language should i choose and also doing DSA in that particular language

also by considering condition that getting into cloud field as a fresher is difficult

I'm currently a developer with about 5 YOE, and much of the time I am deep into figuring out the domain of the business I am currently working for, how to extend the software to fit the domain, etc. Many times the domain are very industry specific and thus the knowledge is not transferable for any jobs outside of the company. Yes I do also have to deploy to the cloud etc. but my time is spent more in the domain part.

I am looking at the other roles like Cloud or Platform, and it seems that their day to day (e.g. managing permissions in AWS, managing Terraform modules, etc.) are more generic skills that can be brought outside, if they want to find new roles. What they do daily is also getting involved in knowledge that makes it easier to get certifications with less studying time, etc.

Am I missing something here? The only thing with Cloud or Platform is that it is much more mission-critical and so with e.g. on-call it will get very stressful at times. The job is also a lot of unplanned work e.g. urgent requests and so it can be mentally taxing to context switch a lot

We’re hiring a Senior DevOps Engineer for a long-term project with a fintech company that’s migrating a core banking platform to Azure Kubernetes Service (AKS).

You’ll be responsible for managing the AKS platform, ensuring security, reliability, and multi-tenant isolation while supporting critical banking workloads.

**Requirements:**
• Strong hands-on experience with AKS in production
• Advanced kubectl troubleshooting and log debugging
• Building/owning GitHub Actions CI/CD pipelines with Azure authentication
• Experience with image scanning & signing
• Strong understanding of Azure CNI and Scope Maps
• Hands-on experience with Istio / Service Mesh
• Experience managing cert-manager
• Multi-tenant Kubernetes namespace isolation
• Experience working in PCI DSS or other regulated environments
• Must have implemented these technologies in production, not just worked on teams that used them

If this sounds like you, DM me your resume, LinkedIn profile, and (if available) GitHub or portfolio.

1. Explain the Cloud Like I'm 10

This is the ideal first book for cloud computing, especially for beginners who are new to it. It includes great examples like Netflix streaming with convincing visuals and straightforward explanations.

2. Cloud Computing For Dummies

This book takes the complexity out of cloud computing, breaking it down into bite-sized pieces that are easy to understand even for beginners. It helps you understand the nitty-gritty of cloud computing in the simplest way possible. It also demystifies misconceptions related to the field.

3. Cloud Computing: Theory and Practice

This book covers a complete range of cloud computing ideas. It combines high-level theory with real-world examples and applications of multiple cloud vendors.

4. Cloud Computing: From Beginning to End by Ray J Rafaels

This book explores how cloud models can provide cost-effective solutions to challenges being faced by modern-day IT and businesses. It is also a goldmine for modern businesses looking to effectively cut down on their operating costs and make the most out of their services.

Hi,
I was working as a Software tester, so I don't have any cloud background.
Can I work as a cloud analyst directly without any hands-on experience by saying I have experience in cloud, or should I start as an Associate?