Skip to main content

Project library

30 projects, ranked

Filter by difficulty, then open any project for the full stack, the framework to follow, five name ideas and how to publish it. The harder ones carry the most weight on a résumé.

Why finishing one of these matters

  1. Something to say

    Interviews ask what you have done. A finished project answers with specifics instead of coursework.

  2. Numbers on your résumé

    Records searched, findings confirmed, tests added. Figures a reader can check against your report.

  3. Tools on the page

    Each project leaves you with four or five named tools and a framework you have actually used.

  4. Proof you finish

    A public repository with a readable history shows follow-through, which is rarer than skill at this stage.

Pick one and finish it

Everything runs on public data, published reports or a lab on your own machine. Easy projects prove you can finish and publish something; hard ones are the projects an interviewer spends the most time asking about.

  • EasyGood first projectA weekend of work. Start here if you have never published a project.
  • MediumSolid portfolio pieceTwo or three sessions. Enough depth to carry an interview answer.
  • HardStrongest résumé pieceThe ones worth the most on a résumé: real scope, real decisions, and plenty to talk about.

30 projects. Ranked for a first portfolio, easiest wins first.

What happens after you finish one

Give it a name of its own, publish it on GitHub with your notes and evidence, and put the numbers you counted into one résumé line. Every project page walks through all three.

Browse the career paths