Career Guide · Data Analytics
Data Analyst Portfolio Tips for Complete Beginners in 2026
Quick answer — what actually gets you interviews
Recruiters don't read every line of your project. They scan your GitHub for ~30 seconds. What they look for, in order: (1) the title and description of your projects (does this solve a real problem?), (2) your README (can you explain your thinking?), and (3) the visual output (charts and dashboards). Most beginner portfolios fail on the first two — they're either generic titles ("Titanic Dataset Analysis") or a wall of unreadable code. The tips below fix that.
In this guide you will learn:
- The 4 project types every beginner portfolio needs.
- How to structure your GitHub — the folder layout recruiters expect.
- How to write a README that makes your project stand out.
- The 90-day plan — from zero to a portfolio that gets responses.
- Common mistakes — and how to avoid them.
SECTION 01The 4 project types
A strong data analyst portfolio shows breadth without showing redundancy. You don't need 20 projects — you need these four types, done well.
| Project Type | What It Shows | Tools |
|---|---|---|
| 1. Analysis with insight | You can find something meaningful in messy data | Python or Excel |
| 2. Dashboard | You can present data clearly to stakeholders | Power BI, Tableau, Looker Studio |
| 3. SQL-focused project | You can query real databases | PostgreSQL, BigQuery, SQLite |
| 4. End-to-end project | You can do the whole process — clean, analyze, present | Combination |
SECTION 02How to structure your GitHub
Your GitHub is your portfolio. It should look organized, not scattered. Here's a simple structure that works:
your-github/
├── README.md ← your portfolio homepage
├── project-01-sales-analysis/
│ ├── README.md
│ ├── data/
│ ├── notebook.ipynb
│ └── output/charts/
├── project-02-hr-dashboard/
│ ├── README.md
│ ├── dashboard.pbix
│ └── screenshots/
├── project-03-sql-queries/
│ ├── README.md
│ ├── queries.sql
│ └── results/
└── project-04-end-to-end/
├── README.md
├── notebooks/
├── app/
└── screenshots/
// Naming conventions that work
// Good:
// - "sales-analysis-retail-2026"
// - "hr-attrition-dashboard"
// - "ecommerce-cohort-analysis"
// Bad:
// - "project1"
// - "test"
// - "data-analysis" (too generic)
// - "netflix-dataset" (done by 10k people)
// Prefix with type when relevant:
// - analysis-XXX
// - dashboard-XXX
// - sql-XXX
// - e2e-XXX
// Each repo should be:
// - Public
// - With a real README
// - With a clear purpose in one sentence
SECTION 03How to write a README that works
The README is the first thing a recruiter reads. Most beginner READMEs are just a title and a photo. Yours shouldn't be. Use this template:
# Project Title
## The question
What business question does this project answer?
## Data
Source, size, time period, notes on cleaning.
## Approach
Steps you took — tools, methods, decisions.
## Key insights
3–5 bullet points with the actual findings. Use numbers.
## Charts
Screenshots of 2–3 key charts.
## What I'd do next
Honest reflection — what would you improve?
## How to run
Brief instructions to reproduce the analysis.
# Retail Sales Decline — Root Cause Analysis
## The question
Why did Q3 revenue drop 12% vs. Q2 despite
higher web traffic?
## Data
- Source: Kaggle "Retail Transactions 2025"
- 480k rows, 12 months
- Cleaned 8 issues (duplicates, date formats, outliers)
## Approach
1. Explored trends across regions and categories
2. Segmented users by acquisition channel
3. Compared conversion by product category
4. Cross-checked with support ticket data
## Key insights
- Conversion dropped 18% on mobile (not desktop)
- Mobile checkout failed 6% of the time
- Payment success dropped from 94% to 88%
- Affected mostly new users, not repeat buyers
## Charts
- fig1-conversion-by-device.png
- fig2-payment-success-trend.png
- fig3-new-vs-repeat-users.png
## What I'd do next
- Pull in gateway logs to pinpoint payment failures
- Segment by OS version
## How to run
`pip install -r requirements.txt && jupyter notebook`
SECTION 04The 90-day plan
Here is a realistic 90-day plan for a complete beginner. Adjust to your pace, but keep the sequence.
| Days | Focus | Outcome |
|---|---|---|
| 1–30 | Python/SQL + Excel basics | Confident with tools |
| 31–45 | Project 1: analysis with insight | First portfolio repo |
| 46–60 | Project 2: dashboard | Dashboard + screenshots |
| 61–75 | Project 3: SQL-focused | Query-heavy repo |
| 76–90 | Project 4: end-to-end + polish | Portfolio ready to share |
SECTION 05Common mistakes
Avoid these — they're what kill otherwise good portfolios:
- Using only Titanic/Netflix datasets — everyone does these. Pick something with a business angle.
- No README — a repo without a README is invisible to recruiters.
- Hiding insights in the notebook — put your findings on the README, not on page 34 of a notebook.
- No charts — a data project without visuals is a red flag.
- Repos with old/stale code — if you're applying today, your recent work should be your best work.
- No live dashboard link — link to a public dashboard if possible. It's 10x more impressive than a screenshot.
SECTION 06Interview Q&A — portfolio tips
Q1How many projects do I need?
Four is enough if they're varied and well documented. Two or three strong projects beat ten shallow ones. Quality > quantity.
Q2Do I need to use Python?
Not necessarily — Excel is a valid tool. But a portfolio with Python and SQL shows you're more versatile. Aim for at least one project in each.
Q3Can I use publicly available datasets?
Yes — but frame the project around a business question, not the dataset. "Titanic dataset" is weak; "predicting survivor segments to prioritize rescue operations" is stronger.
Q4Do I need a personal website?
Not required. A well-organized GitHub with a strong profile README is enough. A personal site is a nice bonus, but GitHub is what recruiters actually check.
Q5How do I make my portfolio stand out?
Lead with insights, not code. Show business thinking. A recruiter scanning 100 portfolios cares more about what you found than what tools you used.
SECTION 07Test yourself — portfolio tips quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
Do I need to know Python to build a portfolio?
No. Excel + SQL portfolios get hired too, especially for analyst roles. But Python opens more doors, so add it if you can.
What if I don't have any real data?
Use public datasets, but frame the project around a real question. Kaggle is fine. The insight matters more than the source.
How long should my README be?
One screen — roughly 300 words. Lead with the question, then insight, then charts, then method. If it's longer, it's not a README, it's a report.
Is it okay to use tutorials to build projects?
For learning, yes. For your portfolio — no. Recruiters spot tutorial projects. Build something original, even small.
What if my portfolio looks basic?
That's fine. A basic portfolio with real insights beats a fancy one with no substance. Focus on clarity, not complexity.
SECTION 09Related reads
Classroom & online · Noida
Build your data portfolio with guidance
Our Data Analytics Course includes portfolio projects, dashboard work, and interview prep built around real business questions.
₹15,500 · full programme- Excel + SQL + Python + Power BI
- Portfolio projects & GitHub
- Mock interviews & resume help
- Weekday & weekend batches