Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Build Credibility Without a Degree
Transcript
- Lucas: You've finished a coding bootcamp. You can build a full-stack app, you understand REST APIs, you know your way around a database. But when you sit across from a hiring manager who has a CS degree from a four-year university, there's this unspoken question in the room. Luna: Right — 'Why should I trust you over someone who spent four years studying this?' How do you answer that without a diploma on the wall? Lucas: Exactly. And my answer — and I've seen this work for dozens of career changers — is that you don't need a degree. You need a credibility stack. A collection of signals that together say 'I know what I'm doing.' Luna: Credibility stack. I like that. What are the layers? Lucas: There are four main ones, and I want to be specific here. First, certifications — but not just any certifications. Bootcamp certs alone don't move the needle. I'm talking about industry-recognized ones: AWS Certified Solutions Architect, Google's Professional Cloud Architect, the CISSP if you're going into security. Luna: Those take real study time. I know someone who spent three months just on the AWS Solutions Architect prep. Lucas: And that's the point — the signal is in the effort. A bootcamp grad who passes the AWS SA exam is telling a hiring manager 'I can learn complex systems on my own.' That's worth more than a data structures course from 2018. Luna: Layer two? Lucas: Open-source contributions. Not just forking a repo and fixing a typo. I mean meaningful contributions — adding a feature, writing documentation that actually helps, triaging issues. One of my favorite examples: a bootcamp grad I know contributed a new parser to a popular JavaScript linting tool. That single pull request got him three interview requests. Luna: Because it's public proof of competence. Anyone can claim 'I know JavaScript' on a resume. A merged PR is evidence. Lucas: Layer three is writing and speaking. Start a blog, write about what you're learning. Doesn't have to be fancy — Medium, Dev.to, your own site. Even better, speak at a local meetup. There's a network called Papers We Love that welcomes newcomers. Or just present your capstone project at a bootcamp demo day and invite local developers. Luna: I've seen people get hired just because a hiring manager read their blog post about debugging a tricky issue. It's like a resume that keeps working for you. Lucas: Layer four — and this is the one most people skip — build something with real users. Not a todo app tutorial clone. Build a tool that solves a problem for a specific group. A Chrome extension that helps designers export colors. A Slack bot for standup reminders. A VS Code snippet pack for React developers. Luna: That's a step up from the typical bootcamp portfolio. How many users is 'real'? Lucas: Honestly? Even twenty users who aren't your mom sends a strong signal. Because it means you shipped something, you handled feedback, maybe you fixed a bug. That's more than most junior devs with degrees have done. Luna: So the whole stack is: certs, open source, writing or speaking, and a real-user project. Do you need all four? Lucas: No. Two strong ones can be enough — especially if one of them is the real-user project. But the combination is what creates a narrative. 'I don't have a CS degree, but here are four independent validations of my skills.' That's hard to argue with. Luna: Let me push back a little — isn't there a risk of spreading too thin? If you're studying for an AWS cert, contributing to open source, writing blog posts, and building a side project, when do you actually apply for jobs? Lucas: Fair point. The key is sequencing. Start with the project — that's your anchor. While you're building it, you'll naturally encounter questions you can blog about. Those blog posts become material for a meetup talk. And by the time you're looking at jobs, you pick one cert to study for. It's not four things simultaneously — it's a pipeline. Luna: So the project comes first. Any tips on choosing what to build? Lucas: Solve your own pain. If you've ever been frustrated by a tool at work or a missing feature in an app you use, that's your starting point. One bootcamp grad I know built a simple command-line tool to rename batches of files because his wife, a photographer, was spending hours on it. That tool got picked up by a few blogs, and suddenly he had a portfolio piece that actually mattered. Luna: That's a great story. And it's not about the complexity — it's about the specificity. Lucas: Exactly. A simple tool that solves a real problem is infinitely more impressive than a complex app that nobody uses. Hiring managers see a thousand 'Twitter clones.' They remember the person who built a tool that saved an accountant twenty hours a month. Luna: What about the writing layer? A lot of bootcamp grads tell me they don't feel qualified to write about tech because they're still learning. Lucas: That's the wrong mindset. You don't need to be an expert. Write about what you just learned — that's often more valuable because you remember the struggle. A post called 'How I Finally Understood JavaScript Closures' can help a hundred people who are stuck at the same point. And it shows you can communicate technical concepts, which is a huge skill. Luna: And speaking — meetups can be intimidating for newcomers. Any advice? Lucas: Start small. A lightning talk — five minutes. Or even just do a show and tell of your project at a local bootcamp alumni meetup. The goal isn't to be the next keynote speaker, it's to get comfortable talking about your work publicly. That confidence shows in interviews. Luna: So the credibility stack isn't just about signaling to employers — it's also about building real confidence. Lucas: Exactly. And that's something a degree can give you — four years of incremental wins. But bootcamp grads can build that too, just faster and more targeted. Every merged PR, every blog comment thanking you, every user who downloads your tool — that's evidence that you belong. Luna: I think one of the biggest hurdles career changers face is impostor syndrome. Does the credibility stack help with that? Lucas: Massively. Because impostor syndrome often comes from a lack of concrete evidence. When you can point to a real project with real users, it's hard to tell yourself you're a fraud. The stack builds an external record of competence that your internal critic can't argue with. Luna: Let's talk about the certification layer again — because I know some people worry that certs are just paper and don't prove real skills. Lucas: That criticism has some truth, especially for entry-level certs. But the higher-level ones — like the AWS Professional tier or the Google Architect cert — require hands-on experience. You can't brain-dump your way through those. So they do signal real capability. Plus, they get you past HR filters that screen for keywords. Luna: So certs are more about getting through the door, while the project and open-source work are what close the deal. Lucas: Exactly. Think of it as a two-stage process. The cert gets you the interview. The project and contributions get you the job. Luna: I want to ask about open source specifically. How do you find good projects to contribute to as a beginner? Lucas: Look for projects with a 'good first issue' label. GitHub has a whole curated list. Also, documentation contributions are underrated — many projects have terrible docs, and improving them is a genuine contribution. Start there. Then, as you get comfortable, look for issues tagged 'help wanted.' Luna: And you mentioned that a single meaningful contribution can outweigh a dozen small ones. What's a 'meaningful' contribution? Lucas: Something that affects the user experience. Adding a new feature, fixing a bug that users reported, improving performance. Not just fixing a typo or adjusting a color. That's not to say those are worthless — they're fine for practice — but they don't move the credibility needle. Luna: One thing I've noticed is that bootcamp grads often undervalue their own experience. They think 'I only built a simple tool' or 'I only wrote one blog post.' But that's more than 90 percent of people who want to break into tech actually do. Lucas: Exactly. The bar is lower than people think. Most applicants have no public work at all. A bootcamp grad with one solid project, one blog post, and one open-source contribution is already in the top tier of candidates. Luna: So what's the one thing you'd tell a bootcamp grad listening right now to do this week? Lucas: Pick a small, real problem — ideally something you or someone you know is facing — and build the simplest possible solution. Then put it on GitHub, write a short README, and share it on LinkedIn or Twitter. That single action starts the credibility stack. Luna: And you know, if we've helped you think through a career move or decision, it's worth mentioning that listener support keeps these episodes ad-free and accessible to everyone. A couple of dollars a month genuinely makes a difference — buy me a coffee dot com slash fexingo, if you've gotten something out of the show. Lucas: Yeah, it's a small thing that adds up. We don't run ads, so it's really the community that keeps this going. Luna: Exactly. And speaking of community — if you build that project, share it with us. We'd love to feature it in a future episode. Lucas: That's a great idea. So to wrap up: forget the degree. Build a credibility stack. Start with one small real project, then add a blog post, then a meetup talk, then a certification. Layer by layer, you build a reputation that speaks louder than any diploma. Luna: And you don't have to do it all at once. Just pick one layer and start today. Lucas: Exactly. See you next time.