Real, anonymous reports from people who interviewed for Software Engineer at A healthcare data, newest first and distilled into what to expect across the loop.
I started with a recruiter conversation that felt more like a fit check than an interrogation. We went over my interests and the projects I’d done, then they asked what technologies I knew and how I preferred to work. I also got the usual personality and behavioral questions—how I collaborated, how I handled teamwork, and how I behaved with colleagues.
My interview journey followed a pretty classic sequence: two technical-style rounds, then a manager round, and finally an HR touchpoint. In the first technical discussion, they focused on my core skills and what I could actually do—enough fundamentals to gauge whether my background matched the role.
The interview process typically begins with a recruiter conversation focused on fit, background, and basic technical skills, often including behavioral questions about teamwork and collaboration. Candidates noted that these initial interactions felt professional and structured, setting a positive tone for the subsequent stages.
Candidates experienced multiple technical interviews that varied in difficulty, often covering core programming skills, full-stack concepts, and real-world scenarios. The technical questions were generally relevant to the role, focusing on practical applications rather than abstract theory.
Later stages included discussions with managers that emphasized project experience and soft skills, along with HR conversations that covered salary expectations and company culture. These interactions were described as professional, with a focus on alignment between the candidate's background and the role's requirements.
Some candidates participated in an assessment center format, which involved group activities and presentations, but reported logistical issues and a lack of clear evaluation criteria. This format was seen as less effective for individual assessment compared to traditional interviews.
Candidates expressed frustration with communication delays and lack of follow-up after interviews, with some experiencing long waits for feedback or final decisions. Clear and timely communication was highlighted as a critical aspect that could improve the overall candidate experience.
The interview process was generally described as structured and coherent, though some candidates noted that the pacing could feel slow due to scheduling issues. While the interviews themselves were often straightforward, the overall timeline and coordination were areas for improvement.