Software Engineer Interview Experience - Seattle, Washington
Process
The day involved a full-day onsite interview loop.
It began with a 15-minute meeting with the recruiter.
This was followed by a series of four tech interviews.
Two engineers attended each interview round.
They all opened with some background about themselves and their projects, then we went straight into the tech questions.
Afterwards, I was given time to ask questions of the interviewers.
At noon, I was taken to lunch by two engineers. We had more discussion, but no tech questions, during that hour.
Some of the interviews were conducted with one person in the room and one person teleconferencing in.
Questions
Code an iterator that returns the in-order traversal of a binary tree.
Was this helpful?
Interview Statistics
The following metrics were computed from 16 interview experiences for the Tableau Software Engineer role in Seattle, Washington.
Success Rate
Tableau's interview process for their Software Engineer roles in Seattle, Washington is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Tableau's Software Engineer interview process in Seattle, Washington.
Tableau Work Experiences
- 4.0Great Product, Ruined CultureSoftware Engineer • Current EmployeeSeattle, Washington, United StatesMarch 18, 2024Pros: Great product to work with.Cons: Salesforce acquisition ruined the culture.
- 5.0Fun Place, Growing FastSoftware Engineer • Current EmployeeSeattle, Washington, United StatesApril 20, 2016Pros: Great treatment for the employees and a lot of fun.Cons: Almost nothing. Maybe that is growing like crazy.
- 1.0Terrible place for women in techSoftware Engineer • Former EmployeeSeattle, Washington, United StatesNovember 23, 2017Pros: There is a paycheck, but not competitive with market rates at all.Cons: - The plushy "quiet rooms" are a joke. Many female devs have experienced being locked out of the rooms by unscheduled male devs who want to use the rooms as their own private office/game rooms (because the general office space does suck in terms of quietness and privacy). There were over 30 documented cases of being locked out, and HR still refused to even send a general email out regarding the situation. Frankly, I was horrified by how badly a federally required right was being (mis)managed by this business. - Lots of mansplaining. Very bro-centric culture. - Chaotic development environment. Code quality is non-existent and the bug load is heavy. Managers have historically done a terrible job at prioritizing tech debt and are now paying the price by losing many of their key developers. - Attrition is at an all-time high.
