Guide
Developer portfolio: what to include and how to link it to your resume
Updated:
In short
A good developer portfolio has 3 to 5 finished projects, each with a live link, code on GitHub and a short description of the problem, the technologies and the result. Put the portfolio and GitHub links in the resume header as text, and choose the projects by the type of role you are after.
How many projects, and which ones?
Three to five finished projects are more convincing than ten that were started. Choose projects that show the skills asked for in your target postings: a frontend, an API, a full-stack app with authentication and a database.
How do I describe each project?
Use the same scheme for each:
- The problem it solves, in one sentence.
- Technologies used (TypeScript, React, PostgreSQL, Docker).
- The result or a distinguishing feature: performance, number of users, tests.
- A live link and a link to the code.
What does a good GitHub look like?
Repositories with a clear README (what it does, how to run it, screenshots), commits with understandable messages and tests where they make sense. Pin your best projects on the profile.
How do I link it to the resume?
Put the links in the header as plain text (for example github.com/name), and mention the most relevant projects on the resume with a one-line result. A technical recruiter will open the link, so check it before each application.
Frequently asked questions
Do I need a portfolio site or is GitHub enough?
GitHub is enough to start, if it is tidy. A simple site adds control over presentation but is not required.
Can I include course projects?
Yes, if they are finished and well documented. Add what you changed or extended beyond the original assignment.
What about confidential code from work?
Do not publish it. Describe the impact and technologies on the resume without confidential details and show personal projects for code.
See how an ATS reads your resume
Upload your resume and get a free score from 0 to 100 and the points to fix. No account needed.