HealthStream Software Engineer Interview Questions
& Process

This was one of the most frustrating and pointless interview experiences I’ve had. After spending time preparing for and completing two rounds — including a technical interview — I was told the role was being "placed on hold indefinitely." Which is code for: "we’re wasting your time but won’t admit we never planned to hire anyone." If you value your time, avoid this company. The technical interview was nearly impossible to get through due to an extreme language barrier. The interviewer spoke with such a thick accent that I had to ask multiple times just to understand what he was saying, and even then, the communication felt one-sided and broken. It was clear he also struggled to understand me. When an interview is supposed to be about evaluating technical competence, basic mutual understanding is a minimum requirement. HealthStream failed that standard completely. The company appears heavily biased toward offshore or foreign candidates. There was no attempt to ensure clear communication or a fair playing field for domestic applicants. If you're an American developer expecting a straightforward, professional interview with fluent communication, you’ll likely be disappointed. This felt like they were going through the motions for compliance while quietly favoring imported labor, not actually looking to hire.

Got a phone call a few days after sending in my resume. Then, I guess because I didn't totally bomb that, they had me come in for some in-person interviews at their office a couple days later.

I applied online for a Senior Developer position and got an email from HR within a day or two. I called them up and we had a quick chat about my background, my reasons for wanting to relocate and switch to the healthcare industry. It was a nice conversation. Then, they sent me the official application along with a detailed questionnaire that had six questions. They weren't hard questions, but you needed to give detailed answers. It took me about two days to finish, mainly the application part. The recruiter sent my application to the Hiring Manager, and five days later I heard back. The Hiring Manager liked my questionnaire answers. I thought I'd get an in-person interview to discuss salary, relocation help, and daily tasks. Instead, I had to do a long technical exercise where I had to create a user authentication solution. It wasn't too difficult since I have a similar solution on my own website and could reuse some code. I finished it in 2-3 days, and I actually did way more than required. However, I couldn't complete the data model because I needed software only available on my work computer, and I couldn't justify using it for a quick turnaround and accurate result. The code solution was really detailed though, with comments explaining how the provider model worked. A week after that, the recruiter contacted me again. He said they were moving forward with other candidates. I think the main issues were my location (needing to relocate) and not submitting a data model. The code was definitely not the problem. Honestly, it felt like a PhD homework assignment. I should have asked about the salary range and relocation benefits upfront to avoid wasting my time on this exercise. I wouldn't have done it unless the pay was significantly higher than market rates. I'll definitely be asking about the full interview process for future healthcare industry jobs. Overall, I learned a lot from this experience.