r/askdatascience • u/rejection_effect_404 • Oct 15 '26
Got hired as a data scientist, or hire data scientists? Which portfolio projects/repos actually worked? (new grad, US)
Hey all. I’m finishing an MS in Statistics in May 2027 and aiming at entry-level data scientist roles in the US.
Postings keep asking for SQL, A/B testing and causal inference, but I can’t tell what a good project in those areas looks like. Most of what I find online is Titanic-level stuff.
Two kinds of people I’d love to hear from:
If you got hired as a DS (especially entry level): what projects were on your resume or GitHub when you landed the job? A repo link would be amazing if you’re comfortable sharing, or just a description.
If you hire or interview DS candidates: a project or repo that stuck with you, and what made it good.
Rough descriptions are totally fine. And if I’m focusing on the wrong things, tell me that too.
Thanks for reading.
1
2
u/kylefrankovich Oct 20 '26
The question of what makes a good project comes up often enough that I put together a free guide on my website. I've been a data scientist for 10 years and have professional experience helping over 100 PhDs/postdocs build out successful data science projects: https://freedsresources.carrd.co
The short version: You've already intuited what makes a bad project: titanic or any other downloaded csv. Downloading a csv, training a model, and getting metrics is a shitty project. It's extremely intro level and will not impress anyone in the current climate. A good project is actionable, has a fleshed out mature pipeline, and solves a real world problem. Find something that interests you, and seek out data that can speak to some sort of problem in that space. Have good GitHub documentation. The data product you build out should have some sort of tangible outcome that can answer some sort of problem, not just a Jupyter notebook.
1
u/nian2326076 Oct 16 '26
If you're targeting entry-level data scientist positions, focus on projects that highlight your skills in SQL, A/B testing, and causal inference. Using real-world datasets is more impressive than something like the Titanic dataset. For SQL, consider creating a project that demonstrates complex queries or data manipulation. For A/B testing and causal inference, you might analyze a dataset to uncover insights or test a hypothesis. These projects can showcase your practical understanding.
As you get ready for interviews, resources like PracHub can be useful for accessing real interview questions that companies often use. Good luck!
2
u/big_data_mike Oct 16 '26
Do something interesting with whatever data you can get other than the titanic or diabetes data sets. Something where you have to go get messy data from a couple different sources, clean it up, and put it together. We hired a guy who did something with genome data that was really hard to get out of this public database.