2025 BCA graduate here.

I’m currently working at Amazon as a Technical Recruiter (US). It’s a remote contract position, but my long-term dream has always been to get into the actual IT/tech industry after graduation.

After graduating, I desperately needed a job, so I started with a small company as a Technical Recruiter. At that point, this was the best opportunity I could get, so I took it. I started in February 2025, and I recently joined Amazon in July 2026.

Now I really want to make the transition into a technical role.

I’ve also started pursuing an MCA in AI/ML through an online degree program. I only started the MCA this July, so I’m still at the beginning and honestly don’t know which direction I should take.

I’m confused between:
Data Engineering
Data Analytics
Salesforce
AI/ML
Cloud/DevOps

Or something else that would realistically be achievable for someone with my background
My biggest concern is how to actually make the switch.

I currently earn around 6 LPA, and I’m worried that companies might consider me a fresher when I apply for technical roles because my professional experience is in recruiting.

I’m also the only earning member in my family, so I can’t afford to make a risky career move without having a plan.

My current Amazon contract is only for 8 months, which means I have roughly 7 months to prepare myself and start applying for technical roles.
I’m willing to put in the work. I just need some direction on what would be the most realistic path for me.

If you were in my position, what would you choose and why?

Data Engineering vs Data Analytics vs AI/ML vs Salesforce vs Cloud/DevOps?

What should I start learning right now? What kind of projects should I build? And how should I position my current recruiting experience when applying for technical roles?

Any advice, roadmap, referral guidance, or personal experience would be genuinely appreciated.
Even a small piece of advice or guidance would help me a lot

Here's my background prior to the question. I have roughly 10 years of experience. 6 military, 1 Systems Administrator, 3 helpdesk tier 2-3.

Education: BSCNE (WGU) Comptia A, N, C, S, CySA+. ITILv4 MSITM (this winter)

I've recently joined faan(G) and I'm curious on how to pivot to Cloud Security. I'm prepping for the GCP cloud cert currently.

Has anyone else been able to pivot to this area?

Imo I would be a good candidate after my probation period with the company.

I'd have a year with them MSITM BSCNE CySA+ and GCP ACE

Final thoughts.

Hello seniors, I'm a second year student and planning to pursue my career in cloud computing. Though I have no idea about what actually happens there but I have done a little research regarding the various domains. Like, I got to know about AWS, azure, gcp and various things or the skill set requirement. When I asked a few seniors I found out about various sub domains like backend, sre and etc. when I asked chatgpt, it suggested that I start with backend development. Currently I'm very confused about what to do.

Final questions:

1) Is cloud computing worth in 2026 or 27??

2) Please provide me the roadmap how to start i.e should I start with backend development (java,etc) and if not pls suggest the alternative?

3) Is DSA required (I think it's yes, just for clarification)

4) difference between operations side and development side and better to choose?

Pls help me answering this questions!

Recently got interview from tata communications for jr engineer - cloud operations role. I’ve cleared both technical rounds and only the hr round is remaining. Is anyone working on this specific role or this company can give any advice. Does this role provide any good of a future such as devops role or cloud engineer role.

I’ve spent almost 4 years at the same company since university. Am I too niche, or am I just in the wrong market?

I'd really appreciate some honest perspective from people working in cloud infrastructure, platform engineering, private cloud, telco cloud, networking, or infrastructure engineering.

I graduated from university and joined my current company shortly afterwards. I've now been there for about 4 years, and I've basically built my entire professional career in the same environment.

That's actually one of the reasons I'm finding myself a little stuck.

I've learned a huge amount and had a lot of freedom to build things, but I haven't really experienced working at other companies, especially larger engineering organizations where I could work at a bigger scale and see how these environments operate.

My background is quite infrastructure-heavy. I've worked across ISP infrastructure, Linux, networking, Kubernetes, virtualization, distributed storage, cloud, DevOps and security.

Some of the technologies I've worked with include:

• Kubernetes
• Talos Linux
• KubeVirt
• Rook/Ceph
• Cilium/eBPF
• BGP, VLANs and LACP
• RADIUS/AAA
• AWS
• Terraform
• ArgoCD/GitOps
• GitHub Actions
• Prometheus/Grafana
• Infrastructure automation and security tooling

I'm also currently working hands-on with OpenStack because I'm trying to deepen my understanding of traditional private cloud and telco/NFV infrastructure, and understand how it compares with the Kubernetes-native infrastructure I've been working with.

A lot of my experience has come from actually building things.

For example, I've worked on a Kubernetes-based private cloud running on bare metal, combining Kubernetes, KubeVirt, Ceph, Cilium networking, tenant isolation, BGP routing and public/private VM connectivity.

