Humans of justDice: Uzair, Principal Software Engineer

Our team here at justDice is a blend of fun and professional. And that’s what these posts aim to unlock. We want the Humans of justDice features to focus on getting to know the people and minds behind the scenes. We’ll get to know a different team member every month, giving you an exclusive look into how we work together here at justDice 🙂

Uzair is a Principal Software Engineer at justDice, having been part of our journey for over four years. From launching our first iOS app to building backend systems like Bundle Service and CI/CD, he has played a significant role in shaping the products that millions of users enjoy today.

Known for his thoughtful approach and calm energy, Uzair brings a steady hand to complex technical challenges and a mindset focused on long-term impact. Let’s get to know him a little better.

1. How did you get into mobile development?

Well, I have a bachelor’s in Software Engineering and a Master in Distributed Software Systems. After graduation, I started my career in app development. I then relocated to Germany, and here, as well, I saw the trends shifting towards mobile apps, so I stayed with that. It made sense to continue in that direction—the mobile space was growing fast, and there was a lot to build and learn.

2. And what brought you to us?

I came to Germany for studies, and I did my Master’s at the Technical University of Darmstadt. Initially, I worked in a services-based company, but I then switched to a more product-oriented business. That shift is what brought me to justDice, where I could focus on long-term product development, rather than short-term client projects. justDice offered that, along with interesting challenges.

3. What’s a system or feature you’ve worked on that you’re quietly proud of?

It’s been four years since I started working here at JD. I’ve worked on so many things that made a difference that it’s hard to pick one 😀 , e.g., bundle service, payout templates, our first iOS app, CI/CD, etc. Some of these systems are still in use today, which shows they solved real problems. It’s nice to see that kind of long-term effect.

4. What’s your approach to tech challenges?

I start from the grassroots level, first checking the concept, its feasibility, and the actual problem we are trying to solve with it. Once that is established, I work on the requirements for that system. It helps to slow down at the beginning so you don’t waste time building the wrong thing. Clear understanding up front usually saves time later.

We also recently changed the way we work within our team. Introducing more transparent processes. We are also incorporating ML in our ecosystem to enhance our capabilities for offerwall management, etc. We’re still testing and improving, but the shift has already made things more structured. The ML use cases are still in their early stages, but there is good potential.

5. Has there been a moment when things didn’t go to plan?

Sure, we worked on payout templates to decouple our voucher payouts from FE and to manage them on the BE side. The idea behind this was good, but it did not go as planned, as we grew a lot and managing 100s of vouchers without automation became hard.

From the start, we could have done it in a more automated way so that later we wouldn’t have to revert the templates. That experience was a good reminder that scale creeps up quickly—designing for it early on pays off.

6. How would you describe the team and culture at justDice?

Diversity: We have a very diverse group of people here. We have different ideas, different ways of doing things, and (perhaps most importantly) different food. It’s one of the best parts of our company. It keeps things interesting and strengthens collaboration. You end up learning new things without even trying.

It’s also helped me grow, as I am now more open to new ideas. Leads and management are also open to exploring new ideas and opportunities. That trust makes it easier to suggest improvements or try out a different approach. It doesn’t always work, but at least you can try.

7. Alright… so who’s harder to beat: you at ping pong or you at FIFA?

It depends on the day 😀. One day, your through passes are working, and the other day, you are missing 1v1 goals. But essential here is to always reflect on your mistakes and learn from them 🙂