After a recruiter reached out, I got a 45-minute technical interview at their site in Hod Hasharon. They started by giving me an API and asked me to explain what I understood from it, then I was asked to write a function that worked with that API.
The rest of the session focused heavily on bit manipulation. Overall it felt like a practical test of whether I could quickly interpret an interface and then translate that understanding into correct, low-level logic. I didn’t end up getting an offer, but the questions were specific enough that it was clear what they were evaluating.
1 month ago
Difficult Negative Farnborough, London, England
I applied and, about three weeks later, I was invited to a 30-minute screening interview. They asked me to attend on a specific day, but only about 20 minutes before the scheduled start time they requested I reschedule to Monday. Since I had already rearranged my day for the original slot, I chose to withdraw rather than spend more time adjusting.
It was disappointing that the process became so last-minute so close to the call, and I never got to the actual interview content. In the end, I didn’t proceed further and I still felt like the experience wasn’t managed very professionally.
1 month ago
Average Positive United States
In my screening round, the questions leaned into verification and hardware description concepts—especially UVM and Verilog. I was asked to distinguish…
1 month ago
Average Neutral San Diego, CA
One interview felt unusually informal and it was with the manager of the team. It ended up lasting about two hours even though it was supposed to be a…
2 months ago
Average Negative United States
HR contacted me first, and then I moved into an OA step with two technical rounds afterward. The timing and scheduling felt messy overall: both techni…
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
Interview Structure & Timeline
The interview process typically begins with a recruiter screening, followed by multiple technical rounds that can include coding, system design, and behavioral assessments. Candidates should expect a mix of interview formats, including both individual and group discussions, with varying levels of difficulty across rounds.
Candidates should prepare for a range of technical topics, including data structures, algorithms, operating systems, and hardware description languages like Verilog. Specific areas such as bit manipulation, memory management, and system-level design are frequently tested.
Data structuresOperating systemsBit manipulation
Behavioral & Values Assessment
Behavioral interviews often focus on past experiences and how they relate to the role, with interviewers digging into resume details and using methods like STAR to assess fit. Candidates should be ready to discuss their project experiences and how they align with the company's values.
Behavioral questionsSTAR methodResume deep dive
Difficulty & Interview Experience
The overall difficulty of interviews varies, but many candidates report a mix of moderate to challenging questions that test both theoretical knowledge and practical application. Some interviews may feel informal and conversational, while others can be more structured and rigorous.
Several candidates noted issues with scheduling and communication throughout the process, including last-minute changes and unclear expectations. It's advisable to remain flexible and proactive in confirming details to avoid potential frustrations.
Scheduling issuesCommunicationFlexibility
Outcome & Reflection
Many candidates did not receive offers despite strong performances, indicating that the competition is high and the evaluation criteria can be stringent. Reflecting on the experience, candidates often wish they had focused more on specific technical areas or improved their communication during interviews.