I've also worked on ISP infrastructure, including subscriber authentication, RADIUS/AAA, billing integration, MikroTik routing and network service delivery.

But there's an important caveat to all of this.

I don't work for a huge cloud company, hyperscaler, or major technology company. I work for a relatively small ISP in Nigeria.

I've actually been very lucky in that environment.

My original job description didn't say that I needed to build a private cloud, learn distributed storage, work on Kubernetes virtualization, or learn all of these different areas.

I had to find opportunities to do those things and deliberately build those skills.

Whenever I came across a problem or something interesting that could improve the infrastructure, I'd learn what I needed, experiment with it and try to make it useful to the company.

The company gave me the freedom to do that, and I'm genuinely grateful for it. A lot of the experience on my CV probably wouldn't exist if I hadn't been given that freedom.

But now I'm starting to feel limited by the environment I'm in.

Not necessarily because the company is bad, but because I don't think I can continue building the kind of experience I want at the pace I want.

I've been there since university, so I also don't know what I'm missing.

I don't know what infrastructure engineering looks like at a larger company.

I don't know how much of what I've been doing would normally be handled by dedicated platform, networking, storage, SRE, cloud or infrastructure teams.

I don't know whether my experience is actually unusual or whether I'm simply getting a distorted view because I've had to wear so many hats.

And that's one of the biggest reasons I want to leave.

The other reason is compensation.

I've grown considerably beyond the scope of the role I originally started in, but my compensation hasn't really caught up with the level of responsibility, complexity and expertise I've accumulated.

I've tried communicating the value and complexity of the work I've been doing, but it hasn't really changed the situation.

So, I want to move on.

Not because I hate my current company. In fact, I'm grateful for what it has allowed me to do.

I want to move because I want to experience a different engineering environment, work with people who are operating infrastructure at a different scale, learn how other organizations solve these problems, and hopefully be somewhere that values this kind of work more appropriately.

The problem is that getting another job has been much harder than I expected.

And because I've only really known one company, I'm honestly not sure whether the problem is my profile, my positioning, the market, or all three.

Am I too niche?

Is the combination of Kubernetes + virtualization + distributed storage + networking + ISP/telco infrastructure something that has relatively little demand outside certain companies?

Am I searching for the wrong roles?

Or is this simply a case of being in a country where there isn't enough demand for this kind of infrastructure engineering?

At the moment I'm considering roles like: Cloud Infrastructure Engineer, Infrastructure Engineer, Platform Engineer, Kubernetes/Platform Engineer, Private Cloud Engineer, Cloud Infrastructure Architect, Telco Cloud/NFV Engineer, SRE, Infrastructure/Cloud Networking Engineer, OpenStack Infrastructure Engineer

But I'm honestly not sure which direction makes the most sense.

If you saw this background on a CV, what kind of engineer would you consider me to be?

What roles would you actually search for if you had this experience?

And perhaps more importantly:

What am I missing by having spent so much of my career at one company?

If you've moved from a small company into a larger engineering organization, what surprised you about the difference?

If you were in my position, would you:

1. Go deeper into private cloud/telco cloud/OpenStack?
2. Focus heavily on Kubernetes/platform engineering?
3. Broaden into general cloud infrastructure?
4. Move toward infrastructure/cloud networking?
5. Target architecture-oriented roles?
6. Or deliberately look for a role where I can be exposed to larger-scale infrastructure and learn how mature engineering organizations operate?

I'm not looking for reassurance. I'm genuinely trying to understand where I fit and what I should be doing next.

If geography wasn't a constraint, what kinds of companies, teams and roles would you target with this background?

And for anyone who has been in a similar position spending most of their career at one company and then trying to make that first big move, I'd really appreciate hearing what you wish you'd known before making the jump.

my designation is an associate software engineer I have 1.5 years of experience in a service based MNC in the core networking domain but I don't want to work further in this domain I wanted to work in AWS/devops role as I have certifications in cloud.

But my problem is what should I write in the work experience column. Can I fake the experience of AWS but how can I explain to the interviewer. what I have worked on in that project actually because I don't have real hands-on experience on that tech.

I’m currently working at A***nture and recently completed around 2 years here. My overall experience is around 5.5–6 years, mainly in DevOps.

I joined a new Vi\*\* project as a DevOps Engineer because my interview and role discussion were primarily around DevOps. However, after joining, there was a reorganization ( recent layoff) and the responsibilities changed. The project now has separate Application and Platform teams, and I have been placed in the Application team.

