My journey ran for about a month and a half from applying to the final rejection email. The interviews themselves were pretty pleasant: I had two in-person meetings with team-lead and group-lead, and both times the questions felt fairly straightforward and grounded in fundamentals.
I remember getting asked about bit operations and doing a mid-level LeetCode style problem. The mood stayed positive through each interview, and it seemed like the interviewers were pleased with how I handled the questions and the discussion. After everything wrapped up, though, I eventually received a rejection email with no explanation or reason, about a week and a half after the last step.
4 months ago
Average Positive Yoqne`am `Illit
My first interview was a technical session for a junior role with two interviewers—one was the team lead and the other was a senior. I started by introducing myself and talking through a project I’d done in university, and then they explained more about the role and what they were looking for.
After that setup, they moved directly into technical questions. The round felt like it centered on connecting my background to the kind of problems I’d be doing, rather than being purely abstract. Overall it came off as straightforward and focused, and I left with the impression that they were trying to gauge how I think and communicate under normal technical questioning.
4 months ago
Average Neutral Santa Clara, CA
The first thing I noticed was the tempo: I had a short 45-minute session with five questions. Several of them were more basic algorithm checks—things …
5 months ago
Average Neutral Tel Aviv-Yafo
After an initial HR call, I moved into a technical phase that felt pretty structured and professional. The recruiter screened me on my background, exp…
8 months ago
Average Positive Israel
My interview process ran as a clear three-round flow: two technical rounds followed by an HR conversation. In the first technical interaction, I met t…
Unlock every Embedded 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
Interview Structure & Timeline
The interview process typically consists of a technical phase followed by an HR conversation, with multiple technical rounds focusing on coding and problem-solving. The overall timeline is often around two weeks to a month, with some candidates experiencing delays in feedback after the final round.
Interview phasesTimelineHR conversation
Technical Coding Rounds
Candidates can expect multiple technical rounds that include algorithm and data structure questions, often in a LeetCode-style format, alongside practical coding tasks related to C/C++ and embedded systems. Interviewers emphasize clean code, efficiency, and the ability to communicate thought processes clearly during these sessions.
Coding questionsLeetCodeC/C++
Embedded Systems Focus
Technical questions often center around embedded systems concepts, including Verilog logic design and low-level programming tasks, which require candidates to demonstrate a solid understanding of hardware-software interactions. Expect questions that assess both theoretical knowledge and practical application in embedded contexts.
Embedded systemsVerilogLow-level programming
Behavioral & Personal Context
Interviews typically begin with personal introductions and discussions about past projects, allowing candidates to connect their experience to the role. Interviewers are interested in understanding candidates' motivations and how their background aligns with the team's needs.
Behavioral questionsPersonal experienceMotivation
Atmosphere & Interviewer Dynamics
The interview atmosphere can vary significantly, with some candidates reporting supportive and engaging interactions while others experienced critical or tense environments. The demeanor of interviewers can impact candidates' confidence and overall experience during technical discussions.
Many candidates reported a lack of feedback or closure after the interview process, leading to uncertainty about their performance and outcomes. It's common for candidates to feel left in the dark regarding their application status after completing technical rounds.