Company OAsAll ProblemsPlacement DataInterview ExperiencesPremium
OAHelper

Built by students, for students - practice company-specific OAs, DSA sheets, and real interview experiences to land your dream role.

© 2026 OAHelper.in·Terms·Privacy·Refunds·Trust & Safety·Contact·
Ready to crack your next OA?

Practice company-specific questions trusted by thousands of students across India.

Start PracticingGo Premium
OA Practice·DSA·Placements

Disclaimer: OAHelper is an independent educational platform. We (oahelper.in) do not own the images or questions shown. Content is uploaded by users.

U

Ubs

SDE

Interview Date

28-07-2026

Result

Rejected

Difficulty

Easy

Rounds

03

Drive Type

On-Campus

Interview Date

28-07-2026

Result

Rejected

Difficulty

Easy

Rounds

03

Drive Type

On-Campus

Topics asked

Group problem-solving and system designfraud detectionDSANetworkingOSpseudocodedebugging

Detailed experience

The process consisted of a company presentation, group coding/ideation round, pen-paper MCQ test, technical interview and HR round. In the group round, the team was given a fraud detection problem for UBS with a small dataset and an existing rule-based detection system. The team had to propose an improved solution within a limited time and present it. I focused on preparing the PPT and system design while my teammates worked on the coding. During the round, UBS employees also questioned our approach and the reasoning behind our technical decisions. The MCQ/pen-paper round tested basic DSA, Networking, OS, pseudocode, debugging, situational problem-solving and general logical thinking. The questions focused more on problem-solving and approach rather than syntax-heavy DSA. After the test, we were given additional time to refine our presentation before presenting the fraud-detection solution to the UBS panel. The technical interview was largely based on my resume and was particularly focused on my areas of interest. Questions moved from my hackathon project to Docker, Kubernetes, Linux, cloud concepts and the use of AI, including where AI should and should not be used. I was also given a situational debugging question involving an API endpoint that was not responding correctly. The interviewer was interested not only in technical knowledge but also in how I would reason and make decisions as a developer. The interview was relatively smooth, and knowing the resume honestly and being able to explain technical decisions was important. Not selected for Hr round.

Posted on - 24 Aug 2026