Dbs Bank Data Analyst Interview Guide

Our candidates report that DBS Bank is looking for more than someone who can pull numbers and explain a dashboard. In the retail lending and credit-risk conversations, the strongest signal was comfort with unsecured-product mechanics: origination, channel differences, underwriting logic, company categorization, fraud detection, and how those pieces affect portfolio outcomes. We’ve also seen repeated emphasis on core risk metrics like ECL, resolution analysis, GNS rate, delinquency movement, and TTD, which tells us the team wants analysts who can connect operational behavior to portfolio risk rather than treat these as isolated definitions.

A recurring theme is the expectation that candidates can move from business context into data extraction without losing the thread. One candidate was specifically asked about retrieving warehouse data for portfolio-risk analysis, which suggests DBS values analysts who can translate a risk question into the right data pull and then interpret the result with judgment. In our experience, that combination matters more here than polished theory alone: the interview rewards people who can explain why a metric moves, not just how to calculate it.

We also see a practical, execution-oriented bar in the more technical experiences. Even when the role was junior, candidates were still pressed on foundational coding and system understanding, not just domain knowledge. That mix is telling: DBS seems to favor analysts who are steady under technical scrutiny and can handle both structured problem-solving and the business nuance of credit risk. If there’s one non-obvious differentiator, it’s being able to speak fluently about risk while staying precise about the data behind it.