Data scientist portfolio
A data scientist portfolio is a page on your own domain that aggregates your GitHub repositories, Kaggle competitions, hosted notebooks, and deployed model demos into one narrative, each wrapped in a short case study that states the problem, the data, the method, and the result. Folio builds that hub and pairs it with an ATS-ready resume from the same account. It complements GitHub, Kaggle, and notebook hosts rather than replacing them, framing the work those platforms already hold so a reviewer reads a story instead of a list of links.
Build your data science portfolio free. Own the domain.
Tie your GitHub, Kaggle, notebooks, and model demos into one owned page, with a resume to match. Sign in by email, Google, or passkey. Beta costs nothing and asks for no card, and the resume PDF is never paywalled.
What goes in the portfolio
Reviewers do not click through twelve repos. They read a framed story, then click the one that proves it. Folio gives every piece a place and a writeup.
GitHub
Surface your strongest repositories with a one-line summary each, instead of sending a reviewer to a raw profile sorted by recent push. You choose what leads, and a deep link sends the curious straight to the code on GitHub.
Kaggle
A Kaggle finish means more with context: the metric, the leaderboard position, and the one idea that moved your score. Frame each entry as a short case study and link out to the notebook for the full work.
Notebooks
A clean exploratory notebook is some of the most persuasive evidence you have. Link your hosted notebooks and pair each with a plain-language readout of what the analysis found, so a non-technical reviewer follows the point.
Models
A live model demo is the difference between claiming a result and showing one. Link the deployed app or endpoint, note the stack and the metric it hit, and let a reviewer try it themselves.
Case studies
Every project gets a short writeup in the same four-part shape, so a reader can compare your work at a glance and see how you think, not just what you built. This is the structure that separates a portfolio from a link dump.
Resume
The portfolio gets you read after the filter; a clean PDF gets you past it. Folio drafts a data science resume from the same content, scores it against the applicant tracking system, and exports it free.
How it works
No static-site generator to maintain, no CSS, no separate resume tool to stitch together.
01
Add your GitHub repos, Kaggle entries, hosted notebooks, and deployed model demos. Folio organizes them into a curated shelf you control instead of a raw feed.
02
For each project, capture the problem, the data, the method, and the result in a short writeup. Folio drafts a first pass from what you paste, and you edit every line.
03
Pick a design and go live on yourname.com. Add two DNS records and Folio issues the TLS certificate for you, with no Cloudflare account and no monthly domain fee.
04
From the same content, draft a data science resume, score it against the job with the ATS checker, and export a clean PDF free to send a recruiter.
How it compares
GitHub, Kaggle, and notebook hosts each hold one slice of your work. Folio is the owned page that frames all of it, with the resume in the same account.
| Capability | Folio | GitHub Pages | Kaggle profile | Wix | Notion |
|---|---|---|---|---|---|
| Aggregates GitHub, Kaggle, notebooks | All four sources | Repos only | Kaggle work only | Manual embeds | Manual embeds |
| Structured case-study writeups | Built in template | README only | Notebook prose | Manual | Manual |
| Matching ATS-ready resume | From the same account | Not offered | Not offered | Separate tool | Not offered |
| No build step to maintain | Hosted, zero config | Build and deploy yourself | Platform hosted | Hosted | Hosted |
| Custom domain included | Yes, free during beta | Free with setup | Not offered | Paid plan | Paid plan |
Platform behavior reflects each vendor published free and paid tiers and can change. Verify current terms on each vendor pricing page before you decide.
Why it adds up
The portfolio frames the evidence. The resume gets you through the filter.
4
sources, one page
GitHub, Kaggle, notebooks, models
1
content model
edit once, portfolio and resume update
$0
to export your resume PDF
no download paywall, ever
2
gates, one account
pass the ATS, then win the read
The honest caveat
A Folio portfolio is not a replacement for GitHub, Kaggle, or your notebook host. Those platforms are where the code, the competition history, and the runnable analysis live, and a serious reviewer will click through to them. Folio links out to each, on purpose, so the proof stays where engineers expect to find it.
What Folio adds is the owned page that ties the scattered evidence into a narrative a hiring team can read in one sitting: the curated shelf, the four-part case studies, and a domain that is yours instead of a profile you do not control. Paired with an ATS-ready resume from the same account, it is the page a reviewer reads after the filter and the link you send when you want to be remembered.
FAQ
A strong portfolio aggregates your best GitHub repositories, Kaggle competitions, hosted notebooks, and deployed model demos, each wrapped in a short case study that states the problem, the data, the method, and the result. Curate rather than dump: lead with three to five projects that show range, and deep link to the full code so a reviewer can verify the work.
No. A Folio portfolio complements GitHub, Kaggle, and notebook hosts, it does not replace them. Those platforms hold the code, the competition history, and the runnable analysis, and Folio links out to each. Folio adds the owned page that frames all of it into one narrative on a domain you control.
Show projects that prove range and judgment: an end-to-end analysis with a clear business question, a model you deployed and can demo live, a Kaggle entry with a result and the idea that moved your score, and a clean exploratory notebook. Each one needs a plain-language readout so a non-technical reviewer follows the point.
Yes, the owned hub for your scattered work sits on your domain free during beta. You add two records in your registrar DNS, then Folio handles the TLS certificate the first time someone visits. No Cloudflare account is required and your nameservers stay put, so your portfolio lives at yourname.com rather than a vendor URL.
Yes. The applicant tracking system parses an uploaded document rather than a live page, so a clean PDF remains the thing that gets you through the first screen. Folio drafts a data science resume from the same content as your portfolio, scores it against the job, and exports it free, so the resume and the portfolio never drift apart.
Yes. It is free for the duration of the beta, and the resume PDF download is never paywalled. Build the portfolio, connect your sources, draft a resume, and publish to your domain, none of it asking for a card. Should paid plans launch, the content, slug, and domain you built remain yours.
Keep going