UBS - IT Software Engineer Interview Experience
Interview Experience
I recently interviewed with UBS in June1st round was an online round held on hackerrank it consists of coding and MCQ questions on core subjects like OS, DS, etc.2nd round...
Full Details
I recently interviewed with UBS in June 1st round was an online round held on hackerrank it consists of coding and MCQ questions on core subjects like OS, DS, etc. 2nd round they again gave coding on hackerrank and further shortlisted 3rd round 1st technical interview I was asked oops concept and little more questions on java then some DBMS question and was asked to explain my project in detail the interviewer was quite polite 4th round 2nd Technical interview I was again asked detailed explanation of my project then some questions on cloud computing and other questions on why UBS After all this, I qualified for HR and HR said you will have Mumbai as the location of joining and took my documents. But alas haven't sent an offer letter yet and to my other friend offered the role of IT support.
More Ubs Interview Questions
About Ubs Interview Reports
This question was reported by a candidate who interviewed at Ubs. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Ubs are the higher-signal extractions to take from this report.
For broader preparation context, the Ubs interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Ubs reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Ubs Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Ubs reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.