From Competing in 40+ Countries to Becoming a Cloud Engineer
There was once a professional track and field athlete. He competed across six continents and more than 40 countries, and as retirement approached, he even took on event-operations work for a national sports commission. From the outside, it looked like a smooth career. But one question kept surfacing in his mind.
"What am I going to do once I stop competing?"
He had spent his whole adult life training, which meant he had no IT background and no cloud experience. He didn't even fully understand how computer networks worked. His name is Ifeanyi Otuonye. Today he works as a Technical Account Manager at AWS — but just a few years ago, he was living in a completely different world. His story, featured on AWS's official blog, shows just how far someone can go starting from zero certifications.
Starting to Study With Zero Prior Knowledge
After retiring, he spent about a month researching different career paths. One field kept catching his attention: IT. The problem was, he had no idea where to start.
So he started with the absolute basics — what computer hardware and software actually are, what a network is, how security works. That's when he first encountered the concept of cloud computing, and one name kept coming up every time he searched: AWS.
But the more he looked into AWS, the more overwhelming it got. EC2, S3, VPC, IAM, Lambda — the list of service names kept growing, with no clear sense of what to study first. That's when he discovered AWS certifications. What he valued wasn't the certification itself, but the fact that it gave him an order to study in.
He Failed His First Exam
The first certification he prepared for was the AWS Certified Cloud Practitioner. After about a month of studying, he sat the exam. The result: he failed.
That failure led to an important shift. Instead of simply studying more hours, he changed how he studied. Up to that point, he'd focused mostly on concepts and theory. This time, he started actually using AWS — building services, following hands-on labs, putting together small projects. When something broke, he fixed it and figured out why it hadn't worked. He started spending his time understanding how AWS actually works, instead of memorizing exam answers.
Six weeks later, he took the exam again — and passed. That's when he said something to himself for the first time: "I'm going to become a Cloud Engineer." It was a small certification, but it completely changed his goal.
He Didn't Just Collect Certifications — He Documented the Process
From there, he went on to study for the Solutions Architect – Associate, Developer – Associate, SysOps Administrator – Associate, and Security – Specialty certifications, one after another. But collecting certifications wasn't the only thing he did.
He kept publishing the projects he built and what he learned along the way. He connected with engineers and recruiters on LinkedIn, posted his learning journey consistently, and wrote technical articles. He didn't have the title "Cloud Engineer" yet — but he was already doing the work of one.
One LinkedIn Message, and an 18-Month Career Change
In March 2023, the CEO of a global security company reached out to him directly on LinkedIn, asking if he was interested in joining a remote Cloud Engineering team. An interview followed, and he received an offer.
About 18 months after he started studying cloud computing, a former professional athlete had become a self-taught Cloud Engineer — in a fully remote position, working from his home in the Turks and Caicos Islands.
The Story Didn't End There
He kept learning even after becoming a Cloud Engineer. He stayed active in AWS communities and even taught cloud concepts to others. After relocating to the United States, he went on to earn the DevOps Engineer – Professional and AI Practitioner certifications as well.
Then, an Amazon recruiter reached out — this time with an interview offer for an AWS Technical Account Manager position. He passed the interview and joined AWS. By 2025, when his story was featured on AWS's official blog, he held 10 AWS certifications and was working as an AWS Technical Account Manager.
Why This Story Matters
This isn't a story about "one certification and you're hired." It's closer to the opposite. He failed his first exam. He had no IT background and no cloud experience. Instead, he did three things at once: studied for certifications, practiced hands-on, and kept a public record of what he learned. Opportunity grew out of the combination of all three.
What He Changed After Failing Is the Real Lesson
Anyone studying for a certification runs into this: you remember the answer to a question, but the moment it's rephrased slightly, you're confused again. You can answer "what does this service do?" easily, but "given this company's situation, which service should they choose?" suddenly gets a lot harder.
AWS exams test your ability to judge which service fits a given situation far more than your ability to memorize service names. That's why, when you're practicing, it helps to check not just whether you got the answer right, but why that answer is correct — and why each of the other options is wrong.
If You Have No Background, Treat the Exam Blueprint as a Roadmap
The first time you look into AWS, it feels like there's too much to learn — EC2, S3, IAM, VPC, and then AI, databases, serverless, security. It's easy to burn out fast.
Rather than trying to learn every service at once, it helps to treat the exam's scope as a study roadmap instead. Study one concept, try related practice questions, and go back to the concept whenever you get something wrong. Repeat that loop, and services that once felt disconnected start to click together. Working through practice questions also makes your weak spots obvious — whether you keep missing IAM questions, get tripped up on networking, or slip on cost-optimization scenarios. Checking why you got something wrong matters far more than the score itself.
Conclusion: The Certification Was the Starting Line — He Built the Rest Himself
In Ifeanyi Otuonye's story, the certification was only the starting line. What actually got him to AWS was the way he changed how he studied after failing, and the record he steadily built along the way. It wasn't one certification that changed his life — it was the practice and documentation that certification kicked off, compounding into an actual career.
If you're preparing for your first certification exam right now, it's worth remembering that passing it isn't the finish line — it's the start. If you're worried about the gap between having a certification and having real experience, our post on I Have the Certification But No Experience — Can I Still Get Hired? covers realistic ways to close that gap. And if you're curious about another case where one certification actually changed someone's career from scratch, No Tech Background, One Certification, and a $27,000 Raise is worth a read too.