ReliaQuest Security Analyst Interview Questions
& Process

So, I was contacted on LinkedIn by a recruiter for ReliaQuest. The role sounded awesome given their rep, so I went for it. My recruiter was super helpful and clear about what to expect. First, there was a screening call with some technical stuff and a chat about my background and the job. Then, I did a tough technical assessment, but it was doable. After that, I had an hour-long technical interview with two Senior Employees. They hit me with quick technical and scenario questions – it really tests your tech skills and how you solve problems, so prep is crucial. Next up were behavioral and cognitive assessments, plus a writing sample. The final step was an in-person leadership interview, which was intense but really interesting. What struck me most was everyone's dedication to doing great work at ReliaQuest, from the recruiters to the leaders. It was a great experience, and I'm hyped to join the team!

A recruiter from ReliaQuest contacted me on LinkedIn about a security analyst role. We set up a call, and I was really interested, so I decided to move forward. The first interview was a chat about the job details like pay, benefits, and hours. The recruiter was super professional and friendly, which helped me relax. They asked some basic technical questions to gauge my knowledge. After passing, I got a link for a test with 25 technical questions covering both defense and offense scenarios. Once I passed that, I had my second interview with two senior team members. This one was tough, with deep technical questions, so real preparation is key. The interviewers were very knowledgeable and made me feel comfortable, plus they were really positive and upbeat. This stage gives a good sense of the kind of person ReliaQuest values. After the technical round, I was sent two tests for behavioral and cognitive assessments. If all those were cleared, an onsite interview was scheduled. First, the local manager interviewed me to check my mindset, asking a few scenario-based questions that weren't overly technical. Then, just when I thought it was over, I had another interview with the leadership team, which mixed behavioral and technical questions. The technical part was extremely challenging, so be ready! The whole process is a bit long, but it definitely shows what kind of employee the company is looking for. The recruiter stayed in touch, and I got interview/test results within 3-4 hours.

It started with a recruiter call, then a phone screen talking about the OSI Model and port numbers. After that, I moved to a behavioral interview that's pretty basic, just make sure you have specific situations to talk about using the STAR method. Then came the technical interview which was tough and lasted an hour, covering port numbers, DMZ topology, Nmap, WAFs, XSS, SQLi, CSRF, SSRF, and basic blue/red team topics. After passing that, there was a cognitive test and a behavioral test. The final interview was about an hour, a mix of technical and behavioral. I declined the offer because of a comparable offer, and concerns about company culture, management, and burnout, plus the lack of remote work.