UBS (Union Bank of Switzerland) Interview Experience | On-Campus
Interview Experience
UBS came to our campus to hire FTEs.The first test conducted on Hackerrank consisted on 30 MCQs on Java(OOPS concepts, Collection framework etc) and some questions on DSA,...
Full Details
UBS came to our campus to hire FTEs.The first test conducted on Hackerrank consisted on 30 MCQs on Java(OOPS concepts, Collection framework etc) and some questions on DSA, DBMS and Mental Ability problems along with a coding question. Coding Question- There is a huge circle of infinite radius. You can move either clockwise (represented by 'C') or anticlockwise (represented by 'A') or unknown (represented by '?'). User inputs an integer T representing the number of trials in the first line. Then the user inputs the combination of movement string in subsequent T lines like so: 1 AAAA?C You have to answer what was the maximum displacement assuming anything in place of the ?. In this case we can assume that ? is A and so the truck was at some point 5 positions away from the origin and so the output should be 5. They shortlisted 42 students from some 400 students. Interview- There are about 3 rounds.They might ask you to write some code on paper and discuss your projects with you in detail.They had asked other puzzles from other people as well.You may be asked to go through a psychometric test as well.By the time I was called for first round of interview people had already given three rounds and were done through HR(And still did not get the job for no reason) I was asked to find the sum first n prime numbers-Pen Paper code geeksforgeeks.org/sum-of-the-first-n-prime-numbers/ They discussed my projects and asked me if I had any questions for them. UBS selects a fixed number of students so you have very low chances of getting selected if you interview later as they forwarded people to further rounds without taking first round for all people in my college. However my interviewers were very friendly and it was a good experience overall. All the best :D
About This Question
This is a candidate experience report from a ubs interview for a swe role during the oa round reported in 2025.
It covers the following topics: Strings, Math, Backtracking .
Topics
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.