What the problem is
Not that these projects are bad. That everyone has built them.
To-do lists, weather apps, blogs and online shops are the four subjects that turn up in every other beginner's CV. A reviewer recognises them from the first screen and concludes: took a course, repeated the assignment.
That may be unfair. But it's the actual reaction, and it has to be reckoned with.
What the reviewer sees
They page through dozens of applications a week. They have no time to work out how your to-do list differs from the previous nine. They're looking for a hook — something that stands out.
A well-worn subject provides no hook. Worse, it works against you: it suggests the person has no ideas of their own.
Three ways to rescue a tired subject
If the project already exists and you'd rather not bin it, it can be turned into a real one.
Add a constraint nobody else has. A to-do list that orders tasks by deadline and your actual workload. A weather app that says not the temperature but whether to take a coat and umbrella, in plain language.
Change the user. A to-do list for one person is dull. One for a family, where chores are divided and everyone sees who took what, is a problem with genuine difficulty in it.
Take it to unusual depth. The average version is deployed haphazardly. Yours has validation, tests, error handling and a clear README. That alone sets it apart.
What to build instead
Take something you'll use yourself. Expense tracking from receipts, a subscription-renewal reminder, search over your own notes, a bot with a timetable.
Such projects win twice: the subject is rare, and you talk about it vividly, because you were solving a real problem rather than completing an assignment.
Stronger still
The subject stops being the main question altogether if the project was built by a team and your part is confirmed.
Then the conversation isn't about whether the idea is original but about how you worked: what you owned, how you negotiated, what you raised in someone else's code. Hiring managers care about that far more than the plot of the project.
Хватит читать — пора делать
На CohortX можно найти команду под пет-проект и получить тот самый опыт, о котором спрашивают на собеседовании.
Похожие статьи
- Presenting a repository so people actually look at itNaming, structure, commit history, what to hide and what to pin — the small things that decide whether your code gets opened.
- Как оформить репозиторий, чтобы его смотрелиНазвание, структура, история изменений, что скрыть и что закрепить — мелочи, которые решают, откроют ваш код или нет.
- A README that makes people open the projectWhat to put in your repository's README, in what order, and why without it nobody looks at the code.