How many rounds is the UBS Full Stack Engineer interview process?

Candidates report 2 stages: Online Assessment and Technical Interviews. The interview process section above breaks down what each stage covers.

What topics come up in the UBS Full Stack Engineer interview?

UBS Full Stack Engineer interviews most often cover Java, Binary search, Spring Boot, Microservices architecture, and Problem solving / DSA, based on topics extracted from real candidate reports.

UBSFull Stack Engineer

Updated Jul 23, 2025

UBS Full Stack Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Full Stack Engineer at UBS, newest first and distilled into what to expect across the loop.

Get your personalized UBS Full Stack Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Difficult Positive Hong Kong

I took an online assessment that ran for about 70 minutes. It included one DSA question plus a larger set of non-DSA questions—sixteen non-conding items alongside the coding piece. The time commitment and the mix of question types made the test feel substantial.

The DSA problem was about finding the common prefix for an array of strings, returning up to three words that share the prefix as the user types. The key requirement was efficiency, so I needed a binary search approach to keep the time complexity around O(log n). That made it feel more “algorithmic” than typical easy coding screens.

> 1 year

Difficult Negative Weehawken, NJ

My interview journey started with a strong technical first round. I was asked about Java 8 and 17 features, plus Spring Boot, Hibernate, and microservices. They also referenced an architecture diagram from my recent experience, and I felt good about how I explained it.

The second round was with a director, and it was a completely different vibe. The interviewer was knowledgeable, but the communication came across as condescending, and I often didn’t get clear feedback on whether my answers were correct. I did a deep dive into Java topics that I appreciated, but the design questions felt vague and broad, and when I asked clarifying questions the responses didn’t really help me understand what they expected. Even when something I said didn’t “add up” for them, I wasn’t given a smooth explanation.

Unlock every Full Stack Engineer interview experience

Real Full Stack Engineer interview experiences

Difficulty, sentiment and outcomes
New reports added every week

See all experiences

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.