Nuix Software Engineer Interview Questions
& Process

I had a really great time interviewing here. They sent over two smaller take-home assignments that were specific to the FE and BE tech stack. After I finished those, I had my technical interview. It was super relevant to the kind of stuff a software engineer actually does. The take-homes were a good jumping-off point for the technical questions, and then it moved into design talks and solving problems in real-world engineering scenarios. I actually enjoyed it a lot. It felt more like chatting with my own team than an outside interview. The team was so supportive and made me feel comfortable the whole time. I could really tell they have a good team vibe. After the technical interview, we did a behavioral round talking about different work situations. I did get an offer, but I turned it down for another role. Honestly, I'm still not sure if I made the right call because I really liked the team and what they work on.

The whole process includes a HackerRank coding challenge, an on-site whiteboard discussion, and a final Skype video call. The interview process wasn't super organised and the criteria felt a bit subjective. The HackerRank had 6 questions in 2 hours: 3 medium-level algo coding questions and 3 subjective questions on multithreading, performance, and troubleshooting. After that, I had the on-site interview, which was a bit messy; the first round was delayed because the interviewers were in a meeting. They asked about a past project and some high-level design stuff. The second on-site round was tougher with 2 engineers asking me to solve 2 algorithm problems with pseudocode on the whiteboard, which thankfully went well. The final stage was a Skype call, which I thought would be behavioral based on the invite, but it turned out to be another data structure question that I didn't quite grasp and didn't go great. I was rejected because of that last round, with feedback that they wanted an 'engineer' rather than a 'developer,' which I found a bit rigid. I feel like 'Software Engineer' should cover more than just data structures and algorithms, especially given the Java Web stack requirements in the job ad, but maybe their data mining focus means they lean heavily on data structures.

So there are like 3 phone/video calls first up, you know, talking to the recruiter, the hiring manager, and then an engineering manager. Then the main interview has you talk about your past experiences, answer some programming questions in Java or React, and then you do a little coding challenge.