Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Build Portfolio Websites That Get Noticed
Transcript
- Lucas: You spend twelve weeks in a bootcamp. You build a weather app, a to-do list, maybe a clone of some popular site. Then you graduate and wonder why recruiters aren't flooding your inbox. Luna: And the standard advice is just 'build a portfolio.' But that's like telling someone to cook a great meal without giving them a recipe. Lucas: Exactly. So today I want to zoom in on what actually makes a portfolio website work for a bootcamp grad. Not the generic 'here's my projects' page — I mean a site that tells a story and proves you can deliver. Luna: We're talking about the difference between a digital resume and a sales pitch. Lucas: Right. And I want to anchor this with a real example. There's a bootcamp grad named Marcus — he came from retail management, did a six-month part-time program in web development. When he finished, he had the usual projects: a weather app using an API, a task manager with local storage, and a landing page for a fake coffee shop. Luna: That sounds like every bootcamp portfolio I've ever seen. Lucas: Exactly. And he wasn't getting callbacks. So he pivoted. Instead of showcasing three generic projects, he picked one — the coffee shop landing page — and turned it into a full case study. He actually reached out to a local coffee shop near him, offered to rebuild their outdated website for free. They said yes. Luna: That's smart. Real client, real problem. Lucas: He documented everything. The old site had a 40 percent bounce rate on mobile. He redesigned it with a mobile-first approach, added an online menu with filtering by dietary preference, integrated a simple ordering form through a third-party service. He published the project on his portfolio with before and after metrics: mobile load time went from 4.2 seconds to 1.1 seconds, bounce rate dropped to 22 percent, and the coffee shop saw a 15 percent increase in online orders within a month. Luna: So he didn't just say 'I built a website.' He showed the impact. That's the kind of thing that makes a hiring manager stop scrolling. Lucas: Exactly. And that's the first principle I want to talk about: specificity over breadth. A single project with measurable outcomes is worth more than a dozen tutorial projects. Luna: I think a lot of bootcamp grads feel pressure to show they can build lots of things. But recruiters are looking for problem-solvers, not feature factories. Lucas: Yeah. And the second principle is about the portfolio site itself. It needs to be clean, fast, and mobile-responsive. If your portfolio site takes three seconds to load on a phone, you've already lost the recruiter. Luna: Plus, if you're applying for a front-end role, your portfolio is literally the first test of your front-end skills. Lucas: Right. So use a simple static site generator or even plain HTML and CSS. No heavy frameworks unless you're showcasing a framework-specific project. And include a live demo link for every project — not just a GitHub repo. Recruiters don't want to clone your repo and run it locally. Luna: And if the project uses an API that requires a key, make sure the demo works with a demo key or a mock. Nothing worse than clicking a link and seeing a blank page. Lucas: Great point. Third principle: include a case study format for each project. Write a paragraph on the problem, your approach, the tech stack, and the results. Use bullet points for key metrics. And include a screenshot or a short screen recording. Luna: What about the about me section? I see a lot of bootcamp grads write generic bios like 'passionate developer seeking opportunities.' That doesn't say anything. Lucas: It's filler. Instead, connect your previous career to tech. Marcus's about section said something like 'After six years managing a retail team of 15, I learned how to optimize workflows and communicate across departments. Now I apply that same mindset to building web applications that solve real business problems.' That's specific and shows transferable skills. Luna: It also shows that you're not just a coder — you understand business context. That's huge for non-technical hiring managers. Lucas: Exactly. Fourth principle: include a clear call to action. Have a contact form, a link to your LinkedIn, and maybe a calendar link for a quick chat. Make it as easy as possible for a recruiter to reach you. Luna: And make sure your LinkedIn profile matches the story your portfolio tells. I've seen portfolios that say one thing and LinkedIn that says another. That inconsistency can hurt. Lucas: Great catch. Now, let's talk about mistakes. One big one is including every single project you've ever done, including the tutorial ones. That dilutes your brand. Only show work that you're proud of and that demonstrates a skill a job description asks for. Luna: Another mistake is neglecting accessibility. If your portfolio site isn't keyboard-navigable or has poor color contrast, it's a red flag for companies that care about inclusive design. Lucas: Absolutely. And a third mistake: no performance optimization. Compress images, minify CSS and JavaScript, use lazy loading. A fast site shows you care about user experience. Luna: So what about hosting? Should bootcamp grads pay for hosting or use free options? Lucas: Free options like GitHub Pages or Netlify are perfectly fine. But use a custom domain — yourname dot com — it costs about ten to fifteen dollars a year and looks professional. It's one of the cheapest investments you can make. Luna: Totally agree. And it's easier to remember than 'yourname.github.io'. Lucas: Okay, let's come back to Marcus. After he rebuilt his portfolio with that one case study, he applied to fifteen jobs. He got five callbacks and two offers within three weeks. The offer he accepted was at a mid-size e-commerce company, front-end developer, sixty-five thousand starting salary — which is solid for a first tech role in a mid-cost city. Luna: That's a great outcome. And it all started with focusing on one real project instead of a dozen generic ones. Lucas: Right. And I want to emphasize that this approach works even if you don't have a real client. You can create a fictional project but treat it like a real one: define a problem, design a solution, and measure the impact. The key is to show your thinking process. Luna: Or you could contribute to an open-source project and document your contributions. That's another way to show real-world impact. Lucas: Good point. And that leads to another principle: include a section for contributions or side projects that aren't full apps but show collaboration, like pull requests you've made or documentation you've improved. Luna: So we've covered specificity, design, case studies, about section, call to action, and avoiding common mistakes. Anything else? Lucas: One more thing: keep your portfolio updated. If you learn a new technology, add a project that uses it. If you land a job, update your portfolio to reflect your new role. An outdated portfolio suggests you've stopped learning. Luna: That's a good rule of thumb. I'd also recommend asking a friend or mentor to review your portfolio before you start applying. Fresh eyes catch things you miss. Lucas: Absolutely. And if you're not sure where to start, there are plenty of free templates out there. But customize them — don't just change the name and call it done. Recruiters have seen those templates. Luna: Lucas, I'm curious — have you seen any bootcamp grads successfully use a portfolio that wasn't a traditional website? Like a GitHub profile or a CodePen? Lucas: Yeah, but those are supplementary. A portfolio website is your home base. GitHub and CodePen are great for showing code snippets and experiments, but they don't tell a story. Your portfolio is where you control the narrative. Luna: That makes sense. So the website is the anchor, and then you link out to your other profiles. Lucas: Exactly. And if we've helped you think through your career move or your portfolio strategy, we want you to know something. This show is completely ad-free, and that's only possible because a small group of listeners chip in monthly through buy me a coffee dot com slash fexingo. It's a simple way to keep this resource available to everyone. Luna: Yeah, it's a small thing that makes a big difference. We really appreciate everyone who supports the show. Lucas: So back to portfolios — one final tip: include a testimonials section if you have any. If Marcus's coffee shop client said something nice, he could put that on his site. Social proof is powerful. Luna: Even a LinkedIn recommendation can be repurposed there. Lucas: Right. And if you're just starting out, you can ask a classmate or a mentor to write a short blurb about working with you. It doesn't have to be a client. Luna: So to wrap up, a strong portfolio is focused, tells a story, shows real impact, and is technically solid. That's the recipe. Lucas: And it's achievable. Marcus did it in a weekend after his bootcamp. You can too. Luna: Next episode we'll talk about how to leverage your portfolio in interviews. Until then, keep building.