How to hire a nonprofit program coordinator (job description, interview questions, screening workflow)

The standard advice for this role is "hire someone who's passionate about the mission." At a small nonprofit, that advice quietly sets you up to fail. The thing that sinks a program coordinator hire is almost never a shortage of caring. It's organizational follow-through: the grant report numbers that do not match what actually happened, the volunteer schedule that falls apart the first busy week, the participant who slips through because no one was tracking it. A resume shows a mission-aligned background and a nonprofit title. It cannot show whether someone keeps a system from collapsing when three things break in the same afternoon, with no second coordinator to catch what falls. This guide is built to screen for that follow-through under pressure, not for how well someone talks about the cause.

What a program coordinator actually does at a small nonprofit

At a large NGO, a program coordinator sits inside a program team, with a data manager tracking outcomes and a volunteer coordinator running the roster separately. At a small nonprofit, one person is usually all three. They're the one who confirms an intake appointment actually happens, tracks down the sign-in sheet from Tuesday's workshop, and makes sure the numbers in the grant report match what actually occurred, not what was planned.

The title undersells the job. At an organization with a handful to a few dozen staff, the program coordinator is often the only layer between you, the executive director, and the people the program actually serves. When something breaks (a venue falls through, a volunteer doesn't show, a funder wants a mid-quarter update by Friday) this is the person who catches it before it reaches you.

The core responsibilities, in practice:

• Scheduling and logistics for program activities: venues, volunteers, participants, supplies
• Tracking attendance and outcomes data accurately enough to survive a grant report
• Recruiting, scheduling, and keeping volunteers engaged, since most small nonprofits run on volunteer labor they can't afford to lose
• Communicating directly with program participants, often as the only staff member they interact with regularly
• Flagging problems to you before they become funder-facing problems
• Doing whatever the week actually needs, since there's no second coordinator to hand things to when it gets busy

If you're hiring for this role for the first time, or replacing someone who quietly absorbed too much for too long, the job description below should describe the real job, not the tidy version of it.

Job description you can post today

Copy this, then adjust the specifics (your program, your funding cycle, your team size) to match your organization.

Program coordinator
[Organization name] is looking for a program coordinator to run the day-to-day logistics of [program name]. You'll be the connective tissue between our mission and the weekly work of actually delivering it, working closely with [executive director / program director] on everything from scheduling to grant reporting.

What you'll do
Coordinate scheduling and logistics for program activities. Track attendance and outcomes data accurately enough to support grant and funder reporting. Recruit, schedule, and manage volunteers who support the program. Serve as a primary point of contact for program participants. Flag problems early, before they become a funder-facing issue.

What we're looking for
Someone organized enough to keep several moving pieces on track without the system falling apart the first time a schedule changes. Comfortable with basic data entry and reporting, spreadsheets at minimum. Genuinely interested in [organization's mission], not just looking for any admin role to fill the gap.

Schedule
[Insert hours, e.g. full-time, Monday-Friday, with occasional evening or weekend program hours]

[Insert your actual pay range and benefits: base pay, health coverage, PTO, any flexibility you offer. Be specific here. A vague line like "competitive salary" reads to candidates as confirmation that a nonprofit role pays badly, even when your offer is reasonable for the market. Naming a real number and real benefits does more to attract strong candidates than another sentence about mission.]

10 interview questions, and what a good answer sounds like

1. Walk me through how you'd set up and run a single program activity, from scheduling to wrap-up.

You're checking for a real process, not a job description recited back to you. A strong answer moves through confirming the venue or space, lining up volunteers, communicating with participants ahead of time, running the actual activity, and closing the loop afterward (attendance logged, follow-ups sent, supplies restocked). A candidate who can only describe the activity itself, without the logistics on either side of it, is describing the part of the job that's easiest to picture, not the part they'd actually be doing most weeks.

2. It's the last week of the month. A grant report is due Friday, a volunteer just canceled for Saturday's event, and a participant needs an answer today. There's no one else to hand any of it to. What do you actually do?

This is the job in miniature, so listen for a real triage process, not a vague "I'd prioritize." A strong answer names what gets handled first and why, what gets a fast interim response instead of a full solution, and what they'd flag to you rather than quietly absorb. A weak answer either claims they'd handle everything at full quality with no tradeoffs (not credible, and a sign they haven't done this kind of week before) or has no method at all beyond working later.

3. How would you track and report on this program's outcomes for a funder who wants numbers, not just a story?

Listen for a concrete method: what they'd measure, how often, and how they'd catch a data problem before it reaches a funder rather than after. A strong answer treats data hygiene as part of the job, not an afterthought bolted on before a deadline. A weak answer talks generally about "tracking progress" without describing what a spreadsheet or system would actually look like, which usually means they haven't owned this responsibility before.

4. Tell me about a specific time you kept a project or event organized despite last-minute changes. What did you actually do?

Push for specifics if the first answer is general. A strong answer names the actual changes, what they adjusted, and how they kept other people (volunteers, a boss, participants) informed along the way. A weak answer stays abstract ("I'm good under pressure") without a real example, which is the same gap you're checking for on the scenario question above.

5. What draws you to [organization]'s mission specifically? Give me one concrete example from your own life or work, not a values statement.

This is the question that separates genuine interest from a rehearsed answer written for any nonprofit posting. A strong answer names something specific: a person, an experience, a reason this particular mission and not just "helping people" in the abstract. A weak answer could be copy-pasted into an application for a completely different cause without changing a word. That's not disqualifying on its own, but it's worth noting, and it's a reason to weight this question less than the organizational ones above if you're choosing between two strong candidates.

6. Tell me about a volunteer relationship that got difficult. How did you handle it?

Small nonprofits depend on volunteers they can't afford to lose, so this matters more than it looks like on paper. A strong answer shows they addressed the issue directly but kept the relationship intact, rather than either avoiding the conversation or letting the volunteer burn out and leave. A weak answer treats volunteers as interchangeable or can't produce a real example at all.

7. A participant needs something you don't have the authority or budget to give them. What do you do?

Listen for whether they know the difference between a decision that's theirs to make and one that needs to go to you. A strong answer escalates appropriately and communicates honestly with the participant in the meantime, instead of overpromising or going quiet. A weak answer either makes a call they shouldn't be making solo, or freezes and does nothing until someone else notices.

8. Walk me through how you'd build a simple system to track something recurring, like attendance or supply inventory.

You want to hear an actual method: what tool, what fields, how they'd catch an error, how often they'd update it. A strong answer sounds like something they've actually built before, even informally. A weak answer is vague about the mechanics and heavy on intent ("I'd make sure it's organized"), which tells you they haven't had to build the thing themselves.

9. Tell me about a time you had to tell a boss or funder about a setback. How did you approach it?

This checks whether they flag problems early or sit on them. A strong answer describes raising the issue promptly, with context and, ideally, an option or two for how to handle it. A weak answer describes finding out about problems only when someone else noticed, or waiting until the last possible moment to say anything.

10. What would you actually do in your first two weeks here, before anyone tells you what to do?

A strong answer names specific things: learning the current tracking system, meeting the volunteers, sitting in on a program session, reviewing the last grant report. A weak answer is generic enough to apply to any job ("I'd get to know the team and the processes"), which suggests they haven't thought concretely about what this particular role actually involves.

A scorecard you can score candidates against

Ten questions only help if everyone interviewing is listening for the same thing. Score every candidate on the same six signals, so you are comparing evidence instead of six different gut feelings. Copy this into a doc and fill in a row per candidate.

How to screen nonprofit program coordinator candidates without losing a week to it

Truffle is a candidate screening platform that combines one-way video interviews, talent assessments, and resume screening. For a lean nonprofit with no HR function, screening a stack of resumes on top of running the actual program is exactly the situation it's built for: you don't have a recruiter to hand this to, and the program doesn't pause while you read applications.

A workflow that fits a small nonprofit:

• Resume screening first, for the obvious mismatches. Not every applicant to a mission-driven posting has coordination experience. Resume screening narrows the pile to people whose background actually includes scheduling, logistics, or program support work, so you're not reading two hundred resumes to find the six worth a closer look.
• An organizational skills assessment before you spend interview time. This role lives or dies on follow-through, not just enthusiasm for the mission. A clerical and organizational skills assessment gives you evidence on accuracy, attention to detail, and the kind of administrative follow-through the job actually requires, before you've spent an hour on a conversation.
• A short one-way video interview for the finalists. Ask 2-3 of the questions above, especially the mission-alignment question and the competing-deadlines scenario, so you can see how someone actually communicates under pressure before you commit to a live call. One-way video interviews let candidates answer on their own time and let you review the answers on yours.
• One live conversation to close it out. By the time someone reaches a live interview, you've already confirmed they're organized and genuinely interested. Use the live conversation to talk through the actual week-to-week, not to re-ask what the assessment and video already answered.

None of this replaces your judgment. The tools surface the evidence, resume data, assessment results, video responses, in one place so you can decide who's worth your time, instead of doing that reading yourself at night on top of running the program.

3 questions from the skills check we'd actually run for this role

A skills check only helps if it tests the follow-through the job needs, not trivia. These three are pulled straight from Truffle's clerical and organizational skills assessment, the assessment we'd point you to for this role. They separate someone who talks about being organized from someone who actually is. Try them yourself before you decide what "job-ready" means for your opening.

The point isn't these three questions. It's that a short, job-relevant skills check like this tells you in twenty minutes what a resume and a warm conversation about the mission can hide: whether someone is actually accurate and organized under a little time pressure. Truffle surfaces the results against the bar you set. You still decide who clears it.

Common hiring mistakes for this role

Being vague about pay and letting the "nonprofit means low pay" assumption go unanswered. The word "nonprofit" alone signals underpaid to a lot of candidates, whether or not it's true of your actual offer. A vague "competitive salary" line does nothing to correct that. Naming a real range and real benefits is one of the few levers you have to counter an assumption that's suppressing your applicant pool before anyone even reads the rest of the post.

Hiring purely on mission passion without testing organizational skill. Genuine enthusiasm for the cause matters, but it's not the same skill as keeping a grant report accurate or a volunteer schedule from falling apart. A candidate who talks beautifully about the mission and can't answer the competing-deadlines scenario with anything concrete will struggle the first time three things break in the same week.

Underestimating how much this person will be asked to do without backup. At a small nonprofit, this role tends to expand to fill whatever isn't covered elsewhere. If you don't say that plainly in the interview, either the hire is blindsided in month two or you end up with someone who never signed up for the scope you actually need.

Dragging out the process while a strong candidate takes another offer. Small nonprofits often move slowly because the executive director is also running the process on top of everything else. A candidate good enough to run your program logistics is also good enough to have other offers. A workflow that gets you to a decision in days, not weeks, is the difference between hiring them and hiring whoever's still available later.

Writing a posting that blurs this role with a general admin assistant job. A program coordinator owns outcomes, volunteers, and participant relationships, not just calendars and inboxes. A generic posting undersells the responsibility and can pull in candidates looking for pure admin work who aren't prepared for the parts of the job that involve real judgment.