Everyone tells you to build projects. Nobody tells you what you'll walk away knowing. So here's the list I wish I'd had, with the specific skill behind each one and how to build it without paying for anything.
A working app used to be expensive to produce. That cost was the proof — it took you two weeks, so you must have learned something.
AI can scaffold a todo app in twenty minutes. So the app itself no longer proves anything. What proves something now is being able to explain why you made each decision, and what broke along the way. Build things where the hard part isn't the code.
Half-built repos are a real problem in interviews — people will ask why you stopped, and "I got bored" is a bad answer. Pick one from this list. Finish it. Deploy it. Then pick the next.
No project on this list requires money, a company, or a credit card. Where a service is normally paid, I've noted the free way to do it. That includes payments — see project 1.
Something people reserve a slot for. A salon, a tutor, a padel court. Users pick a time, pay a deposit, get a confirmation. The interesting part isn't the calendar — it's everything that happens when the payment doesn't go smoothly.
Pick a site with data you actually want. Job listings, prices, football fixtures. Pull it every day, store the history, notice when things change. The project isn't finished when it works once — it's finished when it survives the site changing.
Take an app you already built, or any open-source one. Measure how slow it is. Make it faster. Publish the before and after numbers. This is the only project on the list where the README is the deliverable.
Your class, your gym, your gaming group, your family. Something small they genuinely need. The value here is unfakeable: real people using it and complaining at you when it breaks.
Not a ChatGPT wrapper. Something that uses a model and stays useful when the model is wrong, slow, or returns nonsense. That distinction is the whole project.
Live scores, a shared whiteboard, a multiplayer game, a queue display. Two browsers open, one changes, the other updates instantly. Simple to describe, full of edge cases.
Move data from one shape into another where the models genuinely conflict. A CSV export into a proper relational schema. One API's format into another's. The interesting work is the 3% of records that don't map cleanly.
A CLI, a VS Code extension, a GitHub Action. Something that removes a small annoyance from your own workflow. Because you use it daily, you'll actually maintain it — which is the rarest signal on this whole list.
The project isn't done when it works on your laptop. These are the things that turn it from an exercise into something you can show someone.
1. Deploy it. A link someone can click beats a repo they have to run. Vercel, Netlify, Railway — all free.
2. Add demo credentials. If there's a login, put a test email and password in the README. Nobody is signing up to look at your project.
3. Write a README that answers three things in 60 seconds. What problem does this solve, what did you build it with, and what was the hardest part.
4. Document one decision you'd defend. Why this database, why this approach. This is what people ask about, and it's the thing AI can't produce for you.
5. Write down one thing that broke and how you fixed it. Interesting failures are more convincing than a clean build. Everyone knows nothing works first time.
6. Commit as you go, not all at once. A history that shows the thing growing over weeks says more than a single "initial commit" with 4,000 files.
7. Be able to explain every line. Use AI to build faster, absolutely. But if you can't explain what it wrote, you don't have a project — you have a screenshot.