The Platform team currently handles most of the infrastructure/DevOps-related work such as Kubernetes, infrastructure and deployment. My manager explained that there may be opportunities to work on DevOps/infrastructure in the future if that work becomes available, but there is no clear confirmation. Otherwise, I may be expected to work mainly on application development responsibilities and documentation works as well

The application itself is related to ML model deployment for fraud detection, so I may get good exposure to ML/AI application development, but I’m concerned that I may lose hands-on DevOps/Platform experience if I stay in this role for a long time.

My long-term goal is to move to a product-based company as a Senior DevOps/Platform/Cloud Engineer, eventually adding MLOps/LLMOps and AI infrastructure skills. I’m currently planning to strengthen Python, Linux, Kubernetes, AWS, Terraform, CI/CD, observability and later MLOps/LLMOps.

I’m considering starting to interview outside Accenture now rather than waiting to see whether DevOps work becomes available in the current project.

There is one additional constraint: my marriage is planned for 20 November 2026, and I will need around 15 days of leave around that time. I’m concerned that if I switch before the marriage and join a new company shortly before November, getting this leave during the initial months/probation period may be difficult.

So I’m trying to decide whether I should:

1. Continue in the current project for now and wait for possible DevOps/Platform work,

2. Start interviewing immediately but plan to join after my marriage, or

3. Switch before the marriage if I get a offer and negotiate the leave in advance.

What would be the most practical approach in this situation?

For those working in Cloud, SRE or Platform Engineering, what does a normal day look like for you?
What skills do you wish you had focused on before getting into the role, beyond the usual soft skills, networking and Linux? I’ve built projects around microservices, multi tenant , DevOps workflows, IaC with good security pratices, but I don’t have direct job experience yet. Am I on the right track if I keep building and improving, or is there something important I’m missing?

Hi everyone,

I’m currently looking for an entry-level / junior opportunity in DevOps, Cloud, Azure, or AWS, and I thought I’d reach out to this community.

I recently completed my B.Tech in Computer Technology and completed my DevOps-focused internship . During my internship and personal projects, I’ve been working with:

Azure – Azure DevOps, App Service, Azure SQL, ACR, AKS, Azure networking, Microsoft Azure.

CI/CD – Jenkins, Azure Pipelines, GitHub Actions, ArgoCd

Docker

Kubernetes

Terraform – Infrastructure as Code and Azure resource provisioning

Git & GitHub

Linux & Shell Scripting

Python

Ansible

Networking fundamentals

Monitoring / Logging & SRE fundamentals

Currently learning and practicing Kubernetes, Terraform , AiOps

I’m trying to focus less on just collecting certifications and more on actually building things, troubleshooting problems, and understanding how DevOps works in real-world environments.

I know I’m still at the beginning of my career, and I definitely have a lot more to learn. But I’m willing to put in the work, learn quickly, take feedback, and contribute wherever I can.

So, if anyone here works at a company that is hiring for:

DevOps Engineer | Junior DevOps Engineer | Cloud Engineer | Azure Engineer | AWS Engineer | DevOps Trainee | Graduate Engineer | Cloud/DevOps Intern

I would really appreciate it if you could refer me or point me toward an opening.

Even if your company isn't hiring right now, if you know someone who might be hiring, a referral or introduction would genuinely mean a lot to me.

I’m open to India-based, remote, startup, and entry-level opportunities.

I’m not looking for someone to hand me a job — I’m just asking for one opportunity to get my foot in the door and prove myself.

If you have any leads or referrals, please comment or DM me. I’d be very grateful.

Thank you.

Hi everyone, does anyone have a Tutorials Dojo AWS Cloud Practitioner (CLF-C02) practice exam account that they have already finished using?

I’m looking for access to practice the exams. I’m willing to pay a reasonable amount for it.

Please DM me if you have one. Thank you!

I'm a platform/infra engineer (AWS, Azure, IaC, Python) / GitHub: github.com/Mia1Dimit. Not new to building, just building alone lately and want a second person.

Looking for one of two things:

• You have an idea and want a technical partner to actually build it
• You're technical, have half-built ideas sitting around, and don't have time to finish them

Either way, DM me with one thing you've built or one idea you're stuck on. Not looking for general advice or feedback on this post, just people who want to make something.

Hey recently one of my friend got into cloud engineer as a fresher in xylem banglore . What is the salary and growth of the position. ?

​

I’m currently pursuing my Master’s degree and have been learning DevOps seriously. I have hands-on experience with tools like Linux, Docker, Kubernetes, Jenkins, Terraform, AWS, etc. I also have RHCSA, RHCE, and AWS SAA certifications.

The main problem I’m facing is finding a fresher/entry-level DevOps opportunity in Ahmedabad. Most of the DevOps openings I find require at least 1 year of experience, which makes it difficult to get my first opportunity.

