24 Sep, 2026
When I look at data analyst portfolios, I notice one common problem. Many beginners list Python, SQL, Excel, Power BI, and Tableau as skills, but their portfolios do not show how they use those skills to answer real business questions. A strong data analyst portfolio should make the analysis easy to understand. The reviewer should be able to see the problem, the dataset, the cleaning process, the analysis, the visualisation, and the insight that came from the work.
I’m Riten, founder of Fueler, a skills-first portfolio platform building the career infrastructure for 100 million creative professionals. Fueler connects talented individuals with companies through assignments, portfolios, and projects, not just resumes or CVs. Think of it as Dribbble/Behance for work samples combined with AngelList for hiring infrastructure.
The goal is not to build ten dashboards just for the sake of having ten projects. The goal is to show that you can take messy data, ask a useful question, analyse it, and communicate what the numbers mean.
A strong data analyst portfolio should answer six simple questions:
This structure matters because a dashboard alone does not necessarily demonstrate analytical thinking.
Fueler's own data analyst portfolio guide follows a similar approach. Strong projects start with a problem statement and business context, document data collection and cleaning, explain the analysis and visualisation, and finish with actionable insights and outcomes.
If you are building your first portfolio, this guide to building a career portfolio that actually gets jobs can also help you structure the portfolio around proof of work rather than simply listing skills.
Ecommerce is one of the easiest areas to turn into a practical data analyst project because there are many questions you can investigate.
You can use an Indian ecommerce dataset containing orders, products, customers, locations, payment methods, discounts, delivery information, and order values. The exact dataset can come from a public dataset repository or a self-created dataset based on publicly available information. Be clear about the source and whether the data is real, anonymised, or synthetic.
The main objective could be to understand what drives ecommerce sales in India.
You could analyse sales by city, state, product category, month, customer segment, payment method, and order value. You could also examine repeat customers, average order value, discount behaviour, and cancellation rates.
Questions you can answer:
Tools you can use:
The final output could be an interactive ecommerce dashboard followed by a written analysis explaining the most important customer behaviour patterns.
This is also similar to the type of business-focused analytics work seen in Fueler portfolios. Mohammad Kayser, for example, has documented ecommerce-related work including an Amazon Product Recommendation System alongside other analytics projects.
What you can learn:
Indian startup data can make a particularly useful portfolio project because it allows you to combine business analysis with publicly available information.
You can collect data about Indian startups, funding rounds, industries, cities, funding stages, investors, and funding amounts from publicly available datasets.
Your objective could be to understand how India's startup ecosystem has changed over time.
For example, you could compare Bengaluru, Mumbai, Delhi NCR, Hyderabad, Pune, Chennai, and other startup hubs. You could also analyse which industries attracted more funding and whether funding patterns changed between different years.
Questions you can investigate:
A Power BI or Tableau dashboard could provide the visual layer, while SQL or Python can handle cleaning and deeper analysis.
The important part is to avoid turning the project into a simple list of startups. The analysis should explain the patterns in the data.
Fueler has also published recent content around Indian startup careers and hiring, making startup-related analysis a useful domain for a portfolio targeting Indian technology companies.
What you can learn:
Inflation is another strong public-data project because India has extensive economic data available through government and public statistical sources.
You can build a project around Consumer Price Index data and examine how prices have changed across different categories and periods.
Instead of simply plotting inflation, ask a more useful question:
Which categories have contributed most to changes in consumer prices?
You can compare food, fuel, housing, clothing, healthcare, transport, and other categories depending on the dataset you select.
You can also compare inflation trends across rural and urban populations if your dataset supports it.
Questions you can answer:
A good project could include a line chart for inflation over time, category-level comparisons, and a final written explanation of the major trends.
Do not stop at the visualisation. Explain what the trend means for households, businesses, or consumers.
What you can learn:
Food delivery provides an interesting way to study consumer behaviour.
You can build a dataset around orders, restaurants, locations, cuisine categories, order values, delivery times, ratings, discounts, and customer frequency.
Your main question could be:
What factors influence food delivery order behaviour in Indian cities?
You could compare customer behaviour across cities such as Bengaluru, Mumbai, Delhi, Hyderabad, Pune, Chennai, and Kolkata.
You can analyse whether delivery time, ratings, discounts, cuisine, or order value are associated with customer behaviour.
Possible analysis:
You could then create a Power BI dashboard with filters for city, cuisine, customer type, and order month.
For a beginner, this project is useful because it combines several skills in one case study without requiring complex machine learning.
What you can learn:
Public transport and road safety datasets can help you build a portfolio project with a clear social and operational problem.
Fueler has previously used a public-transit example to demonstrate how a data analyst can turn public data into proof of work. The example focuses on analysing several years of local transit data, identifying route inefficiencies, and using the findings to think about better scheduling.
You can create a similar project using Indian public datasets.
For example, analyse road accidents by state, city, vehicle type, road conditions, time of day, or month depending on the dataset available.
Questions you can investigate:
You could combine SQL for analysis with Power BI for visualisation.
The final case study should not simply say that one state has more accidents. Explain what patterns you found and what additional data would be required before making policy decisions.
What you can learn:
Financial inclusion gives you another strong Indian dataset project.
You can analyse publicly available banking data related to bank branches, deposits, loans, digital payments, financial access, or account penetration.
The goal could be to understand differences in financial access across Indian states and regions.
Questions you can investigate:
You can create a state-level dashboard and allow users to filter by year, financial indicator, and region.
This type of project is also useful for demonstrating SQL and dashboard skills because the data can contain multiple dimensions that need to be joined and transformed.
Debal Adhikari's Fueler portfolio provides a useful reference for this type of analytical presentation. His documented bank analytics projects use SQL, Tableau, Power BI, and Excel to analyse loan data across customer grades, states, payment information, and other variables.
What you can learn:
Another project I would recommend for students is an analysis of Indian startup hiring.
You can create a dataset containing startup roles, job functions, locations, experience requirements, skills, salary information where publicly available, and work arrangements.
Your objective could be to answer:
What skills and roles are Indian startups hiring for?
You can compare technology, product, marketing, design, sales, data, and operations roles.
Questions you can answer:
You could build a dashboard that lets users select a role and see the most common skills associated with it.
This project is particularly useful if you want to target startup roles because it connects data analysis with a real career question.
Fueler's recent Indian startup hiring content also highlights data science, data analytics, product analytics, SQL, Excel, Python, statistics, and data visualisation as relevant skills for candidates targeting startup roles.
What you can learn:
Sports analytics is one of the easiest ways to make a data portfolio more engaging.
The Indian Premier League provides years of publicly available match information that can be used to analyse team and player performance.
You can examine runs, wickets, strike rates, economy rates, venues, toss decisions, win percentages, player consistency, and team performance over different seasons.
The important part is to frame the project around questions rather than creating another generic IPL dashboard.
For example:
Does winning the toss appear to be associated with match outcomes?
Or:
Which players consistently perform across different seasons?
You can also compare team performance at different venues or analyse how chasing teams perform under different conditions.
Mohammad Kayser's Fueler portfolio already includes an IPL Analytics project, making his work a useful example of how sports data can become portfolio proof of analytical ability.
What you can learn:
Healthcare datasets can demonstrate that you know how to work with sensitive and complex information.
For a portfolio project, use an appropriately anonymised or public dataset and clearly state the source and limitations.
You could analyse disease prevalence, hospital admissions, demographic patterns, healthcare access, or disease outcomes depending on the dataset.
The objective should be analytical rather than pretending to provide medical advice.
For example:
How does disease prevalence vary across Indian regions and demographic groups in the selected dataset?
You can examine trends by age group, gender, location, year, or disease category where the dataset supports those dimensions.
A good case study should spend time discussing data quality and limitations. Healthcare data can contain missing values, reporting differences, sampling problems, and other issues that affect interpretation.
What you can learn:
Digital payments have transformed consumer behaviour in India, making payment data another useful portfolio area.
You can use public datasets related to digital transactions, payment volumes, transaction values, geography, or payment methods.
Your objective could be to understand how digital payment behaviour has changed over time and across different parts of India.
Questions you can investigate:
You could create an interactive dashboard with state, year, transaction type, and transaction-value filters.
The project becomes stronger if you connect the numbers to a business question, such as where a digital payments company might focus expansion or where transaction adoption appears to be changing.
What you can learn:
These projects cover different industries, but they follow the same analytical process.
The first step is defining the question. Do not begin with “I want to make a Power BI dashboard.” Begin with “What do I want to understand?”
The second step is finding the right data. Government datasets, public APIs, Kaggle datasets, company reports, and other legitimate public sources can provide useful starting points. Always document where the data came from.
The third step is cleaning the data. Real datasets are rarely perfect. You may need to handle missing values, inconsistent categories, duplicate records, incorrect data types, and unusual observations.
The fourth step is analysis. Use SQL, Python, Excel, or statistical methods to answer the original question.
The fifth step is visualisation. A dashboard should make the important patterns easier to understand, not simply display every available metric.
The final step is recommendation. Explain what someone could do differently based on the analysis.
Fueler's recent data analyst guidance recommends this same progression: business problem, data, cleaning and analysis, tools, discoveries, and recommended action.
Do not upload only a screenshot of your Power BI or Tableau dashboard.
A recruiter should understand your project even if they never open the dashboard.
I recommend structuring each project like this.
Start with one clear question.
For example:
Which Indian cities generate the highest ecommerce revenue and repeat-purchase activity?
Explain where the data came from, the period covered, number of rows, important columns, and any limitations.
Show what you changed.
This could include removing duplicates, handling missing values, standardising categories, changing data types, or creating calculated fields.
Explain the SQL queries, Python analysis, statistical methods, or Excel calculations used.
Show your dashboard or charts.
Do not include ten charts simply because you can. Use the visuals that help answer your original question.
Write the actual findings in simple language.
Instead of:
“Category A has a higher average.”
Write:
“Category A generated the highest average order value, suggesting that customers purchasing these products tend to place larger orders.”
Explain what a business, organisation, or decision-maker could investigate or do next.
Mention what your dataset cannot prove.
This is particularly important for public datasets. A correlation does not automatically establish causation, and a dataset may not represent the entire Indian population.
You do not have to build your portfolio in isolation. Looking at real portfolios can help you understand how other analysts present projects.
Mohammad Kayser has one of the broader analytics portfolios on Fueler. His profile describes him around data science, data analytics, machine learning, statistics, and solving real-world problems with data. His timeline includes projects covering an Amazon Product Recommendation System, IPL Analytics, Finance Analytics, SQL Employee and Customer Analytics, Sales Forecasting, and a Power BI Data Profession Survey Dashboard.
What makes his portfolio useful to study is the variety of datasets and analytical problems. You can see examples spanning business analytics, finance, ecommerce, sports, forecasting, and machine learning.
What you can learn:
Koustav Hazra describes his Fueler profile as a combination of data and design, and his profile includes eight projects.
Fueler's data analyst portfolio guide highlights his use of Tableau, Power BI, Python scripts, custom charts, interactive dashboards, and visual storytelling for management audiences.
What you can learn:
Vanshika Mishra has documented professional analytics work from her time at Philips. Her Fueler project describes monthly trend analysis of post-market surveillance data across multiple medical-device product groups and quality-monitoring dashboards used across more than 50 product groups. It also documents a self-service analytics spreadsheet that reduced manual reporting time by 40% and Power BI dashboards for more than 10,000 products that reduced manual reporting workload by 80%.
This is a useful example because the project does not only list tools. It connects analytics work to operational outcomes.
What you can learn:
Ritik Maity describes himself as a data analyst skilled in Python, Excel, Power BI, and other data analysis tools. His Fueler timeline includes a customer churn prediction project, a Vrinda Store Sales Analysis Dashboard, a data analyst internship, credit-card fraud detection, and breast cancer detection.
His Data Analyst Intern project documents analysis of customer and sales data using descriptive and inferential statistics, along with data audits and predictive analysis.
What you can learn:
Ishita Singh is another useful profile for people interested in the intersection of analytics, business, and product strategy. Her Fueler timeline lists experience as a Data Analyst at Barclays and projects including Fashion Brand Analysis for Snitch, Blue Tokai Coffee Growth Strategy, a Flipkart case competition, FMCG Strategy Analysis for Haldiram, a PwC corporate report, and Social Justice Data Dashboards.
Her portfolio demonstrates that data analysis does not have to exist separately from business strategy.
What you can learn:
You do not need twenty projects.
For a beginner, I would rather see three to five detailed projects than twenty dashboards with almost no explanation.
Try to cover different types of analysis.
For example:
Project 1: Ecommerce sales and customer behaviour
Project 2: Indian startup funding analysis
Project 3: Public-sector or transportation analysis
Project 4: Financial or digital-payment analysis
Project 5: Consumer or product analytics
This gives a recruiter evidence that you can work across different business problems.
Your portfolio should also show the tools you know. SQL, Excel, Power BI, Tableau, Python, pandas, statistics, and data visualisation can all be demonstrated through projects rather than simply listed in a skills section.
When building these projects, start with credible public sources.
Depending on the project, useful sources can include government open-data platforms, RBI datasets, Census-related datasets, public economic datasets, public transport datasets, company reports, publicly available sports data, and research datasets.
You can also use Kaggle when the dataset has clear documentation and licensing information.
The important thing is to document your source.
Your project should say something like:
Dataset source: Public government dataset
Period: 2018 to 2025
Rows: 125,000
Key variables: State, district, category, year, value
If you create or combine data yourself, say so.
Never present synthetic or manually collected data as official company or government data.
A data analyst portfolio is not really about showing that you know Power BI or Python.
It is about showing that you can take a question, work with imperfect information, find a pattern, and explain what that pattern means.
That is why real Indian datasets can be so useful.
They give you familiar business and social contexts. Ecommerce, startups, digital payments, public transport, inflation, healthcare, employment, and consumer behaviour are all areas where data can be connected to real questions.
Fueler's recent guidance on data analyst careers makes the same point: a strong portfolio should move from business problem to data, analysis, insight, recommendation, and result.
That is the difference between a dashboard portfolio and an analytical portfolio.
The best data analyst portfolio projects are not necessarily the projects with the most complicated SQL queries or the most colourful Power BI dashboards.
They are the projects where the reader can understand the question and follow your reasoning.
If I open your portfolio, I should be able to see where the data came from, what you did with it, what you found, and why the finding matters.
That is why I would start with one Indian dataset that genuinely interests you.
If you like ecommerce, analyse consumer behaviour.
If you are interested in startups, analyse funding or hiring.
If you like finance, work with banking or digital-payment data.
If you care about public problems, explore transportation, healthcare, or employment datasets.
Then document the work properly.
Show the messy dataset. Show the cleaning. Show the SQL or Python analysis. Show the dashboard. Most importantly, explain what you learned.
A portfolio should not just prove that you can use a tool.
It should prove that you can use data to understand a problem.
Good beginner projects include ecommerce sales analysis, customer behaviour analysis, Indian startup funding analysis, IPL analytics, inflation analysis, digital-payment analysis, and public transportation dashboards. Choose a project where the dataset and business question are easy to explain.
You can use government open-data sources, RBI datasets, public economic datasets, research datasets, public sports data, company reports, and well-documented Kaggle datasets. Always check the source, licensing conditions, date range, and limitations before publishing your analysis.
Three to five detailed projects are a strong starting point. Instead of creating many similar dashboards, use projects that demonstrate different skills such as SQL, Python, Excel, Power BI, Tableau, statistics, customer analytics, financial analysis, and business intelligence.
Include the business question, dataset source, data-cleaning process, tools, analysis methodology, visualisations, key insights, recommendations, and limitations. If you have measurable results, include them with enough context to make the claim credible.
Yes. You can use public datasets to create self-initiated projects. A strong project can demonstrate your ability to clean data, write SQL, analyse information, build dashboards, and communicate insights even when you have not worked as a professional data analyst. The important thing is to clearly label self-initiated projects and never present them as client work.
Fueler helps professionals showcase proof of work through projects, assignments, case studies, and achievements.
Our mission is to help the next 100 million professionals build a verified professional identity through proof of work
You've read the article. Now turn your skills into proof of work and unlock more opportunities.
Create a clean portfolio with projects, assignments, resumes, and AI stack details that companies actually want to see.
Create your Fueler portfolio →Stand out by solving real tasks from companies hiring on Fueler.
Explore assignments →Make your work public and let recruiters discover your skills through actual projects instead of keywords.
Get discovered →
Trusted by 159400+ Generalists. Try it now, free to use
Start making more money