University of Utah logo

University of Utah Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

2.1 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at University of Utah.

Showing 3 of 12
University of Utah logo
University of Utah

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

They have 2 rounds. The first round focuses on behavioral questions, possibly to assess if candidates are looking for a long-term internship until graduation and are in their second year of CS. The second round is a technical interview where they ask basic questions about SQL, OOP, and include a Leetcode challenge.

Confirmed questions3 questions
  • Basic SQL questions
  • Object-Oriented Programming questions
  • A Leetcode challenge
University of Utah logo
University of Utah

Software Developer

Engineering · a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Technical screen Onsite Group
Interview formats
Technical Coding Presentation Group

It started with a recorded interview where I had to answer some questions. Then the hiring manager reached out and we set up the next interview. In that one, I had to build Salesforce LWCs and an Apex class to show data, and they gave me some info about the job. The last interview involved me joining a regular planning meeting for the role, where I had to diagram the business flow in LucidChart and join the discussion. They said I'd hear about onboarding soon after. But the hiring manager ghosted me and then emailed the day after the expected call to say they changed their mind and weren't hiring me. Although the interviews were very hands-on, it felt like they were taking advantage of me for free work, making me build stuff and attend a planning meeting for an app I knew nothing about.

Confirmed questions1 question
  • Can you describe how you would build an LWC and an Apex class to fetch and display a list of student information?
University of Utah logo
University of Utah

Software Design Engineer

Engineering

Senior Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding Technical

The hiring process at the University of Utah took an unusually long time. It started with a recruiter calling me for an initial behavioral interview. Then, I had to complete a take-home coding test, followed by a technical panel interview. The whole process lacked transparency, and the team I interviewed with seemed very unprofessional. After waiting over 3 months for a response, the recruiter sent a vague email explaining why I wasn't selected. What's worse, they considered me for a Software Design Engineer-Senior role without even asking if I was interested, despite me not applying for it. They asked questions about Java, specifically multithreading, SQL, and Spring. If you have a lot of free time, you can apply, but be warned about the long wait and uncertain outcome.

Confirmed questions1 question
  • Can you tell me about multithreading in Java?

University of Utah Software Engineer Interview Questions

Quoted word for word from University of Utah interview reports.

Can you write a SQL query to get data from a RDBMS based on a given set of tables?

Read reports

How do you implement a Many to Many Association in Hibernate?

Read reports

Can you describe how you would build an LWC and an Apex class to fetch and display a list of student information?

Read report

How would you query data from tables in a hypothetical scenario?

Read report

Formats, difficulty and experience

Across all 12 University of Utah interview reports.

Interview formats

Technical 37%
Behavioral 33.3%
Coding 18.5%
System Design 3.7%
Presentation 3.7%

Interview difficulty

Easy 41.7%
Average 50%
Difficult 8.3%

Candidate experience

Positive 66.7%
Neutral 16.7%
Negative 16.7%