Taro Logo

Software Engineer Interview Experience

July 1, 2013
Neutral ExperienceNo Offer

Process

The process began with an HR phone screen to assess suitability. This was followed by two technical phone screens covering basic object-oriented concepts, data structures, fundamental algorithms, and software engineering practices.

The on-site interview, while a positive experience overall, felt like interview overload. The day ran from 9:30 AM to 5:00 PM, ostensibly to allow for team member interactions. It consisted of eight 1:2 interviews, where candidates were expected to solve two questions in 45 minutes, discuss implementations, and allow time for Q&A. The difficulty of the questions wasn't exceptionally high, but the sheer duration was challenging.

By the final round, I was mentally exhausted. It seemed they saved the most demanding problem for last, asking for a design and coded solution to a dynamic programming problem. Unfortunately, I could only stare at the whiteboard.

I wish the on-site interview loops were shorter.

Questions

DP problem - similar to N Queens. Was solvable, but not after 7(x2) rounds of white-boarding!!!

Was this helpful?

Interview Statistics

The following metrics were computed from 41 interview experiences for the Tableau Software Engineer role in United States.

Success Rate

29%
Pass Rate

Tableau's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive66%
Neutral22%
Negative12%

Candidates reported having very good feelings for Tableau's Software Engineer interview process in United States.

Tableau Work Experiences