uTest logo

uTest Interview Questions
& Process

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

Based on 18 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
61.1% Positive experience

Which role are you interviewing for?

9 roles · 18 reports

Candidate interview experiences

First-hand accounts from people who interviewed at uTest.

Showing 4 of 18
uTest logo
uTest

Senior Java Developer

Engineering · more than a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Take home Background check
Interview formats
Behavioral Technical Coding

Got contacted by a top manager on LinkedIn. We exchanged emails, and I asked about H1B sponsorship. The manager confirmed they are committed to sponsoring. Had an initial Skype interview about my background. I reconfirmed visa sponsorship twice, and they said yes. Then, another Skype interview with a Java developer, purely technical, covering basic coding, algorithms, and Big O. Passed that, and received a substantial take-home task involving data structures, data access, and text search. It took about half a day. Afterward, the manager said he needed to check with legal about the visa. I followed up for two months every 10-12 days, and the answer was always 'still checking'. Finally, after two months, the manager informed me they could not sponsor the visa. I'm questioning the professionalism of the managers at uTest.

Confirmed questions4 questions
  • Tell me about your background.
  • Could you answer some standard Java questions?
  • Could you answer some algorithm questions?
uTest logo
uTest

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Onsite Technical screen Panel
Interview formats
Technical Coding Behavioral

I found the job on LinkedIn and the HR reached out to me about a week later. First, I had a phone screen with the VP of Engineering over Skype. Then, I was invited to come in for an on-site meeting with the team, which went well. I was supposed to have three 1-on-1 interviews with a Software Architect, a Senior Software Engineer, and the CTO. The first two interviews were standard technical ones where I had to do whiteboarding and some algorithm problems in Java, and they also asked SQL questions. The people interviewing me were nice and knew their stuff; after I finished writing my answers on the board, they gave me some really helpful technical tips. The last interview was different and pretty cool. They didn't ask any specific technical questions, but it did cover a lot of different aspects of what it's like to work as a Software Engineer.

Confirmed questions1 question
  • Did they ask any tricky algorithm questions?
uTest logo
uTest

Software Engineer

Engineering

Entry Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral

So I'm a new grad with a Master's in computer engineering and under a year of experience. After a nice phone screen, I went in for an on-site interview. It was basically 5 back-to-back interviews with tech leads and managers, almost 3 hours total. They had me do some whiteboarding, some paper work, and just talk through my answers. I felt pretty good about the technical stuff, but one interviewer didn't get my hash map solution, which is apparently what Amazon uses for the same problem. The third interviewer, who was the solutions architect, was really weird. He kept laughing and saying "I don't know" and shrugging. I think he'd already decided he didn't want juniors, and the product manager later confirmed he didn't give me a shot. The last two went fine though, and I think I left a good impression. Then I got this email with a misspelled name saying I had no Java knowledge or anything else, which is totally not true. It was weird because it was the same manager from the phone screen. I liked most of the engineers I met, but I guess you can't judge a book by its cover. I got the feeling they're biased and maybe being female didn't help since they were all guys. I wouldn't recommend interviewing here unless you have no other choice. The office was kind of depressing and boring, and I felt like I would have outgrown it fast anyway. But it's okay, I got a great offer from my dream company a couple weeks later.

Confirmed questions2 questions
  • Can you tell me about general algorithms?
  • Do you know Java?
uTest logo
uTest

Project Manager

Operations

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

Getting the first interview took days and lots of emails to get a response after the initial contact. After that, it was pretty smooth with a number of interviews, nothing unusual. But after all the interviews, I didn't even get a 'thanks for applying' or 'we're moving on with other candidates.' Just complete silence. It feels disrespectful.

Confirmed questions1 question
  • What are some typical Project Manager questions?

uTest Interview Questions

Quoted word for word from uTest interview reports.

What strategic changes would you propose to our go-to-market approach?

Read report

Formats, difficulty and experience

Across all 18 uTest interview reports.

Interview formats

Behavioral 41.4%
Technical 37.9%
Coding 13.8%
Other 3.4%
Presentation 3.4%

Interview difficulty

Easy 22.2%
Average 66.7%
Difficult 11.1%

Candidate experience

Neutral 22.2%
Positive 61.1%
Negative 16.7%

Reports by job function

Engineering 15
Sales 2
Operations 1