Nobody told us the first week of bootcamp would include a three-way argument about whose track matters most.
At SkillNg, we had separate specialists come in for frontend, backend, and cloud computing/DevOps. Each one opened their session the same way: introducing the track, explaining why it matters, and taking at least one shot at the others. It was funny at first. Then it turned into an actual debate.
The frontend dev made the case that the user interface is everything. If something looks broken or feels slow, users leave. Does not matter what is happening underneath. The backend dev fired back that a beautiful interface with no data, no logic, and no API is just a static webpage. Then both of them turned to the cloud computing instructor and asked, more or less, what we actually do.
He did not bite. He just said:
"No matter how good your creation is, you cannot render it in thin air. You need somewhere to save it, run it, and deliver it to people. That is where cloud computing comes in."
The room went quiet. That was the end of the debate.
I have been thinking about that moment since, mostly because I think a lot of people starting out in tech have the same question. Cloud sounds abstract. Infrastructure sounds boring. So what does it actually mean in practice?
The honest answer is that cloud is what makes code a product
Frontend and backend are about building. Cloud is about what happens after you build. You can write the cleanest React components in the world. You can design an API that handles every edge case. But if that code only runs on your laptop, it does not exist for anyone else. Cloud infrastructure is what closes that gap: the servers, the networking, the storage, the pipelines that take your build and put it somewhere the internet can reach. A simple way to think about it: frontend is the shop floor, backend is the warehouse, and cloud is the building itself, plus the electricity and the loading dock.
What cloud engineers actually work on
Deployment. Someone has to configure where the application runs and how it gets there. Cloud engineers set up the environments, the containers, the compute resources. When a developer pushes code, it does not magically appear in production. Something has to receive it, test it, build it, and ship it. That something is what cloud and DevOps people build.
Scaling. Imagine your app gets picked up by a newsletter with a large audience and 10,000 people hit it at once. A server with fixed capacity buckles. Cloud infrastructure with auto-scaling spins up additional instances automatically to absorb the load, then scales back down when things settle. No one has to manually intervene at 2 am. That kind of reliability does not come free; someone has to design and configure it.
Storage and databases. The backend developer writes queries. But where does the database live? Who makes sure it does not go down, that the data is backed up, that it can be read from multiple regions without becoming a bottleneck? Cloud engineers do. Services like AWS RDS or Google Cloud Storage handle this, but they still need to be provisioned, secured, and maintained properly.
CI/CD pipelines. This is where DevOps earns its name. A CI/CD pipeline automatically runs your test suite, builds the application, and deploys it whenever new code is pushed. Without this, teams are copying files to servers by hand, which is slow and breaks often. With it, you can ship ten times a day and catch problems before they reach users.
Security at the infrastructure level. A backend developer secures their API. A cloud engineer secures what the API runs on: the firewalls, access policies, SSL certificates, network configuration, and compliance requirements. These are different jobs. Both matter.
Cost. Before cloud computing, companies bought physical servers upfront and hoped they sized them right. Too small and the app crashes under load. Too large and you are paying for capacity you will never use. Cloud's pay-per-use model changed that. You pay for what you actually consume, and you can adjust in real time.
The thing both sides missed in the debate
Frontend and backend developers use cloud infrastructure constantly without thinking about it. GitHub is cloud. The npm registry is cloud. Every third-party API they call in their apps runs on cloud servers somewhere. They were arguing against the foundation they were standing on.
That is not a knock on them. It is just how infrastructure works when it is done well: invisible. Nobody thinks about electricity until it goes out. Cloud is not competing with the other disciplines. It is the layer that makes them matter outside of a development environment. A good frontend and a solid backend are prerequisites for a good product. Cloud is what determines whether that product actually reaches anyone.
Where I am now
I am still early in the SkillNg program, and this is clearly the beginning of a long learning curve. AWS alone has more services than I can keep track of right now. But that first session reframed how I think about what we are learning. If you are starting out and trying to choose a track, I would not recommend choosing based on which one sounds most impressive. Choose based on what kind of problems you want to spend your time solving. If the idea of owning the infrastructure that everything else depends on sounds interesting, cloud is worth a serious look.
And the next time someone asks what cloud engineers do, you have an answer.
Top comments (0)