Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Use Open Source Contributions to Land Jobs
Transcript
- Lucas: Luna, we talk a lot on this show about portfolios and side projects as the great equalizer for bootcamp grads who don't have a computer science degree. But there's one specific kind of portfolio work that I think gets overlooked, and it might actually carry more weight with hiring managers than a polished personal project. Luna: Okay, I'm intrigued. What's the secret weapon? Lucas: Open source contributions. Not just forking a repo and adding a star — actual meaningful pull requests that solve real problems. I've been digging into hiring data from a few mid-size tech companies, and the signal to noise ratio on a candidate with a couple of merged PRs is surprisingly high. Luna: That's interesting because I think a lot of bootcamp grads feel intimidated by open source. Like, 'I just learned JavaScript last month, who am I to fix a bug in a project with thousands of lines of code?' Lucas: Right, and that fear is totally normal. But the reality is that many open source projects — especially the ones that are actively maintained — have a culture of welcoming first-time contributors. There are even initiatives like 'First Timers Only' and labels on GitHub like 'good first issue' that are specifically designed for people who are new to the ecosystem. Luna: So where does a bootcamp grad even start? I imagine there are thousands of projects out there, and it's easy to get paralyzed by choice. Lucas: Yeah, choice paralysis is real. I'd say the smartest approach is to start with tools you already use in your learning journey. If you're building projects with React, look at the React ecosystem — something like a documentation fix, a typo in a readme, or a small CSS bug in a component library. Those are low-risk, high-visibility contributions that teach you the workflow of opening a pull request, communicating with maintainers, and handling code review. Luna: And documentation fixes — that's practically a rite of passage. I think a lot of people don't realize that maintainers actually appreciate those because documentation is often the last thing they have time to polish. Lucas: Exactly. There's a well-known story from a few years back about a bootcamp grad named Sarah who got hired at a SaaS company called Stitch Fix. She started by submitting a single pull request to fix a broken link in their documentation. That one contribution led to a conversation with a senior engineer, which led to an interview, and eventually a job offer. It's not an exaggeration to say that open source can be a direct pipeline to employment — especially for companies that use those tools themselves. Luna: That's a great example. And it's not just about the code — it's about showing that you can collaborate in a public, transparent way, which is exactly how most tech teams work internally. Lucas: Right. When I talk to engineering managers, they consistently say that a candidate who has a history of merged pull requests demonstrates three things: first, that they can read and understand an existing codebase — not just write greenfield code from scratch. Second, that they can follow the conventions and style guidelines of the project. And third, that they can handle feedback gracefully in a code review setting. Luna: And all of those are skills that bootcamp projects don't always teach, because you're usually the sole author of your project and there's no code review process. Lucas: Exactly. So the question becomes: how do you get started without feeling like an imposter? I'd say the most important thing is to pick a project that has a welcoming community. Look for repos that have a 'CONTRIBUTING.md' file, a code of conduct, and labels like 'help wanted' or 'good first issue'. The React Native repo, for example, has a dedicated 'good first issue' label that's regularly updated. Luna: And what about the process itself? I think the workflow of forking, branching, committing, and opening a pull request can be intimidating the first time, even if you've used Git before. Lucas: Totally. That's where practice with a few small, low-stakes contributions helps. I'd actually recommend making your very first PR to something like 'first-contributions' — it's a repo specifically designed to walk you through the entire Git workflow with a tiny change. Once you've done that, the mechanics aren't scary anymore. Luna: That's a smart way to build muscle memory. And then you can move on to something like fixing a typo in a popular library's documentation. I've seen people land jobs just from that — it's a foot in the door. Lucas: Yeah. And here's the thing: once you have a few contributions under your belt, your GitHub profile becomes a much stronger signal than a resume bullet point that says 'completed a bootcamp'. Because any employer can see the actual code, the conversation in the PR, and the fact that a maintainer — a real engineer at a real project — approved your work. Luna: So it's basically like having a third-party endorsement built into your portfolio. I love that. Lucas: Exactly. And it's not just for junior roles. Even experienced engineers use open source contributions as a way to signal expertise in a specific technology. For bootcamp grads, though, it's one of the fastest ways to close the credibility gap with candidates who have a computer science degree. Luna: Let's talk about the time investment. If someone is job hunting and needs results in, say, eight to twelve weeks, how many contributions should they aim for? Lucas: I'd say two to three quality contributions over a couple of months is enough to make a meaningful difference. The key is quality over quantity. One well-documented bug fix that solves a real issue is worth more than ten trivial README typos. And you can often find issues that are tagged 'good for beginners' that are actual bugs, not just documentation. Luna: And what about the interview itself? How do you talk about open source work in an interview without sounding like you're just listing tasks? Lucas: Great question. You want to frame it as a story: 'I noticed an issue in this project I was using, so I dove into the codebase, reproduced the bug, wrote a fix, and submitted it for review. The maintainer suggested a small change, I iterated, and it got merged.' That narrative shows initiative, problem-solving, and collaboration — all in one. Luna: It also shows that you're the kind of person who takes ownership of problems, which is a huge green flag for any employer. Lucas: Right. And one more thing — don't underestimate the networking effect. When you submit a PR to a widely-used project, the maintainers are often senior engineers at companies you might want to work for. A positive interaction with them can lead to a referral or at least a conversation. Luna: So it's not just portfolio building, it's also relationship building. I think a lot of bootcamp grads don't realize how much of tech hiring is about trust and reputation. Lucas: Exactly. And that trust is built in small increments — one PR at a time. Luna: You know, Lucas, it's funny — we've been doing this show for a while now, and I think if even one listener today decides to make their first open source contribution because of this conversation, that's a pretty tangible win. Lucas: I hope so. And honestly, if this episode helped you think through your career move — even just gave you one concrete idea — that's worth something. If it's worth a coffee to you, there's a link: buy me a coffee dot com slash fexingo. No pressure, but listener support is what keeps this show ad-free and focused on practical advice. Luna: Yeah, completely agree. Every little bit helps us keep doing deep dives like this one. Lucas: Alright, back to the topic. One thing we haven't touched on is how open source contributions can be especially powerful for bootcamp grads targeting remote-first companies. Many of those companies, like GitLab and Zapier, have cultures that are deeply rooted in open source — they literally use public contributions as a primary hiring signal. Luna: That's a great point. And I know GitLab has a public handbook that explains exactly how they evaluate contributors for potential hires. It's almost like a cheat sheet for career changers. Lucas: Exactly. So if you're a bootcamp grad and you're thinking about applying to a remote company, contributing to their open source projects — or even just engaging with their community by filing good bug reports — can put you on their radar before you ever submit a resume. Luna: It's like a backdoor to the hiring pipeline. And it's completely meritocratic — your code speaks for itself, regardless of your background. Lucas: Right. So to wrap up, here's a concrete action plan for anyone listening: first, set up your GitHub profile with a clear bio and links to your portfolio. Second, find a project you use or admire that has a 'good first issue' label. Third, make a small documentation fix or a trivial bug fix to learn the workflow. Fourth, gradually take on more substantial issues. And fifth, mention your contributions in your resume and cover letter — link to the PRs. Luna: And don't forget to be patient and kind to yourself. The first PR can feel huge, but every contributor started somewhere. Lucas: Absolutely. Open source is a marathon, not a sprint. But if you stick with it, it can be one of the most rewarding parts of your career journey.