Real, anonymous reports from people who interviewed for Software Engineer at A healthcare technology, newest first and distilled into what to expect across the loop.
My process landed on a difficult, technical-heavy set of rounds. After the initial steps, I ended up in a multi-round interview where the questions drilled into how frameworks and core Java/Spring features work. I was asked what Spring Boot annotations are commonly used for and why, and I had to explain my understanding clearly rather than just naming them.
I got far enough that I was being told I needed an HR discussion, but it was confusing because it sounded like it was mandatory to do it face to face in a specific location far from my hometown. I asked what the HR discussion round actually involved and what kinds of questions they planned to ask, since I didn’t have clarity on the purpose or format.
The interview process typically follows a structured sequence starting with an online screening, followed by technical assessments, and concluding with HR discussions. Candidates noted that the timeline could feel drawn out, especially in campus recruitment settings.
Candidates faced a variety of technical assessments focusing on core programming fundamentals, including Java, SQL, and data structures. The difficulty ranged from basic to challenging, with an emphasis on understanding concepts rather than rote memorization.
The HR discussions were generally supportive and focused on fit, strengths, and career goals, but candidates expressed a desire for clearer communication regarding the expectations and format of these rounds. Some found the HR process disorganized or lacking depth.
Interviews included practical coding questions and problem-solving scenarios that required candidates to demonstrate their reasoning and approach, often tied to real-world applications. This aspect was noted to be more challenging in later rounds.
Many candidates reported a friendly and supportive atmosphere during interviews, with interviewers providing feedback and engaging in discussions about the candidates' projects and experiences. This helped alleviate some pressure during technical evaluations.
Some candidates experienced logistical issues such as long wait times for interviews or unclear communication about the next steps, which detracted from the overall experience. These challenges were particularly noted in campus recruitment processes.