UBS Software Engineer interviews typically combine an online assessment, one or two resume-driven technical rounds, and an HR or behavioral conversation, with content ranging from Java, SQL, and DevOps tooling to medium-level coding problems and low-level design depending on the track.
$118K
Avg. Base Comp
$145K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Across these reports, UBS Software Engineer interviews tend to be experience-driven and focused on fundamentals rather than obscure algorithm tricks. Several candidates started with an online assessment, often HackerRank-style. It mixed role-specific technical questions (Java and SQL, or full-stack Java with React) with numerical or pattern-recognition items and situational-judgment scenarios. One internship candidate also had a recorded video round with about a minute to think and two minutes to answer each prompt, with no redo. Candidates who moved forward describe technical rounds that lean heavily on your resume. Interviewers asked people to walk through past projects and defend their choices. That ranged from Terraform and CI/CD pipelines written live on a shared screen to Selenium, API testing, and TestNG/JUnit for an automation-focused role. Other reported topics include low-level design, Spring Boot and Java basics, OOP versus functional programming, database normalization and schema design, React props and state, and a linked-list coding problem. One graduate candidate was also given a loosely framed parking-space allotment design prompt, so ask clarifying questions when a problem isn't labeled. A behavioral or HR conversation, sometimes with several interviewers on the call, typically closes the loop and covers fit and growth potential. Preparation should flex by track, since intern, graduate, full-stack, DevOps, and automation roles all appear here. Across all of them, being able to explain your own work in depth is the most consistent theme. One candidate also received no feedback after the technical round despite following up, so it helps to set your own timeline expectations.
Synthesized from 23 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Ubs process.
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.
Prep tip from this candidate
Be ready for a HackerRank-style screen that can shift between Java+SQL and full-stack Java+React, and don’t ignore the numerical/pattern-recognition and situational judgment sections. For the Teams round, review Java basics, Spring Boot, design patterns, and be able to explain a low-level design approach plus the technologies and database you’d choose for a simple backend/frontend setup.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Ubs
How would you evaluate whether a decision tree is the right model and assess its performance before and after deployment
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Shortest Path Algorithms | |
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| Student Tests | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Random SQL Sample | |
| Bagging vs Boosting | |
| Size of Joins | |
| P-value to a Layman | |
| Duplicate Rows | |
| Type-ahead Search | |
| Type I and II Errors | |
| Justify a Neural Network | |
| International e-Commerce Warehouse | |
| Unified Inbox | |
| Cyclic Detection | |
| Three Zebras | |
| Precision and Recall | |
| Swap Variables | |
| Success Measurement | |
| Target Indices | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Client Solution Pushback | |
| Modifying a Billion Rows | |
| Same Characters |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report starting with an online assessment, often HackerRank-style, that combines role-specific technical questions with numerical, pattern-recognition, or situational-judgment sections. Technical content included Java and SQL, or data structures and algorithms at an easy-to-medium level. One internship candidate also completed a cognitive test and a recorded video interview with about one minute to think and two minutes to answer each prompt.
Candidates describe technical rounds centered on walking through their resume and past projects, with follow-up questions testing whether they understand the tools and decisions behind their work. Depending on the track, this included writing a CI/CD pipeline live (Terraform, Azure/AKS), Java and Spring Boot basics, Selenium and API testing, SQL, OOP versus functional programming, database normalization, or React props and state.
Some candidates encountered design or scenario-style prompts that weren't always labeled as such. Examples include a parking-space allotment system, low-level design implementation, choosing a backend/frontend stack and database, and explaining how you'd handle an error. These prompts reward clarifying questions and clear trade-off reasoning.
The loop typically closes with a managerial, behavioral, or HR conversation, sometimes with multiple interviewers on one call. Reported questions include self-introductions, why you chose your college, hobbies, fit, and growth potential. One candidate had a 1.5-hour combined technical and managerial round, and another never received feedback afterward despite following up.
