I had a technical phone interview, followed by a 4-hour in-office interview, and then a 1-hour interview with some upper management.
The phone interview was pretty typical. I was asked some general, basic black-box testing questions.
The 4-hour in-person interview was a bit more technical. Since I have some coding experience, they asked me to write a function that would take a random array of integers and see if the sum of two integers was equal to another value passed in (i.e., public bool findSum(int[] array, int sum)). The person asking this question definitely wanted me to consider performance. I answered this question well, in my opinion.
The last interview with the VPs didn't go so great. They asked me a couple of tough questions for which I didn't have great answers (i.e., if I were testing a piece of software that lived on top of a database, what extra test cases I would come up with for different languages). I came up with tests for every new character (FYI, the Chinese alphabet has thousands of characters) and a few other tests, but I definitely think they were looking for something specific that I didn't come up with.
Find the sum in an array.
(i.e., public bool findSum(int[] array, int sum))
The following metrics were computed from 1 interview experience for the Tableau QA Engineer role in Seattle, Washington.
Tableau's interview process for their QA Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Tableau's QA Engineer interview process in Seattle, Washington.