I interviewed at the Yokneam site with a team leader and another employee. They opened by explaining the company and framing the role, then they asked me to tell them about myself and to walk through a project I had done during my university studies. I was expected to go into real detail about how it was implemented and why I made specific design choices.
After that, the technical part turned very hardware/low-level. I was asked a bit-manipulation question, then a memory-management question that focused on registers and a set of operations they defined. Once I finished those technical questions, the interview wrapped up without any extra rounds or follow-ups.
2 months ago
Average Positive Haifa
I got a call from HR to coordinate a time, and then I joined a two-hour technical interview. I didn’t make it past the first interview, which was disappointing, but the format itself was straightforward.
They started by talking about the role and the company, then asked me to introduce myself. After that, I had to discuss a project I had worked on, and answer a handful of questions about it before the conversation shifted to coding. The coding portion had two questions written in C, and that was the main technical focus by the end of the session.
2 months ago
Difficult Positive Taipei
My process started with an OA, and it immediately felt demanding. The topics included LeetCode-style questions from easy to medium, plus C++ data-stru…
4 months ago
Easy Negative Israel
I went through two indoor interviews with a team lead and a group lead, and overall the vibe felt pretty good. We kept things grounded in fundamentals…
5 months ago
Average Positive Yoqne`am `Illit
My first technical interview was for a junior position and it was run by two interviewers: the team lead and a senior. I introduced myself and talked …
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 spans about 25 days, beginning with an HR screening call, followed by one or two technical interviews, and concluding with an HR wrap-up. Candidates should expect a structured flow with clear stages, though the timing may vary by team and location.
HR screeningTechnical interviewsTimeline
Technical Focus Areas
Technical interviews cover a mix of low-level hardware questions, coding tasks, and system design problems, often emphasizing embedded systems knowledge. Candidates should prepare for topics like bit manipulation, data structures, and algorithm efficiency, as well as practical coding in languages like C and C++.
Bit manipulationData structuresC/C++ coding
Project Discussion & Experience Evaluation
Candidates are frequently asked to discuss their past projects in detail, focusing on implementation choices and problem-solving approaches. This aspect is critical for interviewers to gauge candidates' practical experience and understanding of their work.
Expect a variety of coding challenges, often including algorithmic problems and practical tasks related to concurrency and memory management. Candidates should be ready to write clean, efficient code while explaining their thought process and trade-offs.
Coding challengesProblem-solvingConcurrency
Behavioral & Cultural Fit
Interviews often include behavioral questions aimed at assessing cultural fit and alignment with the company's values. Candidates should be prepared to articulate their motivations for joining Nvidia and how their experiences align with the role.
Behavioral questionsCultural fitMotivation
Interview Experience & Feedback
Candidates report varying experiences with interviewers, from supportive and constructive interactions to more challenging dynamics that can impact confidence. The lack of feedback post-interview is a common frustration, making it important to seek clarity on performance where possible.