Le processus a pris 1 jour. J'ai passé un entretien chez Intuit (San Diego, CA) en janv. 2008
Entretien
Group of 10-12 people has been formed at 8:00 am, and an HR person assured us that we all going to be interviewd for different positions and we are not competing. After this announcement HR guys mangaed us to go from the office to office interchangebly, meaning the same interviewers talk to each of us in turn. The questions was divided by general category, such as to describe your biggest achievement / failure and why you want to join company, and technical questions. Some interviewers asked strictly technical questions, some only general and some asked questions from both categories. I was very impressed when I learned that all of interviewers passed training how to interview candidates and followed instructions what questions to ask.
Questions d'entretien [2]
Question 1
What is the biggest achievement when you worked on yor project?
One of interviewers gave me a piece of code where 'while' loop incorporated several embedded 'for' loops and several variables was initialized in one of the loops, and asked me to describe what this code doing.
J'ai passé un entretien chez Intuit (New York, NY)
Entretien
The interview process consisted of multiple stages. It began with an initial screening call with a recruiter, where they asked about my background, current role, and interest in the position. This was followed by a technical interview that focused on test automation, API testing, and problem-solving. I was asked to write test cases, explain bug lifecycle, and walk through test strategies for both frontend and backend applications. In the final round, I had a behavioral interview with a QA manager and a developer to assess team fit, communication, and collaboration skills. Overall, the process was structured, professional, and took around two weeks from the first contact to the offer.
Questions d'entretien [1]
Question 1
They asked me to describe how I would design an automated test strategy for a web application with both frontend and backend components. I had to explain the tools I would use, such as Playwright for UI testing and Postman or REST-assured for API testing, as well as how I would structure the test cases, manage test data, and integrate the tests into a CI/CD pipeline.