Tableau Interview Questions and Answers Part-1
Question 1
In a simulated scenario, we have numerous stakeholders for a dashboard. You have to interact with these stakeholders. How would you go about it?
In a simulated scenario, we have numerous stakeholders for a dashboard. You have to interact with these stakeholders. How would you go about it?
Answer
In a scenario where one dashboard has numerous customers at varying levels, (for eg, field staff, deputy regional manager, CEO etc.) the best option is to meet and obtain requirements from them independently. Every individual will have different business requisites and questions that need answering.
Every designation will have unique KPI’s (Key Performance Indicators) to analyze, definitive business questions to answer, different data-sets to inspect and display different details. We cannot expect one size to fit each and every individual. The acceptable method is to adapt dashboards according to client demands and requirements.
In a scenario where one dashboard has numerous customers at varying levels, (for eg, field staff, deputy regional manager, CEO etc.) the best option is to meet and obtain requirements from them independently. Every individual will have different business requisites and questions that need answering.
Every designation will have unique KPI’s (Key Performance Indicators) to analyze, definitive business questions to answer, different data-sets to inspect and display different details. We cannot expect one size to fit each and every individual. The acceptable method is to adapt dashboards according to client demands and requirements.
Question 2
Imagine a scenario with multiple stakeholders. Would you build numerous variations of the same visualization for them? How does your thought process work in this case?
Answer : In any scenario, if we talk to everyone at the same time, it is impossible to focus on one person. There is no “one” answer for different and unique questions. Every individuals’ needs are varied. I believe that if we create a single dashboard for all the customers in the enterprise, not even a single individual will gain from it.
We should tailor the dashboard accordingly to achieve the specific needs and requirements of each customer. It is necessary to understand their needs first, in order to create a solution applicable to their demands.
We should tailor the dashboard accordingly to achieve the specific needs and requirements of each customer. It is necessary to understand their needs first, in order to create a solution applicable to their demands.
Question 3
How would you implement reports access for both external and internal customers?
Answer : We have to devise, design and utilize a merger of row level security, roles and permissions required to protect the security of consumers and, custom tables. Our first step would be to have a discussion, at the server level, with our internal team. After that, a discussion with our external and internal customers is mandatory. We have to design the best solution according to the needs and requirements of the consumers.
Question 4
You have to design architecture which is robust, scalable and secure. How would you go about it?
Answer : The architecture design depends on a multitude of factors. Some of them include
- Types of users (internal and external)
- The actual number of users interacting with the dashboard
- Server model (perpetual or term)
- Licensing model (user-based or core-based)
Question 5
How do you communicate and build a rapport with stakeholders?
Answer : The first step is to properly understand and visualize the clients’ requirements. Accordingly, we should design and build the dashboard. The client must be aware of each and every development in the project. We should be transparent in our dealings and let them know if there is any change in the project delivery dates. Approval of the client is necessary to make any unforeseen changes.
Question 6
How do we agree upon and handle the expectations of the customers?
Answer :
- We have to be transparent with our dealings and honesty as a standard should be maintained.
- We have to set goals and mention how close we are to these goals when we converse with our clients every single time.
- Always make sure to promise less and deliver more. This will surprise the client and goodwill of the enterprise will increase.
- We have to constantly communicate with our clients.
- We have to constantly deliver status reports to our clients.
- We have to know our limits first before committing to a client.
- If there is any change in the project delivery date, the client must be intimated beforehand.
Question 7
How would you capture requirements?
Answer : There are many ways to capture dashboard/report requirements. Some of them include,
- We can use a business specifications document to capture requirements.
- We can use technical specifications document ( high level and low level) to capture requirements.
- We can use wireframe to capture requirements.
- We can use storyboard to capture requirements.
- We can capture requirements as User Stories.
Question 8
How do we capture business questions?
Answer :
We can capture business questions as user stories. The answer to each and every business question will form a story, which acts as the basic framework for designing and building the dashboard.
We can capture business questions as user stories. The answer to each and every business question will form a story, which acts as the basic framework for designing and building the dashboard.
Question 9
What should be done in the case of a delay or an issue that affects the final delivery of the project?
Answer :Communication with the client is key. The client must be notified immediately whenever a problem is encountered or a delay is sensed by our internal team, the client must be notified immediately. This is to ensure that the client does not incur any business impacts and if they do, they have a chance of notifying their customers way beforehand.
Question 10
How would you assure that the customer is satisfied with your choices, be it technicalities of a project or the advantages of choosing a specific design choice?
Answer : At the beginning of every project we must visually show our clients and customers, proof of concepts. This will assure the client that we understand what they require. It is mandatory to communicate the advantages of using a new approach if it is required.
Question 11
How would you dispatch delivery across the entire business enterprise?
Answer :The first task is to ascertain an experienced user or a power user. These users have more computing knowledge and understand business solutions well. We should showcase our solution to them and make sure they understand the benefits of it. Once power users are accustomed to the solution, they will help others in various fields across the enterprise, adopt the solution. We must analyze and roll out the solution phase wise. As a result, new requests and user questions will be easier to handle.
Question 12
How do we make certain the branding is uniform throughout the delivery?
Answer : We should ensure that our team follows the company blueprint/specifications. These include formatting, font, colors, logo, and any other branding material. We have to make sure that the dashboards are all uniform and consistent across the board. We should also cite everything in a document for people to understand and follow.
Question 13
How important is the documentation process in the project?
Answer :It is absolutely vital to maintain proper documentation. A few of the reasons are mentioned below.
Proper documentation will aid and assist other or new team members to analyze the report and make alterations if required.
This document can be used for auditing and change control purposes.
This document serves as the tool of reference when impact analysis of a current change (adding, removing or altering a new field etc) is raised.
It is always prudent to utilize tools that document the entire process. This optimizes resource time and helps to capture all the details more efficiently. Rapiddox is an example of such a tool.
Proper documentation will aid and assist other or new team members to analyze the report and make alterations if required.
This document can be used for auditing and change control purposes.
This document serves as the tool of reference when impact analysis of a current change (adding, removing or altering a new field etc) is raised.
It is always prudent to utilize tools that document the entire process. This optimizes resource time and helps to capture all the details more efficiently. Rapiddox is an example of such a tool.
Question 14
How do you plan on communicating with stakeholders during the design and building phase of the dashboards?
Answer : Our internal team arranges a weekly showcase for our stakeholders. This helps us to furnish the reports, conceptualize ideas, explore feedback, and emphasize the alterations. This process ensures that everyone is on the same page and on the right path.
Question 15
State the differences between storytelling data and showing data.
Answer : When computer analysts analyze the data to find a story in it and bring the data to life it is known as storytelling. Storytelling helps us to display the facts to the stakeholders. This enables quick understanding on part of the stakeholders and helps them to take decisions and actions quicker.
Showing data encompasses the presentation of data. Users may explore and seek solutions and answers from the self-serve analytics dashboard which presents this data. Showing data does not necessarily prompt an action on part of the stakeholder. It helps stakeholders analyze and explore different data sets.
Showing data encompasses the presentation of data. Users may explore and seek solutions and answers from the self-serve analytics dashboard which presents this data. Showing data does not necessarily prompt an action on part of the stakeholder. It helps stakeholders analyze and explore different data sets.
Question 16
What different tasks can server administration be used for?
Answer : Server administration can be used for a multitude of activities. Some of them include
- Installation of new server instances.
- Creating and modifying schedules.
- Addition of new users.
- Active Directory configuration.
- Maintaining existing and new users.
- SSO (single sign-on).
- Licensing.
Question 17
Have you ever compromised on quality to deliver unique client requirements?
Answer : Certain clients do not follow conventional standards of data visualization. Their requirements are unique. Such clients are not a rarity anymore. In the case of a different requirement, our team first and foremost, communicates the advantages and disadvantages of the process to the respective clients. At the end of the day, we have to follow and implement what the client tells us to do.
Question 18
What would you do in the case of an out of the ordinary report request? How would you prioritize your actions?
Answer : It is not uncommon to receive such report requests occasionally. Various teams give us ad-hoc reporting requests now and then. Usually, we follow the chain of command when we receive such a request. We respectfully ask the team to route the request via our manager. After that our manager delegates the work based on priorities.
Question 19
What are some of the third party tools we can use in the Tableau/Data visualization project?
Answer : There are multiple third-party tools available in the market today. Some of them include
- Tabmigarte – It helps us to migrate data between numerous environments.
- Tabjolt – We can test load using Tabjolt.
- Rapidox – We can use this tool to document workbooks.
- Powertools – We can use this tool to optimize Performance tuning by adopting the aptest practices.
- Tabmon – We monitor performance using Tabmon.
Qliksense
Qlikview
Pentaho
