Overview
Nedbank is a South African multinational financial services company offering retail, business, and corporate banking. I worked on their internet banking application — a complex, security-critical web platform used by thousands of banking customers.
The project was ongoing, with a focus on maintaining the existing application while continuously improving existing features and delivering new functionality.
My Role
I joined the frontend team as an Angular developer working on the internet banking platform. My work spanned both maintenance and active feature development, requiring a strong understanding of the existing codebase and banking domain requirements.
What I Built
- New features added to the internet banking application as part of the product roadmap.
- Improvements to existing features, addressing bugs, edge cases, and usability issues.
- NgRx-based state management implementations for new and updated application flows.
- Responsive UI updates ensuring the application worked correctly across desktop and mobile screen sizes.
- Consistent implementation of financial UI patterns and form flows in line with banking compliance and UX standards.
Challenges & Solutions
Internet banking applications carry significant complexity — financial data must be handled precisely, user flows need to be intuitive under stress, and the codebase tends to be large and long-lived. Working across an existing platform meant understanding a broad codebase quickly and making changes carefully to avoid regressions in critical flows.
Security was a constant consideration throughout the project. Working on a banking platform meant being mindful of how data was handled, ensuring sensitive information was never exposed in the UI layer, and following established security practices across all feature work.
The project also required strong communication in English with a distributed team of QA engineers, business analysts, and product owners. Translating banking domain requirements into technical solutions, and clearly communicating progress and blockers, was an essential part of the day-to-day workflow.
I focused on understanding the application’s NgRx architecture before making changes, writing targeted improvements rather than broad refactors, and thoroughly testing any flows that touched account or transaction data. Onboarding quickly into a large, long-lived codebase and delivering relevant changes with minimal disruption was a key part of my contribution.
Results
Over the engagement, the platform continued to evolve with new features and steadily improved UX across key banking flows. The NgRx state management approach kept complex data flows predictable, and the responsive design updates extended the usability of the application on mobile devices.