OneTrust logo

OneTrust Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 37 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
54.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at OneTrust.

Showing 3 of 37
OneTrust logo
OneTrust

Software Engineer Intern

Engineering · half a year ago

Intern Average Positive experience Accept offer 2 rounds
Interview process
Onsite Panel
Interview formats
Technical Coding System Design Behavioral Presentation

There was an in-person interview where I was asked some basic technical design and algorithms questions. After that, I had a panel interview with 3 engineers. This part included questions about my background and relevant experience, some logic and algorithm puzzles, and whiteboarding a prototype design.

Confirmed questions1 question
  • Can you design a system similar to tinyurl?
OneTrust logo
OneTrust

Principal Software Engineer

Engineering

Staff Average Negative experience No offer 8 rounds
Interview process
Recruiter call Technical screen Technical screen Background check Background check Background check Background check Offer
Interview formats
Coding Technical Technical Behavioral Technical Technical Technical Technical

So, I really think you should not waste your time interviewing with this company, the technical team there, they don't really respect you or your time. The first step was a recruiter call, and I have to say, I really recommend this recruiter, she was so helpful, humble, and respected my time, and always gave me feedback and kept me updated. The first technical round was 45 minutes, it was a medium Leetcode problem on HackerRank and questions about Java basics, Spring, Microservices, and databases. After that, I had three more rounds scheduled for one day, for three hours straight. The interviewer in the second technical round asked me a question and gave me some restrictions. I answered based on the restrictions, but at the end, he said he was actually expecting an answer that included parts of those restrictions. When I asked him about the restriction, he just apologized, said he misspelled it, and gave a negative feedback. The other two rounds were great and went well. Then, my recruiter told me that I was supposed to have a Business Critical and Cultural Fit interview earlier, but due to some miscommunication, they were all scheduled as technical interviews. I agreed to do them again. The first interviewer for this round joined 15 minutes late and asked me which technical round it was (screening or second round). After I explained my situation, he started with a technical screening again. He seemed completely unprepared and showed me a logical description, asking me to explain it. He didn't even try to listen to what I was saying and asked me to repeat myself a couple of times, saying he didn't follow. This happened for a few questions. After 15 minutes, he abruptly ended the interview while I was still explaining an answer. This call was supposed to be 45 minutes, but he was only there for 15 minutes, and he didn't even turn on his camera. It was a huge humiliation. The next round was again a good one, and I really liked the interviewer's maturity. Overall, I'd say the junior technical team is very immature and lacks direction. Seriously, don't waste your time interviewing with them.

Confirmed questions8 questions
  • Could you solve a Leetcode medium program?
  • Can you explain the basics of Java?
  • Tell me about Spring.
OneTrust logo
OneTrust

Software Engineer

Engineering

Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Technical screen Offer
Interview formats
Technical Technical

The interview process had 2 tech rounds, which I thought were good and quite challenging. The HR person initially said I'd get an offer, but a few days later, I was told no offer would be extended because they had reached their headcount. This felt like an excuse since I saw new job postings from them. Regardless of the real reason, they should have been upfront. So, the process was long, the interview experience itself was good, and the HR person seemed nice, but maybe only seemed that way. The overall experience was negative, reinforcing the idea of always having multiple offers. It's frustrating when organizations like this impact everyone else.

Confirmed questions4 questions
  • Can you explain Java concepts?
  • Tell me about Java Collections.
  • What do you know about Spring Security?

OneTrust Software Engineer Interview Questions

Quoted word for word from OneTrust interview reports.

Given a string like 'aaabbcccdeff', what is the output if we count the characters?

Read reports

What is the difference between List and other collections?

Read report

How would you find the sum of the upper, lower, left, and right parts of a 2D array, specifically excluding the forward and backward diagonals?

Read report

How would you convert Class components to Function components?

Read report

Formats, difficulty and experience

Across all 37 OneTrust interview reports.

Interview formats

Technical 42.6%
Coding 26.7%
Behavioral 23.8%
System Design 5.9%
Presentation 1%

Interview difficulty

Easy 5.4%
Average 78.4%
Difficult 16.2%

Candidate experience

Positive 54.1%
Neutral 21.6%
Negative 24.3%