In 2024, my work at Temenos deepened into systems where performance and scale were no longer abstract ideas. I spent most of my time on backend-heavy problems, working with [Java x Spring Boot x MySQL x SQL Server], trying to understand why systems slow down and how they recover.

I worked closely with databases, refactoring stored procedures, untangling nested queries, and optimizing execution plans. Indexing, query paths, and data access patterns stopped being theory and started becoming instincts. Testing performance through tools like [Postman] taught me that correctness alone is not enough — systems must remain predictable under pressure.

At the same time, I worked on API layers and backend services where scalability mattered. Using [Java x RESTful APIs x cloud-based services], I learned how small backend decisions quietly influence user-facing speed and reliability.

In 2023, still at Temenos, my focus shifted toward decision-driven systems. I worked on multi-level approval flows for SME banking, where logic directly translated into trust. Using [Java x Spring Boot x React x MySQL], I helped build configurable approval matrices that automated complex decision paths while remaining secure and auditable.

These systems forced me to be explicit. Every rule needed to be readable. Every condition needed to justify its existence. Working on approval logic taught me restraint — writing code that explains itself, instead of trying to impress.

On the frontend, I used [React] to build dashboards that surfaced backend states clearly. Approval statuses, pending actions, and real-time feedback loops mattered. I learned that frontend clarity often prevents backend failures before they happen.

Earlier in my time at Temenos, I worked on customer-facing financial features like cardless cash withdrawal systems. This work combined [React x Node.js x TypeScript x GraphQL x MySQL], and pushed me to think carefully about security and time-bound logic.

I worked on flows where codes expired, validations mattered, and failure states had to be handled gracefully. Automated alerts, audit tracking, and secure backend workflows became part of how I thought about system design. It was here that I learned how fragile trust can be — and how software either reinforces it or breaks it.

My professional journey began at Tata Consultancy Services in 2021, working on web applications for a global airline. Using [JavaScript x Spring Boot x SQL], I contributed to systems that had to remain stable during peak usage and high traffic.

This was where I learned how software lives inside teams. [Git], testing pipelines, agile sprints, and release cycles were not side details — they were the structure that allowed software to exist beyond a single developer. I learned how collaboration, documentation, and consistency shape long-lived systems.