I applied through an employee referral and the process took 3 weeks - interviewed at Tableau Software in November 2013.
Interview Details – Phone screen and in person interview with 5 teams. 4 out 5 teams asked coding questions.
Interview Question – Find closet match in a BST Answer Question
Very Easy Interview
I applied through college or university and the process took 4+ weeks - interviewed at Tableau Software in April 2013.
Interview Details – HR phone screen, homework, technical phone screen, on-site interview
Interview Question – Implement binary search tree and reverse a string in C++ and Java Answer Question
I applied online and the process took 6+ weeks - interviewed at Tableau Software.
Interview Details – Had a series of interviews: 1 phone interview with HR, 1 phone interview with small team, an in-person interview with 8 different team members, 1 phone interview with manager, also had to write an essay…
There was a lot of waiting & calling me back in to check on one thing or another…Projected dates for a decision were prolonged several times...
Overall, I felt that the team was still relatively new & they didn't quite know how to go about the interview process or what they really wanted/needed…I was more than qualified for the offered position, and graciously went through all the hoops they requested - Ultimately they went with their less-experienced internal candidate because they "wanted to demonstrate that they would promote from within" and "were loyal to their existing staff."
I applied online and the process took 3 weeks - interviewed at Tableau Software in November 2013.
Interview Details – Interview through the open session interviews. I spent 3 hours doing mini interviews with different members of the team with scenarios such as "What would you say to this client" or "Sell me this item". Overall it was quite smooth and everyone was great to work with. At the end, they invited me to prepare a demo for the following week.
During the product demo, they want to see your use of Tableau and less the who presentation you have prepared. But mind this, definitely prepare a full presentation as if it was a product demo to a potential customer. Also, USE YOUR OWN DATA. I don't care where it comes from, but they have seen the sample data so much they could walk you through it in your sleep. Be fun and original.
Interview Question – Sell me this pen. You have fifteen minutes. Go. View Answer
I applied through an employee referral and interviewed at Tableau Software.
Interview Details – Got referred by a friend, and then went through a technical phone screen. Nothing hard, just questions about items on my resume. Went to an onsite interview and was asked to write some basic algorithms. Was asked a lot of questions about how to optimize my solutions to make it run faster. Was also asked how to test each function, had to list out inputs and outputs that I would apply to each function.
Interview Question – Explicitly asked not to share questions. Answer Question
I applied online and the process took 4+ weeks - interviewed at Tableau Software in November 2013.
Interview Details – get me quickly within two weeks
Interview Question – a maze question that ask you to get out of the maze View Answer
I applied through an employee referral and the process took 5+ weeks - interviewed at Tableau Software in October 2013.
Interview Details – I interviewed twice for a Solution Architect role that paid up to $145-160k total comp ($105-120k base, plus ~10-15% bonus, plus restricted stock units that would vest over four years) with up to 80% travel required. (This is what HR told me in the first interview.) I share this info in the interest of transparency so that others going for the same role may know what compensation range to expect.
Both interviews appeared to go very well and I was promised two deeply technical interviews plus a complex demo I would be asked to deliver. (They said they were hiring two of these roles every month to keep up with growth.) An offer seemed assured were these subsequent interviews and my demo to also go well.
During my first phone interview I was asked to spend a couple hours getting to know the software and build an example dashboard which I shared with the interviewers although HR failed to hand it off to the next interviewer as I thought they would—after I gave him the dashboard, the second interviewer remarked that he was impressed given I had no background in their particular product but had obviously started to pick it up quickly.
The disappointing aspect of the process was that I was an internally referred candidate, and therefore a candidate to treat a bit better; and uniquely well-qualified and well-known from a competitor. However the HR department dropped the ball several times on following up with me. My internal contact had to remind HR twice to contact me after they failed to respond to my follow-ups on more than one occasion.
So—After being congratulated and assured more interviews, they dropped the ball again, never following up and not responding to my email wondering about scheduling those promised next two interviews. My internal contact was exasperated and reported the situation to their HR VP. My contact's complaint finally yielded a lackluster HR apology and response asking if I wanted to continue interviewing. I declined at this point, as it seemed they were insincere from the get-go. Perhaps they had second thoughts about my candidacy but they were not forthright about it.
The experience left me with a bad taste in my mouth about the organization. It's probably better once you get through the front door but be wary of a recruitment process than might string you along.
Interview Question – Questions were perhaps too easy. A few technical questions about architecture, SSO, Web app tiers, etc. but no challenging questions like "tell me about a project that failed." Both interviews were perhaps suspiciously soft. Answer Question
I applied through a recruiter and the process took 2 weeks - interviewed at Tableau Software in August 2012.
Interview Details – Step 1: call with recruiter
Step 2: download product (if you're not a former customer)
Step 3: use the crap out of the product and fall in love with it...or just stop the process
Step 4: Call with hiring manager
Step 5: Build a workbook with specifications given by Recruiter
Step 6: Call with colleague for technical interview
Step 7: In person interview: demo the workbook you've built. Show your analysis skills, your ability to talk to customers, discuss, think on the fly. Show your creative problem solving
Step 8: Accept Job offer
Interview Question – I later found out that the technical expectations were much higher than I originally thought. SQL, full understanding of databases, connections, networking, servers, etc. will be highly valued in this role. HOWEVER, if you can't comfortably talk with customers, you'll have a hard time. Answer Question
Negotiation Details – I didn't negotiate.
Very Easy Interview
I applied online - interviewed at Tableau Software in October 2013.
Interview Details – 1. 15 Minute phone interview
2. Onsite Interview
3. 15 minute written communication
Pick one of four questions
Why work at Tableau, What technology you like and how you learn, The best way to provide customer service,
4. One on one interview 15 minutes with 22 questions
My personal opinion is this process was a waste of my time and theirs.
Interview Question – What is: A Row, A Field, three databases, what is the output of this sql query, what does group by do
what is 127.0.01, if a user cannot connect to another computer, difference between relational database and a Cube, average, median, standard deviation, parts of a computer network, and more View Answer
I applied online and the process took 2 weeks - interviewed at Tableau Software in July 2013.
Interview Details – Started with an HR phone screen for possible fit. 2 rounds of technical phone screens [ Basic OO concepts, DS, basic algos and S/W Engg practices]. On-site : Though it was a great experience, it was interview overload - 9:30 am - 5:00pm (on the pretext of candidate being able to meet team members). 8 rounds of 1:2 interviews(so, you would need to solve 2 questions in 45 mins, discuss the implementation and leave some time for Q&A). Nothing stood out as being extremely difficult but for the duration.
I was brain dead by the last round, and it looked like they had kept the best for the last! Was asked to come up with design and code solution to a DP problem in the last round...the best I could do was stare at the white board.
I wish the on-site loops were shorter.
Interview Question – DP problem - similar to N Queens. [Was solvable, but not after 7(x2) rounds of white-boarding!!!] Answer Question
2 people found this helpful
Pros: “Unbelievable talent, excellent product, great visionary leadership by co-founders. The good and bad of hiring such a high level of personnel is that it often takes a reaaaally long time to…” “Unbelievable talent, excellent product, great visionary leadership by co-founders. The good and bad of hiring such a high level of personnel is that it often takes a reaaaally long time to get the team fully staffed for the needs to be met. However, the members of my team are all the best and brightest and I'm glad to work among them. It's a lot of fun to be on board with one of the premier software companies in the world right now. Open door policy to talk to other members of the company: Product Management, Engineers, Developers have all been very open and willing to help me with questions and growth. The communication among colleagues is great.” – Full Review
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
Your response will be removed from the review – this cannot be undone.
No thanks –