Wiz Interview Questions
& Process

The interview process was great! I didn't succeed all the way through as after the second interview it was clear that the role did not align with my career direction. It would have been five stages: 1) Recruiter Interview 2) Hiring Manager Interview 3) Interview with two people already in role 4) Presentation to demonstrate role competency (Configuration of items in Sandbox env). You would work in the sandbox and then present back your findings in way of PowerPoint 5) Interview with EMEA Solutions Engineer.

Started with an HR screening to go over my background and the interview process. Then there was a take-home test with AWS and Kubernetes questions that I had two days to complete. Had a good chat with the hiring manager, mostly about customer experience and my past roles. Next, I went through two 45-minute technical rounds that involved scenario-based questions and tested my skills in Linux, AWS, and troubleshooting applications. After that, HR let me know I had great feedback and they were getting an offer ready. But then, they went silent for a whole month while preparing the offer. After I followed up a few times, they said they needed another month. When that month passed and I followed up again, HR told me the roles were filled or unavailable and presented a different position that was out of my time zone and required weekend work. I said I was open to it. We had another hiring manager call, then I waited six weeks, and finally got a generic rejection email without any specifics on why I wasn't a good fit.

It was a two-round interview process. The first round was a quick tech screen with the hiring manager. The second round was a panel interview where I had to build a technical lab environment. This lab included cloud infrastructure, infrastructure as code, and DevOps pipelines using Kubernetes. It was pretty time-consuming and the scope was quite open-ended. From what I've seen on Glassdoor, the panel interviews can be a bit hit or miss in terms of focus. For my interview, it zeroed in almost exclusively on Kubernetes. While the second panel interview is set up to be comprehensive, mine specifically felt like a Kubernetes engineering interview. There were very few questions about what I built, including cloud architecture, DevOps, or security concepts. The panel really focused on Kubernetes command-line questions and troubleshooting concepts. I still think Wiz would be a fantastic place to work, but I'm guessing there are some growing pains, possibly in areas like this interview process and with leadership injecting their own expertise into interviews, which isn't unusual in tech. The questions felt a bit outdated and strangely specific in certain areas.

The interview process had 5 rounds plus a take home test that was time-consuming. Wiz didn't give useful feedback. It turned out that 4 interviewers wanted a specific skill I didn't have, which they should have asked about from the beginning, especially after I completed a 4-hour take home test. My advice is to directly ask about the skills they need, rather than having the first few interviewers be clueless about the hiring criteria. It seems like interviewers don't communicate or are bad at their jobs. Maybe it was my fault for not realizing this. I passed the technical tests but wasn't selected, so don't waste your time interviewing here. Make sure to clearly ask what skills they are looking for. I had 3 different sets of interviewers asking for very different skills, and a recruiter who couldn't communicate the skills she was looking for. My advice to the company is to clearly state the specific skills you need, don't waste people's time. If you need someone with vast Kubernetes experience, just say so, don't wait until round 5 to mention it. I'd like those 7 or so hours of my life back.