Exactly one year ago I joined the R&D team at Matrixx Software as a Software Engineer. Stepping into the telecommunications industry has been a true paradigm shift. I realized that telco is a "small world" niche ecosystem where today’s competitors are tomorrow’s colleagues, and specialized knowledge is the ultimate currency where I'm initially lost on these vast codebase of unknown lack of insight haha.
At Matrixx, we build mission-critical Charging and Monetization solutions. Our products sit at the heart of global client telco infrastructure around the globe, enabling providers to charge customers in real-time based on complex policies and massive data usage.
One of my steepest learning curves was mastering the domain of the network because I really think it cant be using common sense wasn't enough to built the mental models of developing an endpoint or component that are built around telcos. I’ve spent the year understanding Diameter Protocol Adapters. Which supports Real-Time Billing and Charging, Diameter Adapters often implement the Diameter Credit-Control Application (DCCA) to enable real-time billing for data, voice, and multimedia services. This is crucial for controlling prepaid subscriber spending limits and enforcing policies in an Online Charging System (OCS).
I’ve also gone deep into our deployment lifecycle. Our applications are orchestrated via Kubernetes, and I’ve had the chance to collaborate closely with Technical Consultants to understand how business logic translates into configuration with our customers. A highlight has been working within their internal team developer environment that contains all MATRIXX development essentials compiled into a kit, our blueprint environment that allows clients to reuse proven deployment patterns for even the most complex pricing models.
Beyond the core billing logic, I’ve had the opportunity to own a critical yet simple component that allowed me to have some ownership during my time at Matrixx. By building a Java Spring Boot parser, I focused on data transformation to feed downstream components.
While maintaining the parser, I have also integrated and supported features across the project, such as Streaming & Storage by working with Redpanda and Apache Iceberg, and Orchestration by incorporating Apache Airflow into our data pipeline orchestrator to streamline complex workflows.
While building and defining the schema, I learned that we have to adhere to the TMFORUM documentation, which also defines having different modules to ensure compatibility between other components.
There so many modules TMFORUM APIs with different potential use cases to solve or innovates. Serve as a good life experiences
Coming from a Fintech background, there a lot of contrast on how thing handled and build. While Fintech is often characterized by a rapid pace and strict financial regulations, Telco presents a different kind of challenge. The complexity lies in the design and requirements, where there isn't always a "standard" way to solve a problem, requiring a more experimental and architectural mindset.
As I say goodbye to my colleagues at Matrixx Software, I wish everyone great success and hope our paths cross again in the future. Thank you for being helpful and supportive during my time there. I understand circumstances change and are beyond our control, but we must do what we have to. Best of luck!
I’ve realized there is still so much to learn for me in many industries that i may be, but that’s the exciting part. My goal is to continue evolving into a Backend Engineer. I want to contribute to the impactful infrastructure that keeps the world connected. In my next chapter, I hope to serve the people around me and proudly say that I did that.
I honestly can’t wait to see what the rest of 2026 brings.