IDeaS - A SAS Company Interview Questions
& Process

So the first step was a phone screening. After that, there was a HackerRank challenge with one Java question, one SQL question, and one systems design question. The final round was a mix of behavioral questions and a project presentation where you could do a code overview, demo, or talk about the high-level system design.

So I interviewed for a Senior Test Engineer position and it was kind of a bummer. The interview itself was pretty standard and not too difficult, but it became really obvious that the company's approach to QA is super old-school. The interviewers, who've been there forever, are all about manual testing and didn't seem to care at all about modern automation. Even though I'm really good at both manual and automation testing, they seemed to see my interest in automation as a problem. It felt like they don't want someone who's good at all aspects of QA, just someone who will only do manual testing like it's always been done. If you're looking to get better at test automation or work in a more up-to-date QA place, this probably isn't it.

The interview was about automation, focusing on scenarios and API automation testing. It included a coding question in Java about character counts in a string, a comparison of Regression Testing vs Retesting, an explanation of Agile methodology, and specific Selenium commands for window and alert handling.

I talked to the recruiter, which was good. Then there was HR, Hiring Manager/Director, an in-person panel, and a VP/SVP call. The company seems to be growing and changing, which is positive. The process had several stages, including a 2-hour in-person panel with sales scenarios and presentations. I had to cover my own expenses for the travel for this.