Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / Bootcamp Grads in Nonprofit Tech
Transcript
- Lucas: Most of our listeners know us for breaking down how bootcamp grads break into proptech, healthtech, or even quant finance. But there is a massive, underserved market that rarely gets discussed in these circles: the nonprofit and public sector technology space. Luna: Right. And it is weirdly ironic because everyone talks about tech saving the world, but then they all rush to join the highest bidder in Silicon Valley instead of fixing the systems actually running local governments and charities. Lucas: Exactly. And the data backs this up. A recent report from the Urban Institute highlighted that nearly seventy percent of large nonprofits say their technology infrastructure is outdated or inefficient, yet only five percent of tech job postings target those sectors. It is a supply problem, not a demand problem. Luna: So you have organizations desperate for help but no one speaking their language. How does a junior developer even find those doors? Lucas: The first thing you need to understand is that the role rarely looks like a standard senior engineer position. At places like Feeding America or local housing authorities, they do not have twelve layers of management. They have one person who wears every hat, and they need someone who can build something useful by Friday, not next quarter. Luna: That sounds exhausting. Do they have the budget for expensive tools or just whatever is free on GitHub? Lucas: Usually the latter. You will see a lot of reliance on open-source stacks, Microsoft Office integrations, and basic cloud services. The key skill is not mastering Kubernetes; it is knowing how to connect a Salesforce database to a simple Python script that automates donor reporting. It is pragmatic, messy, and incredibly high-impact. Luna: I remember reading about a group in Detroit using low-code platforms to track vaccine distribution during the peak of the pandemic. They didn't have engineers, just volunteers with some training. Lucas: That is a perfect example. And that is where bootcamp grads shine. You are trained to be hands-on and fast. In the corporate world, you might spend six months planning an architecture review. In the nonprofit world, if you spend six months planning, the crisis has passed and you are irrelevant. Luna: But isn't the pay usually terrible? I mean, we are talking about people trying to pay off student loans. Lucas: It is a valid concern, but the landscape is shifting. We are seeing more hybrid models where startups build tools for nonprofits and offer them at subsidized rates. Companies like Salesforce and Amazon have dedicated grant programs. So while the base salary might be lower than Big Tech, the cost of living adjustments and the remote nature of many roles can make it financially viable. Luna: So it is not about going broke for a cause. It is about finding organizations that have secured sustainable funding. Lucas: Precisely. Look at Code for America. They run fellowships that place engineers in city halls across the country. One fellow I spoke with recently was working on streamlining permit approvals in Oakland. She wasn't building AI models. She was writing scripts to parse PDF forms and feed them into a database. Simple work, but it cut processing time by forty percent. Luna: That feels tangible. You can point to a line of code and say I fixed that bottleneck. Corporate tech often feels like moving numbers around in a spreadsheet nobody reads. Lucas: It does. And that visibility is crucial for your resume. If you can say you reduced operational costs for a major charity by twenty percent, that is a story any future employer will respect. It shows you understand business value, not just clean code. Luna: How do you translate that when applying? Most resumes are tailored for keywords like microservices or CI/CD pipelines. Lucas: You flip the script. Instead of listing technologies, lead with outcomes. Your summary should say you automate workflows to save time, not that you know React and Node. When you list your projects, describe the problem solved, not the stack used. Did you help a food bank distribute meals faster? Did you help a legal aid clinic manage client intake? That is the hook. Luna: Do you recommend volunteering first to get a foot in the door? Lucas: Yes, but with a caveat. Don't just sign up for anything. Go to sites like Catchafire or Taproot Foundation. These platforms match professionals with specific skill sets to nonprofits. Treat it like a freelance gig. Set boundaries, define the scope, and deliver. If you burn out doing unpaid work for six months, you are not helping anyone. Luna: Boundaries are so important. I think a lot of bootcamp grads feel guilty if they aren't giving everything away immediately. Lucas: They do. But sustainability matters. The best way to give back long-term is to build a career that allows you to keep contributing. Maybe you take a corporate job for two years, save money, and then pivot to a nonprofit leadership role. Or maybe you stay in tech but consult part-time for three different causes. Luna: There is also the networking angle. Nonprofits are smaller communities. Your reputation travels faster. Lucas: Absolutely. In a firm of five thousand people, you are a number. In a nonprofit of fifty, you are the hero who fixed the email server. Those relationships become your professional safety net. I know several people who landed their current high-paying corporate roles solely because a former nonprofit colleague recommended them after seeing how reliable they were under pressure. Luna: That is a great point. Reliability is underrated in tech interviews. Lucas: It is huge. Especially when you consider the culture fit. Nonprofits often have flatter hierarchies. You might present your idea directly to the executive director. In big corps, you have to get past five middle managers before they hear your name. Luna: I can see the appeal. Less bureaucracy, more direct impact. But does the tech stack stagnate? I worry about falling behind industry standards. Lucas: It is a real risk if you only stick to legacy systems. But many modern nonprofits are adopting agile methodologies quickly because they have to compete for talent. You will still learn SQL, you will still use version control. The concepts transfer perfectly. You are not learning obsolete skills; you are learning efficient ones. Luna: Efficiency is always a good skill to have. What about the interview process itself? Is it technical or behavioral? Lucas: Heavily behavioral. They want to know if you care about their mission. Can you explain complex technical issues to a board member who doesn't code? That communication skill is worth more than raw coding speed in these environments. Prepare stories about empathy, patience, and clarity. Luna: So essentially, you are interviewing for a translator role as much as an engineer. Lucas: Spot on. You are the bridge between the technical reality and the human need. That is a powerful position to be in. Luna: It reminds me of that article about how government agencies are finally upgrading their IT systems after decades of neglect. Lucas: Yes, and that is another avenue. State and federal tech roles are opening up with better benefits and job security. The pace is slower, but the stability is unmatched. For someone looking to settle down and raise a family, that trade-off makes sense. Luna: Stability plus purpose. That is a combination fewer people talk about in the hustle culture era. Lucas: It really is. And for bootcamp grads who might feel imposter syndrome about not having a CS degree, this sector is very forgiving. They care about what you can build, not where you studied. It is a meritocracy of output. Luna: That is encouraging. It takes the pressure off the pedigree and puts it on the portfolio. Lucas: Exactly. Build a small project that solves a real problem for a local organization. Put it on your GitHub. Send it to them. Watch what happens. Luna: Proactive and practical. I like that approach. Lucas: Before we go, I want to mention something about the show. We produce this network entirely on listener support. If we have helped you think through a career move or decision, consider buying us a coffee at buy me a coffee dot com slash fexingo. It keeps the servers running and the research deep. Luna: Yeah, and honestly, your contributions let us dig into niches like this one instead of just covering the same trending topics everyone else is. Lucas: It makes a difference. Thanks for listening. Where do you think the biggest untapped opportunities lie for tech workers looking to make a difference?