All posts
·2 min read

Why I Work With Non-Profits

Most developers optimize for salary. I optimize for meaning. Here's how I got there and what I've learned building tech for mission-driven organizations.

non-profitfreelancecareer

Most developers I know optimize for salary, interesting problems, or prestige. I spent years doing the same — chasing technically challenging roles at well-funded companies. The work was good. The pay was good. Something felt off.

The shift

The thing that changed it was a small side project I did for a local food bank. They needed a way to manage volunteer sign-ups — nothing fancy, just a form that didn't break on mobile and a dashboard someone other than their old IT volunteer could maintain.

It took me a weekend. They used it for three years. At some point the director emailed me to say it had helped them coordinate over 4,000 volunteer hours that year.

No startup I'd worked at had that kind of measurable, direct impact on people's lives. That was the shift.

What I've learned

Working with non-profits is different from working with startups or agencies in a few specific ways:

Budgets are real constraints. There's no "let's just burn some runway on this." Every dollar spent on software is a dollar not spent on the mission. This has made me a much more pragmatic engineer — I default to boring, proven tools. I scope tightly. I hand off something the client can actually maintain.

Your users are often not technical. The staff member who will use your admin dashboard has 12 other jobs and isn't going to read documentation. Building for non-technical users has improved my UI instincts more than anything else.

Stakeholders care deeply. When you ship something for a non-profit, people are genuinely invested. That's energizing in a way that "increasing engagement metrics" isn't.

The tradeoff

I won't pretend it's all upside. Timelines slip. Decisions go through committees. Budget constraints sometimes mean you can't build the right solution, only the affordable one.

But I've found that the constraints make me a better builder — not a frustrated one. And the work feels worth doing in a way that's hard to replicate anywhere else.

If you're building something that matters and need a developer, I'd love to talk.

Working on something that matters?

I help non-profits and mission-driven teams build software that lasts. Let's talk.