Samsung Semiconductor Inc (US) Interview Questions
& Process

I went through an interview process at Samsung Semiconductor that involved a significant take-home task. I chose to do it and attend the interview even though I was sick and traveling during a blizzard. That was my call, and looking back, it was a bad decision because I didn't realize how sick I was and got really ill afterward. While that part was on me, what happened next wasn't. It's perfectly fine for a company to not proceed with a candidate, but the total absence of any follow-up or closure after the interview was unprofessional and showed a lack of respect. The hiring manager, who seemed to be handling recruiting duties, didn't give me any update, rejection, or communication after I spent a lot of time and effort on the assignment and interview. Asking candidates to do unpaid work and then not even closing the loop shows they don't value their time and effort. For a company like Samsung, this candidate communication is disappointing and not okay. I'm fine with the hiring decision, but the interview process and the overall candidate experience were handled badly and are way below what I'd expect from a top global company.

It was a great experience with a warm and welcoming team. The process involved 4 virtual rounds and 2 onsite rounds. We covered basic ML concepts, a coding round, a Director round, and an HM round. Then, there was an onsite team teaming session involving a presentation and problem-solving.

I had a call with a recruiter from an agency, then a call with the hiring manager, followed by a take-home assignment, and finally an onsite interview. The whole process was quite fast. However, the hiring team was not very responsive and didn't follow up after the last round. Despite that, it was a good experience to learn about the semiconductor field, and I got to visit their great headquarters in San Jose.

My interview at Samsung was pretty good, mixing technical and behavioral stuff. First, they hit me with problem-solving questions about data structures, algorithms, and making solutions better. I had to do coding challenges, talk through my methods, and mention time/space complexities. They also checked my system design knowledge and programming basics. Then, they asked about teamwork, handling changes, and dealing with stress. They wanted to hear about old projects, how I worked with people, and any tough spots I ran into. The whole thing was solid, and the interviewers were cool, trying to see if I was technically good and would fit in.