Login

r/Cloud

▲ 4 r/Cloud

How hard is it to switch cloud/DevOps platforms in a bad job market?

Hi everyone, I wanted to ask hypothetically, if someone had 4–5 years of cloud/Devops engineering experience, primarily with AWS, and the market shifted heavily toward Azure, how difficult would it be for them to find a cloud engineering job in a difficult job market like the one we’re in now? Would having mostly AWS experience significantly hurt their chances if most of the available Cloud/DevOps jobs were Azure-oriented?

reddit.com
u/MediocrePass4780 — 7 days ago
▲ 2 r/Cloud

Is the cloud support associate job market cooked??

I have been studying to get a job in a Clous support associate , but when I searched for the role online on job portals I don't see any openings, is it a good option to try and get in it at the moment? am I wasting my time?

reddit.com
u/Remote_Finger8081 — 7 days ago
▲ 3 r/Cloud+1 crossposts

Portfolio Projects for transitioning from L2 IT to Cloud

Hi! I am currently working as Tech support, and am fairly early on with this, but I am really loving learning about cloud engineering and would like to transition into a Cloud Support role in about a year.

I am having trouble figuring out what projects to do/ what technologies to feature in a portfolio. Here are the projects I currently have planned. If there are any tools or angles, I am missing please let me know! Or which projects I should combine/scrap:

  1. Ticket submission and managing web app.
    1. 3 Tier Web App (In progress detailed description below)
    2. Uses Terraform, Kubernetes, Python, GoLang, Trivy.
  2. Data Analytics Pipeline with Data Governance
  3. Microservice Architecture with Containerization
  4. Auto Backup + Disaster Recovery
  5. Prometheus Observability Stack
  6. AI Inventory Management Application (Prob w an AWS provided model)

Current project (a bit all over the place, but its 3/4 to being a Inquiry Management app. Used copilot to generate an overview of the repo):

  • Project type: Cloud-native 3-tier inquiry management system focused on end-to-end workflow handling, with React for the UI, ASP.NET Core for the application/API tier, and PostgreSQL for persistent data.
  • Core functionality: inquiry creation, assignment, status tracking, search/filtering, and operational visibility across the ticket lifecycle.
  • Stack:
    • Frontend: React, HTML/CSS/JS (the repo is strongly front-end weighted: ~40.2% HTML)
    • Backend/API: ASP.NET Core
    • Data layer: PostgreSQL
    • Containerization: Docker
    • Orchestration/deployment: Kubernetes
    • Infrastructure as code: HCL/Terraform-style provisioning (~7.9%)
  • Language composition:
    • HTML: ~40.2%
    • Go: ~29.1%
    • Python: ~20.9%
    • HCL: ~7.9%
    • Dockerfile: ~1.2%
    • Mako: ~0.7%
  • Technical interpretation:
    • The repo is designed as a full-stack cloud demo: user-facing web app plus service/backend orchestration and deployment automation.
    • Go and Python likely support operational tooling, automation, or auxiliary services; HCL indicates infrastructure deployment and environment provisioning.
    • Overall, it’s a production-style reference implementation for full-stack + cloud engineering practices rather than a simple CRUD app.

I have tried to look online for what projects people recommend, but mostly people are promoting their courses so it's hard to tell what is good advice and what's bait for the course.

u/LatterWall7905 — 10 days ago