Employers want evidence that you can do the job. Credentials demonstrate that you learned something; side projects demonstrate that you can apply it. A well-documented project that solves a real problem shows exactly what a hiring manager needs to see before taking a chance on someone without a traditional background: that you can think, execute, and communicate your work clearly. Side projects provide that evidence before anyone has given you the job to do it.
How to choose the right project
Four criteria should guide your choice. The project should solve a real problem — not a contrived exercise, but something that actually exists in the world and that you have some firsthand familiarity with. It should showcase the specific skills your target role requires: a PM-focused project needs prioritization and communication, a data analyst project needs querying and storytelling, a UX project needs research and design decisions. It should be completable in two to four weeks so it does not become an indefinite drain on your momentum. And it should be something you can talk about with genuine enthusiasm — hiring managers can tell when someone is reciting a project versus actually caring about it, and enthusiasm signals genuine interest in the domain you are trying to enter.
The documentation formula that makes projects portfolio-worthy
The project itself is only half the portfolio asset. The documentation is the other half. Every project needs five elements: the problem and why it matters, the process you followed and what you learned along the way, the solution you built or recommended, the outcome or what you would measure to know if it worked, and a reflection on what you would do differently with more time or resources. This structure forces you to show strategic thinking, not just execution. It signals that you understand why decisions were made, not just what was decided.
The publication mistake to avoid
Many career changers build a solid project, publish it somewhere, and then wait for something to happen. Nothing happens. The project that nobody sees does not exist as portfolio evidence. After publishing, actively share the work on LinkedIn, explain your thinking in the post, invite feedback and questions, and link to the project everywhere your name appears. Engagement with the post itself creates visibility with people who were not searching for you.
How to talk about projects in interviews
Frame side projects as real work, because they are. Discuss your decisions and the reasoning behind them, not just the output you produced. Acknowledge what you would do differently if you had more time, more data, or more resources — this shows self-awareness and continuous improvement thinking. The question interviewers are silently asking is: can this person think like someone already doing this job? Talking about your project like a practitioner, not a student, answers that question.