Real, anonymous reports from people who interviewed for Software Engineer at Samsung Ads, newest first and distilled into what to expect across the loop.
Get your personalized Samsung Ads Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
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 in-person portion I went through also followed a similar vibe: I was asked two easy LeetCode-style questions but had to write the code on paper. Alongside that, they focused a lot on my past experiences—matching what I had put on my resume to the kind of skills they wanted to see. Overall, the process felt like it was testing how clearly I could connect my experience to concrete problem-solving, not just whether I could grind out perfect solutions.
6 months ago
Easy Positive India
After a recruiter-style HR screening call, I moved into a technical discussion with a Samsung employee, and then I finished with another HR round. The whole thing felt pretty smooth and structured, like everything had a clear sequence and the scheduling was handled well.
The technical part leaned into fundamentals and DSA-style thinking, and the process as a whole didn’t feel chaotic. Even when the questions weren’t trivial, the interview still felt organized enough that I wasn’t guessing what format they wanted from me. By the time I reached the final HR conversation, it felt like the earlier rounds had set the stage—my background and fit were being evaluated alongside the technical side.
6 months ago
Average Positive Noida
I went through a fairly standard structure, but the coding side had a very specific feel: concepts mattered more than showing off a long, perfect impl…
7 months ago
Average Negative Egypt, GA
My process started with a long coding assessment—one question that stretched for hours—then there was a CV shortlist step before I moved into the actu…
> 1 year
Average Positive South Korea
I started with a conference call and then moved into a fairly step-by-step series of interviews. About a week later, I did a first technical interview…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical / coding screen
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.
LeetCodeDSAcoding on paper
Behavioral & values
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.
STARexperience walkthroughmotivation
System / ML design
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.
system designML conceptspractical applications
Interview structure & timeline
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.
structured processmultiple roundstimeline
Difficulty & outcome
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.
high difficultycompetitivefoundational knowledge
What candidates wish they'd done
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.