Real, anonymous reports from people who interviewed for Software Engineer at OneTrust, newest first and distilled into what to expect across the loop.
My process started promisingly, but it quickly became clear that coordination and expectations weren’t as consistent as I wanted. I attended an in-person round with technical design and algorithm-style questions, and then it moved into a panel format with multiple engineers. The panel included background and relevant experience discussion, logic and algorithm puzzles, and a whiteboard session focused on designing a prototype.
After I applied, the process started with a preliminary test meant to check technical knowledge and problem-solving. Once I cleared that, a recruiter call kicked things off, and then the interview loop unfolded with a mix of technical and people-focused conversations. I ended up going through multiple rounds over a relatively smooth process, with scheduling and coordination that felt organized rather than chaotic.
The interview process typically starts with a recruiter screening followed by multiple technical rounds, often including coding assessments and design discussions. Candidates noted variations in structure, with some experiencing unexpected shifts in focus during interviews.
Candidates faced a mix of coding challenges, algorithm questions, and system design tasks, with a strong emphasis on data structures and foundational programming skills. Some reported a focus on practical coding skills rather than theoretical knowledge.
Behavioral interviews were included to assess candidates' past experiences and fit with company culture, often involving discussions about previous work and problem-solving approaches. The effectiveness of these interviews varied, with some candidates feeling they were not adequately evaluated.
Candidates reported mixed experiences with communication throughout the process, including delays in feedback and unclear closure after interviews. Some expressed frustration over a lack of transparency and timely updates regarding their application status.
The difficulty of interviews varied, with some candidates feeling pressure from challenging questions and a competitive atmosphere, while others found the experience manageable and straightforward. Preparation for coding and logical reasoning was emphasized.
Candidates noted discrepancies between what was communicated about the interview process and what they experienced, leading to feelings of unease regarding the overall professionalism and organization of the interviews.