Real, anonymous reports from people who interviewed for Software Engineer at Siemens Healthineers, newest first and distilled into what to expect across the loop.
After a recruiter call to schedule everything, I went into a two-round virtual process. The first technical round felt very focused on applied knowledge: we talked through OOPS, .NET Core, and design patterns, and then I had to handle a couple of programming questions. One was about a stack, and another was more implementation-focused—swapping two variables without using a third one. I was trying to go step by step and stay practical since the round felt geared toward real engineering work.
My process started with a technical discussion, then moved quickly into coding-focused rounds and eventually a manager conversation. Each technical round lasted about an hour, and everything felt like it was trying to measure how I think, how I communicate, and whether I can produce clean, well-structured code under realistic time pressure. The coding parts were genuinely enjoyable for me since I like solving hard problems, and I spent a lot of time making my solutions readable and logically tight rather than just “getting it to pass.”
Candidates can expect multiple technical rounds focusing on applied knowledge, including OOP concepts, design patterns, and practical coding problems. The interviews assess both problem-solving skills and the ability to communicate technical reasoning clearly.
One of the later rounds may involve discussing architecture concepts, including UML diagrams and Kubernetes, which can be challenging due to time constraints. Candidates should prepare to explain their design choices and implementation strategies under pressure.
Expect a managerial round focused on fit and collaboration, followed by an HR conversation that covers logistics and compensation. These rounds assess how well candidates align with team dynamics and company culture.
The interview process often begins with an online assessment that includes coding and multiple-choice questions on core computer science fundamentals. Candidates should be prepared for a rigorous evaluation of their foundational knowledge.
Overall, candidates report a structured and professional interview environment, with interviewers aiming to create a supportive atmosphere. However, some candidates experienced pressure and mismatched expectations regarding the technical bar.
Candidates often leave interviews without clear feedback or understanding of their performance, which can be frustrating. It's common for candidates to feel that the process lacks closure, regardless of whether they receive an offer.