Tableau Portfolio Projects: 6 Dashboard Ideas That Show Hiring Managers You Can Do the Job

A hiring-ready Tableau portfolio project answers a business question with an interactive dashboard and documented findings, not a chart export. Publish your work on Tableau Public and get human feedback on whether your conclusions follow from the data.

What makes a Tableau project portfolio-ready

A portfolio-ready Tableau project shows how you answered a question, not just how you made a chart. A tutorial dashboard may look polished, but it gives a hiring manager little evidence that you chose the metrics, checked the data, or interpreted the results yourself.

Skillify Solutions recommends documenting the business question, analytical workflow, findings, and limitations. Treat that as a useful practitioner framework, not a universal hiring standard. For example, a sales dashboard could identify a region with declining revenue while noting that the dataset lacks information about pricing changes. Ask an instructor or peer to challenge your interpretation before you publish. The six ideas below each give you a business question, charts to build, and skills the finished dashboard can demonstrate. If you are still getting oriented, start with what Tableau is and what it is for.

Sales performance dashboard

A sales performance dashboard should answer which regions or products underperform and what the available data suggests about why. Sales dashboards are a common beginner project, so a chart of total revenue alone gives a reviewer little evidence of your judgment.

Use a transaction-level dataset with dates, regions, products, sales, and profit. Put sales, profit, and profit margin in KPI cards, then show monthly trends with a line chart and compare products or regions with sorted bars. Calculated fields for profit margin and growth over the previous period demonstrate that you can build useful measures rather than rely on raw totals.

HR attrition dashboard

An HR attrition dashboard can show how you analyze people-related data without overstating what it proves. Use a public dataset with employee records to ask which departments and roles have the highest share of employees marked as having left, and how that share varies by tenure or pay band.

Start with a bar chart of attrition share by department, with the employee count beside each rate. Add a role filter and a chart that compares attrition share across tenure bands. These views demonstrate segmentation and correlation visualization while giving a reviewer enough context to judge whether a high rate comes from a small group.

Public health data dashboard

A public health dashboard can show how you handle a large dataset before you build charts. Use public county-level health estimates, such as CDC PLACES, to ask which regions report higher diabetes prevalence and how those estimates change over time.

Build a map that shades counties by prevalence and a line chart that compares selected regions across available years. Add a filter for the health measure so a reviewer can test whether the pattern holds for another outcome. Before charting, check for missing counties, changes in measure definitions, and inconsistent year labels. Use rates rather than raw case counts when comparing places with different populations, and note when the source provides estimates rather than direct counts.

Public transit performance dashboard

A public transit dashboard can show how you work with operational data that needs careful interpretation. Choose a city transit agency’s public dataset with route and time fields, then ask which lines have the most delays during peak hours. Check what each field measures before building the dashboard. A late arrival, a canceled trip, and a missing record should not count as the same outcome.

Use a line chart to compare delays by hour of day and a bar chart to compare routes. If the data includes stop coordinates, map where delays occur and let viewers filter by route and day of the week. Add a short note explaining how you defined a delay and whether the dataset covers all trips or only reported incidents.

E-commerce funnel analysis dashboard

An e-commerce funnel dashboard shows where shoppers stop between a visit, a product view, a cart addition, and a purchase. For a growth or marketing analytics portfolio, the business question is which step loses the largest share of shoppers and whether that pattern differs by traffic source or device.

Choose a public, anonymized event dataset with session IDs, event types, and timestamps. Build a funnel chart showing the number of sessions that reach each step, then calculate the conversion rate between consecutive steps in Tableau. Add filters for traffic source and device so a reviewer can test whether a drop-off affects all sessions or a narrower group.

Customer churn dashboard

A customer churn dashboard asks which customer segments cancel most often and what factors appear alongside those cancellations. Use a public subscription dataset with cancellation status, tenure, contract type, and monthly charges. Show churn rates by contract type in a bar chart, then use a heat map to compare tenure and monthly-charge groups. Display each group’s customer count so a high rate based on a small sample does not mislead the reader.

To demonstrate predictive-adjacent thinking without a machine-learning model, create a calculated field that flags active customers who match segments with high historical churn. Label the flag as a screening rule, not a prediction. Explain which customers you would prioritize for a retention review and what the dataset cannot establish. A higher churn rate among customers on one contract type, for example, does not prove that the contract caused them to leave.

Publishing on Tableau Public so it looks hiring-ready

Create a Tableau Public profile and use it as the destination for your finished dashboards. Before you publish a workbook, remove any private data and write a title that states the business question. Add a short description of the dataset, your main finding, and any limits on what the data can tell you.

Give reviewers a way to test your finding. Add a visible filter for a useful category, such as region or date, and configure a dashboard action so selecting a chart updates another view. For example, clicking a sales region could show that region’s monthly trend. Test the interaction yourself and make sure a reviewer can return to the full view.

Tableau’s help pages cover the exact settings: how to publish a workbook to Tableau Public, how to set up dashboard actions, and how to create device-specific dashboard layouts. Menus can shift between versions, so check them against the release you use.

What hiring managers actually check

A reviewer should be able to find your business question and answer within a minute. On a sales dashboard, put “Which regions lost margin?” above the charts, then show the region and product breakdown behind your finding. If you leave the conclusion unstated, the reviewer has to do the analysis.

Your write-up should also mark the limits of your evidence. On an HR attrition dashboard, a link between tenure and departures does not explain why employees left if the dataset lacks departure reasons. Skillify Solutions recommends presenting the question, findings, and limitations alongside the dashboard so a reviewer can see your reasoning, not just your Tableau skills. Ask another person to challenge your interpretation before you publish. Layout matters too: the dashboard design principles that make internal reports usable apply just as much to portfolio pieces.

Pre-publish checklist

• Check the data. Reconcile totals with the source file, test calculated fields, and note missing records that affect your findings.

• Check the title and labels. Name the business question in the title, and show units, date ranges, and definitions for metrics such as churn or attrition.

• Test the interactivity. Use every filter and dashboard action, then confirm the charts update as you intended.

• Add a short write-up. State where the data came from, what you found, what the data cannot establish, and what you would investigate next. Ask an instructor or peer whether they can follow your reasoning.

• Test the link. Open your Tableau Public dashboard in a private browser window to confirm an employer can view it. Before sharing, check that the dashboard answers the business question you set out to investigate.

FAQ

How many Tableau projects do I need?

Start with one or two finished projects that answer different questions. A sales dashboard might show how you compare performance across regions, while a transit dashboard might show how you investigate delays. Check the calculations, explain your findings, and publish each project before starting another.

Is Tableau Public free?

Tableau Public lets you create and share public visualizations for free. Treat anything you publish there as public. Before uploading a workbook, remove private records, personal information, and data you do not have permission to share.

Turn projects into a job-ready portfolio

For a beginner analyst, one or two finished, published Tableau projects can show more judgment than five half-finished dashboards. Each project should explain the question you investigated, the evidence behind your findings, and the limits of your analysis. Pick one dataset this week and build around a question you can answer. Before you share it, ask another analyst to challenge your conclusions. Pair it with a query-based project, like the ones in our guide to SQL portfolio projects, so employers see both how you get the data and how you present it.

If you want structured feedback while you build, the Data Analytics Course is an 11-week live program with one class per week and about 6 to 8 hours of weekly work. It covers SQL, Python, visualization and data storytelling, statistics, experimentation, and AI-assisted analytics, and ends with a capstone and career-readiness week. Developers who want to ship LLM-powered applications can look at the engineering track instead.

• Data Analytics Course

• AI Engineering Course