Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Build a Portfolio on GitHub
Transcript
- Lucas: So you've finished bootcamp. You've got the certificate, you've got the final project, and you've sent out maybe a hundred applications. You're getting rejection emails — or worse, silence. There's one thing that consistently changes that outcome, and it's not a better résumé. Luna: Let me guess — it's the GitHub profile. Lucas: Exactly. And not just having a GitHub account. I mean a thoughtful, curated portfolio of work that shows how you think, how you solve problems, and how you communicate. A recent survey from a recruiting platform — I think it was HackerRank — found that developers with a well-maintained GitHub profile receive about 30 percent more recruiter messages on LinkedIn. That's not a small edge. Luna: Thirty percent is huge when you're competing against hundreds of other bootcamp grads. But a lot of people don't know where to start. They have their final project up, maybe a couple of forked repos, and that's it. Lucas: Right. And forked repos with no original commits actually hurt more than they help. It signals that you haven't done independent work. So today I want to walk through three concrete things that turn a mediocre GitHub into one that gets you interviews. First, pick one problem domain and go deep. Second, write documentation that tells a story. Third, make one meaningful open source contribution per month. Luna: Let's start with the problem domain. What does that look like in practice? Lucas: So instead of having five unrelated projects — a to-do list app, a weather API wrapper, a calculator — you pick something like 'tools for freelance designers' or 'automation for job seekers.' And you build three or four projects around that theme. Maybe a tool that scrapes job listings and filters by salary, a second that auto-generates cover letters using a template, and a third that sends email alerts when new jobs match your criteria. Now an employer sees a pattern. You care about job search automation. You're building a toolkit, not just completing exercises. Luna: That makes a ton of sense. I actually remember a story from a bootcamp grad named Maya — she built a Python tool that automated her own job search. She wrote a scraper for LinkedIn and Indeed, added a simple Flask front end, and documented the whole thing. She landed a role at a mid-size SaaS company because the hiring manager said, 'This is exactly the kind of initiative we need.' Lucas: That's a perfect example. And the documentation part is where most bootcamp grads drop the ball. You can write the cleanest code in the world, but if your README is one line saying 'this is my project,' nobody's going to take it seriously. Good documentation tells a story: what problem does this solve, how do you set it up, how do you run it, what are the limitations, what would you do next. Luna: And include a screenshot or a GIF of it working. That's a quick visual signal that the project is real and functional. Lucas: Absolutely. A demo GIF in the README probably doubles the chance that someone actually looks at the code. I also recommend adding a short 'why I built this' section in the README. It makes the project feel human. Employers are looking for people who are curious and self-motivated, not just people who can follow a tutorial. Luna: That leads right into the third piece — open source contributions. What counts as meaningful? Lucas: Meaningful doesn't mean you have to rewrite the core algorithm of React. Start small. Look at the issue tracker of a project you actually use. Find issues labelled 'good first issue' or 'help wanted.' Fix a typo in the documentation — that's a contribution. Add a test. Improve error handling. The goal is to demonstrate that you can work within an existing codebase, follow the project's conventions, and communicate with a maintainer. That's a skill bootcamps don't always teach, but it's what you'll do every day on the job. Luna: And if you're nervous about the interaction, remember that most maintainers are thrilled when someone shows up and wants to help. They're not grading you. They're just happy the issue gets resolved. Lucas: Exactly. And once you make that first contribution, put it in your GitHub profile's pinned repos. It becomes a talking point in interviews. 'I contributed to this open source library, here's the pull request, here's what I learned.' That story is way more compelling than 'I built a calculator app.' Luna: So let's talk about the bigger picture. A lot of bootcamp grads feel like they're behind because they don't have a computer science degree. But a strong GitHub portfolio can actually level the playing field. It's proof of work. Lucas: Completely agree. A degree tells an employer you sat through four years of classes. A GitHub portfolio tells them you can ship code, work with others, and keep learning. In many ways, it's a better signal. I've talked to recruiters at companies like Stripe and Shopify who say they look at the GitHub profile before the résumé. The résumé tells them what you claim you can do. The GitHub shows them what you've actually done. Luna: And I think there's a psychological aspect too. When you have a portfolio you're proud of, you walk into interviews with more confidence. You have concrete stories to tell. It changes the dynamic from 'please hire me' to 'here's what I can do for you.' Lucas: That's a great way to put it. So let's get practical. If someone listening wants to start today, what's the very first step? I'd say pick that problem domain. It could be anything — productivity tools for students, a dashboard for local weather data, a habit tracker with data visualization. The domain doesn't matter as much as the consistency. Build one project, document it well, then build a second that extends the first. You'll have a portfolio that tells a story. Luna: And don't forget to link your GitHub on your LinkedIn, your résumé, and your personal website. Make it the easiest thing to find. Lucas: Yeah, put it in the top of your LinkedIn 'About' section. Don't bury it. Also, consider adding a 'GitHub' section to your LinkedIn profile — you can display up to five pinned repos. That's prime real estate. Luna: One thing I want to add — avoid the temptation to pad your profile with lots of small, trivial projects. Quality over quantity. A single well-crafted project with thorough documentation and a couple of open source contributions is worth more than a dozen half-finished tutorials. Lucas: Yeah, I've seen profiles with fifty repos and almost every one is a 'hello world' or a fork of a tutorial. That doesn't help. It actually makes you look unfocused. Better to have five solid repos that each demonstrate a different skill — maybe one shows your API design, another shows your front-end chops, another shows data processing. That's a signal of breadth and depth. Luna: And if you're building projects, think about the technologies you want to work with. If you want to get into data engineering, build something that processes a dataset and visualizes it. If you want front-end, build an interactive dashboard. Match the portfolio to the job target. Lucas: Exactly. Which brings me to a thought about the value of this show. We try to keep every episode practical and ad-free because we believe this kind of advice should be accessible to anyone making a career change. If you've found this conversation helpful — or any of our past episodes — there's a simple way to support that mission. It's buy me a coffee dot com slash fexingo. No pressure, no perks, just helping us keep the shows free of ads and focused on what matters. Luna: Yeah, it's a small gesture that makes a big difference for us. And it lets us keep doing deep dives like this without worrying about sponsors. Lucas: So back to the portfolio. The final piece I'd mention is consistency over time. A GitHub profile with commits from six months ago and nothing since looks like you gave up. Even if you're not actively job searching, try to make one small commit per week — fix a bug, update documentation, add a test. It keeps your profile alive and shows you're still learning. Luna: And if you're working on a side project, treat it like a real product. Use issues, milestones, maybe even a project board. That shows you understand how software development works in a team setting. Lucas: Right. And one more thing — if you're not sure what problem to solve, look at your own life. What repetitive task do you do every day that could be automated? That's your first project. It's authentic, you're motivated to finish it, and you'll use it yourself. That passion comes through in the code and the documentation. Luna: And if you're stuck, start with a fork of an existing open source project. But don't just leave it forked. Add a feature, fix a bug, or improve the documentation. That's still meaningful work. Lucas: Alright, let's wrap this up. The single biggest takeaway from today: your GitHub portfolio is your most powerful job search asset as a bootcamp grad. Pick a domain, document your work, contribute to open source. Do those three things consistently, and you will stand out. The market is competitive, but the bar for a good portfolio is surprisingly low. Most people don't do this. If you do, you're already ahead. Luna: And remember, the goal isn't perfection. It's progress. Every commit, every README, every pull request is a step toward the job you want. Lucas: Well said. Thanks for listening, and we'll see you next time.