Hamilton Group Interview Questions
& Process

There were two virtual interviews and a separate MS Excel test. The Excel test was untimed and quite challenging, intended to gauge MS Excel knowledge, but it wasn't graded. The two virtual interviews were more significant.

After my CV was sent in, I got a link for an automated test from Codality. I had to fix the framework setup because it was set to C++ instead of Python. I looked at the five tasks given. One was about Postgres, which wasn't something I had said I was good at. They said it would take 45 minutes. Just reading the tasks would have taken me 10 minutes. I wasn't up for doing them in that clunky framework, so I just closed the browser and backed out of the hiring process. It felt like a waste of my time and didn't really reflect what a developer does day-to-day. This approach seems lazy and poorly planned. Having spent the day before recruiting for my own company, I didn't see the point in how Hamilton was trying to judge a developer's skills. I wish I'd paid attention to other bad reviews of their process. Luckily, I didn't waste too much time. Also, if Codality wants to test Python skills, they should use a Python coder, not one written by a C programmer.

I was contacted by the internal recruiter after I applied and then an interview was arranged. I went through two interview stages, a first and a second. The second stage interview had an interviewer with a really bad attitude and a grumpy face, like they were annoyed to be interviewing me. They asked some really outrageous questions. I never got any feedback, communication, or updates, and it's been almost 3 months! Based on my interview experience, this is definitely not a company I'd want to work for, and I wouldn't want to work with those people. It's just another terrible organization with awful practices, culture, and behavior. Avoid this company.

I had a video call with two engineers, then a Codility test. After that, there was a video call with the Head of IT and Engineering, followed by a video call with the CTO. They didn't mention SQL at all in the job specs or Glassdoor, only Redis. SQL wasn't brought up in the initial engineer chat either. It was weird that 40% of the Codility test was SQL, felt like a waste of time.