I applied for a Software Engineer (SWE2) role at UiPath through the careers portal in mid-April 2026, and a recruiter reached out a few weeks later after my profile was shortlisted. My background going in was about 3 years and 10 months, and my recent work was backend-focused with Java and Spring Boot.
That was the extent of what I went through in this dataset—my experience record captured the application and the HR contact step, but it didn’t include the rest of the rounds, how the technical process ran, or whether I received an offer. Overall, it felt like the process had started, but I didn’t have visibility into the remainder from what was reported.
3 months ago
Average Positive Bengaluru
After getting through initial resume screening, I moved into a first round technical screen where I had to solve medium LeetCode-style problems in an hour. The interviewer also asked questions tied back to my resume before jumping into the coding.
A little later, I went through an assessment and live coding setup that felt noticeably more intense. The assessment included two problems over 90 minutes to test competitive programming fundamentals. Then I had a technical discussion where I talked through past projects and internship experience, followed by a live coding session on HackerRank with a Java challenge. It was a tough sequence, but the difficulty also felt consistent with a serious technical evaluation, and I ultimately received an offer from that process.
4 months ago
Difficult Positive Cluj-Napoca
My process for a Software Engineer role at UiPath came in four main rounds, and it stayed fairly technical from start to finish. First was a tech scre…
4 months ago
Difficult Negative Romania
My interview journey started with a recruiter approach and an initial chat, then about a week later I had a technical conversation with a VP. After th…
4 months ago
Average Negative London, England
I went into my UiPath interview expecting a collaborative design discussion, but it quickly felt off. Interviewers asked me to design a solution for a…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
The interview process typically consists of multiple rounds, often starting with a technical screen followed by coding, algorithms, system design, and behavioral interviews. Candidates should expect a thorough evaluation across various technical domains, with some reporting as many as five rounds.
Multiple roundsTechnical screeningSystem design
Technical Assessment & Coding Challenges
Candidates will face coding challenges primarily based on LeetCode-style problems, with varying levels of difficulty from medium to hard. Live coding sessions and assessments on platforms like HackerRank are common, emphasizing problem-solving and algorithmic skills.
LeetCodeLive codingAlgorithm challenges
System Design Interviews
System design interviews are a key component, where candidates must demonstrate their ability to architect solutions, discuss trade-offs, and explain their reasoning. These discussions often involve real-world scenarios relevant to the company's needs.
System designArchitectureTrade-offs
Behavioral & Cultural Fit
Behavioral interviews focus on candidates' past experiences, teamwork, and problem-solving approaches, assessing cultural fit and alignment with company values. Candidates should prepare to discuss their resume and past projects in detail.
The interview atmosphere can vary; some candidates report friendly and professional interactions, while others experienced discomfort or misalignment in expectations. Clear communication from interviewers is crucial for a positive experience.
CommunicationInterview atmosphereProfessionalism
Timeline & Feedback
Candidates often report delays in the interview process, with some experiencing ghosting or unclear timelines. Feedback can be inconsistent, and candidates should be prepared for potential long waits between rounds and decisions.