Guides · For hiring managers

How to write a nonprofit job post

Updated October 3, 2026

A good job post does two jobs. It helps the right people say "that's me." And it helps everyone else say "not for me" before they spend an evening on an application.

Most nonprofit posts fail at both. They're long, vague, and full of requirements nobody checks. This guide shows how to write one that's short, honest, and fair.

Start with what the person will do

Before you write anything, answer one question: what will this person get done in their first year?

Write three to five outcomes. Be specific.

Weak: "Manage volunteer programs."
Strong: "Grow our weekend food distribution from 40 to 70 regular volunteers, and keep them coming back."

These outcomes are the heart of the post. Everything else supports them.

Put pay in the post

List the pay range near the top. Many states and cities require it. Post it even where they don't.

A range saves everyone time. It also makes your hiring fairer. People who don't know to negotiate, often women and people of color, are the ones who lose when pay is hidden.

Keep the range honest. If you'd never pay the top of it, don't list it. A range wider than about 25 percent from bottom to top tells people you haven't decided.

Also say:

Full time or part time, and the hours if part time.
Benefits, in plain words. "Health insurance, fully paid for you" beats "competitive benefits."
Where the work happens. On site, hybrid, or remote, and which states you can hire in.

Cut the requirements

Every requirement you list turns people away. Some people apply when they meet half the list. Others won't apply unless they meet every item. Long lists cost you the careful ones.

For each requirement, ask: would we really turn down a great candidate who didn't have this?

Degrees. Most nonprofit jobs don't need one. If the work needs a license, say that instead.
Years of experience. Describe what the person needs to be able to do. "Has managed a budget over $500,000" is more useful than "7+ years."
Nice to haves. Put them in their own short list, labeled clearly. Or leave them out.

Aim for five requirements or fewer.

Describe your org honestly

Two or three sentences about who you are and who you serve. Then one or two about what it's like to work there. Be specific. "We're a team of nine. We meet every Monday and mostly work on our own after that" tells people more than "a collaborative, mission-driven culture."

If something is hard about the job, say so. "Our database is a mess, and fixing it is part of this job" will attract people who like fixing things. It'll also save you from hiring someone who quits in month three.

Skip the words that don't say anything

Cut these, or replace them with something specific:

Passionate, rockstar, ninja, self-starter
Fast-paced environment
Wears many hats
Other duties as assigned
Competitive salary
Culture fit

Explain how to apply and what happens next

Keep the application short. A resume and two or three short questions usually tell you more than a cover letter. Good questions ask about real work:

"Tell us about a time you recruited people to show up for something. What worked?"
"What would you want to learn in your first month here?"

Then say what happens next:

When you'll start reviewing applications.
How many rounds of interviews there are.
When people will hear back.

And promise that everyone who applies will hear back. Then keep that promise. See how to reply to applicants kindly.

Use a simple structure

Job title. Use a common title people search for. Put the pay range right after it.
Two sentences on what the job is and why it matters.
What you'll do in the first year: three to five outcomes.
What you need: five requirements or fewer.
Pay, benefits, hours, and location.
About us: four or five sentences.
How to apply and what happens next.

Most good posts fit on one page.

Post it where the right people look

Where you post decides who applies. See where to look for boards, newsletters, and groups by focus and region. Some community spaces have their own rules about who can post. Read them first.