Qualtrics

  www.qualtrics.com
Work in HR? Unlock Free Profile

Qualtrics Interview Questions & Reviews

Updated Jun 24, 2014
All Interviews Received Offers

Getting an Interview  

32%
29%
19%

Interview Experience  

52%
23%
23%

Interview Difficulty  

Average Difficulty
46 candidate interviews
Relevance Date Difficulty

No Offer

Positive Experience

Difficult Interview

Sales Representative (Entry Level) Interview

Sales Representative (Entry Level)

I applied through an employee referral and the process took 2 weeks - interviewed at Qualtrics.

Interview Details – My interview process only lasted two weeks. Mine started as a referral so once i sent in my Resume i got a call later that day to conduct a phone interview. Next, I came in to take a tour of their establishment, which following i was interviewed by a team lead, head of the Opportunity Sales Reps, and the Head of the VP Sales. After the interviews, I was told that i would know by the end of the week once they finished their meeting for the new hiring. It still is the beginning of the week so I don't know if i got the offer yet or not.

Interview Questions


Declined Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Provo, UT

I applied through a recruiter and the process took 3 weeks - interviewed at Qualtrics.

Interview Details – I was contacted on LinkedIn by their tech recruiter. I initially had no interest in moving to Utah but the company looked very interesting after researching it. Seems to be in that stage where its about to break through to be a world wide brand. Which is typically the best time to join a company. I responded and we set up a phone interview the next day.

