As LogicMonitor is part of Vista Equity, they do require something that resembles an IQ/reasoning test as part of the hiring process - you can Google to find out more about it, but it's something that every person at every Vista-owned company is required to do. If you're a fan of standardized tests and have reasonably good mental math and spatial reasoning skills, you'll do fine. Besides that, there was the standard phone screen, then a video interview, then an on-site. The majority of the interview process was a culture fit - some questions were asked regarding Linux and software stack familiarity, but in general I think they're looking for whether or not you're trainable, and more importantly, able to self-teach. Overall I was very pleased with the interview process, and received an offer, which I happily accepted.

There was an initial coding assessment (4 questions, 1-2 hours), followed by a 45 minute interview with the manager, and then two more 45 minute interviews with different members of the team/department. There was also a CCAT assessment (similar to an IQ test). I appreciated that the process was quick with little to no delays; many things could be scheduled next-day. I had a great interview with the manager. He was fantastic at probing to find out exactly where my knowledge started and stopped. We were able to go into detail about things I knew a lot about, and even cover some niche topics. I felt like I was accurately able to showcase my depth of knowledge and experience. I'm disappointed in the team member interviews. They seemed unwilling to probe to find out how much I actually knew, and defaulted to assuming that I didn't know enough. For example, I was asked about Kubernetes CRDs; I've never had a reason to write a custom CRD before, but I've deployed them. There are so many other aspects of Kubernetes that I've written specs for and deployed hundreds of times (deployments, statefulsets, daemonsets, services, ingresses and ingress controllers, configmaps and secrets)... but I wasn't asked to go into depth about any of these. It was like immediately upon hearing I haven't really used X much before, I must not know much about Y or Z either. DevOps/SRE is a broad field and experience with tools isn't always 1-to-1 but what's important is how you solve problems and build solutions. A good interview is able to keep pushing to figure out what you do know, not just immediately discount you from what you don't, IMO. And where more depth or detail is required, ask for it! Don't expect mind reading or just say "ok" and move on to a different topic.