Samsung Electro-Mechanics Interview Questions
& Process

The hiring process was pretty structured and tough, with several rounds. It kicked off with an online assessment, and then about 25 folks got shortlisted, though how they picked wasn't super clear. Next up was Technical Round 1, a 30-min chat about Python basics, OOP, basic DSA, a string coding question, and a conceptual question on KNN. This cut the list down to 10. Technical Round 2 really dove into the projects on our resumes, asking detailed questions to check our practical know-how. Only 4 people made it to Technical Round 3 (Managerial Round), where they wanted to see hands-on coding, like writing the R² score calculation from scratch for an ML project. Finally, 2 candidates were selected for the HR Round, where they asked about why I wanted to join and my strengths/weaknesses. Even though I did well in all technical rounds, I didn't get the offer after the HR round, and they didn't really say why.

The interview process had five parts. First was an online test with questions on DBMS, SQL, and OS. Then, a technical interview about OOP concepts like abstraction, polymorphism, encapsulation, and inheritance, where I had to code and talk about past projects. The next part was also a technical interview, but this time focused on projects and behavioral questions, checking my technical skills, how I talk, and how I solve problems. After that, there was a .NET language technical round where I had to do a coding question about data structures and algorithms, specifically counting words/numbers in a string and showing their frequencies. Finally, there was an HR round for the last chat about the job. I'm still waiting to hear back about the DSA round, nobody has gotten any updates.

We had a technical screening for about 30–45 mins covering Kubernetes basics like pods, nodes, services. There were hands-on questions where I had to write YAML for deployments, services, ConfigMaps, and Secrets. We also went through troubleshooting scenarios, like what to do if a pod is in crashloop or a node fails. Networking in Kubernetes, including CNI plugins, service discovery, and DNS, was also discussed. Then there was a technical deep dive, lasting 45 mins, focusing on managing production clusters. This included questions on upgrades, etcd backups, and monitoring tools like Prometheus and Grafana. We also covered Helm, Operators, and the difference between StatefulSets and Deployments. Security practices, such as RBAC, NetworkPolicies, and Secrets management, were also part of this round.

The entire interview process took place on-site in Calamba. It started with a general aptitude and behavior exam that's pretty straightforward. Then there was a brief initial screening with HR, focusing mainly on background checks and personal questions. Following that was a panel interview with HR managers, which was behavioral in nature, assessing your personality and what you learned in college and internships. The final stage was a technical interview with the line managers, where they might ask you to discuss your thesis.