Your technical portfolio: prove your skills with projects
How to build a portfolio and GitHub that convince technical employers, and present your projects in your CV and interviews.
What you will learn
- Choose projects that prove in-demand skills
- Document a project with a clear README
- Present a project confidently in a technical interview
Section 1 · 11 min
Why technical people need a portfolio
AreenNarrated by Areen · move between slides freely.
In technical fields (software, data, design, engineering), employers often say: "Show me what you've built." A portfolio proves your skill better than any CV line, especially for a new graduate without long experience.
🃏 What employers like in projects (tap)
Which projects?
- Your graduation project or a standout course project, cleaned up and documented.
- A project solving a problem close to you: a room-booking system for your club, an expense tracker, an analysis of open data on a topic you care about.
- A project that fills a market gap: if ads ask for React, Power BI or Python, build something small with it.
- A contribution to an open-source project, even improving documentation.
✍️ Reflect and write
Which three projects will you put in your portfolio, and which skill does each prove?
Sign in to save your answers.
🔒 2 more sections in this course
Sign in or create a free account to continue the course, save your progress and answers, and earn the certificate once credited.
A platform tool for this course: CV builder
To get credit: prepare this before the session or training
Before the session:
- Pick one of your projects (course, graduation, personal) and write a README with the six elements
- Write how you'd present it in two minutes
Discussion:
- Which project could you build in a month to close a gap in your skills?