When operating at the scale of a global financial institution, reliability is not an abstract aspiration, it is a regulatory expectation and a business imperative.
One good example is Standard Chartered Bank as its Technology & Innovation unit has spent the past several years transforming how its internal software applications are tested, monitored, supported, and engineered, turning Site Reliability Engineering (SRE) into a core capability across the Group.
Standard Chartered Bank has just over 85,000 employees and has a presence in 59 markets, claiming to serve customers in 150 countries worldwide. Its T&I organisation underpins a wide range of group functions such as finance, liquidity risk, legal, compliance, audit, human resources, among others.
Across the T&I domain, responsible for a large portfolio of non-customer-facing software systems, the bank initiated a push to test, launch and roll out upgrades to improve its operational resilience.
Over a two-year period, the team placed “a heavy emphasis on improving the stability and reliability of the functions applications,” according to a case study seen by QA Financial.
That meant focusing on “improving monitoring and the reduction of low priority incidents,” many of which were draining time and attention but ultimately “added no value to the bank.”
The question soon became unavoidable: could modern SRE practices help reduce noise, automate toil, and embed reliability in a more structured way, despite the huge diversity of applications across the bank’s estate?
Eveline Oehrlich, Chief Research Officer at the DevOps Institute, described the situation clearly: “The team wanted to explore if they could apply SRE practices within the bank environment.”
Standard Chartered Bank chose not to begin with a top-down overhaul, Oehrlich said. Instead, it launched a pilot.
A small team of five ‘SRE evangelists’ was appointed and placed directly into different application teams.
According to the report, the pilot covered a diverse range of applications, representing different deployment models, vendor-hosted, on-premise, and SaaS, and varying levels of architectural complexity.
Rather than reinvent tooling, the evangelists adopted a pragmatic strategy. As the case study explained, the aim was to “build on the existing capabilities rather than starting from scratch.”
By using and enhancing existing tools, the SRE team could “augment, correlate and prioritie incidents,” sharply reducing the noise that overwhelmed operations teams.
Oehrlich highlighted the importance of this grounded strategy: “The approach was very much a ‘get things done’ attitude.”
Changing the culture
One of the most significant parts of the transformation was cultural. Standard Chartered Bank partnered with the DevOps Institute to create the “Functions T&I SRE Academy,” a programme combining structured internal learning modules with external SRE certification, supported by coaching and a 100-day application review cycle.
This was designed to help people step into new engineering-oriented roles. As Oehrlich noted: “The teams embraced the training and could see how a previous role as a support person could develop into an SRE Engineer.”
The SRE Academy stopped being a pilot initiative and was integrated into the bank’s broader learning platform, creating a formal career path. The report states that this shift meant that “SRE is basically self-seeding across the team.”
The SRE approach also changed how the bank planned for reliability. Instead of retrofitting monitoring just before go-live, the SRE teams began working with business stakeholders and delivery teams early in the lifecycle to define Service Level Objectives (SLOs) and Service Level Indicators (SLIs). These started at a high level, then evolved as teams became more confident.
“A previous role as a support person could develop into an SRE Engineer.”
– Eveline Oehrlich
The bank moved towards “observability by design,” ensuring visibility into performance and reliability metrics from the start of each project.
Dashboards gave the business real-time insight into operational health, helping teams understand when stability was at risk. As the report emphasises, this process “allows the business to understand when they get close to a potential error budget breach.”
This shift positioned reliability as a shared responsibility, not something delegated to operations as an afterthought.
Expansion
Since the pilot launched in 2019, SRE has increasingly shaped how the bank manages its applications. The initial evangelists now serve as advisors to teams across the Technology & Innovation organisation.
Standard Chartered Bank created a global SRE community of practice to share knowledge, align on best practices and embed consistent methodologies across the enterprise.
The bank also formalised SRE roles within its engineering career framework, offering foundation, practitioner and leader paths to support long-term skill development.
As Standard Chartered Bank moves further into cloud-centric architectures, SRE now participates earlier in design phases, ensuring supportability, observability and reliability are engineered into systems from the start, rather than patched on later.
For QA and software-testing leaders in financial services, Standard Chartered Bank’s shift to SRE may offer a clear lesson: reliability must be engineered, not inspected.
The bank demonstrated that SRE does not require rebuilding an entire tooling ecosystem. It can begin by enhancing what already exists, embedding reliability experts into delivery teams, and investing in structured learning supported by leadership and community.
COMING IN 2026
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
- Inside Rabobank: Engineering resilience by design
- Can AI agents finally automate data testing?
- Continuous testing drives DORA compliance
- Why software testing may face a major rethink
- Buy or build? AI rewrites software testing for banks
QA FINANCIAL PODCASTS
LISTEN TO OUR EXCLUSIVE CONVERSATIONS
WATCH NOW
