Trading Comfort for Curiosity: My Journey Into Cloud Engineering from the Girl who Swipes on Bumble

Curiosity Took Me Where Comfort Never Could

How a Virtual Assistant Who Swiped on Bumble Ended Up Falling in Love with Cloud Computing

If you had met me a few years ago, you probably wouldn't have guessed that I'd one day be studying cloud computing.

You also probably wouldn't have guessed that one of my early job responsibilities was managing someone else's Bumble account.

Yes. That Bumble.

Swiping. Filtering. Maintaining conversations. On behalf of a client. Professionally.

I'd like to tell you I handled it with effortless grace and zero internal commentary. I'd be lying. But I showed up, I did it well, and I have never once put it on a résumé, until now, apparently, in a global magazine. So that's growth.

Here's what that season taught me, though: no task is beneath you when you're building your future.

Not even helping someone's virtual love life while your own career is still figuring itself out.

From there, opportunities started opening up the way they do when you just keep saying yes to honest work. I moved into customer support, social media management, then into property management, where I found myself coordinating operations for short-term, mid-term, and long-term rentals across the United States, the United Kingdom, Spain, Canada, and parts of Africa.

Let me paint that picture for you.

Some mornings, I was handling a guest emergency before I'd had my first sip of water. Other days, I was coordinating cleaners in one time zone, responding to a maintenance crisis in another, and reassuring a property owner in a third, all while my phone refused to stop buzzing. Properties thousands of miles away, running smoothly, largely because someone (me) was paying very close attention.

Looking back now, I realize I wasn't just managing properties.

I was managing systems.

I was learning how to solve problems under pressure, document processes before they became disasters, and stay calm when everything decided to be urgent at the exact same time.

And yet.. after two years of genuine growth, I felt something I wasn't expecting.

Comfort.

The sneaky, well-dressed kind. The kind that doesn't announce itself loudly. It just quietly pulls up a chair, hands you a warm drink, and whispers, "You've come far enough. Stay here. You've earned it."

Hey, I almost listened.

But another voice kept interrupting. Curious, slightly annoying, absolutely persistent:

"What exactly is this cloud engineering everyone keeps talking about?"

Now.. full transparency! I was not someone who loved coding. If you had asked me to choose between writing code and doing almost anything else, I would have needed a moment to think of what anything else meant, just to confirm it was still the winner.

So this wasn't about chasing trends.

This wasn't a strategic pivot with a five-year roadmap.

This was pure, unfiltered, slightly illogical curiosity. The kind that doesn't ask for your permission before it signs you up for classes.

So I signed up for classes.

Day one felt like someone had handed me a book written entirely in a language I'd never encountered, except a few words looked almost familiar, which was somehow worse. False confidence is a dangerous thing.

Elasticity.

Latency.

Bandwidth.

Hybrid cloud.

CAPEX. OPEX.

The words blurred together on the page. My notes looked like the fever dream of someone who had Googled "tech terms" and written them all down without reading the definitions. I sat there wondering if I had made a very confident mistake.

Then something shifted.

I stopped trying to perform competence I didn't have yet.

I stopped pretending to follow along and started asking the questions I actually needed answered. Out loud. In class. Without apology.

I started asking myself simpler questions after each lesson:

"How would I explain this to my younger sibling?"
"What real-life thing does this remind me of?"
"If I forget the definition tomorrow, will I still understand the idea?"

And slowly, not overnight, not dramatically, but steadily, things started clicking.

A public cloud became an apartment complex: many tenants, shared building, but everyone has their own private space and their own front door key.

A private cloud became a house that belongs entirely to one person. No neighbors. No shared walls. Full control, full responsibility.

Scalability started reminding me of expanding a property portfolio, as your portfolio grows, you hire more staff to keep up with demand.

Elasticity looked exactly like peak booking season in property management: you bring in extra cleaners for the holiday rush, and once January arrives and the bookings slow down, you scale back. The resources flex with the need.

The cloud stopped being a wall of intimidating jargon.

It became a place I recognized.

And that, genuinely, changed everything.

I document my learning obsessively now.

Not because I have it all figured out.. I absolutely do not, but because I remember exactly how it felt to be standing at the door of a subject that seemed designed to exclude me. I write every explanation for the version of me who sat in that first class wondering if she had made a terrible mistake.

Every note is for someone who thinks they're "not technical enough."

Every analogy is for someone who needs the concept to make sense before it can stick.

Because here is what this journey has taught me, and I mean it plainly:

You don't have to start with confidence. You start with curiosity. Confidence tends to show up later, usually when you least expect it, often while you're in the middle of explaining something you didn't know you understood.

I'm still early in this journey.

I don't have every certification. I haven't built every project I've dreamed up. There are classmates who grasp concepts faster than I do, and engineers with years of experience I haven't accumulated yet.

And I have made peace with that, not in a resigned way, but in a genuinely freeing way.

Because I stopped measuring myself against the most advanced person in the room.

I measure myself against who I was yesterday.

Just recently, after finishing my skincare routine.. because moisturizing is non-negotiable regardless of career stage.. I looked at myself in the mirror and said quietly,

"You've done well."

Not because I'd reached some finish line.

But because I could see, clearly, how much had changed.

The woman in the mirror wasn't defined by the job titles she'd held or the ones she hadn't yet earned.

She was defined by her willingness to keep evolving. To stay curious past the point of comfort. To ask the embarrassing question in the room if it meant she actually understood.

From swiping on a dating app for a client, professionally, don't forget, professionally! to coordinating properties across the world, to learning the architecture of cloud systems one honest question at a time:

The path has not been linear.

But it has been entirely, deliberately mine.

If you're reading this and feeling behind… if you're convinced that the window for reinvention has somehow closed without your permission.. I hope this offers a different view.

You don't need to know everything before you begin.

You don't need to be the most technical person in the room.

You don't need anyone's permission to start over, start differently, or start again.

Sometimes, the people who go the furthest are simply the ones who refuse to sit down.

I'm still writing this story.

This isn't the final chapter.

It's not even close.

But isn't that the best kind of beginning?