Sbi Interview Questions (2026)
3 questions · GeeksforGeeks (3)
Top topics
SBI Interview Experience for Data Scientist
Question Details
SBI Data Scientist Manager/Deputy Manager post was held on 7/8th Dec 2020 for around 11 posts. Interviews are based through video conference in multiple cities (Mumbai, Bangalore, Delhi, Patna, etc). Interviews are done in slots means even if the time written on your invitation letter is 12:00 PM then there is the possibility that your turn will come at 3.00 PM. At this time they will call you one by one for document verification (Please be prepared with all the documents listed in bio-data form). Interview Preparation Tips: Nothing to carry in the interview room (No file, No resume). They will give you one bio-data form you need to fill that form and all the questions will come from that only. Important fields to fill in the form (questions will come from this only): Qualification, Experience, Achievements, and Hobbies. Interview Details: Location: Bangalore(SBI LHO office) Date: 7th DEC 2020 Duration: 20 min Panel Members: 5 Questions: You belong to which place(native /are you ok with Mumbai location as it's only for Mumbai location. Tell us your experience in XYZ company and why you left your previous company Questions related to project & resume? How would you create 3d graphs and the difference between seaborn and matplotlib ? What is a box plot and how do you treat outliers? Some more basics question on ml /deep learning and python Why SBI?
Topics
More from Sbi
Related companies
Sbi Interview Process Overview
The Sbi interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Sbi runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Sbi coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Sbi Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Sbi updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Sbi reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Sbi's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Sbi Interview Mistakes
Reports tagged "no hire" at Sbi consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.