Software Engineer applicants have rated the interview process at UBS with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 49% positive. To compare, the company-average is 62.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 25 days to get hired, when considering 53 user submitted interviews for this role. To compare, the hiring process at UBS overall takes an average of 26 days.
Common stages of the interview process at UBS as a Software Engineer according to 53 Glassdoor interviews include:
One on one interview: 22%
Phone interview: 19%
Skills test: 17%
Group panel interview: 13%
Presentation: 10%
Background check: 7%
Personality test: 4%
IQ intelligence test: 3%
Drug test: 3%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 6 weeks. I interviewed at UBS (London, England) in Mar 2024
Interview
Slightly disorganised process over many weeks. I had two stages, knowledge screen then hackerrank. The latter was pretty easy but i got a rejection several weeks later. Still not clear what they were looking for
I joined for a junior role and the interview process was very straightforward. First step was filling some online forms about general fit. Then a technical interview over Teams - no live coding was involved, only questions about my past experience, the technologies I worked with and how I would solve problem xyz. After that it's straight to manager interview and decision.
Interview questions [1]
Question 1
Give a detailed overview of how you would design a pipeline for streaming large amounts of data and reduce the risk of throttling or failure.
Made it to 3rd round.
1st round -> Aptitude Assessment
2nd round -> Hirevue
3rd round -> Mob Programming
Didnt make it past the mob programming session, (mob programming includes a group coding session where you and two other candidates work together to solve a problem)
Group interview with 2 other people. They give us a problem, allow us 15 minutes of prep time, then each will sequentially get access to a keyboard to code for 10 minutes. After the code, each person is asked about what went well and what could be better