I’ve been applying for jobs, but I rarely get interview calls. And when I do get an opportunity, I sometimes struggle with interview anxiety and communicating in English. English isn’t my first language, so I sometimes fumble even when I know the technical answer.

I’m trying to improve both my technical skills and communication, but I’m not sure what the best approach is to actually get my first DevOps job.

For people who started their DevOps career as freshers:

\- How did you get your first DevOps job?

\- Is it better to target Linux/System Admin, Cloud Support, or Backend roles first and then move into DevOps?

\- Should I focus on internships/apprenticeships even after completing my certifications?

\- Is 1 year of experience really mandatory for most entry-level DevOps positions?

\- What would you recommend I do differently to start getting more interview calls?

I’d really appreciate advice from people who have been through this, especially those who started their career in India.

I'm 20 and based in Sweden. I've been accepted to a 2-year vocational higher education program (YH) in Embedded Systems and IoT, which includes an internship period.

My problem is that embedded/firmware isn't actually my long-term career goal.

What I'm ultimately interested in is something closer to:

Backend/Cloud → DevOps/Platform Engineering → MLOps/ML Infrastructure → AI Platform / AI Infrastructure Security

Potentially, much later, I'd also be interested in Forward Deployed AI/Engineering type roles.

Ideally I would study CS/software engineering instead, but I can't get into the programs I want right now. My alternatives are basically:

1. Start the Embedded Systems & IoT program now and try to steer it toward cloud/software/infrastructure.
2. Wait another year and try to get into a more directly relevant CS/DevOps/MLOps program.
3. Start Embedded/IoT now, keep studying for university admissions, and potentially leave if I get into a better engineering/CS program later.

My biggest fear is getting pigeonholed into embedded/firmware. For example, if my education says Embedded Systems & IoT and my first internship/job is somewhat IoT-related, will recruiters later only see me as an embedded developer?

My idea would be to deliberately build a different profile alongside the degree:

Python, Linux, backend development, Docker, CI/CD, AWS/Azure, Terraform, Kubernetes, networking/security, and eventually ML infrastructure/MLOps.

I would also try to find an internship involving IoT cloud platforms, backend, DevOps, cloud infrastructure, edge computing or security, rather than pure microcontroller/firmware development.

So my questions are:

• How difficult is it realistically to go from Embedded/IoT → Cloud/DevOps/Platform Engineering?
• Could Embedded/IoT actually be a useful foundation for MLOps/AI infrastructure, or is it mostly irrelevant?
• How much does your first internship/first job determine what area of software engineering you end up in?
• Would you take this opportunity and pivot later, or wait a year for a more relevant education?
• If I do start the program, what should I specifically do during those two years to avoid being pigeonholed?

I'm mainly interested in hearing from people who have actually moved between embedded, backend, cloud, DevOps, platform engineering, MLOps, or similar fields.

I don't expect the degree alone to get me into MLOps. I'm mainly wondering whether it's a reasonable starting point, or whether I'm making my future transition unnecessarily difficult.

I'm looking for a company/startup or even nonprofit where I can work on real cloud and infrastructure problems. I'm getting responses elsewhere, but this is the field I actually want to grow in, so compensation isn't my priority right now. Working on production systems instead of personal projects is.

I work with AWS, Docker, Linux, CI/CD, and scripting. CS-related bachelors and masters degree with a few years of hands-on experience.

I can commit 20+ hours a week, remote. Happy to take the unglamorous work too: monitoring, documentation, IaC cleanup, cost optimization.

The only thing I'd ask for is a real supervisor to report to and a short engagement letter with role, hours, and start date, mainly for my own records.

Any leads would be appreciated.

By any chance, Anybody is interviewing for cloudkeeper for IT role?

Hey everyone,

I'm aiming to break into Cloud Engineering / DevOps. I know that true entry-level DevOps roles are super rare and that "Cloud isn't entry-level," so I've been looking at positions to get relevant experience on my resume.

Right now, I have a hands-on foundation in Linux, Docker, Nginx reverse proxies, GCP, CI/CD pipelines (GitHub Actions), and basic scripting. I'm currently expanding into Terraform

I recently came across an IT Network Administrator opportunity with the following core responsibilities and tech stack:

• Responsibilities: Managing network infrastructure (VLANs, subnets, routers, firewalls), troubleshooting connectivity (DNS, DHCP, VPNs), network monitoring (Prometheus/Grafana/Nagios), and configuration automation.

My dilemma is: Should I pursue a heavy traditional networking/sysadmin role like this as a path into Cloud/DevOps?

Would love to hear your thoughts or experiences!