My journey into frontend engineering started with curiosity rather than a predefined career plan. In the early days, I was fascinated by how digital products worked behind the scenes and how a simple interface could shape the entire user experience. What began as an interest in web technologies slowly evolved into a long-term commitment to building scalable and meaningful frontend systems.
Like many engineers, I started by working on smaller development tasks and learning through experimentation, debugging, and continuous practice. Those early experiences taught me the importance of fundamentals, patience, and problem-solving. Over time, I realised that frontend engineering was not only about visuals or components. It was about architecture, usability, performance, maintainability, and creating systems that could support real business growth.
As my experience grew, I had the opportunity to work across different industries and enterprise environments where applications were far more complex than traditional websites. These projects introduced me to large frontend ecosystems, distributed teams, scalability challenges, and long-term product engineering. Working in such environments fundamentally changed how I approached software development.
During my time at IBM, I became deeply involved in frontend modernisation initiatives and enterprise application development. I worked on large business platforms, payment integrations, and frontend optimisation projects where reliability and user experience were critical—those years helped me understand how engineering decisions directly impact scalability, maintainability, and delivery quality in production systems.
My journey continued at Accenture, where I moved further into frontend architecture and technical leadership. I led frontend engineering teams, contributed to scalable architecture strategies, and worked on building reusable UI systems for enterprise applications. This phase of my career strengthened my understanding of micro-frontends, design systems, frontend governance, and engineering collaboration across large programmes.
One of the most rewarding aspects of that experience was helping teams move towards more maintainable frontend ecosystems. I enjoyed introducing standards, improving developer workflows, mentoring engineers, and solving architectural problems that became increasingly important as applications and teams scaled.
Today, at NatWest Group, I work as an Associate Vice President, leading frontend architecture initiatives for enterprise-scale platforms. My work focuses on scalable ReactJS ecosystems, micro-frontend architecture, Nx Monorepo implementation, frontend performance optimisation, and reusable engineering foundations that support long-term product development.
Over the years, I have learned that good frontend engineering is not about chasing trends. It is about understanding how to build systems that remain stable, adaptable, performant, and maintainable as business requirements evolve. Technology changes constantly, but strong engineering principles continue to matter.
What keeps me motivated is the opportunity to solve meaningful engineering problems, improve developer experience, mentor teams, and contribute to products that people genuinely rely on. I enjoy creating frontend systems that are not only technically sound but also practical for teams working under real delivery pressures.
My journey is still evolving. I continue to explore modern frontend technologies, architecture patterns, and engineering practices that can improve scalability, performance, and user experience. Every project, challenge, and collaboration adds another layer of learning, and that continuous growth is one of the things I value most about this profession.