Shure logo

Shure Software Engineer Interview Questions
& Process

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

Based on 18 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
55.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Shure.

Showing 3 of 18
Shure logo
Shure

Software Engineer

Engineering · more than a year ago

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Technical Behavioral Presentation

So, the whole thing took about a month. After I talked with the hiring manager, it took like, almost two weeks to get to the last panel interview. That panel interview was pretty long, like 4 hours, and it included talking to team members and then a final chat with HR. One thing that kind of bothered me was during the cloud computing talk, the interviewer started googling stuff and then asked me more questions based on that. I felt that was a bit unfair, you know, since I was answering based on my own experience and expected them to do the same. The last part was with HR, where we discussed my salary expectations. Then it took another week to hear back, and they said they liked me but went with someone else.

Confirmed questions6 questions
  • Could you explain what happens when a browser page is reloaded?
  • Tell me about your experience with Node.js.
  • What do you know about TypeScript?
Shure logo
Shure

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call Phone screen Phone screen Phone screen
Interview formats
Technical Behavioral

I applied on the company website and HR reached out to set up a 45-minute phone interview with an engineering manager. Right before the interview, we had to reschedule. We found a new time, and the interview lasted an hour. The first half was about the company, and the second half was about C++ and multiprocessing basics. We both seemed interested in a second interview. After waiting two days to schedule, I suggested a follow-up time and offered another option. Two days later, I got an apology for the scheduling issues and was told to expect an invite based on my availability. The invitation never came, and a day after the proposed second interview, I got a rejection email. Not sure what happened internally, but the communication was definitely a problem.

Confirmed questions1 question
  • Could you explain the difference between a process and a thread?
Shure logo
Shure

Software Engineer Intern

Engineering

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

After my resume was selected, I got an email saying there would be a 5-minute recorded video to answer basic questions like why Shure? and why this role? Then, after two weeks, I heard back from the Recruiter. The next part had three rounds all in one: an HR Round with basic questions mostly about my resume and projects, a Manager Round where they asked a few questions from my resume and projects, and finally, a technical round. In the technical round, they asked 'Why Shure?', 'What is TCP and UDP, how is TCP faster than UDP?', 'Advantages of C#?', and to 'Design a database for a clothing website?', also considering how a developer would increase complexity for things like filters and discounts. Mostly, the questions were from my resume and their requirements.

Confirmed questions3 questions
  • Questions about TCP/IP.
  • What is C#?
  • Concentrated on database.

Shure Software Engineer Interview Questions

Quoted word for word from Shure interview reports.

Could you explain the difference between a process and a thread?

Read reports

Could you explain what happens when a browser page is reloaded?

Read reports

Have you seen OOP principles misused? Which OO design elements are most often abused, and how can we stop that?

Read report

Could you explain the core principles of Object-Oriented Programming?

Read report

Formats, difficulty and experience

Across all 18 Shure interview reports.

Interview formats

Technical 34.8%
Behavioral 34.8%
Coding 19.6%
Other 4.3%
Presentation 4.3%

Interview difficulty

Easy 5.6%
Average 94.4%
Difficult 0%

Candidate experience

Positive 55.6%
Negative 16.7%
Neutral 27.8%