Stage 5 · Lesson 1 of 7

Proof over credentials

Proof is anything a reviewer can open to check your skills. Examples are a (one that is live on the web), a data report with its queries, or a with the bugs you found. A merged (a code change a project accepted) or a clear technical write-up also counts.

Without a or tech job title, proof is what lets a stranger trust you. That is the idea of . It answers "can you actually do this?" before anyone asks.

It also gives interviewers something concrete to talk about. Aim for a few finished pieces that match your target role, not many half-built ones. Polishing them for applications is covered in the Job search roadmap.

Common trapa resume listing many completed courses with nothing to open.

A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it

Resources for this stage

Start with

BookFree
Automate the Boring Stuff with Python
Al Sweigart · Beginner
Free book on automating spreadsheets, files and reports: ideal for projects from your old job

Practise

First Contributions
A guided first pull request, so your first real contribution is not your first time using Git
Good First Issue
Beginner-friendly issues in active projects once you have done a practice pull request

Keep handy

Kaggle Datasets
Public datasets from many industries, often including the field you came from
Hashnode
A free developer blog for your write-ups and case studies

Also worth your time

Learn In PublicRead
The short essay behind learning in public, and why it keeps paying off