Six stages, one connected system

I began my career developing and maintaining production applications using Java, JavaScript, SQL and MySQL. The systems I worked on were already in daily use, so every change had to respect the people and processes that depended on them.

This stage taught me how production systems actually behave: how backend applications, databases and business requirements fit together, and how to deliver enhancements without disrupting the services already running.

My career started with code. Working on production applications taught me that software development is not only about building new features. It is also about understanding existing systems, solving problems carefully and maintaining the reliability people already depend on.

As my responsibilities grew, I moved deeper into backend services built with Java, Spring and Spring Boot — REST APIs, SOAP integrations and the MySQL databases behind them. I contributed to architecture discussions and worked closely with QA and product teams.

Investigating complex production issues became a regular part of the job. Tracing a problem through services, integrations and data taught me how individual technical decisions ripple out into performance, reliability and the wider customer experience.

As my responsibilities grew, I became more involved in backend services, integrations and complex production issues. This helped me understand how individual technical decisions affect performance, reliability and the wider customer experience.

Moving into technical project delivery changed my day-to-day work from primarily writing software to managing how software gets delivered. I worked with clients to understand their needs, translated requirements for engineering teams, and led sprint planning, prioritisation and milestone tracking across multiple concurrent programmes.

The platforms varied — ERP, eCommerce, inventory, ticketing and knowledge management — but the delivery challenges were consistent: managing risks and dependencies, coordinating testing, preparing launches and keeping clients informed along the way.

Moving into technical project delivery changed how I looked at technology. A technically correct solution still needs clear requirements, realistic planning, stakeholder alignment and disciplined execution to create business value.

At GK Telecom I work across technical delivery and service delivery for digital telecom platforms — web applications, mobile applications and the backend systems behind them. The work spans platform architecture, product execution, partner integrations, payments, customer onboarding and compliance-related workflows.

My role sits between engineering, product, operations, commercial teams, external technology providers, telecom partners and senior stakeholders. Beyond delivery, I own operational readiness: incident and escalation management, vendor coordination and the continuous improvement that keeps a live service healthy.

My current work sits between technical delivery and platform operations. I help define what needs to be delivered, coordinate the teams and partners involved, manage technical and operational risks, and make sure the service can continue to improve after launch.

As CTO at eROAMING, I provide technical architecture and delivery direction shaped by both my software engineering background and my delivery responsibilities. I design practical solutions around real product requirements: how frontend, backend, APIs and operations connect, how customer and partner journeys flow, and how the platform stays scalable and reliable.

Architecture only matters if it can be delivered and operated, so I spend as much time managing technical trade-offs and translating designs into deliverable work as I do on the designs themselves. Increasingly, practical GenAI runs through all of it — research, structuring requirements, documentation, analysis and process optimisation.

I approach architecture from both a technical and delivery perspective. A good architecture must support the product journey, integrations, operational teams, future changes and the practical realities of delivery.

Away from platforms and delivery plans, I follow cricket, explore new places and enjoy understanding how different cultures live, eat and use technology. Travel across more than ten countries has given me a different kind of education — one that shapes how I work with teams and customers around the world.

Cricket was my first love. It has always represented a combination of patience, preparation, teamwork and knowing when to take responsibility.