Samsung behavioral interview: Core values
The core values are published by Samsung; the HR round is short and conversational rather than a scored values interview.
| Progress | Principle | Your story |
|---|---|---|
| PeopleOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
| ExcellenceHigh standards | Write a story | |
Sample answer: Tell me about a time you were not satisfied with good enoughWhether you notice quality problems others have learned to live with, fix them in a way that sticks, and know when high standards matter more than speed and when they do not. They want a standard you raised for the team, not just your own code. Situation On my team, about one in five builds failed because of flaky tests, tests that pass or fail at random. Everyone had learned to click "re-run" until the build went green, and real failures were sometimes re-run away. Task Nobody had asked anyone to fix it, but in one month two real bugs reached production because their failing tests were dismissed as flaky. I decided to get flaky failures down to a level where a red build meant something again. Action I started by measuring. I wrote a small script that read three months of build history and listed every test that had both passed and failed on the same code. Twenty-three tests caused almost all the flakiness, and most shared two causes: tests that depended on the clock and tests that shared one database without cleaning up. I fixed the worst ten myself over two sprints, mostly by using a fake clock and giving each test its own data. For the rest, I proposed a simple rule to the team: a flaky test goes into quarantine within a day with a ticket and an owner, so it cannot block builds or hide real failures, and it comes back only when fixed. I added a weekly report of the flaky rate to our team channel so the number stayed visible. Result Flaky failures dropped from about 18 percent of builds to under 2 percent in two months, average time to merge fell by about a third, and we had no more bugs reach production that were dismissed as flaky. The quarantine rule is still part of how the team works. Tip: Show you raised the bar on quality even when nobody asked, and why it mattered. High standards: weak answer, follow-ups and level differences | ||
| ChangeOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
| IntegrityIntegrity and trust | Write a story | |
Sample answer: Tell me about a time you had to tell someone something they did not want to hearWhether you are honest when it costs you something: raising a problem early, owning your part without spin, and rebuilding confidence through actions. They want to see that people could rely on what you said afterwards. Situation I built a dashboard for our product team that showed weekly active users for a new feature. Three weeks after launch, the product lead used it in a planning meeting to argue for expanding the feature to more markets. Task While adding a new chart, I noticed that users who switched between our app and website were counted twice. The real number was about 25 percent lower than the one in the planning slides. I had to tell the product lead, quickly and clearly, even though the mistake was mine and the decision was already in motion. Action I spent an hour confirming the error with a second query so I would not raise a false alarm, then messaged the product lead the same afternoon instead of waiting for our next meeting. I wrote three things: what was wrong, the corrected number, and that it was my mistake in how I joined two data sources. I added that the trend was still upward, so they could judge whether the decision still held. I fixed the dashboard that day, put a visible note on it explaining the correction and its date, and checked my other two dashboards for the same join, finding one more small error. Then I added a test that compares our user counts against the source system each day. Result The product lead re-ran the numbers; the expansion still made sense but went to two markets instead of four. They told me later that hearing it from me within hours, with the correct number ready, made them trust the dashboards more, not less. The daily check has since caught two data problems from other teams before anyone used them. Tip: Show you were honest when it was uncomfortable, and how you earned trust back. Integrity and trust: weak answer, follow-ups and level differences | ||
| Co-prosperityOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
How to answer
Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.
Behavioral questions by theme, with a tip for each · How the behavioral round is scored
Questions people ask
What is the Samsung behavioral interview based on?
Core values: People, Excellence, Change, Integrity, Co-prosperity. The core values are published by Samsung; the HR round is short and conversational rather than a scored values interview.
How do I answer Samsung questions on "People"?
Whether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Show you took responsibility beyond your task: you noticed, you acted, you followed through. A typical question: Tell me about a time you took ownership of something outside your role
How do I answer Samsung questions on "Excellence"?
Whether you notice quality problems others have learned to live with, fix them in a way that sticks, and know when high standards matter more than speed and when they do not. They want a standard you raised for the team, not just your own code. Show you raised the bar on quality even when nobody asked, and why it mattered. A typical question: Tell me about a time you were not satisfied with good enough