Programmer portfolio

An employer looks at a portfolio for a couple of minutes. In that time they need to see what you can do, how you write code and whether you finish what you start. A few finished projects with clear READMEs and an honest history of the work show that best.

Updated
In this article

What to put in your portfolio#

  • Two or three finished projects, not ten abandoned ones. Finished means it runs by following the instructions and does what it promises.
  • A project from real life — automating one of your own tasks, a bot, a scraper, a small service. It is more interesting than a tutorial calculator.
  • Solved problems — if you have been learning, show the path: a repository with problems by topic and your own explanations.

A README people read#

Every project's README has:

  1. One sentence — what it is and who it is for.
  2. A screenshot or an example of the output.
  3. How to run it — commands that work from scratch.
  4. What you used and why.
  5. What you would do next.

The last point says a lot about you: you can see the weak spots in your own work.

Your commit history is a portfolio too#

A project uploaded as a single commit called "final" looks downloaded. Meaningful commits over several weeks show how you work: small steps, clear messages, fixes after review. Keep the history honest from day one — it cannot be convincingly redrawn after the fact.

Your profile#

The profile page is the first thing people open. On Skillok a profile has a README — a short story about you, your stack, links to your best projects — and an activity calendar that shows how regularly you work. Public repositories are listed on the profile.

Your learning path as an advantage#

If you are just getting into the field, do not hide your studies. Challenges with automatic checking of solutions in Python and JavaScript, notes, courses you have finished — all of it sits in repositories with dates and shows your trajectory: what you studied and in what order.

Common mistakes#

  • a tutorial project copied without changes;
  • no instructions for running it;
  • secrets and passwords in the code — check the whole history, not just the latest version;
  • forty repositories, of which two are worth a look.

If you are deciding where to host the code itself, the GitHub alternative page lists what Skillok repositories can and cannot do.

Try it on your own task

Create a repository — history, issues and pull requests from day one.

Create a repository

Was this helpful?

More solutions

Employee training platform A classic corporate LMS means courses, assignments, reports and certificates. Skillok covers part of that in a different way — through a repository of materials, issues as assignments, and challenges with automatic checking. If you need reports on every employee and SCORM compatibility, we will say it right away — those are not here. Confluence alternative Confluence keeps documentation as pages inside spaces. In Skillok documentation is a set of markdown files in a repository, and you work with it the way you work with code — edit, history, review. That is stricter and more transparent, but there is no visual page builder and no real-time co-editing. GitHub alternative Skillok is built like GitHub and repeats the familiar parts — repository, commits, branches, issues, pull requests, projects, organizations. The interface is available in English and Russian. Below is an honest list of what already works, what does not yet, and how to move your code in a few minutes. Notion alternative Notion is built from page blocks and databases. Skillok works differently — your notes are plain markdown files in a repository, and every change has a history. If you care about text, order and being able to take everything with you at any moment, this may suit you better. If you need database tables with formulas and real-time co-editing, it will not. GitLab alternative If you use GitLab for repositories, issues and code review, and do not want to maintain a server, Skillok covers that part. If you live in GitLab CI and the package registry — honestly, that is not us yet. Here is what matches and what does not. Employee knowledge base An employee knowledge base solves one problem — a new person finds the answer alone without distracting colleagues. A huge encyclopedia does not do that well. A clear route does — what to read on day one, what in the first week, and how to check that it all makes sense.

More articles

Programming and IT How to become a software tester from scratch Software testing is a common way into IT without deep programming at the start. But a tester's job is not "clicking buttons": you need to understand how the application works, design checks using test design techniques and describe defects clearly. Below is the order to study things in and practice assignments you can show an employer. Programming and IT Regular expressions A regular expression is a compact description of a set of strings. The same syntax works in grep, in your code editor, in JavaScript, PHP, Java and Python, so you only need to learn it once. This page covers the pattern language itself, not the library of any particular language. Programming and IT How to learn to code from scratch You can teach yourself programming without a technical degree if you write code with your own hands from the first week instead of only watching lessons. Below is how to choose a first language, what to install, which order to take topics in and how to tell that you are really making progress.