Volunteering in IT: helping a non-profit as your first CV line

Why it's valued

A volunteer project has what coursework doesn't: a real client. A person with their own wishes, deadlines, revisions and a habit of changing requirements halfway.

That's what employers value most. Working with a client is a separate skill, and interviews ask about it: how you established what was needed, what you did when requirements shifted, how you explained timelines.

There's usually a reference at the end, too. Non-profits give them readily.

What's usually needed

• a website, or an update to one;
• a bot for taking requests;
• data processing, exports, reports;
• mailings, forms, integrations;
• sometimes just tidying up what someone built and abandoned.

The tasks are typically small and within a beginner's reach. That's the point: they can actually be finished.

Where to find it

Easiest through people you know and local communities. Many organisations never publish such requests but answer a direct letter gladly.

Write briefly: who you are, what you can do, how many hours a week, and what specifically you could build. A vague "I'd like to help" usually goes unanswered.

What to agree up front

1. What counts as finished. Otherwise the project becomes endless revisions.
2. A deadline. Approximate is fine, but say it out loud.
3. Who decides on their side. One person, not "we'll all take a look".
4. What you'll be able to show. Check in advance whether you can publish the code and talk about the work. Usually yes, but ask.
5. A reference. Raise it at the start, not on the last day.

What to watch for

Endless revisions and creeping scope. Volunteer work slides easily into years of unpaid support. The definition of done is the cure: what was agreed is built, the project is closed.

If you want to continue, that's a separate agreement, not an assumption.

How it reads on a CV

Not "volunteer", but as ordinary work: the organisation, the problem, what you built, the outcome. For example: "Built an intake system for an animal shelter: form, database, notifications. Requests stopped getting lost in email."

That's how it reads too — as experience, not as a good deed.