Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Salesforce hiring for Tableau roles
Salesforce is a cloud software company best known for its CRM platform, along with products such as Tableau, Slack, MuleSoft and Data Cloud. Its India centres in Hyderabad and Bengaluru handle large parts of product engineering and support. It hires for software engineers, quality engineers, data engineers and analysts working on CRM, analytics and AI features.
For Tableau roles, this Salesforce practice set focuses most on Dashboards and Tableau Server (6), Data Connections and Modelling (5), Filters, Parameters and Actions (5), LOD Expressions (4). It has 2 easy, 16 medium, 12 hard questions, so you can start easy and work up to the harder ones.
Company type
Product
Headquarters
San Francisco, California, USA
Main India offices
Hyderabad, Bengaluru, Mumbai, Gurugram
Salesforce Tableau interview process
Online coding assessment
Technical round 1 (DSA)
Technical round 2 (design or domain)
Hiring manager round
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for SalesforceStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
✓ 3 questions free • Unlock the rest in seconds
01
You get the error cannot mix aggregate and non-aggregate arguments. How do you fix it?
The formula mixes a row-level field with an aggregated one, such as IF [Sales] > AVG([Sales]). Either aggregate everything, for example IF SUM([Sales]) > 1000, or make everything row level. If you need to compare a row with an overall average, use an LOD such as [Sales] > {FIXED : AVG([Sales])}, which returns a row-level value that can be mixed safely.
02
How do you improve dashboard performance in Tableau?
Use the performance recorder to find slow queries and rendering. Use extracts with only needed fields and rows, aggregate data, reduce marks and sheets, limit quick filters and relevant values, prefer integer and boolean calculations, avoid heavy custom SQL, use fixed dashboard size for caching, and hide unused fields. Workbook Optimizer in Desktop also suggests improvements based on best practices.
Show and hide buttons let users collapse or expand a floating container, such as a filter panel or help text, by clicking a button. They save space on crowded dashboards and keep the main view clean. You enable it from the container menu with Add Show/Hide Button, and style it with images or text. They also work well for mobile layouts.
04
Sales team wants year over year growth for each month on a single chart. How do you build it?
Place MONTH(Order Date) discrete on Columns and YEAR(Order Date) on Color with SUM(Sales) on Rows. Add a quick table calculation Percent Difference, compute using Year, relative to previous. Each month now shows growth versus the same month last year. Alternatively calculate with LOOKUP(SUM([Sales]), -1) partitioned by month and addressed by year.
05
Monthly sales files arrive in a folder every month. How do you avoid manual work each time?
Use a wildcard union on the folder with a pattern such as Sales_*.xlsx so new files are included automatically on refresh. Alternatively, build a Tableau Prep flow with a wildcard input and schedule it with Prep Conductor. Ensure every file has the same column names and types. Use the Path or Table Name field to derive the month if it is not in the data.
Create a set on Category. Build a calculation: IF [Category Set] THEN [Sub-Category] ELSE '' END, and place Category and this calculation on Rows. Add a set action on select that assigns values to Category Set and removes them when cleared. Clicking a category expands only its sub-categories, creating an asymmetric drill down that standard hierarchies cannot do.
Key functions are RUNNING_SUM, RUNNING_AVG, WINDOW_SUM, WINDOW_AVG, WINDOW_MAX, LOOKUP, PREVIOUS_VALUE, INDEX, FIRST, LAST, SIZE, RANK, RANK_DENSE, RANK_PERCENTILE and TOTAL. They operate on aggregates, so arguments must be aggregated, such as RUNNING_SUM(SUM([Sales])). WINDOW functions accept start and end offsets for moving calculations.
08
Top 10 products do not change when the user selects a region. Why?
Top N filters run before normal dimension filters, so Top 10 is computed on all regions, and then the region filter removes some of those products. Add the Region filter to context, so it runs first and Top 10 is calculated within the selected region. The Region pill turns grey to show it is a context filter.
09
How do you publish a workbook to Tableau Server or Cloud?
Sign in through Server, Publish Workbook in Desktop. Choose the project, name and description, set permissions or inherit from the project, and decide whether to embed credentials or prompt users for data sources. Choose to show sheets as tabs if needed and include external files for extracts. After publishing, set an extract refresh schedule and verify the views in the browser.
10
A manager wants to download dashboard data into Excel but you must protect sensitive fields. What do you do?
Control capabilities through permissions: allow Download Summary Data but deny Download Full Data, or deny downloads entirely for some groups. Remove sensitive fields from the data source or hide them, and apply row-level security so downloaded data is limited to the user's scope. Provide a dedicated crosstab sheet with approved fields for export and document what is allowed.
11
How do you blend sales data with a targets file in Tableau?
Connect to both sources. Build the view with the primary source, for example Region and Month from sales. Switch to the targets source in the Data pane, check the link icon next to Region and Month so they are active linking fields, then drag Target onto the view. Tableau aggregates targets to those fields. Make sure the linking field names and values match exactly.
12
Count customers by the number of orders they placed.
Orders per Customer:
{FIXED [Customer ID] : COUNTD([Order ID])}
Convert it to a dimension and discrete, place it on Columns, and put COUNTD([Customer ID]) on Rows. The chart shows how many customers placed 1, 2, 3 or more orders, a common customer frequency analysis.
13
How do you use a parameter action to let users click a bar and change a reference line?
Create a float parameter, for example Selected Value. Add a reference line using that parameter. Then go to Dashboard, Actions, Add Action, Change Parameter, choose the source sheet, target parameter Selected Value, and source field SUM(Sales), with aggregation set as needed. Clicking a bar updates the parameter, and the reference line moves to compare other bars with it.
14
Management wants new versus repeat customers per month. How would you build it?
Create First Purchase Month: {FIXED [Customer ID] : MIN(DATETRUNC('month', [Order Date]))}. Then Customer Type: IF DATETRUNC('month', [Order Date]) = [First Purchase Month] THEN 'New' ELSE 'Repeat' END. Put MONTH(Order Date) on Columns, COUNTD(Customer ID) on Rows and Customer Type on Color. Validate a few customers manually to make sure classification is correct.
15
Two tables have different grains: daily sales and monthly targets. How do you model them?
Use a relationship between the tables on Region and a month key, since relationships keep each table at its own grain and avoid duplicating targets across days. In the view, aggregate sales to month level and compare with targets. If using joins, first aggregate daily sales to month in Prep or SQL. Blending on Region and MONTH(date) is another option.
16
Clicking a chart filters others, but users get confused when everything goes blank. How do you improve the experience?
Set clearing behaviour to Show all values instead of Exclude all values, add clear titles that show the current selection using dynamic text, and add an instruction line such as Click a region to filter. Use highlight actions where filtering is unnecessary. Provide a reset button through a parameter action or navigation button, and test with real users.
17
How do you create a navigation menu between multiple dashboards?
Add Navigation objects or buttons from the Objects pane, set each to go to a target dashboard, and style them with text or images. Place them in a horizontal container at the top of each dashboard for consistency. Use Go to Sheet actions for drill-through from charts. Hide sheets and use Show Sheets as Tabs off when publishing, so users rely on the custom menu.
18
A live connection dashboard on a large database is very slow. What options would you evaluate?
Check the performance recording to see slow queries. Options include switching to an extract with aggregation and extract filters, adding database indexes or materialised views, removing custom SQL, enabling referential integrity assumptions, reducing the number of marks and quick filters, and using context filters wisely. If real-time is not required, a scheduled extract usually gives the biggest improvement.
Tableau uses exponential smoothing models to forecast continuous time series. It chooses the best model, with or without trend and seasonality, based on the data and shows prediction intervals. You need a continuous date and a measure. Options include forecast length, aggregation level and ignoring the last incomplete period. It suits quick projections, while complex forecasting needs Python or R integration.
20
Leadership wants one dashboard that shows 25 KPIs. How do you design it without clutter?
Clarify the top five decisions the dashboard should support. Show 4 to 6 headline KPIs as cards at the top, group the others into themed sections or separate tabs, and use drill-down actions to detailed views. Use consistent formatting, small multiples and sparklines for trends. Prototype with users, gather feedback, and remove KPIs that nobody uses.
21
Using FIXED with SUM in the view gives a huge inflated number. Why?
FIXED returns a value repeated on every row at the fixed level. If the view is at a finer level, or at the total level, SUM adds the repeated values, multiplying the result. Use MIN, MAX or AVG to bring back the single value, or make sure the view level matches the FIXED dimensions. This is a frequent mistake when using table-level totals.
22
A CXO wants a dashboard that updates every 15 minutes during a sale event. How do you design it?
Assess whether the source supports frequent queries. Options are a live connection to an optimised warehouse table with pre-aggregated data, or frequent incremental extract refreshes if allowed. Keep the dashboard light with few marks, headline KPIs and a trend, and enable auto-refresh behaviour or ask users to refresh. Load test before the event and monitor during it.
23
A Snowflake or BigQuery live connection is costing a lot due to many queries. How would you reduce it?
Use extracts where real-time data is not needed, schedule refreshes outside peak hours, and aggregate extracts to required grain. Reduce quick filters with relevant values, limit dashboards that auto-refresh, and use published data sources so caching is shared. Work with data engineers on materialised or clustered tables. Monitor query history and cost per dashboard to target the worst offenders.
24
Business wants financial year April to March in reports. How do you handle it?
Right-click the date field, choose Default Properties, then Fiscal Year Start, and select April. Tableau then shows FY quarters and years based on April. For a label such as FY 2025-26, create a calculation: IF MONTH([Order Date]) >= 4 THEN STR(YEAR([Order Date])) + '-' + RIGHT(STR(YEAR([Order Date]) + 1), 2) ELSE STR(YEAR([Order Date]) - 1) + '-' + RIGHT(STR(YEAR([Order Date])), 2) END.
25
What are the performance considerations of LOD expressions?
Each LOD generates a subquery joined back to the main query, so many LODs on large live data increase query complexity. FIXED on high-cardinality dimensions such as Order ID can be expensive. Keep the number of LODs small, prefer extracts, use FIXED with minimal dimensions, and check performance recordings. Sometimes pre-aggregating in the database is better than complex nested LODs.
26
How do you build a waterfall chart showing profit build-up by sub-category?
Put Sub-Category on Columns and SUM(Profit) on Rows, add a Running Total quick table calc, and change mark type to Gantt Bar. Create a calculation -SUM([Profit]) and put it on Size so each bar extends from the previous total. Colour by profit sign and enable Show Row Grand Totals to display the final bar.
Moving Avg:
WINDOW_AVG(SUM([Sales]), -2, 0)
This averages the current month and the two previous months. Compute along month. Use a dual axis to show actual sales as bars and the moving average as a line, which smooths seasonal noise for trend analysis.
28
What is the difference between Only Relevant Values and All Values in Database?
For quick filters, All Values in Database shows every value of the field regardless of other filters. Only Relevant Values shows only values that remain after other filters, creating cascading filters such as states within the selected region. Relevant values need extra queries and can slow dashboards, so use them carefully on large data. All Values in Context is another option.
29
What are good practices for colour use in dashboards?
Use colour with a purpose: highlight key data and keep the rest neutral. Use sequential palettes for ordered values, diverging palettes around a meaningful midpoint such as zero profit, and categorical palettes with fewer than eight colours. Keep colours consistent across sheets, check colour-blind friendliness, avoid red and green only, and never use colour as the only way to convey meaning.
30
Write a calculation for year-to-date sales compared with last year to date.
YTD Sales:
IF YEAR([Order Date]) = YEAR(TODAY())
AND [Order Date] <= TODAY()
THEN [Sales] END
LYTD Sales:
IF YEAR([Order Date]) = YEAR(TODAY()) - 1
AND [Order Date] <= DATEADD('year', -1, TODAY())
THEN [Sales] END
Growth:
(SUM([YTD Sales]) - SUM([LYTD Sales])) / SUM([LYTD Sales])
Tips to crack the Salesforce Tableau interview
Learn Salesforce core ideas like multi-tenancy, objects and Apex basics, and know what Tableau and Data Cloud do.
Practise test automation concepts using Selenium or similar tools if applying for quality engineering roles.
Read about Salesforce's values of Trust, Customer Success, Innovation, Equality and Sustainability for behavioural questions.
Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
Practise the hard questions on this page aloud; Salesforce interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Salesforce Tableau interview?
Candidates usually go through 5 stages: Online coding assessment; Technical round 1 (DSA); Technical round 2 (design or domain); Hiring manager round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Salesforce Tableau interview?
This practice set leans on Dashboards and Tableau Server (6), Data Connections and Modelling (5), Filters, Parameters and Actions (5), LOD Expressions (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Salesforce interviewers ask you to walk through real work.
Are these the exact questions asked at Salesforce?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Salesforce's. They are not a leaked or verified list of past questions.
Where does Salesforce hire Tableau professionals in India?
Salesforce has large teams in Hyderabad, Bengaluru, Mumbai, Gurugram. Openings and locations change often, so check the Salesforce careers page and filter by city and experience.