Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Build a Portfolio That Gets Noticed
Transcript
- Lucas: So let me ask you something, Luna. If a bootcamp grad sends you a link to their portfolio, how long do you spend looking at it before you decide yes or no? Luna: Honestly? Maybe thirty seconds. If I don't see something that grabs me in the first few seconds, I'm gone. Lucas: Right. And that's the reality for most hiring managers. They're not reading your 'About Me' paragraph. They're scanning for signal. So today, I want to talk about what actually makes a portfolio stand out — not just 'build a calculator app' advice, but how to structure your projects so they tell a story. Luna: I love that. Because I see so many portfolios that are just a list of assignments from the bootcamp. Like, here's a weather app, here's a to-do list, here's a blog. No context. Lucas: Exactly. And that's fine if you're just learning. But if you want a job, you need to shift from showing what you built to showing the problem you solved. Let me give you a concrete example. I talked to a grad from a web dev bootcamp — let's call her Priya. She didn't have a fancy internship. But she volunteered to build a small inventory system for a local food bank. It was a simple CRUD app, maybe a week of work. Luna: But she could say it saved them ten hours a week of manual spreadsheet work. That's way more impressive than building the twentieth weather app. Lucas: Exactly. She framed the project around impact: 'I reduced manual data entry by 70 percent for a nonprofit serving 500 families per week.' That's the kind of thing a hiring manager remembers. It shows you understand business context, not just syntax. Luna: And it's real. It's not a tutorial project. You can actually point to it and say, this is being used by real people. Lucas: Right. So the first principle is: every project in your portfolio should answer three questions. What was the problem? What did you build? And what was the measurable outcome? If you can't answer all three, maybe that project doesn't belong on your front page. Luna: I'd add a fourth: what did you learn? But that's more for the blog post or the readme. The recruiter just needs the headline. Lucas: Yeah, the readme is where you go deeper. And honestly, a well-written readme is underrated. It's often the first thing a technical person reads after the project demo. Luna: Okay, but let's be real — a lot of bootcamp grads don't have a real-world project like Priya's. They have class projects. What do you do if you're in that position? Lucas: Fair question. One option is to contribute to an open source project. Even a small fix — a documentation update, a bug fix — shows you can work on a codebase you didn't write, which is most of what you'll do on the job. Luna: I think open source can be intimidating for beginners. A lot of projects have complex setup steps and unwritten rules. Lucas: It can be. But there are projects that explicitly welcome first-timers. There's a list called 'First Timers Only' — you can find issues tagged 'good first issue.' And honestly, even if you just fix a typo in documentation, that's a contribution. It shows you read the docs, which is a skill in itself. Luna: I like that. But I also think building something from scratch, even if it's not for a real client, can be powerful if you treat it like a real product. Add tests, write a readme, deploy it. Show the whole lifecycle. Lucas: Absolutely. And that brings me to the second principle: quality over quantity. I'd rather see three solid projects than ten half-finished ones. Curate. Pick the projects that best tell the story of the kind of engineer you want to be. Luna: Right. If you want to be a front-end developer, don't lead with a backend API. Lead with the polished UI project. It sounds obvious, but I see people burying their best work on page two. Lucas: Yeah, the ordering matters. And the visual design matters too. Even if you're not a designer, a clean layout with good typography and consistent spacing goes a long way. Use a template if you have to. But don't make the recruiter hunt for the demo link. Luna: Quick honest thing — a handful of listeners chip in monthly through Buy Me a Coffee dot com slash fexingo, and that's literally what funds making episodes like this. No ads, no sponsors — just listeners who find value in the show. So if you've gotten something useful from any episode, that's the way to keep it going. Lucas: Yeah, it's a small group, but it makes a big difference. And it keeps us independent. Alright, back to portfolios. Another thing I see missing from bootcamp portfolios: a section for 'non-code' skills. Communication, project management, domain knowledge. Those are often what get you hired over someone with a CS degree. Luna: Interesting. So you're saying if someone came from marketing and then did a bootcamp, they should highlight that they understand stakeholder management? Lucas: Exactly. Frame your past experience as an asset. 'I can translate business requirements into technical specifications.' That's gold for a startup or a mid-size company. Your previous career is not a weakness — it's your differentiator. Luna: Okay, but what about the portfolio itself? Should they build it from scratch or use a platform like GitHub Pages or a portfolio builder? Lucas: I'd say build a simple static site from scratch. It shows you can deploy something. But don't spend two weeks perfecting the CSS. Use a framework or a template. The content is what matters. And make sure it's mobile-responsive. Recruiters will look at it on their phone. Luna: And include a link to your GitHub. Even better, pin your best repos. And make sure the readme is well written. I've clicked on so many repos that just say 'my project' — that's a missed opportunity. Lucas: Yes. And include a screenshot or a gif of the project in action. Visuals catch the eye. A recruiter might not read the readme, but they'll look at a screenshot. Luna: So let's sum it up. First, focus on impact — show the problem and the outcome. Second, curate for quality not quantity. Third, highlight your unique background. Fourth, make it easy to navigate and visually clean. Lucas: And fifth — iterate. Your portfolio is not static. As you learn more, update it. Replace weaker projects with stronger ones. And always have a live demo if possible. Nothing beats clicking a link and seeing the app work. Luna: I think that's a solid framework. One last thing — how important is the domain name? Should you buy a custom domain? Lucas: It's nice but not necessary. yourname.github.io is fine. But if you can get yourname dot com for ten bucks, it looks a bit more professional. It's a small signal. Luna: Alright, I think we've given people a clear path. Now go update that readme. Lucas: And if you're listening and you have a portfolio story — good or bad — we'd love to hear it. Drop us a note. We might feature it in a future episode.