Initially, the process involved a 30-40 minute phone screening, followed by an on-site interview. I did not pass the phone interview. The interview took about 15 minutes, as I felt the interviewer was not satisfied with my answers. The interviewer did not ask questions like, "Tell me a bit about your background" or "Why would you want to work for Intuit?"
It seemed strictly business-like, and the interviewer simply listened to my answers without comment, making it difficult to comprehend whether I had answered correctly or incorrectly.
What kind of difficulties have you observed when performing cross-browser testing?
What's the difference between an interface and an abstract class?
Have you ever faced a situation where you foresaw a possible bug that a developer would introduce and warned them beforehand? If yes, please explain.
Have you identified certain risks while testing?
The following metrics were computed from 2 interview experiences for the Intuit Software Development Engineer In Test role in United States.
Intuit's interview process for their Software Development Engineer In Test roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Intuit's Software Development Engineer In Test interview process in United States.