Real, anonymous reports from people who interviewed for Software Engineer at Samsung Ads, newest first and distilled into what to expect across the loop.
My journey started after a hackathon, which meant I ended up interviewing alongside a cohort of candidates. The first round was split into multiple interviews in a single day, and it kicked off with a technical session where I had to solve LeetCode problems. One of the questions was about a linked list cycle, and there was also a math-based problem—enough variety that I had to shift gears quickly.
My interviews leaned heavily on communication and experience walkthroughs. I had an online panel with two engineers where they asked questions in English, and I was allowed to answer in English too. It was honestly enjoyable because the conversation kept circling back to my previous work and what I had done, but the language barrier still made everything feel slightly more effortful than it should have.
The initial technical rounds focus on problem-solving skills with a mix of LeetCode-style questions, often emphasizing data structures and algorithms. Candidates should be prepared for a variety of topics, including linked lists, graphs, and fundamental concepts, with some interviews requiring coding on paper or in a competitive format.
Behavioral interviews are a significant part of the process, with a strong emphasis on discussing past experiences and how they relate to the role. Candidates should be ready to articulate their motivations and how their background aligns with the team's needs.
Some candidates may encounter system design questions that require them to explain their approach to building applications or platforms, often integrating machine learning concepts. This round tests both technical knowledge and the ability to think through practical implementations.
The interview process is typically well-structured, often consisting of multiple rounds that include technical assessments followed by behavioral discussions. Candidates can expect a timeline that may stretch over several weeks, with a mix of remote and onsite interviews.
Overall, the difficulty of the interviews is described as average to high, with candidates reporting a need for strong foundational knowledge and the ability to handle varied question types. Many candidates did not receive offers, indicating a competitive selection process.
Candidates often reflect on the importance of thorough preparation, particularly for the depth and pace of questions asked. Some expressed a desire to have practiced more on presenting their experiences and technical knowledge clearly.