Taro Logo

Embedded Software Engineer Interview Experience - United States

September 1, 2025
Positive ExperienceNo Offer

Process

The whole process took less than 3 weeks.

  1. A quick 30-minute call with the recruiter to go over your resume. If they like you, then you'll interview with a manager.
  2. The first technical interview with the manager was an hour long. We went through my experience, the manager's experience, and then a coding question. It was an easy-medium linked list coding challenge.
  3. If you get to the final round of interviews, you will be interviewed by 4 people in a half-day interview of 4.5 hours. This includes one hour per person and a 30-minute lunch break. This round of technical interviews is the most tiresome, and the coding questions are not bad either.

I really suggest you keep practicing LeetCode and HackerRank medium-hard problems because these people expect clean, almost perfect O(n) O(1) answers in a span of 30 minutes. This was my first time doing this style of interview, and for me (I got VERY anxious), it was brutal. Though the questions shouldn't be that bad to solve, they expect you to respond like ChatGPT and even comment your code.

I think this is achievable if you get time to practice at least 3-5 medium to hard exercises daily on LeetCode for at least a month. I only did about 30 exercises in total. They don't care if you did a brute-force approach to the problem first. If you don't have time to give the best answer to the problem, they'll probably not make you an offer.

Questions

They asked a lot of behavioral questions, with some subtle ones in between. Those were fine, no issues there. The coding questions were about:

  • String manipulation
  • Bit manipulation
  • Hash tables (or the closest you can get in C and C++)
  • Bytes manipulation and memory alignment

Everything was in C, and there was no dynamic programming. If you really want to get an offer from a company like this, I strongly suggest polishing your programming style and your knowledge of the language. Really master C or C++. They don't care if you understand the problem from a high-level perspective; these people are trained to select a candidate who can give the right answer to the coding challenge in the right amount of time and discuss the answer.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Snap Embedded Software Engineer role in United States.

Success Rate

0%
Pass Rate

Snap's interview process for their Embedded Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Snap's Embedded Software Engineer interview process in United States.

Snap Work Experiences