Sonar logo

Sonar Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 134 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
39.6% Positive experience

Which role are you interviewing for?

30 roles · 134 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Sonar.

Showing 4 of 134
Sonar logo
Sonar

Renewals Specialist

Sales · half a year ago

Entry Easy Negative experience No offer 1 round
Interview process
Recruiter call Background check
Interview formats
Behavioral

The interview process was pretty straightforward and the actual conversation went well. The recruiter was about 10 minutes late to our scheduled call, but was professional during the interview. I was told I would be moving forward, but then there was no communication for several weeks. Eventually, I got a follow-up saying the role was closed and another candidate was already far along. Honestly, clearer communication and more transparency about candidate status and timelines would really make the experience better. It was confusing to be told I was progressing, then have a long silence, and then a delayed update and rejection. It raised some concerns for me as a candidate.

Confirmed questions1 question
  • Can you tell me about yourself and why you're interested in Sonar?
Sonar logo
Sonar

Software Engineer

Engineering · nearly a year ago

Staff Difficult Negative experience No offer 7 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Technical screen Panel Panel
Interview formats
Coding Behavioral Technical Technical Technical Behavioral Behavioral

I was about halfway through their very long interview process getting great feedback and I knew I aced the first technical interview before I was abruptly told they were no longer hiring for this position. It’s frustrating to invest significant time and energy across so many steps, excel in them, and consistently hear positive feedback, only for the opportunity to disappear for reasons unrelated to performance. The stages were: 1. Online Coding Test 2. Recruiter Interview 3. First Technical Video Interview 4. TestGorilla Assessment - Culture Fit 5. Technical Assessment 6. Cross-Functional Interview 7. Leadership Interview

Confirmed questions3 questions
  • Given a scenario similar to LeetCode 1169. Invalid Transactions, identify suspicious transactions and then write a Unit Test to validate your solution.
  • Explain the difference between composition and inheritance, and discuss scenarios where one is preferred over the other.
  • Describe the factory pattern and the builder pattern, and explain when to use each.
Sonar logo
Sonar

Communications Manager

Marketing · nearly a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Presentation
Interview formats
Behavioral Technical Presentation

I had two interviews at Sonar that took over two weeks to complete. First, I spoke with the hiring manager, then I had a technical interview. The first interview was a bit uncomfortable because the hiring manager didn't seem experienced with interviewing, never asked follow-ups, and didn't share what to expect next. It took them two weeks to schedule the next interview. For the technical interview, I had to do a long case study in an hour and then present it to three people. The day after, I found out I didn't get the job. The recruiter's email didn't even mention the correct position. I asked for feedback, and they said it was positive but gave no details. I pushed for specific feedback, especially since I did a long assignment, but they ghosted me. Overall, the process felt unprofessional and like a waste of my time.

Confirmed questions1 question
  • Can you share an instance where you developed a communications campaign?
Sonar logo
Sonar

Data Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 6 rounds
Interview process
Take home Recruiter call Technical screen Technical screen Onsite Onsite
Interview formats
Coding Behavioral System Design

So the hiring process had 6 stages. First was a code assignment, it took about an hour on Codility with 3 LeetCode style questions. Then, a recruiter interview, which was super positive. The recruiter was really helpful and gave feedback fast after each part. I really liked how professional and encouraging they were. After that, a technical Q&A with two developers, one asking and one taking notes. It was chill and they made sure I was comfy. Next, a system design interview where I had to design an ETL process. It was tough but fun, my first time doing this type of interview. The interviewer was good at keeping things relaxed. Then, a People & Culture interview, which is the usual behavioral stuff, like how you'd handle work situations. Finally, a CTO interview, which was pretty much the same as the last one. It was a long process, but talking with the recruiter and the technical people made me feel good and want to keep going.

Confirmed questions2 questions
  • Could you explain the concept of data mesh?
  • What does a slowly changed dimension refer to?

Sonar Interview Questions

Quoted word for word from Sonar interview reports.

For the fourth Python code example, what value does the 'name' variable hold after the function call?

Read reports

What is the sum of the modified numbers in the fifth Python exercise?

Read reports

Regarding the second Python exercise using numpy, what is the dot product result?

Read reports

How would you maximize the number of nails that end up having the same length when hammering down at most K nails?

Read reports

Can you tell me the complexity of finding the middle node in a singly linked list?

Read report

Can you evaluate the expression using the syntax tree from the simple parser?

Read report

Can you write a function to find two elements in an array that sum to a specific number, aiming for O(1) time complexity?

Read report

Write a CLI program that takes movie records from a CSV file and supports commands like count or average, with options to filter by fields such as duration or type.

Read report

When discussing API usage, which requests should be used, and how can data be sent in GET requests?

Read report

Formats, difficulty and experience

Across all 134 Sonar interview reports.

Interview formats

Behavioral 34.9%
Technical 30.8%
Coding 17%
Presentation 7.3%
System Design 4.1%

Interview difficulty

Easy 21.6%
Average 63.4%
Difficult 14.9%

Candidate experience

Positive 39.6%
Neutral 13.4%
Negative 47%

Reports by job function

Engineering 82
Sales 17
Marketing 9
HR 6
Operations 4
Design 4