DBS, Southeast Asia’s largest bank and one of the world’s highest-rated financial institutions, has spent more than a decade rebuilding its technology core to support a fully digital banking model across Singapore, Hong Kong and the wider region.
Known for its early and aggressive push into mobile banking and cloud-ready architecture, the bank has repeatedly been named ‘World’s Best Bank’ for its ability to fuse engineering discipline with customer-centric digital services.
Behind those accolades sits a long-running effort to modernise its legacy estate, industrialise software testing and embed resilience directly into its delivery pipelines.
For QA and software testing teams across global financial services, DBS’s transformation offers one of the clearest examples of how an incumbent can evolve into a technology-driven institution built on automation, rapid release cycles and disciplined test engineering.
The groundwork for DBS’s transformation began as early as 2010, when CEO Piyush Gupta challenged his newly appointed CTO, David Gledhill, to overhaul the bank’s fragmented technology landscape.
At the time, DBS was operating in 12 markets with “totally different core banking systems,” and a major transformation programme was already running behind schedule and over budget. Gledhill assessed that the initiative lacked clear outcomes and cancelled the project outright, an expensive but pivotal reset that Gupta would later call a necessary “down payment on digital transformation.”
From that point on, DBS began reframing itself as a technology-first organisation. Gledhill popularised a guiding question, namely “What would Jeff do?”, a prompt to think like Amazon founder Jeff Bezos and benchmark the bank’s engineering culture against the world’s leading digital giants.
Internally, this mindset evolved into ‘GANDALF’, a shorthand for emulating the best of Google, Amazon, Netflix, Apple, LinkedIn and Facebook, culminating in the ambition for DBS to become the ‘D’ in that elite group.
Automation as a foundation for resilience
As part of its digital-to-the-core strategy, DBS placed automated testing at the centre of its technology renewal. A widely cited case study notes that automated testing reached “almost 100%” for some digital channels, an achievement few incumbent banks have matched.
This level of automation became critical for DBS’s ability to push frequent releases to mobile and internet banking platforms while maintaining reliability and regulatory compliance in Singapore and Hong Kong.
In Hong Kong, DBS went further by integrating automated testing across multiple mobile apps and key customer-facing web platforms. Continuous Integration and Continuous Deployment (CI/CD) pipelines were designed to minimise human error, reduce testing bottlenecks and accelerate release cycles.
According to one project summary, the bank reduced manual testing effort from “20 man-days for testing a new function to 1 man-day for checking the report,” while shrinking functional test execution from “five days… to a few seconds to run the test script.” The bank also achieved hourly scheduled test runs, an uncommon level of frequency for a major Asian financial institution.
These gains were not only about speed; they formed part of DBS Hong Kong’s broader shift toward resilience engineering, ensuring that new features could be deployed quickly without compromising availability or stability.
Reinventing the core
DBS Hong Kong also undertook one of its largest-ever core system programmes, replacing legacy platforms that were limiting scalability and slowing product innovation. The bank set out to build a modern, open, scalable and resilient core that could support real-time processing, regional alignment and future digital expansion.
The 24-month transformation covered requirements definition, process redesign, system build, extensive testing, performance assurance and a tightly controlled migration to the new core.
To mitigate cutover risk, the bank executed a pilot deployment a month before the full migration, followed by a miniature trial migration to validate data integrity.
This staging approach narrowed the implementation window and reduced system downtime during the final go-live, critical given the inclusion of high-risk channels such as ATM, mobile and internet banking.
Comprehensive integration was another major testing challenge, involving 109 upstream and downstream systems across a variety of protocols. DBS introduced generic APIs to simplify interoperability and built middleware cache layers to ensure speed and stability.
The bank also developed new extraction utilities to minimise batch windows and improve performance, components that are now being reused across the bank’s wider footprint.
Benefits
For DBS Hong Kong, upgrading the core and embedding automation across delivery pipelines produced tangible operational benefits. The bank reduced account-opening and servicing turnaround times, accelerated product launch cycles and cut processing time for key transactions.
Payments that previously required extended handling were eventually completed in “half the time taken earlier,” while cash withdrawals, deposits, transfers and FX operations all saw significant time reductions.
More importantly, the bank established a digital-ready foundation capable of supporting contextual, real-time and omnichannel experiences—a critical objective in one of Asia’s most competitive mobile-banking markets.
Across Singapore and Hong Kong, DBS’s investment in automated testing, CI/CD and platform modernisation has positioned it as one of the region’s most advanced digital banks.
For QA and testing teams elsewhere, its path underscores several lessons: automation must be treated as a core engineering capability, not an add-on; resilience depends on system simplification and architectural coherence; and modern digital banking requires continuous testing, not periodic testing.
DBS’s transformation continues to be studied across the industry for a reason. Few banks have achieved this degree of scale, automation and digital resilience, and fewer still have embedded it into the culture to the point where thinking like a technology company has become the organisational norm.
Why not become a QA Financial subscriber?
It’s entirely FREE
* Receive our weekly newsletter every Wednesday * Get priority invitations to our Forum events *
REGULATION & COMPLIANCE
Looking for more news on regulations and compliance requirements driving developments in software quality engineering at financial firms? Visit our dedicated Regulation & Compliance page here.
READ MORE
- Leapwork engineering head: Why test automation so often fails to deliver
- World Economic Forum warns financial sector must strengthen AI risk controls
- How Banca Progetto is hard-wiring quality into Italy’s digital banking space
- How Wealthsimple builds quality into the product, not around it
- Digital revamp puts spotlight on internal controls at China Construction Bank
WATCH NOW
QA FINANCIAL PODCASTS
Listen to Sudeepta Guchhait on Nasdaq’s new Mimic AI testing platform
QA Financial sits down with Sudeepta Guchhait, Senior Director of Product Framework & Quality Engineering at Nasdaq
——–
Listen to Wesley Scheffel and Robin Rain on Schroders’ DevOps strategy
We catch up with Wesley Scheffel, Head of Cloud Platform and Product Engineering at Schroders, and Robin Rain, Head of Cloud Platform Architecture
——–
Listen to Citi’s Jason Morris on Lightspeed and the future of continuous delivery
Jason Morris, Head of Developer Pipelines for Securities Markets and Banking at Citi, talks about Lightspeed
