Ubs Software Engineer Interview Guide

The process was pretty straightforward, but it felt broader than a pure coding screen. I had two rounds in total. The first was a HackerRank-style technical test, and the exact content seemed to depend on the role. In my case, it covered Java plus SQL, and the other version I saw for the same process was full-stack Java with React. The questions weren’t especially deep algorithmically, but they did require careful reading and attention to detail. There was also a numerical/pattern-recognition section, so I had to slow down and actually observe each question instead of rushing through it. Alongside that, there was a personality-style assessment with scenario questions where you pick the most suitable action, plus a company culture/logical understanding test that felt very situational.

The second round was on Teams and was more technical discussion than coding challenge. They focused on low-level design implementation, and in another interview I saw for the same role, the conversation also included Java basics, Spring Boot, design patterns, computer science fundamentals, and a walkthrough of projects on the resume. My own questions were similar in spirit: self-introduction, why I chose my college, hobbies, what backend and frontend technologies I’d use, what database I’d pick, and how I’d handle an error if it occurred. The interviewers were two people, and the whole thing lasted about 30 minutes. Overall, the process felt more like a mix of technical screening and fit/culture checks than a heavy coding interview. I didn’t get an offer, and the most important takeaway for me was to prepare for role-specific technical basics, low-level design, and those situational judgment tests rather than only grinding algorithms.