Taro Logo

Staff Software Engineer Interview Experience - Geneva, Switzerland

July 1, 2026
Negative ExperienceNo Offer

Process

I went through a five-stage interview process with Sonar for a senior engineering role. I have no issue with ultimately being rejected. Companies are entitled to choose whichever candidate they think is best. However, I was disappointed by the communication, the lack of respect for candidates' time, and how little opportunity I had to evaluate the team and role despite the lengthy process.

The first stage was a recruiter call. The recruiter was friendly, but couldn't tell me much about the technical side of the role, the team or the roadmap.

The second stage was a 30-minute online technical interview. I reviewed a short piece of code with Clean Code and SOLID principles in mind and answered some technical questions. The exercise was straightforward, but the interview filled the entire 30 minutes, leaving essentially no time for me to ask questions. It also wasn't clear whether either interviewer was from the team I would potentially join.

For the third stage, Sonar specifically asked me to make myself available as soon as possible because they "tend to move quickly with our hiring process." I rearranged my schedule and attended a two-hour onsite coding interview a few days later.

The coding interview itself was reasonable. The challenge was to build a small Java command-line application that loaded data from CSV, supported various filtering and aggregation operations, and was designed with Clean Code, SOLID principles and testability in mind. There was quite a lot to implement in two hours, although AI use was explicitly permitted. I completed the requirements with a working, tested solution that I was happy with.

The interview consisted mostly of independent coding, with the two interviewers returning at checkpoints to discuss progress, design decisions and next steps. Both developers were pleasant and I enjoyed the technical part of the process.

However, the two developers were from different teams. After three stages, I therefore still hadn't really met anyone from the team I might actually be joining. There was also relatively little time for my questions because the interview was understandably focused on completing the exercise.

The communication after this stage was where my experience deteriorated significantly.

I was told to expect feedback later that week. I heard nothing. I followed up the following week and was told they were still "gathering feedback" and would get back to me soon. More than three weeks eventually passed before I received an update, with no real acknowledgement or apology for the delay.

I found this particularly disrespectful given that Sonar had specifically asked me to rearrange my schedule because they wanted to move quickly.

I nevertheless progressed to a fourth stage: a cross-functional interview with someone from the legal team. He was nice and professional, but it was essentially a generic HR-style interview and didn't give me much additional insight into the engineering role, team or how I would actually work at Sonar.

The fifth and final stage was a 20-minute interview with the CTO. I found him arrogant and came away from that conversation with a poor impression. For example, when asking why I wanted to work at Sonar, he phrased the question as "to what do we owe the pleasure?". Other questions included how many days I had worked onsite in my previous role (but no discussion about this), whether I'd got what I wanted from that role, and what my colleagues would identify as my strengths and areas for improvement. There was generally little follow-up or deeper discussion after my answers.

That's obviously a subjective impression, but by the end of this interview I had serious doubts about whether Sonar was somewhere I would actually want to work.

More broadly, I found it a red flag that after five interview stages I had learned surprisingly little about the team I would potentially be joining. Interviews should work in both directions, particularly for senior positions, and I didn't feel this process gave me sufficient opportunity to evaluate Sonar as an employer.

The following week I again heard nothing, so I contacted the recruiter. I then received a generic rejection saying another candidate's experience more closely aligned with the "specific scope and strategic scale required for this role."

Again, I have no problem with Sonar choosing another candidate. What disappointed me was receiving essentially no useful feedback after investing considerable time in five interview stages.

I replied asking whether their feedback meant it was worth applying for another Staff Software Engineer position they had advertised which appeared closely aligned with my background. I received no response.

I applied anyway and received another generic rejection stating that "the skills demonstrated on your profile do not match what we need for the team in this specific role." This was confusing given that Sonar had just spent five interview stages assessing the same background for another senior engineering position.

Overall, there were things I liked. The developers conducting the coding interview were pleasant, the technical exercise was reasonable, and I appreciated the pragmatic approach of explicitly allowing candidates to use AI.

But my overall impression was negative. The messaging was inconsistent, expected feedback timelines were repeatedly missed, at one point I waited more than three weeks after being told Sonar wanted to move quickly, and after five stages I received no meaningful feedback and surprisingly little exposure to my prospective team.

I won't apply to Sonar again. That's not because I wasn't offered the position. By the final interview I already had significant reservations about accepting it. It's because I didn't feel that the considerable time and effort Sonar expected from me as a candidate was reciprocated with the same level of communication and respect.

Questions

The process included generic HR questions, why do I want to work there, my strengths, and areas I can improve.

There was no deep evaluation of technical skills other than coding, no system design.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Sonar Staff Software Engineer role in Geneva, Switzerland.

Success Rate

0%
Pass Rate

Sonar's interview process for their Staff Software Engineer roles in Geneva, Switzerland is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Sonar's Staff Software Engineer interview process in Geneva, Switzerland.

Sonar Work Experiences