HR & Behavioural Tableau Interview Questions

Situation: during my final-year project I had sales data in spreadsheets that nobody could read quickly. Task: I wanted to make the trends obvious. Action: I learned Tableau, built a dashboard with KPIs, trends and filters, and presented it to faculty. Result: decisions took minutes instead of hours. I enjoy turning data into decisions, and a BI role lets me do that daily while growing in SQL and analytics.

Situation: a regional head could not understand a scatter plot of discount versus profit. Task: help him act on it. Action: I replaced jargon with a simple story, highlighted the quadrant of loss-making high-discount orders, added a clear title and tooltip, and walked through two examples. Result: he reduced discounts above 30 percent in two regions, and margins improved the next quarter.

Situation: while refreshing a weekly revenue dashboard I noticed one region had dropped 60 percent overnight. Task: confirm whether it was real. Action: I checked row counts in the source, found a failed ETL load for two days, informed the data engineering team and added a warning banner. Result: the leadership meeting used corrected figures, and we added an automatic row-count check to the pipeline.

Situation: a client needed a what-if pricing dashboard in one week. Task: I had not used parameter actions before. Action: I studied official help pages, built a small prototype on sample data, and asked a senior to review it before applying it to real data. Result: the dashboard launched on time and the client used it in a pricing review meeting.

Situation: the marketing team planned to increase spend on a segment they believed was growing. Task: check the trend before budget approval. Action: I built a cohort analysis using FIXED first purchase date and found repeat purchase rates in that segment had fallen for three quarters. Result: they shifted part of the budget to retention campaigns, and repeat purchases improved the next quarter.

Situation: a new team member struggled with LOD expressions and kept producing wrong totals. Task: help her become independent. Action: I set up weekly thirty-minute sessions, explained the order of operations with small examples, reviewed her workbooks with comments, and shared a checklist. Result: within six weeks she delivered a cohort dashboard on her own, and the checklist became part of team onboarding.

Situation: a director needed weekly sales numbers for a board call in three hours. Task: deliver correct numbers fast. Action: I clarified the exact metrics, reused an existing certified data source, built a simple view first, validated totals with finance, then improved formatting. Result: the numbers were ready in two hours and matched finance, and I later added the view to our standard dashboard.

Situation: I published a dashboard where a percent of total used Table Across and gave wrong numbers after a layout change. Task: fix it and rebuild trust. Action: I informed the stakeholder immediately, corrected the calc with Specific Dimensions, added a validation sheet comparing totals, and re-shared. Result: the issue was fixed within an hour, and I now test calcs after every layout change.

Situation: a sales head wanted a 3D pie chart for regional share. Task: deliver what he needed while keeping the chart readable. Action: I made both versions, showed how the bar chart made the rank and gap between regions obvious, and kept his preferred colours. Result: he chose the bar chart for the monthly review and asked me to apply the same style to other reports.

Situation: a supply chain team asked for an inventory dashboard without clear details. Task: understand what they needed. Action: I met users to ask which decisions they make, which KPIs and filters matter, refresh frequency and who will use it, then sketched a wireframe and confirmed it. Result: the first version was accepted with only minor changes, saving rework time.

Situation: finance wanted revenue after returns while sales wanted gross revenue on the same dashboard. Task: satisfy both without confusion. Action: I arranged a short call, documented both definitions, and added a parameter to switch between gross and net with a clear label and tooltip definitions. Result: both teams used the dashboard, and the definitions became part of our data dictionary.

Situation: I received eight dashboard requests in one week as the only senior BI developer. Task: deliver the most valuable work first. Action: I listed requests with business impact, effort and deadlines, reviewed them with my manager, delivered quick wins using existing data sources, and shared timelines for the rest. Result: high-impact requests were delivered on time and stakeholders appreciated the transparency.

Situation: in my internship I could not get a running total to restart each year. Task: solve it without wasting a day. Action: I reproduced it on sample data, checked documentation on addressing and partitioning, tried Specific Dimensions, and asked a senior with a clear description when still stuck. Result: I fixed it within an hour and wrote a note for the team.

Situation: the operations team tracked delivery delays in spreadsheets updated weekly. Task: give them daily visibility. Action: I built a dashboard on a scheduled extract with delay KPIs, a city map and a drill-down to late orders, and trained the team leads. Result: they spotted delays a day earlier, and late deliveries reduced by about 12 percent over two months.

I see myself growing from building dashboards to owning analytics for a business area. In the first two years I want to master Tableau, SQL and data modelling and get certified. Later I want to design data sources, mentor juniors and work closely with business leaders on decisions. I would like to grow within one organisation where I can see the long-term impact of my work.

Situation: a sales director asked me to remove returns from revenue on the leadership dashboard to show higher growth. Task: keep reporting accurate while meeting his need. Action: I explained the impact on other reports, showed gross and net side by side with clear labels, and escalated the definition to finance for a final decision. Result: finance confirmed net revenue, and the director accepted it.

Situation: an earlier dashboard I built had low usage after launch. Task: improve adoption on the next project. Action: I involved users in design, ran a short training session, added a how-to-use panel, set subscriptions for managers, and checked usage statistics monthly to remove unused views. Result: weekly active users doubled compared with the earlier dashboard, and feedback guided the next release.

Situation: my dashboard needed customer data that was spread across three systems. Task: get a reliable, single table. Action: I wrote clear requirements with grain, fields and refresh needs, shared sample SQL, and reviewed their view together, testing counts against source systems. Result: they built a curated table, my dashboard became simpler and faster, and we reused the table for two other reports.

First compare filters, date ranges and data refresh time between both sources. Check the aggregation used, for example SUM versus AVG, and whether joins have duplicated rows, which inflates totals. Use View Data to inspect underlying rows and COUNT the records. Check null handling and whether Excel has hidden rows or manual adjustments. Document the cause and fix it at the data source level.

Employee ID is numeric, so Tableau classified it as a measure. Right-click it in the Data pane and choose Convert to Dimension, and optionally Convert to Discrete. Now it acts as a label rather than an aggregated number. If you need the number of employees, use COUNTD(Employee ID) instead of SUM. Fixing default properties early avoids wrong numbers across all sheets.