From Call Centers to Cloud Architect: The Unlikely Path to Tech

How tinkering, imposter syndrome, and late-night study sessions built a career in tech—and why your passion matters more than your path.

If you're here expecting one of my usual deep dives into cloud architecture or DevOps wizardry, buckle up—this is going to be a little different. This is not a technical article about best practices or how-tos. Instead, it’s a story. It’s about where I started, how I got here, and the messy, sometimes funny, and often unexpected journey along the way. I wanted to share my experiences not because I have all the answers, but because I think there's value in being open about the ups and downs, the successes, and the faceplants. If you’re someone just starting out, or someone who’s been around for a while and needs a reminder that nobody has it all figured out—I hope this helps. And hey, maybe you’ll find a little inspiration or at least a laugh at my expense. So, let’s get into it.

Some people recall their childhood Christmases filled with toys, laughter, and the smell of gingerbread. Mine? Well, let’s just say Santa had me debugging Windows XP. I’d like to think my parents gave me the ultimate gift: curiosity wrapped in a software update. By the time I was in the 5th or 6th grade, I was already dabbling in operating systems, which, to be fair, was a lot more fun than most middle school hobbies.

That innocent tinkering set me on a path I didn’t even know existed. At the time, I wasn’t exactly dreaming of architecting cloud solutions while troubleshooting Windows 98 crashes. But looking back, those moments were my first taste of the creative problem-solving I’d come to love.

Now, I didn’t start my career with an office full of blinking servers and Kubernetes clusters. No, I began in a call center. Imagine taking calls from irate customers while trying to keep your cool and smile through the frustration—it’s basically the IT equivalent of being a Zen master. Picture this: me, a headset, and the challenge of helping someone reset their email password while keeping my cool as they forgot it again. Looking back, I think that job gave me one of my most important skills: the ability to take a deep breath and keep moving, even when things seem, well, broken. Objectivity, patience, and the wisdom to know that every problem has a solution—even if that solution starts with, "Have you tried turning it off and on again?"

I was a curious learner, even back then. On breaks, I’d crack open a book on networking or read up on new tech—anything to quench that insatiable thirst to understand how things worked. Nights were spent studying, sometimes falling asleep at my desk, laptop still glowing. And then the next morning, it was back at it again—rinse, repeat. My next employer recognized that spark, took a chance on me, and gave me my first opportunity in tech. From there, it was like riding a roller coaster with no lap bar—terrifying at times but thrilling, and it only moved forward.

Transitioning into a more technical role wasn’t just about skills—it was about curiosity. Employers noticed I was willing to learn, and thankfully, one of them took a chance on me. That’s when things really started to change. My new job was my playground, and I was like a kid in a candy store. Except the candy was scripts, servers, and occasionally a stubborn network configuration.

Cloud? Yeah, I’ll admit it: that was overwhelming at first. My early days as a cloud architect felt like standing at the base of an impossibly steep mountain, one covered in acronyms and buzzwords I couldn't even pronounce. Where to start? Which course, which document, which button? There were acronyms I didn’t understand, tools I’d never heard of, and concepts that seemed designed to confuse mere mortals. But like anything worthwhile, I took it one small step at a time. I dove into courses, tinkered, broke things, fixed them, broke them again (it's the best way to learn), and slowly, steadily, the fog cleared. I started to see the architecture beyond the chaos—I began to understand how to bring things together, to make them secure, to make them work.

And of course, certifications were part of this roller coaster ride. Some people love to collect stamps; apparently, I like to collect certifications. Not for the piece of paper but for the structure, the challenge, and frankly, for the ability to keep learning how to learn. If you’ve ever wondered why someone has over ten certifications, let me assure you—it’s not a love of exams. The hardest one for me? Definitely Azure Administrator. I took that one early on, back when I was still struggling to keep my head above water. It felt like running a marathon with new shoes—uncomfortable but worth it. I was studying after work, during weekends, and at times, I’d be reading late into the night until I’d wake up with a drool stain on the study guide. Glamorous, right? But I wasn’t alone. My then-girlfriend—now my wife—was right there with me, offering encouragement, snacks, and the occasional "you should really sleep now" nudge.

And then came my first architecture role—totally unexpected, like walking into a room and realizing you’re the one supposed to be giving the presentation. I’d never aimed for it, never thought I was the "architect type." I pictured architects as these sophisticated, slightly intimidating tech geniuses who effortlessly mapped out infrastructure like it was second nature. That wasn’t me—or so I thought. But life has a funny way of working out, and before I knew it, I was in the thick of it, sketching out designs, making decisions, and realizing that, maybe, just maybe, I belonged there.

My “aha” moment came when I was offered a role as a cloud architect. Honestly, I didn’t see it coming. I wasn’t gunning for architecture roles, but sometimes life surprises you in the best way. Designing solutions that bridged on-premises infrastructure with cloud innovations felt like building something meaningful. It wasn’t just technical—it was creative, and I loved it.

Mentors came in all forms—colleagues who shared knowledge over coffee, a manager who trusted me with challenges that stretched me, even DevOps peers who taught me that the best kind of mentorship is sometimes the one that isn’t labeled as such. These people, knowingly or not, helped shape the professional I am today. From a DevOps wizard who taught me to dissect problems like a surgeon to a manager who believed in me more than I believed in myself, these people shaped my journey. And to this day, I try to do the same—whether it’s mentoring teammates, asking the right questions, or just being there to say, "Hey, it’s okay if you’re stuck. Let’s figure this out."

And let me not forget imposter syndrome. We’ve been well-acquainted for quite some time. There’s a little voice in the back of my head that loves to chime in at the most inconvenient times, saying, "Are you sure you belong here?" Honestly, I don’t think I’ll ever fully silence it. Instead, I manage it. If you think imposter syndrome disappears after a few career wins, let me burst that bubble. It doesn’t. Even now, with all my certifications and projects, there are days I feel like I’m playing catch-up. The trick isn’t to eliminate those feelings—it’s to manage them. I remind myself that everyone’s journey is different, and I take comfort in the fact that every new challenge I’ve faced, I’ve eventually tackled. The truth is, the feeling of not knowing it all? It’s just proof that there’s always more to learn.

To those starting out—whether you’re refreshing Windows XP for the thrill of it, working a call center job, or staring at a certification study guide at 3 AM—know that every step matters. Start small. Build something, anything. Learn the basics, practice with passion, and don't chase money. Chasing money gets you tired; chasing curiosity gets you skilled. And skilled? That’s when the money comes chasing you. Foundations matter more than shiny titles. Passion drives progress; the money will follow.

Every "aha!" moment, every foundation you lay, every tiny brick of knowledge—they all build towards something bigger. Think about the Eiffel Tower. It took time, solid foundations, and a lot of patience. Your journey is no different. It’s messy, it’s uncertain, and it’s yours—and honestly, there’s no better one to be on.

Now, I want to hear from you! What’s your journey into tech been like? Have you decided to pursue a career in tech? Have you had those late-night “aha!” moments or battled with imposter syndrome? Share your story, your challenges, or even your advice in the comments below. Let’s start a conversation about how we’ve all navigated our unique paths in this ever-evolving field. Together, we can inspire and learn from one another.
Nicolae-Loredan Calimanu