Real, anonymous reports from people who interviewed for Software Engineer at Samsung Semiconductor, newest first and distilled into what to expect across the loop.
I started with a personality check, then moved into two interviews—one focused on personality and one that was technical. The order felt a bit randomized: the personality interview and the technical interview were slotted in without me having much control over which came first. The whole thing ended up being a pretty long stretch, taking nearly 5–6 hours total.
After I passed a hackathon, the process moved forward with a group of about a dozen other people and me. The first day felt packed: it was split into three interviews that all happened in the same day. The technical round was the lead-in, and I had to solve LeetCode-style questions, including a linked list cycle problem plus a separate math-based question. I felt it was fair overall.
The interview process typically involves multiple rounds, starting with an HR screening followed by technical interviews, which may include coding assessments and behavioral discussions. The flow can vary significantly, with some candidates experiencing a coherent sequence while others find the transitions between rounds disjointed.
Candidates can expect a strong emphasis on technical skills, including coding challenges that often resemble LeetCode problems, system design discussions, and practical coding exercises. The technical rounds may also cover core concepts in data structures, algorithms, and relevant domain knowledge, with varying levels of depth based on the interviewer.
Behavioral interviews are a key component, focusing on candidates' backgrounds, experiences, and fit for the team. Interviewers often aim to understand candidates' thought processes and how their past work aligns with the role, which can include discussions about personal projects and academic backgrounds.
Candidates may face challenges related to communication, particularly if English is not their first language. The ability to articulate technical concepts clearly and effectively can be crucial, especially in interviews that blend technical and behavioral questions.
While many candidates found the interview process to be organized and professional, the overall experience can vary greatly. Some reported feeling overwhelmed by the length and intensity of the process, while others appreciated the structured approach, even if it did not lead to an offer.
Most candidates did not receive offers, and many reflected on the unpredictability of the questions and the overall process. Common takeaways include the importance of preparation and the need for clarity regarding what each stage of the interview entails.