For a fresher, the projects section is the most important part of a data analyst resume. You have little or no work experience, so the projects are your experience. Yet most project lines on fresher resumes say almost nothing. This article shows how to fix that.
What a recruiter looks for in a project line
A recruiter or hiring manager reads each resume for a short time. In that time they want to know four things:
- What business problem did you work on?
- What did you do (clean, analyse, model, build a dashboard)?
- Which tools did you use?
- What did you find or recommend?
If your line answers all four, it is good. If it only lists tools, it is not.
A weak line and a strong line
Here is a typical weak line:
Weak: "Sales Analysis Project using Python, Pandas, Matplotlib. Did EDA and visualisation."
It names tools but not the problem, the work or the result. Compare:
Strong: "Analysed six months of order data for a fictional quick-commerce brand to find why repeat customers were dropping. Cleaned and joined orders, customers and delivery tables in SQL; built cohort retention in pandas; found that customers whose first order arrived late were far less likely to order again, and proposed a first-order delivery guarantee."
The strong line is longer, but every part earns its place. Notice that it does not invent a precise percentage. If your project produced a real number from the data, use it. If it did not, describe the finding clearly instead of making one up. Interviewers will ask how you got any number you write.
A simple formula
Use this pattern for each project, as two or three bullet points:
- Context + problem: "For [type of company], investigated [problem]."
- Work + tools: "[Cleaned / joined / modelled / built] using [SQL, pandas, Power BI…]."
- Finding + action: "Found [insight]; recommended [action]."
How many projects?
Two to four strong projects beat eight weak ones. Try to cover different skills: one SQL-heavy analysis, one Python cleaning and EDA project, one dashboard, and, if you are aiming at data science roles, one machine learning model. Projects from different industries (banking, healthcare, retail) also show range.
Make the project easy to check
- Put the code on GitHub with a clear README: problem, data, approach, findings.
- For dashboards, add a screenshot or a published link.
- Use the same project title on your resume and on GitHub so the reader can find it.
Common mistakes
- Listing "Titanic" or "Iris" as your main project. Everyone has these; they show you followed a tutorial.
- Copying a project description from a course without changing it.
- Writing skills you cannot explain. If "regression" is on your resume, expect questions about it.
- Two-page resumes for freshers. Keep it to one page.
Where to get projects worth writing about
You need problems with business context and messy data. Our live projects give you a fictional company, a business requirements document and realistic datasets, and each one comes with a ready resume entry once you finish. Our resume builder then turns your finished projects into a clean one-page resume.
For the overall plan of what to learn before you start projects, see the data analyst roadmap for freshers.
Practise what you just read
Reading helps; writing the code yourself is what sticks. Start here: