Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Land a Job at a Nonprofit
Transcript
- Lucas: You spend twelve weeks learning React and Python, you build a clone of Twitter, and then you start sending out resumes. Almost everyone aims for the same names — Google, Stripe, a hot Series A startup. But I think there's a lane that gets overlooked, and it actually fits a lot of bootcamp personalities really well. Luna: Let me guess — you're about to say nonprofits. Lucas: I am. And I know the immediate reaction — 'I didn't go through a bootcamp to make fifty thousand dollars at a charity.' But the data from the 2025 Nonprofit Tech Impact Report tells a different story. Nonprofits are now competing for tech talent with real salaries, real titles, and a kind of project ownership that's actually hard to get at a big company. Luna: I worked at a civic tech nonprofit for two years after my own bootcamp. My title was 'software engineer', I owned the entire front end of a tool used by three hundred food banks, and I made sixty-eight thousand dollars. Not Google money, but I wasn't making fifty either. Lucas: And the report backs that up. Median salary for a mid-level software engineer at a large nonprofit — think the Red Cross, the Nature Conservancy — was ninety-two thousand in 2025. That's not life-changing, but in many cities it's a solid middle-class wage. And the work is often broader in scope because teams are smaller. Luna: Exactly. You're not just a front-end developer. You might be doing the front end, helping with the database, even talking to the program directors about what features they actually need. You get product sense way faster than someone at a company with fifteen layers of management. Lucas: So the first practical step is: find the right org. Not every nonprofit is tech-forward. You want to look at places with an explicit 'digital transformation' initiative or a dedicated product team. The report highlighted that organizations with over fifty million in revenue are the ones building in-house engineering teams. Smaller ones often outsource, which isn't the same experience. Luna: I'd add: look for job titles like 'software engineer', not 'webmaster' or 'IT coordinator'. If the job description is just 'maintain our WordPress site', that's not the role you want. You want somewhere that's building software, not just installing plugins. Lucas: Good filter. Another one: on the careers page, look for mentions of 'product manager' or 'designer'. If they have those roles, they're serious about building tech. And use Idealist, TechSoup's job board, and LinkedIn's 'nonprofit' industry filter. Those are the best aggregators. Luna: One thing I found really helpful was going to nonprofit tech meetups. I went to a 'Tech for Good' event in my city, and I met the CTO of my future employer. He was there looking for developers. That kind of networking is way more efficient than cold applying. Lucas: Absolutely. And speaking of the application itself — let's talk about how you frame your portfolio. If you've only built a Twitter clone and a weather app, you need to reframe those projects around impact. Say you built the weather app — talk about how it could help a disaster relief organization coordinate resources based on forecasts. That's a narrative shift, not a technical one. Luna: Yeah, they're not going to be impressed by your use of Redux. They want to know you understand their mission. In my interview, I spent half the time talking about how I'd approach building a tool for caseworkers. I didn't even get asked about algorithms. Lucas: And that's actually freeing for bootcamp grads who might not have a CS degree. Nonprofit interviews tend to focus more on problem-solving, collaboration, and your ability to learn. The second question they often ask is 'why us?' If you can't articulate a genuine connection to their mission, you won't get the job. Luna: Right. They want to see that you've done your homework. Before my interview, I used their service, I read their annual report, I followed their social media. I came in with three ideas for features they could build. That made a huge impression. Lucas: Now, let's be honest about the trade-off. The salary is lower. The report shows the average tech role at a nonprofit pays about 20 to 30 percent less than the equivalent for-profit role. But the benefits are often better — more vacation, flexible hours, and a real sense of purpose. For some people, that's worth the difference. Luna: And for bootcamp grads, sometimes the lower bar to entry matters more. I had no professional coding experience before my bootcamp. A nonprofit was willing to take a chance on me because I was passionate about the mission. That first job gave me the experience I needed to eventually move to a higher-paying role. Lucas: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, it really helps us keep doing episodes like this. Lucas: So back to the nonprofit path. Once you land the interview, prepare for a different kind of behavioral question. They might ask, 'Tell me about a time you had to do more with less.' Or 'Describe a situation where you had to convince someone who wasn't technical.' These come up more than the typical Amazon-style STAR questions. Luna: Definitely. And they'll probably ask about your salary expectations early. Don't undersell yourself. Know the range from the report and be ready to say, 'Based on my research, I'm looking for something in the eighty to ninety-five thousand range for this role.' If you lowball, they'll take it. Lucas: Another tip: some nonprofits offer tuition reimbursement or professional development budgets. If the salary is a bit low, you can negotiate for a learning stipend or a conference budget. That's often easier for them to approve than a higher base salary. Luna: I used my nonprofit's $2,000 annual learning budget to take a cloud computing certification course. That cert helped me get my next job. So it's not just about the paycheck. Lucas: Let's talk about the portfolio again. If you have time, build one project specifically for a nonprofit. It could be a simple donation tracker or a volunteer scheduling app. But make it real — deploy it, put it on GitHub, and in your README, explain the problem it solves and who it helps. That kind of project speaks volumes. Luna: Even better if you actually volunteer with a nonprofit and build something for them. I did that — I spent a weekend building a simple database for a local animal shelter. It wasn't pretty, but it worked. I put that on my resume and got a lot of positive feedback. Lucas: And it shows you can deliver a real product, not just a tutorial project. That's the kind of experience that makes a nonprofit hiring manager think, 'This person can hit the ground running.' Luna: Exactly. I think a lot of bootcamp grads overlook this because they think nonprofits are only about low pay and outdated tech. But the landscape is changing. The report says that 68 percent of large nonprofits now have a dedicated digital team. That's up from 45 percent just three years ago. Lucas: So the demand is there, and the supply of bootcamp grads targeting this space is still relatively low. That means less competition for you. If you're willing to consider a mission-driven organization, you can get a job that gives you real responsibility, a supportive team, and a career foundation you can build on. Luna: And you get to feel good about your work. I know that sounds cheesy, but it's true. When I shipped a feature that helped a food bank serve a hundred more families, that mattered. It kept me motivated when I was debugging at 10 p.m. Lucas: Not cheesy at all. That's the kind of thing that sustains a career. So if you're a bootcamp grad sending out resumes and getting tired of the same rejection emails from big tech, try the nonprofit route. Tailor your portfolio, network at tech-for-good events, and go in with genuine curiosity about their mission. It might be the best career move you make this year. Luna: I can second that. It worked for me.