GE HealthCare Software Engineer Interview Experiences 2026
Real, anonymous reports from people who interviewed for Software Engineer at GE HealthCare, newest first and distilled into what to expect across the loop.
Get your personalized GE HealthCare Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I went through a fairly compact technical conversation. It started with a quick sit-down where I talked about myself and then walked through projects from my resume. After that, I was moved into a whiteboarding/coding exercise, and the focus was on how I structure my thinking as I work through the problem rather than trying to hide behind buzzwords.
In both moments, the early part felt friendly and conversational, but once the coding started the tone tightened up. I remember discussing my previous role and what I personally contributed, then getting pulled into a DSA question (like working with a linked list) after some OOPs basics. Overall, it felt like a straight path to test practical understanding and communication while solving.
6 months ago
Average Negative France
My journey started with an HR interview remotely, and then I had a technical interview on-site. I remember that the early part centered on my CV and motivations, with questions that dug into past stages and projects. When it came time for the technical interview, it felt like they were trying to map my experience to the role in a fairly direct way.
After that, the process stalled hard. I was supposed to hear back about a week after the technical interview, but instead I ended up ghosted for more than a month. By the time I finally realized no update was coming, it made the whole thing feel poorly managed, especially because the interview itself hadn’t felt particularly hostile.
7 months ago
Average Negative Canada
My process started with a recruiter screen, then I quickly moved into two coding rounds. After that came a system design round, and finally a behavior…
7 months ago
Easy Neutral Paris
I had an interview that felt light on “exam” pressure and more focused on fit. I was brought in through a consulting agency, and the session started w…
9 months ago
Average Positive Seattle, WA
After an initial recruiter call, I had a technical screen where I was asked a medium LeetCode-style problem. A short time later, I moved into four mor…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter call, followed by a series of technical rounds that may include coding, system design, and behavioral interviews. Candidates reported varying timelines, with some experiencing delays in communication after their interviews.
Candidates faced multiple coding rounds that often included LeetCode-style problems, focusing on data structures and algorithms, as well as system design questions. The technical interviews were generally described as challenging but fair, emphasizing problem-solving and clear communication.
LeetCodeData structuresSystem design
Behavioral & Fit Interviews
Behavioral interviews were integrated throughout the process, focusing on candidates' past experiences, motivations, and cultural fit. These discussions were often conversational and aimed at understanding how candidates would align with the company's values and team dynamics.
Behavioral questionsCultural fitMotivations
Interview Atmosphere
The overall atmosphere of the interviews was described as supportive and collaborative, with interviewers encouraging candidates to articulate their thought processes. However, some candidates noted that the tone shifted to a more serious approach during technical assessments.
Supportive environmentCollaborativeTone shift
Communication & Feedback
Candidates expressed frustration over the lack of timely feedback and communication after interviews, with some reporting long waits or automated rejections without meaningful insights. This aspect significantly impacted their overall impression of the interview experience.
FeedbackCommunication issuesRejection
Preparation Insights
Candidates wished they had focused more on specific technical topics relevant to the role, such as advanced JavaScript concepts or system design principles. Preparing for a mix of coding and behavioral questions was also emphasized as crucial for success.