Milliman Qa Engineer Interview Questions
& Process

The interview process was really quick and ran smoothly. I had three interviews in one week: first a phone screen, then a chat with the hiring manager, and finally a panel interview. Everything was good until the panel interview where there were two QA engineers. About 85% of the interview was questions from one of them, which were pretty standard and I felt I answered them well. But the other interviewer asked just one question that I thought was trivial and not really a good skill assessment. He asked about the internal workings of the .click() function in UI automation. I said it's a standard library method with not much custom technical complexity. The other panelist agreed, but he kept saying I was wrong. It was a bit weird because his point didn't align with standard knowledge of the tool. So, that part didn't feel very productive or like a good skill check. Even though the process was efficient and organized overall, that specific part of the panel interview felt a bit off for the level of technical evaluation I expected for the role.

The interview was pretty standard, focusing on DSA problems, diving deep into past projects, and testing basic SQL query knowledge. They really dug into projects and SQL. Having good communication skills definitely helps, and any prior experience gives you an extra edge.

I went through about 4.5 hours of Zoom interviews with various team members, managers, and recruiters. This took place over several weeks because people were on vacation. After all the interviews, I was expecting an offer, but the recruiters started low-balling me on salary. They offered the lowest rate in the range, which is way off for my area. While we were negotiating, they reposted the job with a higher salary range of 194k, and we were still haggling over 176k. It felt like a complete waste of time; their advertised 'range' was misleading, and the job didn't actually pay based on location as they claimed.