Xealth Software Engineer Interview Questions
& Process

First there was a take home coding challenge. Then a phone tech screen where we talked about Node express concepts based on the job description and did some medium coding problems. Finally, an onsite with 5 rounds: 3 technical rounds, each with 3-4 medium coding problems, mostly graph based, and 1-2 basic system design questions.

I interviewed in early 2021. The recruiter didn't even read my resume, just seemed to be following a script and firing off questions without much interest in my actual skills. He asked two questions that could have been answered if he'd just glanced at my resume. Plus, he really pushed for invasive details about my other interviews (names, size, location) and my past jobs (how would past employers/coworkers rate me?). I was hesitant at first, but he insisted on knowing names. When I asked about the company's future direction, he was standoffish and unsure. I get that it's an early stage, but I'd prefer questions relevant to the job, like experiences and behavioral ones, and maybe actually reading the resume.

It started with a recruiter chat, then a take-home coding challenge that was pretty tough but fun. After that, I had a video call with a senior engineer where we talked about algorithms, but it was a bit confusing since the recruiter said they wouldn't ask those kinds of questions. They were surprised I was local but still did the video screen. The on-site part was pretty standard: first, a chat with a product manager about the product, then an hour-long technical interview with algorithm questions and a whiteboard session. Lunch followed with two engineers where they talked about their work. Another technical round had more medium-difficulty LeetCode style questions. The final round was with the CTO, starting with coding questions and then a challenging system design problem. I didn't get to code it, but my difficulty explaining it quickly led to a rejection, especially since I didn't know Node.js. The CTO wanted to see strong CS fundamentals instead. Overall, the process felt a bit misleading, especially with the recruiter's comments about algorithms. It seems like different people in the company have different ideas about what the interviews are for. Also, the small details, like not validating parking after promising to, made the rejection harder.