My journey into software engineering didn’t follow a perfectly straight line—but looking back, it feels like it led exactly where it needed to.

I studied Computer Science at university in Malaysia. While the program gave me a solid foundation, what truly captured my interest was web/app development. I enjoyed building things—turning ideas into something tangible on a screen. Over time, I worked on many personal and side projects, learning far more through experimentation and real-world problem-solving than through textbooks alone.

To be honest, I was never particularly attached to school subjects themselves. I learned what I needed to, but my motivation always came from doing—from writing code, debugging issues, and slowly improving through practice.

Alongside university, I completed two internships, one of which was full-time while I was still studying. Balancing work and academics was challenging, but it gave me early exposure to real production systems, deadlines, and collaboration. Those experiences helped bridge the gap between theory and reality long before I graduated.

Right before graduation, I applied to Colorkrew—and was fortunate enough to receive an offer.

Why Colorkrew Stood Out

During the interview process, one theme kept coming up: Colorkrew was described as a flat and open organization.
It was emphasized that:
- You can speak up without fear
- Ideas are welcomed, even from fresh graduates
- Being junior doesn’t mean being unheard

That resonated strongly with me. I’ve always been someone who likes to ask questions, share ideas, and challenge assumptions constructively. Knowing that this mindset wasn’t just tolerated but encouraged made Colorkrew feel like the right place to start my career.

Starting Remotely Before Graduation

One thing I deeply appreciated was how accommodating the company was during my transition period.

Before officially graduating, I spent six months working remotely. At a time when I was still wrapping up university commitments, this flexibility made a huge difference. Rather than delaying my growth, I was able to start contributing early, learning the codebase, and understanding how the team worked—all while completing my degree.

Despite working remotely, I never felt disconnected or sidelined. Communication was open, expectations were clear, and I felt trusted even as a fresh graduate who hadn’t yet stepped into the office full-time. That trust gave me confidence and made the eventual transition into on-site work much smoother.

From Intern to Full-Time Engineer: Ownership Matters

One of the biggest shifts I experienced moving from internships to a full-time role was the sense of ownership.

As an intern, it was easier to treat tasks as temporary. If something wasn’t perfect, it didn’t always feel like a long-term problem. There was less weight to decisions, and mistakes felt more contained.

As a full-time software engineer, that mindset changed quickly. I began to realize that code doesn’t disappear after a feature ships, small shortcuts can turn into long-term problems, and bad habits today can come back to bite much harder down the road.

Ownership meant thinking beyond “Does this work now?” and asking, “Will this still make sense months from now?” It meant caring about maintainability, clarity, and impact—not because someone demanded it, but because the responsibility was now mine.

Learning to Care About the “Boring” Parts

One of the most unexpected changes for me was learning to care deeply about the things I once considered boring.

In my personal projects, documentation, structure, and consistency were often afterthoughts—or missing entirely. The goal was usually to make something work, move on, and start the next idea.

In a professional environment, that mindset doesn’t hold. At Colorkrew, I quickly learned that clear documentation saves future teammates time, consistent structure makes codebases approachable, and small organizational decisions compound over time.

These things aren’t flashy, but they matter.

Growing Through Trust and Opportunity

In my first few months at Colorkrew, I found myself consistently asking for:
- Projects with larger scope
- More complex problems
- Exposure to other domains, including infrastructure

Each time, the response was encouraging. Initiative was met with opportunity, not hesitation. I wasn’t expected to know everything—but I was trusted to learn, ask questions, and take responsibility.

That balance between support and trust created an environment where growth felt natural rather than forced.

A Multicultural Place to Learn

Another aspect I value greatly is Colorkrew’s multicultural environment. Working alongside people from different countries and backgrounds brings diverse perspectives into everyday discussions and decisions.

At the same time, I’ve had the chance to learn about and immerse myself in Japan, both professionally and personally. That combination of global collaboration and local culture has made my experience richer than I initially imagined.

Beyond the Code

The culture extends beyond work itself. We even have weekly badminton and bouldering sessions, which make it easy to connect with teammates outside of projects and meetings. These moments help build real relationships and create a sense of balance that makes work more sustainable and enjoyable.

We also have hackathons where collaboration between teams were required and helped me interact and get to know others better!

Looking Ahead

Starting my career at Colorkrew feels less like just getting my first job and more like beginning a long-term journey—one where I can continue growing, taking ownership, and learning what it truly means to build software that lasts.

This is a new chapter for me, and I’m grateful to be writing it here.