13.5 Portfolio and writing
A recruiter understands what you can do in ninety seconds.
The portfolio is the interface to all the work: pinned repositories with clean READMEs, one technical post per capstone, a one-page CV aimed at ML roles — read by a recruiter in about ninety seconds. It sits at the end because it packages everything. The counterintuitive signal is limitations: credibly stating what a project does not do reads as seniority, while claiming everything reads as inexperience, and reviewers know the difference instantly.
Work through these
GitHub profile, pinned repos, clean READMEs
A profile someone can scan quickly, with the good work pinned and each repository explaining itself. Most portfolios fail at the reading stage rather than the quality stage.
Introduction to GitHub · TutorialOne technical blog post per capstone
One written article per project, explaining the decisions rather than the tools. Writing is also how you find out whether you understood what you built.
A one-page CV aimed at ML roles
A single page aimed at the roles you want, which means cutting most of what you could include. The constraint of one page is the whole exercise.
Talking about limitations credibly
Being able to say what your work does not do, credibly and without apology. It is the strongest signal of experience an interviewer can hear.
Sign in to keep your progress.
Free resources
We haven't checked most of these for screen reader use yet.
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.