Marcus answered phones for a 200-person logistics company. Password resets, frozen laptops, the printer on the third floor that jammed every Tuesday. He was good at it, calm with frustrated people, but the salary sat at 42,000 dollars and had barely moved in three years.
The turning point was small. A senior engineer asked him to spin up a test server in the company's cloud account, and Marcus realized he had no idea how. He could fix a stuck Outlook profile in his sleep, but the infrastructure running the whole business was a black box to him.
Fourteen months later, he started a cloud engineering job at 86,000 dollars. Here is how he actually did it, including the parts that were slow and frustrating, because the clean success story you usually read leaves those out.
Why the help desk is a better launchpad than it feels like
When you are reading tickets all day, it is easy to believe you are stuck. Marcus felt invisible, like the job was a dead end with a headset attached.
But frontline support builds skills that cloud teams quietly value. You learn how systems break, how to document a problem clearly, and how to stay patient when something is on fire. Those are not filler skills, they are the difference between an engineer people trust and one they avoid.
His ticketing experience also gave him a map of the company. He already knew which apps mattered, who owned what, and where the pain lived. That context is hard to teach and easy to undervalue.
Hiring managers for junior cloud roles often prefer support veterans over fresh bootcamp grads, because support people have already proven they can work a real job under pressure without melting down.
Picking the first certification without drowning
Marcus made the classic mistake first. He bought three courses in a week, started all of them, and finished none. The cloud certification landscape is loud, and every YouTube video promises a different "fastest path."
He reset and asked a simpler question: what does my own company use? They ran most workloads on AWS, so that became the obvious starting point. Chasing a certification for a platform he would never touch made no sense.
He started with the AWS Certified Cloud Practitioner, the entry-level exam. It is broad and not very deep, which was exactly right for someone who needed vocabulary before depth. If you are weighing options for your own situation, this breakdown on how to choose the right certification walks through the same logic he used.
Start with the cloud provider your current employer already uses. You get free practice on real systems, your studying becomes immediately useful at work, and managers notice.
The study routine that actually held
Marcus did not quit his job, take a loan, or study eight hours a day. That fantasy version burns most people out by week three.
Instead he committed to roughly 60-90 minutes on weekday mornings before his shift, plus one longer session on Sunday. It came out to around 8-10 hours a week. Slow, but repeatable.
His loop was simple. Watch a short lesson, then immediately do the thing in a free-tier cloud account. Reading about storage buckets did nothing for him. Creating one, breaking it, and fixing it stuck.
How long each step took him
| Certification | Rough study time | When he passed |
|---|---|---|
| Cloud Practitioner (foundational) | Around 50 hours | Month 3 |
| Solutions Architect Associate | Around 120 hours | Month 9 |
| SysOps Administrator Associate | Around 90 hours | Month 13 |
Notice the gaps. Life happened. He missed two full weeks when his kid was sick, and another when work got buried in a system migration. The timeline stretched, and that is normal, not failure.
Turning study into proof anyone could see
A certificate on its own is a claim. Marcus wanted evidence, so he started building small projects and writing them up in plain language on a basic portfolio site.
One project hosted a simple static website with automatic backups. Another set up monitoring that emailed him when a test server went down. Nothing groundbreaking, but each one showed he could do, not just recite.
He also volunteered at work. When that senior engineer needed a hand, Marcus raised his. He took the boring cleanup tasks nobody wanted and quietly learned the company's real environment. Within a few months, people stopped seeing him as "the help desk guy."
Do not collect certifications in silence and expect recognition to arrive on its own. The people who get promoted are the ones whose manager has actually watched them solve something. Visibility is part of the work.
The skills that mattered more than the exams
Here is the part people skip. Marcus passed his exams on knowledge, but he got hired on something broader.
In his interview, the panel barely quizzed him on services. They asked how he had handled an angry user, how he explained a technical problem to a non-technical manager, and how he reacted when he did not know an answer. His support years answered all three before he opened his mouth.
That mix of technical ability and communication is exactly the blend covered in this piece on soft skills versus hard skills. The certifications proved the hard skills. The phone work proved the soft ones, and the soft ones closed the deal.
Marcus told me the question that won him the job was "tell me about a time you were wrong." His support background gave him a dozen honest answers. A pure exam-crammer often has none.
Other routes if AWS is not your fit
AWS worked for Marcus because his employer used it. Your path might point elsewhere, and that is fine.
If your company runs on Microsoft, the Azure fundamentals track is a natural mirror of the same idea. If you are still early and unsure whether tech is even your lane, the broader, beginner-friendly Google career certificates give you a low-cost way to test the water before committing to a heavier cloud track.
The principle stays the same across all of them. Pick one platform, go deep enough to build real things, and ignore the noise telling you to learn everything at once.
Start with the cloud platform your employer already uses, not the trendiest one. Study a steady 8-10 hours a week instead of cramming, and accept that the timeline will stretch. Build small projects so your skills are visible, not just claimed. Volunteer for the unglamorous tasks at work to learn the real environment. And remember that your support background is an asset in interviews, because soft skills often decide the offer.
Do I need a computer science degree to move from help desk to cloud engineering?
No. Marcus did not have one, and many cloud engineers do not either. Associate-level certifications plus a few real projects you can talk through are usually enough to land a junior role, especially when you already have support experience to lean on.
How long does this realistically take while working full time?
Plan for roughly a year to 18 months at a steady pace of around 8-10 hours a week. Marcus took 14 months across three certifications, with several gaps when life got busy. Faster is possible, but a sustainable pace beats a sprint that burns you out.
Which cloud certification should I start with?
Start with a foundational exam for whichever provider your employer already uses, such as the AWS Cloud Practitioner or the Azure fundamentals track. It gives you the vocabulary and confidence to tackle the harder associate exams without feeling lost.
Marcus is not unusually gifted. He just picked one direction, studied a little every morning, and made sure people saw the work. If you are reading tickets right now and wondering whether the door is open, it is. Start with the platform on your own screen, and give yourself a year of steady mornings. I have watched plenty of people do exactly this, and I would bet on you doing it too.
