Ge Healthcare

GE HealthCare visited our college for its Software Engineer Intern hiring process. I applied through the campus recruitment drive and was shortlisted for the initial assessment. The process mainly tested aptitude, technical fundamentals, programming and projects. Compared with some of the DSA-heavy product company interviews, this process had a fairly balanced combination of technical and general questions. Resume Shortlisting The first stage was resume shortlisting. GE HealthCare shortlisted candidates based on their academic profile and resume. The resume was important because the technical interview later focused significantly on the projects and technologies mentioned on it. I made sure I was comfortable explaining everything I had included, especially the technologies I had personally worked with. After the shortlist was announced, we received the online assessment details. Online Assessment The first actual test was an online assessment consisting of 50 questions. It was divided into three major sections: English Usage Analytical Reasoning Quantitative Aptitude The English section tested grammar, vocabulary and comprehension. The analytical section included logical reasoning, puzzles and data interpretation, while the quantitative section covered basic mathematical and numerical concepts. The questions themselves were not extremely difficult, but the number of questions made time management important. I tried not to spend too much time on any individual question and moved on whenever I felt that a question was taking too long. After the assessment, around 30 candidates were shortlisted for the personal interview. Technical Interview The technical interview lasted around 40–45 minutes. The interviewer started with the usual introduction and then asked me to explain my projects. I discussed the main projects on my resume, including the problem I was trying to solve, the technologies I had used and the challenges I faced while building them. The interviewer did not simply stop at the project description. He picked specific features from the projects and asked how I had implemented them. One interesting part of the discussion came from my resume itself. The interviewer noticed an issue with one of the links on my resume and asked me about the error. This led to a discussion about web development and how HTTP errors are handled. I was asked about different HTTP status codes and what happens when a requested resource cannot be found. We also discussed the difference between PUT and PATCH. I explained that PUT is generally used to replace or update a complete resource, whereas PATCH is used when we want to make a partial update. The interviewer then moved to OOP. Questions included the basic principles of object-oriented programming such as encapsulation, inheritance and polymorphism. He also asked about constructors and their different types. Instead of only asking definitions, he asked me to demonstrate some of the concepts through code. I explained how classes and subclasses work, demonstrated inheritance and discussed function overloading. We also talked about access specifiers and how they can be used to implement data hiding. This part of the interview was fairly interactive because the interviewer kept asking follow-up questions based on my answers. After OOP, the interview moved to DSA. The first coding question was quite simple. I was given a list containing numbers from 1 to 10 and asked to replace every second element — the 2nd, 4th, 6th and so on — with my name. I explained the simple traversal-based solution and then wrote the code. The second coding question was the standard Two Sum problem. I first discussed the brute-force approach, which would take O(N²), and then explained the hash-map solution. By storing previously seen numbers and checking whether the required complement existed, the problem could be solved in O(N) time with O(N) additional space. The interviewer was interested in both the implementation and the complexity, so I explained why the hash-map approach was preferable. The technical round also included questions related to my academic subjects and general computer science fundamentals. Similar GE HealthCare internship reports mention DSA, OOP, DBMS and project-based discussions as recurring areas. HR Interview After the technical interview, a smaller group of candidates was called for the HR round. The HR interview started with a basic introduction and then moved to questions about my interests, hobbies and expectations from the internship. One thing that was particularly interesting was that the interviewer asked about my interest in the healthcare and medical technology field. Since GE HealthCare works on medical equipment and healthcare technology, I was asked what interested me about working in this area and what kind of technology or medical equipment could potentially help address healthcare problems. I tried to give a genuine answer rather than simply saying that I wanted the internship because it was a well-known company. I talked about how software is increasingly becoming an important part of medical devices and healthcare systems and how working in such an environment could give me exposure to a domain outside regular consumer applications. The interviewer also asked what I expected to learn during the internship and what kind of work I would like to do. The HR discussion was fairly conversational and did not contain any difficult technical questions. Result After the HR round, the final results were announced and I was selected for the Software Engineer Internship at GE HealthCare. Looking back, the biggest thing I learned from the process was that preparation for an internship interview shouldn't be limited to DSA. The coding questions were important, but the interview also covered projects, OOP, web development and basic CS fundamentals. The project discussion was particularly important. The interviewer could take any feature from the project and ask how it worked internally, so being able to explain the implementation was much more useful than memorizing a project description. For preparation, I would recommend focusing on four areas: DSA: arrays, strings, hashing, trees, linked lists and basic problem-solving. Core CS: OOP, DBMS, OS and basic networking. Projects: understand the architecture, APIs, database, technologies and your individual contribution. Aptitude: quantitative reasoning, logical reasoning and verbal ability. Public GE HealthCare internship experiences also show variation between hiring drives. Some drives have used resume shortlisting followed by an OA and interview, while others have included separate technical and HR rounds. Overall, the GE HealthCare process was a good combination of coding and fundamentals. The interview was not solely about solving difficult DSA problems; being able to communicate clearly and explain my projects and technical decisions played a major role in getting through the process.