Visa Inc. Qa Engineer Interview Questions
& Process

I had a phone call with the recruiter. Then there was an online test that involved a bot and a live coding session. After that, another phone call with the recruiter. The next step was a technical interview, and finally, I had a meeting with an HR specialist.

The interview process had three steps: an online phone screen, a Hackerrank test, and an onsite interview. The Hackerrank was poorly designed and felt random. The onsite interview was lengthy, and the team seemed to lack experience in conducting interviews. For instance, one interviewer asked about calculating data center load using JMeter. Some directors were quite arrogant, having been at the company for over a decade and expecting candidates to possess similar deep domain knowledge. Overall, the Glassdoor reviews for Visa seem accurate; it feels like a government-type environment where people are just holding their jobs. My impression from the onsite was that it's not a great place to work. The recruiter was also unprofessional. After saying the team liked me, he mentioned they needed to review other candidates before deciding, which left me wondering what to do next. I've since moved on and accepted another offer.

The interview process had three rounds. The first round asked about Test Plans, project risks, Agile methodologies and team location, testing High Availability in data centers, deleting trailing spaces in Perl, credit card authorization terminology, factors to consider before accepting a job offer, and the pros and cons of Agile. Round 2 involved designing test cases for a login form including database testing and business rules, testing in Soap UI beyond WSDL, differentiating between class and instance variables, debugging a Java program error, and understanding security testing, inner vs outer joins, and unique vs primary keys. Round 3, conducted by a developer, focused on Junit vs TestNG, testing Web Services, regression testing frequency, white box vs black box testing, unit testing concepts and compilation errors, the importance of testing, troubleshooting testing issues, finding files with specific text in subdirectories, and deciding on test automation.