7 Side Projects That Actually Impress Hiring Managers (And 3 That Don't)

You're scrolling LinkedIn at 10 PM and see another post about someone who built a SaaS that hit $10K MRR in three months. You feel that familiar pressure to start something—anything—that proves you're not just clocking in and out. But here's the thing most career advice misses: not all side projects are created equal. Some quietly signal competence and curiosity. Others scream "I'm desperate to look busy." After four years in product marketing and countless conversations with hiring managers, I've learned to spot the difference.

This list breaks down seven side project types that actually move your career forward—and three that waste your evenings without moving any needles.

What's a Side Project That Actually Helps Your Career?

The projects that matter share a pattern. They solve real problems you encounter. They force you to learn something you couldn't pick up in your day job. And they create artifacts you can point to during interviews without feeling like you're stretching.

A good side project isn't a separate life—it's an extension of your professional curiosity. It's something you'd genuinely want to discuss with a smart colleague over coffee, not something you're gritting your teeth to finish because you heard it looks good on a resume.

1. Build a Tool That Fixes Your Own Workflow

This is the holy grail of side projects because it demonstrates something hiring managers rarely see: initiative combined with self-awareness. When you build a tool to solve a problem you personally experience, you're showing you can identify friction, scope solutions, and ship something functional.

It doesn't need to be complex. A Google Apps Script that automates your weekly reporting. A Notion dashboard that tracks your job applications with custom views. A simple Python script that organizes your downloads folder by file type. The magic is in the thinking, not the code quality.

When interviewers ask about a time you identified a problem and solved it, you have a concrete answer. Better yet, you can share the tool and let them experience your solution directly. Lenny Rachitsky's analysis of product managers who build shows this pattern consistently predicts career acceleration.

2. Document a Complex Process You Had to Learn From Scratch

Knowledge documentation is underrated because it feels passive. It isn't. When you take something confusing you figured out and make it comprehensible for the next person, you're demonstrating communication skills that senior people notice.

Write a detailed guide on configuring a finicky API integration your company uses. Create a video walkthrough of a procurement process that took you three weeks to figure out. Build a decision tree for choosing between software options in your industry.

The format matters less than the clarity. Blog post, Notion page, YouTube video, GitHub repository—pick whatever you'll actually finish. Swyx's "Learn in Public" philosophy has helped countless developers accelerate their careers through documentation.

3. Analyze Public Data and Share Unexpected Insights

Data analysis projects signal analytical thinking without requiring you to collect anything yourself. Find a dataset related to your industry, ask an interesting question, and share what you discover.

A marketer might analyze App Store reviews for competitor apps to identify feature gaps. A finance professional could model salary progression using public compensation data. An operations person might map supply chain patterns from shipping manifests.

The key is the question—not the methodology. A simple analysis answering a genuinely interesting question beats sophisticated techniques applied to boring questions. Share your findings on LinkedIn or in industry Slack communities. The conversation that follows often matters more than the analysis itself.

4. Curate and Annotate Resources for Your Specific Niche

Curation gets dismissed as "just collecting links," but thoughtful curation with commentary demonstrates expertise. Anyone can find fifty articles on a topic. Explaining why specific resources matter—and what to ignore—shows judgment.

Create a newsletter covering industry news with your commentary. Build a reading list for people breaking into your field with difficulty ratings and prerequisites. Maintain a spreadsheet of tools in your category with honest pros and cons based on your testing.

This project type has compounding benefits. It forces you to stay current. It builds an audience of people in your space. And it creates a reference you actually use yourself. Ben Thompson's Stratechery started as exactly this—a curated analysis of tech news—and grew into a seven-figure business.

5. Volunteer Your Skills for a Cause You Actually Care About

Pro bono work gets a bad reputation because people do it thoughtlessly—designing logos for fake nonprofits, building websites that never launch. The version that works is different: find a small organization doing real work, identify a specific problem they have that matches your skills, and solve it properly.

Don't offer to "help with marketing." Offer to set up their email automation so they stop manually sending donor updates. Don't offer to "improve their website." Build them a simple dashboard that tracks their program outcomes.

The constraint forces focus. Small organizations have real problems but limited resources. Solving one concrete thing completely beats partially addressing five vague needs. Plus, you get references from people who've actually seen you work—often more valuable than the project itself.

Why Do Some Side Projects Hurt More Than They Help?

Not every project deserves your time. Some actively signal the wrong things to hiring managers who've seen too many resumes. Here are three categories to skip.

6. Skip: Generic Tutorial Projects Presented as Original Work

Following a tutorial to build a to-do app or deploy a static site is fine for learning. Presenting it as a project on your resume is risky. Experienced interviewers recognize tutorial code immediately—the same styling, the same structure, the same feature set.

If you learned something valuable, mention it briefly: "Built X while learning Y." But don't list the project itself as evidence of your capabilities. It suggests either naivety about what's impressive or willingness to exaggerate—neither signals you want to send.

7. Skip: Projects That Require Constant Maintenance You Won't Provide

Building a SaaS sounds impressive until it becomes a ghost town. When hiring managers click your project link and find a dead app, broken authentication, or a "coming soon" page that's been up for eight months, it suggests you don't finish things.

If you want to build something ongoing, commit to the maintenance or be honest about its experimental nature. A GitHub repository with clear documentation and a local demo is often more impressive than a deployed app that's clearly abandoned.

How Should You Choose Your Next Side Project?

Start with problems, not technologies. What frustrates you weekly? What did you recently figure out that took too long? What would you want to exist for your own use?

Then scope aggressively. A finished small project beats an ambitious unfinished one every time. Set a deadline—two weekends, one month, whatever feels slightly uncomfortable—and ship something complete by that date.

Finally, document what you learned, not just what you built. The career value comes from the stories you can tell about decision-making, obstacles overcome, and skills developed. A simple project with good stories beats a complex project you can't explain.

Your evenings are limited. Spend them on projects that teach you something real and create artifacts you're genuinely proud to share. The rest is just procrastination with extra steps.