Data Analytics · Recruiter View
Data Analyst Portfolio Guide: What Recruiters Want to See
Quick summary — what recruiters want in an analyst portfolio
Recruiters want a data analyst portfolio they can understand in minutes: clear project titles with one-line summaries, business questions rather than tutorial copies, careful cleaning, correct SQL, readable charts, a finding and recommendation in each project, honest limitations and links that work. Red flags include copied projects and broken links.
In this guide you will learn:
- How recruiters scan — a portfolio in minutes.
- Signals of real skill — they look for.
- Red flags — that make them move on.
- A recruiter-view scorecard — for self-review.
- Interview questions — your portfolio will trigger.
SECTION 01The first glance: what recruiters see in seconds
A recruiter or hiring manager may review many applications for one role, so the first look at a portfolio is short. They usually want to know quickly what you have built, whether it relates to the job and whether it looks professional. A clear landing page, meaningful project titles and one-line summaries help them decide to keep reading. Generic names and cluttered pages often end the visit early:
| What they see | Weak version | Strong version | Effect |
|---|---|---|---|
| Landing page | Long list of repos with no context | Three featured projects with one-line summaries | Clear in seconds |
| Project titles | Project1, EDA_final | Repeat Purchase Drivers in Retail | Signals business focus |
| Summary line | None | Found repeat orders fell among late first deliveries | Creates curiosity |
| Relevance | Unrelated to the role | Data similar to the company's domain | Easier to imagine you in the role |
# <Name> - Data Analyst Portfolio
SQL | Excel | Power BI | Python
## Featured projects
1. **Repeat Purchase Drivers in Retail** - found repeat orders fell
among customers with late first deliveries (SQL, Power BI)
2. **Clinic No-show Analysis** - identified time slots with the most
missed appointments (Python, Excel)
3. **Delivery KPI Dashboard** - daily on-time view by city (Power BI)
Contact: email | LinkedIn
import re
titles = ["Project1", "EDA_final_v2", "Repeat Purchase Drivers in Retail",
"sales analysis", "Clinic No-show Analysis"]
for t in titles:
weak = bool(re.search(r"(?i)project\d|final|eda_|^\w+ analysis$", t))
print(f"{t:36} {'rename: say what you found or studied' if weak else 'ok'}")
SECTION 02Signals of real skill
Once a recruiter opens a project, they look for signs that you can do the actual job. These signals usually matter more than which tool you used: a real business question, careful handling of messy data, correct and readable SQL, charts that answer the question, a clear finding and recommendation, and honest limitations. Hiring managers often check one or two details closely, such as a query or a cleaning step:
| Signal | What they look for | Example | Why it convinces |
|---|---|---|---|
| Business question | A problem someone would care about | Which slots have the most no-shows? | Shows business thinking |
| Data care | Documented cleaning decisions | Removed duplicates; explained missing values | Shows trustworthiness |
| SQL quality | Correct joins, readable CTEs | Commented query files | Core analyst skill |
| Judgement | Finding, recommendation and limitations | Correlation noted; next test suggested | Shows maturity |
-- Which appointment slots have the highest no-show rate?
-- Grain check: appointments has one row per appointment.
WITH slot_stats AS (
SELECT slot,
COUNT(*) AS appointments,
SUM(CASE WHEN status = 'NO_SHOW' THEN 1 ELSE 0 END) AS no_shows
FROM appointments
WHERE appt_date BETWEEN '2026-04-01' AND '2026-09-30'
GROUP BY slot
)
SELECT slot, appointments, no_shows,
ROUND(100.0 * no_shows / appointments, 1) AS no_show_pct
FROM slot_stats
WHERE appointments >= 50 -- ignore tiny groups
ORDER BY no_show_pct DESC;
import pandas as pd
appts = pd.DataFrame({
"appt_id": [1, 2, 3, 3, 4],
"slot": ["8-10", "8-10", "10-12", "10-12", "12-2"],
"status": ["NO_SHOW", "DONE", "DONE", "DONE", "NO_SHOW"],
})
print("rows:", len(appts), "unique ids:", appts["appt_id"].nunique())
clean = appts.drop_duplicates("appt_id")
print("after de-duplication:", len(clean))
print(clean.groupby("slot")["status"].apply(lambda s: (s == "NO_SHOW").mean()).round(2))
SECTION 03Red flags that make recruiters move on
Some patterns quickly reduce a recruiter's confidence. Many beginner portfolios contain copies of popular tutorial projects with no new angle, broken links, notebooks full of errors, or bold claims that the data cannot support. None of these are hard to fix. Reviewing your portfolio through a recruiter's eyes and removing these issues often helps more than adding another project:
| Red flag | Why it worries recruiters | How to fix | Effort |
|---|---|---|---|
| Copied tutorial projects | Hard to tell what you did | Add your own question and write-up, or replace | Medium |
| Broken or private links | Looks careless | Test every link before applying | Low |
| Notebooks with errors | Suggests unfinished work | Re-run top to bottom; remove dead cells | Low |
| Overclaiming | Raises doubts about judgement | State limitations and avoid causal claims | Low |
# pip install requests
import requests
links = {
"Retail project repo": "https://github.com/<you>/repeat-purchase",
"Dashboard": "https://app.powerbi.com/view?r=<public-link>",
}
for name, url in links.items():
if "<" in url:
print(f"{name}: replace placeholder")
continue
try:
code = requests.get(url, timeout=10).status_code
print(f"{name}: {'OK' if code < 400 else f'BROKEN {code}'}")
except requests.RequestException as e:
print(f"{name}: ERROR {e}")
import re
writeup = """Late deliveries caused customers to stop buying.
Customers with late first orders had lower repeat rates in this dataset."""
causal = re.findall(r"(?i)\b(caused|causes|proves|guarantees)\b", writeup)
if causal:
print("Causal words found:", causal)
print("Consider: 'is associated with', 'was linked to', 'suggests'.")
else:
print("no overclaiming words found")
SECTION 04Recruiter-view portfolio scorecard
Use these templates to review your portfolio the way a recruiter would:
Score each item 0-2 (0 = missing, 1 = partly, 2 = strong)
Clear landing page with featured projects ___
Project titles describe the question ___
One-line summary with a finding ___
Business question at the start ___
Cleaning steps documented ___
SQL readable and correct ___
Charts answer the question ___
Recommendation and limitations ___
All links work ___
Relevant to the target role ___
Total (out of 20) ___
Ask a friend to spend two minutes on your portfolio, then answer:
1. What kind of analyst role is this person aiming for?
2. What was the most interesting finding?
3. Which tools do they use?
4. Was anything confusing or broken?
If they cannot answer 1-3, simplify the landing page.
For each project, prepare one 'hook' a recruiter may ask about:
Project: Repeat Purchase Drivers
Hook: Why repeat orders fell among late first deliveries
Evidence: Cohort table + delivery time chart
Caveat: Correlation, not proof of cause
Next step: Suggest a delivery-speed test for first orders
SECTION 05Tips to give recruiters what they want
These habits align your portfolio with how recruiters actually review it:
- Design for two minutes — the main point should be clear quickly.
- Lead with findings — titles and summaries should hint at a discovery.
- Show one detail of care — a grain check or cleaning note builds trust.
- Remove red flags first — fix links and errors before adding projects.
- Match the role — feature the projects closest to the job.
SECTION 06Interview Q&A — portfolio reviews
Q1Which project in your portfolio best represents your skills, and why?
Pick one related to the role, explain the question, your cleaning and SQL, the finding and the recommendation.
Q2How did you make sure your analysis was correct?
Describe checks such as grain checks, row counts after joins, totals compared with source data and spot checks.
Q3Is this project based on a tutorial?
Be honest. If it started from a tutorial, explain the new question, data or analysis you added yourself.
Q4What does this finding not prove?
Explain the limits, such as correlation versus causation, sample size or data coverage, and what test would confirm it.
Q5How would this analysis help our business?
Connect the method to the company's domain and suggest a similar question you could answer for them.
SECTION 07Test yourself — portfolio reviews quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
What do recruiters look for in a data analyst portfolio?
Clear projects with business questions, careful data cleaning, correct SQL, readable charts, findings with recommendations, honest limitations and working links.
How long do recruiters spend on a portfolio?
It varies, but often only a few minutes at first. Make the main points clear quickly with titles, summaries and featured projects.
Are tutorial projects bad for a data analyst portfolio?
Not if you add your own question, analysis and write-up. Unchanged copies make it hard to judge your skills.
How many projects do recruiters want to see?
Usually two to four strong, relevant projects are enough. Quality and clarity matter more than quantity.
Should my portfolio match the job I apply for?
Yes, where possible. Featuring projects from a similar domain or with similar tools makes it easier for recruiters to see the fit.
SECTION 09Related reads
Classroom & online · Noida
Build a portfolio recruiters want to see
Our Data Analytics Training Course guides you to build business-focused SQL, Excel and Power BI projects with mentor reviews from a recruiter's point of view.
₹15,500 · full programme- Business-focused projects
- SQL and Power BI
- Portfolio reviews
- Weekday & weekend batches