What I wish I knew before joining CloudRock, and why being surprised was the best part

I wish I knew CloudRock would be this much fun, but I’m so glad I didn’t

Before joining CloudRock, I thought I had a fairly accurate picture in mind: a world full of ERP systems, enterprise clients, long meetings, and even longer acronyms. What I didn’t expect was an experience that felt less like onboarding and more like unlocking a new level.

Looking back, there’s a part of me that wishes I had known how exciting, dynamic, and people-driven this journey would be, but truthfully, I’m glad I didn’t. Because the best part? Being surprised by it. So, here’s everything I thought I needed to know, and why being wrong was the best thing that could’ve happened.

I wish I knew I didn’t need a handbook to succeed

Day One arrived with its usual first-day jitters and an internal checklist I’d created for myself: show up, figure it out, don’t ask too many questions. Spoiler, that checklist went out the window within the first half-hour.

What I quickly realised was that no one had it all figured out. And more importantly, no one expected me to, either. Instead, CloudRock gave me something better, a culture where questions are encouraged, not avoided. What I found? Success here isn’t about having all the answers, it’s about asking the right questions, learning fast, and being open to evolving.

I wish I knew it wasn’t just about the tech

I arrived ready for dashboards, deployments, and delivery deadlines, but was greeted by high-energy Teams chats, spontaneous pep talks, and a calendar suspiciously full of cultural events. What I expected: ERP deep-dives.
What I got: A pulse, a rhythm, and a community that brings its whole self to work, even on a Wednesday afternoon.

What I found instead: CloudRock isn’t just a tech firm. It’s an ecosystem of sharp minds, good vibes, and even better conversations.

I wish I knew asking ‘basic’ questions would be a strength, not a weakness

We’ve all had that moment, hovering over the send button, unsure if the question is too obvious to ask. But here? The response is almost always, “glad you asked that, I was wondering the same thing.”

Mentorship doesn’t arrive in calendar invites here. It’s woven in in-person chats, review calls, and check-ins that make you feel like you’re being invested in not just being paid. What I found instead: Curiosity isn’t just welcomed, it’s celebrated. Especially when it leads to growth.

I wish I knew workplace culture had actual... culture

I assumed “culture” meant the occasional email or an annual team lunch. I didn’t expect floor games, cricket matches, volunteering drives, CIPL madness, or impromptu team jam sessions that somehow still ended on time.

Suddenly, work was no longer confined to the project tracker. It became a space to celebrate, connect, and reset, all while delivering results. What I found instead: Culture at CloudRock doesn’t switch on after hours. It’s embedded in everything we do, and it’s built on one of our core beliefs: we’re better together.

I wish I knew technical knowledge was just one piece of the puzzle

Sure, I came in with the intention to master the tech stack. But somewhere between client meetings, solution demos, and internal syncs, I realised that storytelling matters just as much as syntax. CloudRock didn’t just sharpen my technical capabilities, it taught me how to present with confidence, to speak with purpose, and to lead conversations with clarity. What I found instead: Your skills get you in the room. Your voice keeps you there.

I wish I knew I didn’t need to have it all together on day one

Let’s be honest, the first few weeks felt like standing on a treadmill that just keeps speeding up. New tools, shifting timelines, new faces, and meetings that somehow start sharp at 9:00 AM. And yet, never once did I feel like I was expected to handle it alone. The support was unspoken but ever-present, teammates jumping in without being asked, leads checking in even when you didn’t know you needed it.

What I found instead: You don’t need to sprint from the start. You just need to show up, the rest, you figure out together.

I wish I knew fresh ideas were meant to be shared, not shelved

I assumed being new meant being quiet. That I should learn first, and contribute later. But what I saw instead was a culture where fresh ideas didn’t just land, they stuck. Whether it was suggesting a new way to automate something or just rethinking how a task could be delivered, the response was never “maybe later.” It was often, “let’s do it now.”

What I found instead: You’re not expected to wait your turn. If you’re ready, you’re empowered.

Looking back, and loving the surprise

If someone had told me everything that CloudRock had in store, the mentorship, the madness, the momentum, I might’ve felt more prepared. But the truth is, I would’ve missed the thrill of discovering it all on my own.

The moments I stumbled. The first time I led something without a safety net. The day I realised I wasn’t just “figuring it out”, I was getting it.

To anyone about to begin their CloudRock chapter, don’t wish the unknown away. Because right there, in the in-between of “not sure” and “I got this”, is where the good stuff lives. And trust me, that’s the part you’ll remember.

Previous
Previous

From Campus to Developer the transition from studying to building apps

Next
Next

Inside CloudRock’s Cultivate programme, building confidence, skills & a consulting mindset