What this step is really about
This step is about creating tangible evidence of your skills through side projects. It's not about adding another line to your resume; it's about demonstrating what you can do. When you build something small, you produce a concrete artifact that others can see, evaluate, and discuss. That artifact becomes a conversation starter and a proof point that you can point to in interviews or networking conversations.
Side projects are especially valuable when you're changing careers because they bridge the gap between your past experience and your desired future. They show that you're not just talking about a new field—you're actively participating in it. By building small things, you avoid the overwhelm of a massive project and instead create a series of quick wins that build momentum and confidence.
The goal is proof of skill, not perfection. A side project doesn't need to be groundbreaking; it needs to be genuine. It should reflect your current abilities and your willingness to learn. Even a simple project can demonstrate problem-solving, creativity, and follow-through—qualities that employers and collaborators value highly.
Why it matters for your change
When you're changing careers, you often face a credibility gap. Your resume might show experience in a different field, and hiring managers may wonder if you have the skills required for the new role. Side projects fill that gap by providing direct evidence. They show that you can apply your skills in practice, not just in theory. This is particularly important in fields where portfolios are expected, but even in others, a side project can set you apart.
Moreover, side projects demonstrate initiative and self-direction. They signal that you're not waiting for someone to give you permission to do the work—you're doing it because you're passionate and committed. That attitude is attractive to employers who value proactive learners. It also helps you build a network: when you share your work, you connect with others who share your interests, and those connections can lead to opportunities.
Finally, side projects help you learn by doing. They force you to confront real challenges, make decisions, and iterate. That learning is often more profound than what you get from courses or books. It also gives you stories to tell in interviews—stories about how you solved a problem, what you learned, and how you improved. These narratives are memorable and can make you a more compelling candidate.
The mistake people often make
The most common mistake is waiting until you have a perfect idea or all the skills you think you need. This leads to paralysis. People spend months planning and researching, but never actually build anything. They think a side project must be impressive or original, so they set the bar impossibly high. The result is no portfolio at all—just a lot of good intentions.
Another mistake is trying to build something too large. A massive project can take months or years, and during that time you have nothing to show. You also risk losing motivation when progress is slow. Instead of a finished product, you have a work-in-progress that never sees the light of day. This defeats the purpose of creating proof of skill.
A third mistake is keeping your work private. Some people build projects but never share them. They might feel shy or think the work isn't good enough. But a side project only serves as proof if others can see it. You need to put it out there—on a personal website, a public repository, or a professional network. Without visibility, it's just a hobby, not a portfolio piece.
A simple way to do it
Start by choosing a small, specific problem you can solve in a short time—ideally a weekend or a few evenings. The problem should be related to the field you're moving into, but it doesn't have to be complex. For example, if you're moving into data analysis, you could analyze a publicly available dataset and create a simple visualization. If you're moving into web development, you could build a personal landing page or a small tool that calculates something useful.
Once you have your idea, break it down into tiny steps. Write a list of tasks, each of which can be completed in 30 minutes or less. This makes the project feel manageable and gives you a clear path forward. As you complete each task, check it off. This visual progress will keep you motivated. Don't worry about making it perfect; focus on making it work. You can always refine it later.
When you're done, share it. Create a simple write-up that explains what you built, why you built it, and what you learned. Include a link to the project if possible. Post it on your professional profiles or share it with communities related to your new field. Ask for feedback, and be open to suggestions. Then, start another small project. The goal is to build a habit of creating and sharing, so that over time you have a collection of work that demonstrates your skills.
What to pair it with
Side projects work best when paired with deliberate learning. As you build, you'll encounter gaps in your knowledge. Use those moments as opportunities to learn new skills. For example, if you're building a website and need to style it, take a short tutorial on CSS. This just-in-time learning is more effective than trying to learn everything upfront because you immediately apply what you learn.
Pair your projects with reflection. After each project, take a few minutes to write down what went well, what was challenging, and what you would do differently next time. This reflection turns experience into insight and helps you articulate your growth. It also gives you material for interviews or conversations about your work.
Another powerful pairing is with job shadowing or informational interviews. When you talk to people in your target field, ask them what kinds of projects would impress them. Then build one. This ensures your side projects are relevant and valued. It also shows initiative—you're not just building randomly; you're building with purpose. Finally, pair your projects with a simple portfolio. Even a basic website that lists your projects with descriptions and links can serve as a central hub for your work.
When to slow down
It's easy to get caught up in side projects and neglect other important aspects of your career change, like networking or applying for jobs. If you find that you're spending all your free time on projects but not making progress toward actual job opportunities, it's time to slow down. Remember, the goal is proof of skill, not endless learning. Set a limit: for example, dedicate a certain number of hours per week to side projects, and stick to it.
Also, slow down if you're feeling burned out. Side projects should energize you, not drain you. If you're forcing yourself to work on something you no longer enjoy, take a break. Reassess why you started and whether the project still aligns with your goals. It's okay to abandon a project that isn't serving you. The point is to build a body of work over time, not to torture yourself.
Finally, slow down when you're about to share something publicly. Take a moment to review your work for quality and clarity. Make sure it represents you well. But don't let perfectionism stop you from sharing altogether. A good rule is: if it works and demonstrates your skill, share it. You can always update it later. The key is to keep moving forward without rushing into mistakes.
Questions people ask
Q: How many side projects do I need to show proof of skill? A: There's no magic number, but quality matters more than quantity. Two or three well-executed projects that are relevant to your target field can be enough to demonstrate your abilities. Focus on depth rather than breadth. A single project that you can discuss in detail and that shows a range of skills might be more impressive than several shallow ones.
Q: What if I don't have any ideas for a side project? A: Start by looking at problems in your daily life or in the field you want to enter. What tasks are repetitive or frustrating? Could you build a simple tool to solve that? Alternatively, recreate something that already exists but put your own spin on it. The goal is to practice and produce something, not to invent something completely new. You can also browse online communities for project ideas or challenges.
Q: Can I use side projects from my current job? A: You can, but be careful about confidentiality and ownership. If you work on something related to your job, make sure you have permission to share it publicly. It's often safer to create new projects outside of work that are clearly your own. If you do use work-related projects, focus on the skills you demonstrated rather than proprietary details. Always respect your employer's policies.