Vizient logo

Vizient Software Engineer Interview Questions
& Process

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

Based on 21 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
47.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Vizient.

Showing 3 of 21
Vizient logo
Vizient

Senior Software Engineer

Engineering · more than a year ago

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

I applied and the whole thing took about two weeks, fitting it around our schedules. First, I chatted with two folks who seemed like managers or architects; they mostly asked about my past work and how apps get set up and deployed. Then, I had a session with 4 team members who also asked about my experience, and after that, there was a coding challenge where I had to do CRUD operations and sorting in an MVC app using Angular 13 for the frontend and C# for the backend.

Confirmed questions4 questions
  • Can you explain the difference between Observables and Promises?
  • Could you walk me through the Oauth2.0 flow?
  • What are the steps involved in setting up a Spring Boot application?
Vizient logo
Vizient

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Panel Panel
Interview formats
Behavioral Technical Coding

Was not a good experience. Had 2 phone interviews, then a panel interview, then a technical interview, and then another panel interview. So, 5 interviews in total that took about 4-5 hours. After that, they sent me the benefits PDF and kept in touch via text for about 2-3 weeks, saying the team was meeting to make a final decision that week. I stopped reaching out after 3 weeks and never heard back until the auto rejection email came about a month later. Found a great job shortly after, and honestly, I'm glad I didn't end up with them. Who knows what it's like to work there if this is how they treat people applying!

Confirmed questions3 questions
  • Tell me about yourself.
  • Solve this coding problem.
  • What would your entrance music be if you had a wrestling theme song?
Vizient logo
Vizient

Software Engineer

Engineering

Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Phone screen Offer
Interview formats
Coding Behavioral

I got a call back from HR pretty quick, like within a week. After they did a quick screening, they just told me to come in for an inperson interview, no phone tech screening first. I checked Glassdoor and saw some questions from another user, so I prepped for those (fibonacci and employee hierarchy). I was supposed to meet 3 directors but only 2 showed up, and they were a bit late. The questions were exactly what I saw online, and I guess they liked my answers. Two days later, I had a phone call with the VP of Application Development. He asked more behavioral questions about leadership and goals. I got the offer about two weeks after that.

Confirmed questions2 questions
  • Can you write code to show all Fibonacci numbers below 100?
  • How would you solve the employee hierarchy problem?

Vizient Software Engineer Interview Questions

Quoted word for word from Vizient interview reports.

Write code to print all numbers from 0 to 100 that are divisible by 2.

Read reports

What is the result of the SQL statement: SELECT Case when null = null Then true else false end?

Read reports

Can you print the Fibonacci sequence up to a given number?

Read reports

Can you write code to show all Fibonacci numbers below 100?

Read report

What would your entrance music be if you had a wrestling theme song?

Read report

What are the steps involved in setting up a Spring Boot application?

Read report

Formats, difficulty and experience

Across all 21 Vizient interview reports.

Interview formats

Technical 36.5%
Behavioral 30.8%
Coding 26.9%
System Design 1.9%
Presentation 1.9%

Interview difficulty

Easy 19%
Average 71.4%
Difficult 9.5%

Candidate experience

Neutral 28.6%
Negative 23.8%
Positive 47.6%