UBS Software Engineer interview typically runs 2 rounds: online assessment and technical/behavioral interview. Timeline is about 1-2 weeks, with a structured, role-specific process.
$127K
Avg. Base Comp
$161K
Avg. Total Comp
2-5
Typical Rounds
2-6 weeks
Process Length
We've seen UBS evaluate software engineers less like pure algorithm candidates and more like practitioners who can explain how they build, ship, and troubleshoot real systems. Multiple candidates reported that the strongest signal was not a clever trick answer, but whether they could walk through their own projects with confidence — from Terraform and CI/CD to Azure, AKS, React basics, and deployment choices. That lines up with a recurring theme in the experiences: resume credibility matters, and interviewers quickly probe whether the work listed on paper matches what you can defend live.
A second pattern is UBS’s preference for structured judgment over open-ended coding marathons. Our candidates report a mix of situational judgment, cognitive, and personality-style assessments alongside technical screens, and even the technical questions often stay grounded in practical decision-making: what database to choose, how to handle an error, or how to reason through a pipeline setup. The non-obvious part is that they seem to care a lot about clarity under constraints — especially in timed or rigid formats where you have little room to ramble. Candidates who did well were the ones who could stay precise, explain tradeoffs, and show they understood the why behind their choices, not just the syntax.
Synthesized from 3 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.
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
Describing a data project and its challenges
| Question | |
|---|---|
| Shortest Path Algorithms | |
| Decision Tree Evaluation | |
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| Statistically Significant Test | |
| Student Tests | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Bagging vs Boosting | |
| Random SQL Sample | |
| P-value to a Layman | |
| Size of Joins | |
| Cyclic Detection | |
| Three Zebras | |
| Target Indices | |
| Success Measurement | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Duplicate Rows | |
| Modifying a Billion Rows | |
| Type I and II Errors | |
| Same Characters | |
| Swap Variables | |
| Integer String Addition | |
| Employee Benefits Outreach | |
| The Longest Journey | |
| Triangle as Binary Array | |
| Drink Production Allocation | |
| Blob Indexing |
Synthesized from candidate reports. Individual experiences may vary.
Candidates first complete a HackerRank-style online assessment. Depending on the role, it may include Java and SQL or full-stack Java with React, along with numerical or pattern-recognition questions and situational personality/culture judgment items.
A rigid HireVue-style interview follows, with short preparation time and timed responses. Questions are mostly behavioral and situational, such as introducing yourself, explaining clean code, and discussing a technology topic in the news.
The next round is a live technical discussion, often over Teams or as part of an assessment center. Interviewers focus on low-level design, Java basics, Spring Boot, design patterns, computer science fundamentals, and a walkthrough of projects and resume experience.
Some candidates continue to an assessment center with multiple interviews, including a technical interview, a group case study, and one-on-one behavioral conversations. This stage can also include coding questions, logic or puzzle-style problem solving, and competency or statistics questions.
The final stage is a managerial or HR-style conversation focused on fit, working style, and broader engineering judgment. Candidates may be asked about their projects, debugging approach, performance optimization, accessibility testing, and basic frontend concepts like React props and state before a final decision is made.