29 Days of Silence: My Frustrating Interview Experience with Arm Ra’anana

I usually don’t post reviews, but my experience with Arm’s recruitment process in Ra’anana — especially for a senior-level role — was deeply disappointing and deserves to be shared.

The whole process spanned over two months, starting with a hiccup: I was automatically rejected after missing a phone call while I was abroad. Only after I reached out through an insider did I get recontacted, and things seemed to pick up from there.

I went through two rounds of technical interviews, both of which went very well — the interviewers seemed genuinely impressed. That led to an HR interview, where the recruiter asked for my salary expectations, availability, and even a list of references. I was then given a site tour and introduced to the facilities — usually a sign that you're close to the finish line.

But the very next day, when I proactively followed up, I was told — for the first time — that another candidate was still in the process and they wanted to finish interviewing them before making a decision. I found this highly unprofessional. It’s unusual to get that far (post-HR, post-tour) and still be treated as “under consideration.”

And then began the worst part: 29 days of silence.

During this time, I made repeated calls to both the HR manager and the team lead, just to get clarity — and each time, I was told that no decision had been made. Meanwhile, the job posting was removed from both Arm’s official site and LinkedIn — all while I was still left waiting.

After nearly a month of uncertainty, I finally received the expected "no." No formal explanation and feedback.

This was for the Senior GPU Software Engineer position. I expected better from a company with Arm’s reputation — more transparency, more respect for candidates’ time, and basic communication standards.

If this is how they handle hiring, I can’t help but question what it's like working there.

First round: C language basics and keyword meaning, alignment questions, basic coding

Second round: MCU peripherals description and another very long coding question