Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
UiPath interviews FAQs
Software Developer applicants have rated the interview process at UiPath with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 60% positive. To compare, the company-average is 62.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 27 days to get hired, when considering 25 user submitted interviews for this role. To compare, the hiring process at UiPath overall takes an average of 29 days.
Common stages of the interview process at UiPath as a Software Developer according to 25 Glassdoor interviews include:
Phone interview: 27%
One on one interview: 20%
Skills test: 16%
Background check: 10%
Presentation: 8%
IQ intelligence test: 6%
Personality test: 4%
Group panel interview: 4%
Other: 2%
Drug test: 2%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at UiPath (Bucharest, Bucuresti) in Feb 2026
Interview
The interview was nice. We discussed my CV, including my projects, future ideas, and passions. At the end, I was given a coding task where I had to identify mistakes in a Java multithreading scenario.
Positive experience
Average interview
Application
I applied online. I interviewed at UiPath (Bengaluru)
Interview
It was medium level LC Questions to be solved in one hour which was the first round after direct resume screening, interviewer also asked some questions based on resume before starting
Interview questions [1]
Question 1
Find min element in rotated sorted array and nearest greater element
The recruiter was very responsive and helpful. The coding screening was conducted through a website, without any live interaction. While the question itself wasn’t particularly difficult, the amount of code required to solve it was too much for a 30-minute timed interview (100+ lines of code), especially without anyone available to clarify the problem.