Smiths Detection Software Engineer Interview Questions
& Process

I was initially contacted by an interviewer who asked some basic C++ and multithreading questions. After passing that, I proceeded to the first round with a staff engineer. This interview was more of a self-assessment, starting with a question about polymorphism. I was then asked to implement a virtual function and then build my own vector class in an IDE. I struggled a bit with the copy constructor for the vector, and the interviewer provided some guidance. My feedback from the interview was that I needed to improve my basic understanding, even though I managed to answer and implement most of the questions. Because of this feedback process, I feel it's best to avoid this company.

It was a pretty straightforward process. The interviewers asked some basic questions about Java and OOPS concepts, nothing too difficult. For a developer role, make sure you're solid on C++ or Java. If it's a testing role, then Python is key.

I had a 3-stage interview process for a software engineer role. It started with HR, then a technical interview with the tech lead, and finally a round with the hiring manager and another person. They told me I got the job right after the third interview, but then there was a 2-week delay in getting the formal offer because the VP was traveling and needed to approve it. After chasing them for updates, I was finally told that the VP decided not to fund the position. This whole experience, along with online reviews, makes me question how this company operates. It's baffling how they could post a job, interview me, tell me I'm selected, make me wait, and then pull the plug. I wouldn't recommend wasting your time here.