Health Catalyst logo

Health Catalyst Software Engineer Interview Questions
& Process

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

Based on 14 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Health Catalyst.

Showing 3 of 14
Health Catalyst logo
Health Catalyst

Software Engineer

Engineering · more than a year ago

Mid Difficult Negative experience No offer 1 round
Interview process
Take home
Interview formats
Technical

I had to complete a take-home assignment that took hours to finish. I really don't like take-home tests because they can be a huge waste of time. You put in all this effort, and the company puts in none. I've heard of people who applied and their projects were never even reviewed. My advice for other programmers: DON'T DO FREE INTERVIEWS LIKE THIS! Your time is too valuable to just give to a company. You're taking all the risk, and the company is taking none. Ask for payment. If they won't pay for your time, think about why. My honest advice is to look for jobs elsewhere. Unless you're certain you'll get the job, you might end up spending a lot of time on an interview for a role that might go to someone else.

Confirmed questions1 question
  • Can you design an ASP.net website?
Health Catalyst logo
Health Catalyst

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 5 rounds
Interview process
Phone screen Take home Onsite
Interview formats
Technical Coding Behavioral

So I started with a phone screen where they asked me why I wanted to change careers, why Health Catalyst, and what I knew about the company. Then, that same day, I got a coding assessment. I spent basically the whole weekend and part of Monday on it, putting in maybe 20 hours to make it really good. It was tough! A few days later, they invited me for an on-site. The on-site had three separate interviews, each about an hour long. Each interview had two interviewers who asked me coding problems, asked about my background, and other technical questions. They also left time for me to ask them questions. I liked all the interviewers; they were nice and didn't ask tricky questions. They seemed genuinely interested in getting to know me and my skills. They also did a good job of selling the company and confirming the positive culture I'd read about. I thought the coding example in the interviews was a bit easy, but there were good, challenging questions too. The whole process felt pretty fair, maybe even a little easy. I got an offer for Software Engineer and accepted.

Confirmed questions1 question
  • How do you keep yourself learning?
Health Catalyst logo
Health Catalyst

Software Developer

Engineering

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Panel Technical screen Onsite
Interview formats
Technical Coding Behavioral Presentation

So I interviewed with Health Catalyst for a Software Developer role. While I think it's a great company to work for, the interview process itself was kind of a letdown, mainly due to poor communication. It involved three main steps: first, a 30-minute phone call; second, a take-home coding assignment; and third, a panel interview via video where they went over coding and behavioral stuff. I heard back about a week after the phone screen and was told I'd proceed to the coding project. The project was to build a web API in .NET with a basic JavaScript front-end, and I had a week to finish it, with the expectation it would take about 10-20 hours. I managed to complete it well before the deadline, but then it went radio silent for almost three weeks, even after I emailed to check on it. Once I finally got the green light, I had the panel interview. The interviewers were good and answered my questions well, and the coding problems were reasonable. What really bugged me was the lack of feedback on the take-home project, and it felt like they hadn't even really looked at it, which isn't fair considering the effort involved. For anyone looking at this internship, I'd say: don't apply if this is your first dev job because it seems geared towards experienced people. Definitely know .NET and Angular, as there's no mention of formal mentoring, so you're expected to jump right in. Also, don't over-invest time in the take-home; if you can't do it in 10-15 hours, it might not be the right fit. Health Catalyst seems like a solid company, but I'd consider applying again later once I have more experience. It's a super competitive internship with few spots, so be sure you're qualified.

Confirmed questions6 questions
  • Could you tell me about the software design patterns you know?
  • Can you explain how to write an SQL query for joining two tables?
  • What experience do you have with the .NET framework?

Health Catalyst Software Engineer Interview Questions

Quoted word for word from Health Catalyst interview reports.

Can you create a web application using ASP.NET MVC that allows searching for people by their first and last names?

Read reports

Can you find all employees who report to the same manager?

Read report

Can you explain how to write an SQL query for joining two tables?

Read report

Formats, difficulty and experience

Across all 14 Health Catalyst interview reports.

Interview formats

Technical 40%
Coding 33.3%
Behavioral 16.7%
Presentation 3.3%
System Design 3.3%

Interview difficulty

Easy 14.3%
Average 71.4%
Difficult 14.3%

Candidate experience

Negative 42.9%
Neutral 14.3%
Positive 42.9%