Recruiter phone interview: The first interview was by phone and with their tech recruiter. We basically talked about my overall experience briefly and then about a specific project I worked on. He asked a lot of questions to dig deeper about specifics and why we made certain decisions in the project. We then spent 20-30min talking about Utah, different areas in the area, and relocation in general (I'm in DC). I was concerned about the "culture" of Utah and he did a really good job explaining his previous perceptions on the area and how most of them are exaggerated. We then scheduled a time to do another phone interview with an engineer 2 days later.

Engineer phone interview: The second interview was by phone with a team lead. We talked about my technical experience and familiarity with specific technologies. There were a handful of behavioral questions and high level technical questions. He said the recruiter would get back in touch with me shortly after. I got an email about 20min after the interview asking me how it went on my end and that they wanted to do a 3 hour video interview with me.

Video Interview: This part was a bit weird to get used to. The interview is actually a little over 3 hours long. It started with 5min with the Recruiter to get set up. Overall I met with 6 engineers in sets of 2 for roughly an hour each. The first group tended to focus on my OO and design skills. The second was around database and database design. This was tough because I'm not a dba guy. The third group focused on coding problems. We used a web interface called Collabedit which I liked better than white boarding. I got to pick my language of choice and solve their riddles. The majority of the hour was spent on one problem and then they would through in different angles to it and question your decision making. The recruiter came back in at the end and explained I would hear from him after the team had a chance to share feedback. He reached out the next day and said he wanted to fly me in. I worked with an assistant on the flight details.

On-site visit: I flew in the night before my interview and I was scheduled for 2 days. My hotel was in Park City, which is about 30 minutes away from the Salt Lake airport and over 45min away from the Qualtrics office. I thought that was weird but Ive always wanted to go to Park City. I just wished it was still snowing. I was picked up by the recruiter the next morning who drove me to the office. Apparently he and a handful of employees live there. At the office I got a tour. It is a really cool office with lots of open space, kitchens, couches, no offices, conference rooms are glass so you can see in, engineering has a whole floor for just engineers, and yes, the dog from the video is actually running around in the office. However he doesn't really like to be pet. I met with the CTO. We spent about an hour together going over my background and through architectural discussions. Through his questions I was asked a lot of probing questions on decisions and why I made them. This is the company culture check to find out if your a good or bad fit. I then spent some time in a demo from one of the teams which was really cool. The recruiter drove me through the Provo and Orem area, then we drove up to Salt Lake and around some of the areas he said are the popular areas. We had a beer at a cool place in downtown Salt Lake proving you can get beer in Utah (this was a selling point for me) much a block away from the mormon temple. We drove up to Park City and had dinner on main street with a few employees that live there. I felt wined and dined which made me feel like I did well in the interviews. I had the entire next day to explore on my own and was put in touch with a real estate agent if I wanted to see some places to get a feel for the area. I thought that was cool but decided to drive around and check out areas myself. Having never been to Utah, it is bigger than I thought and really pretty with the mountains bearing down on you. Though I heard air quality is a concern in the winter.

Offer: The recruiter told me I wouldn't hear till after the upcoming friday. Apparently all candidates they want to make an offer to go through an executive committee who has the opportunity to veto a candidate. He called me that next friday to discuss the details of the offer. Unfortunately, my wife vetoed relocation after she told me she is expecting with our first. With all our family in the DC area, it would be tough to make the move with a little one. I wish they had a DC office.

Interview Question – white elephant gift exchange where you can't give to the person who gave to you or to yourself.   Answer Question


No Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Software Engineer
Orem, UT

I applied through a recruiter and the process took 2 weeks - interviewed at Qualtrics in May 2014.

Interview Details – I was contacted by a recruiter through LinkedIn. I had heard about the company and had done some research. Having had read the reviews on here it sounded like a great place to work. As I was employeed at the time it took a little while to get time to interview. After coordinating with the recruiter I was able to take a 30 minute phone interview with an employee that had been there for years. He told me about what he did there and asked about my previous experience. Everything went really well. After which I scheduled an interview about a week and a half after the call. I was told that the interview process would take 3 hours.

The day of the interview, I arrived on time and was able to find the office fairly easily. After I had filled out an NDA I was informed that the recruiter was not there, but was busy attending to personal errands. So the first group of people that I was meeting with showed me around and took me up to a common area with a white board. This interview was about Database design and Optimization. And one of the first things they asked me was if I had been a DBA. Nowhere on my resume do those three letters appear in that order. I was a bit confused about where they would get that idea, but wasn't too concerned. At first they asked me to design a database to store information for a library. Which I though went alright, since I'm not a DBA. Then they started asking questions about scaling and data-warehousing and how my design would deal with X number items. I answered the questions to the best of my abilities, but not coming from a DBA background things could have gone better.

After spending an hour with this group, I met with the second group. This group was focused on programming. They explained that they would start with some simple questions and move on to more complicated questions. Their first problem was to find the first occurrence of a word in an array and to remove it using whatever language I preferred. This was a fairly simple problem and besides a few minor mistakes I felt like my solution was good. They were interested in seeing how I solved problems and that I could write code correctly on the white board. The second question was the same, but allowing for multi-dimensional arrays. For this I took a recursive approach re-using as much of the previous code as I could. In this instance I did really well. I noticed a few bugs before the interviewers and though I really nailed it. After these first two questions were answered they moved on to a different problem. The problem was to represent a cube and be able to determine if two cubes were the same. The cubes could have any number of colors associated with the faces. This problem was a little tougher, but eventually after trying a number of solutions we came to the agreement that my solution would be suffice. After this question there was a Q&A session between me and them. They explained what they do and answered any questions that I had about what they do there. I thought this part of the interview went really well.

On to the final group. This group was the API group. They asked me to design an elevator system from the ground up. Including an API with which to interact with the Database objects and some sample code to determine how to respond to a request from a button push. This part of the interview was a bit uncomfortable. I don't have a lot of experience with API development, but struggled though trying to solve this problem. One of the interviewers was really helpful and talked through a lot of the problems and discussed how to resolve the problems with me. The other interviewer probably said 5 words total and seemed like he was disinterested. Needless to say, this part of the interview didn't go great. It was a little awkward to be honest.

After this last part, I was supposed to meet with the recruiter. Who incidentally was still not present, so I sat around for about 10 minutes at which point the "Director of Technology" met with me briefly. He explained that at Qualtrics they didn't really believe in titles and we mostly talked about non-work related things. We also talked about what the company does and what he was in charge of and his job history. Overall this part of the interview was really chill and I'm still not exactly sure what the point of it was, but I enjoyed it.

Overall I thought the interview went fairly well. I was completely unimpressed with the recruiter who I never even met with, but was looking forward to hearing back within a few days. Needless to say the recruiter was once again a disappointment on this front. After a week I decided to email and ask what was going on which took a day and a half to get a generic 'No Thanks' email. I think this would be a great company to work for, but to this day I'm not even sure what position I was actually interviewing for or what the requirements are.

Interview Question – Design an elevator API including Database design using a whiteboard.   Answer Question


No Offer

Neutral Experience

Average Interview

Panels Sales Representative Interview

Panels Sales Representative

I applied through an employee referral and the process took 4 months - interviewed at Qualtrics.

Interview Details – Appeared to be an excellent company. I was very interested in working there initially and I had a few friends working there. When all was finished I had gone through 5 separate interviews. I was kept on the hook for over two more months. I don't feel like the HR department was very professional. Most of the people I interview with seemed very nice.

Interview Question – I was asked how many cubic liters it would take to fill the Grand Canyon, among other questions.   Answer Question


No Offer

Positive Experience

Average Interview

Marketing Interview

Marketing
Provo, UT

I applied online and the process took 2 days - interviewed at Qualtrics in May 2014.

Interview Details – At first arrival I was given a tour of the building and the departments. I was then put through a series of interviews with many different stakeholders. The process was fair and allowed for a good give and take. The people seemed intelligent and hard working the questions open and fairly standard. I liked the process and the people.

Interview Question – Asked to decipher a bit of code.   View Answer


No Offer

Neutral Experience

Average Interview

Product Specialist Interview

Product Specialist
Provo, UT

I applied online and the process took 1+ week - interviewed at Qualtrics in May 2014.

Interview Details – They first show you around their offices (which to their credit is a pretty cool office) and then sit you down for a first interview. Pretty typical questions asked regarding how you react to certain situations etc, then they have a second and third interview which are more technical and are done by senior management. They pretty much assume you want to work there and kind of treat you like you're an idiot if you don't want to work there because the "company is so awesome". The senior manager that interviewed me was a nerdier guy that didn't really have too much of people skills.

Interview Question – They'll ask you random "technical" questions such as sq. root of 19 or degrees of change on a clock.   Answer Question


Declined Offer

Neutral Experience

Average Interview

Junior Software Engineer Interview

Junior Software Engineer
Salt Lake City, UT

I applied online and the process took 5 days - interviewed at Qualtrics in May 2014.

Interview Details – Sent in resume and application after finding the posting online. Not more than 3-4 days after submission, i was contacted to complete a 45 minute phone interview. Very basic personality and interest based questions, then was asked skill questions pertaining to what skill set you had. Overall nothing surprising or out of the ordinary.

Interview Question – Asked questions about javascript and SQL   Answer Question


No Offer

Positive Experience

Average Interview

Renewal Billing Specialist Interview

Renewal Billing Specialist

Interviewed at Qualtrics

Interview Details – I found the listing for the job on the company's website. I submitted an application and was called the next morning and they asked if I could interview that afternoon. There were three interviews back-to-back, each lasting about half an hour. The company seems to have a really great culture.

Interview Question – What do you think this role entails?   Answer Question


Accepted Offer

Neutral Experience

Average Interview

Account Executive Interview

Account Executive
Provo, UT

I applied through an employee referral and the process took 2+ weeks - interviewed at Qualtrics in February 2013.

Interview Details – I was contacted on linkedin and then a phone interview was set up. I was living out of state so I did a skype interview. I met with several team leads and region leads before talking to the VP of Sales. I flew out, visited the office and then made my final decision.

Interview Question – All of the questions were pretty standard.   Answer Question


No Offer

Neutral Experience

Finance Manager Interview

Finance Manager

I applied through a recruiter and the process took a day - interviewed at Qualtrics.

Interview Details – They sought me out and after the interview called me within 20 minutes to say it wouldn't work.

Interview Question – They didn't have a specific role in mind, so understanding what they wanted was difficult.   Answer Question

Worked for Qualtrics? Contribute to the Community!

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.