Volunteer coordinator: job description, interview questions, and screening workflow

Every candidate for this role can talk about how much they love the mission. Almost none of them can tell you, with a straight face, how they'd fill a Saturday shift after their third volunteer cancels in a row. That's the actual job. A volunteer coordinator's whole reason for existing is a workforce that owes your organization nothing: no paycheck, no performance review, no reason to show up next month except that they want to. Recruiting is the easy part. Getting the same person to come back six times is the part that separates someone who's good at this from someone who just likes people. This guide is built to screen for that, not for how warmly someone describes the cause.

What a volunteer coordinator actually does at a small nonprofit

At a large NGO, volunteer engagement is often its own department: a recruiting specialist, a training team, a scheduling system nobody has to hold together by memory. At a small nonprofit, one person is the entire department. They're the one who posts the volunteer opening, runs the info session, builds the onboarding packet, and is still awake at 9pm texting three people to cover a shift that just opened up.

This is a different job from a nonprofit program coordinator, and the two get confused constantly because small orgs often can't afford to separate them. A program coordinator runs the actual service, the workshops, the intake process, the outcomes a funder is paying for. Volunteers are one input they manage among many. A volunteer coordinator's entire job is the volunteer workforce itself: finding people, training them, scheduling them, and keeping enough of them engaged that the program has bodies to run on. If your org is small enough that one person does both, that's normal, but be honest in the job description about which parts of the job you're actually hiring for.

The core responsibilities, in practice:

• Recruiting volunteers on an ongoing basis, not just once when a program launches
• Running onboarding and training so a new volunteer knows what to do before their first shift, not during it
• Building and maintaining the volunteer schedule, including the constant work of filling gaps when people cancel
• Keeping volunteers engaged enough to come back, since burnout and quiet disappearance are the default outcome without deliberate effort
• Tracking volunteer hours and participation, often because a grant or funder requires that data
• Handling the interpersonal side: a volunteer who's a bad fit, a conflict between two volunteers, a volunteer who oversteps with staff or participants

If you're hiring for this role for the first time, or replacing someone who's been quietly patching a shrinking volunteer base for a year, the job description below should describe the real job. Not the version where everyone shows up on time because they care about the mission.

Job description you can post today

Copy this, then adjust the specifics (your programs, your volunteer base size, your reporting requirements) to match your organization.

Volunteer coordinator
[Organization name] is looking for a volunteer coordinator to build and run our volunteer program. You'll own the full lifecycle: finding people, onboarding them, scheduling them, and keeping them coming back. This role reports to [executive director / program director].

What you'll do
Recruit new volunteers through [your usual channels, community boards, partner orgs, social, word of mouth]. Design and run onboarding and training so volunteers know what to do before their first shift. Build and maintain the volunteer schedule, including filling gaps when people cancel. Keep volunteers engaged over time through recognition, communication, and meaningful assignments. Track volunteer hours and participation for internal use and funder reporting. Handle volunteer-side issues directly: a bad fit, a scheduling conflict, tension between a volunteer and staff.

What we're looking for
Someone who can recruit and, more importantly, retain, not just fill a roster once and hope it holds. Comfortable managing a schedule with real gaps in it, and calm about filling them at short notice. Genuinely interested in [organization's mission], but able to back that up with real organizational follow-through, not just enthusiasm.

Schedule
[Insert hours, e.g. part-time, full-time, or lead-volunteer with a stipend; this is often a part-time or volunteer-led role at very small nonprofits, but decide deliberately for your organization rather than defaulting to that.]

[Insert your actual pay range and benefits, or note clearly if this is unpaid or stipended: base pay or stipend, health coverage if applicable, PTO, flexibility. Be specific here. A vague listing reads to candidates as uncertainty about how seriously the role is treated, even when your actual offer is reasonable.]

11 interview questions, and what a good answer sounds like

1. Walk me through a time you actually recruited a volunteer, not just posted an opening and waited.

You're checking for a real recruiting channel, not a job description recited back. A strong answer names a specific approach that worked: a partner organization, a community group, a personal ask, a follow-up sequence. A weak answer stops at "I'd post it online and share it on social," which describes hoping, not recruiting.

2. Tell me about a volunteer who turned out to be unreliable or a bad fit. What did you actually do?

Listen for whether they addressed it directly instead of quietly working around it. A strong answer names the specific problem, describes a real conversation, and explains the outcome, whether that was a course correction or an exit. A weak answer avoids the conflict entirely or treats the volunteer as replaceable without ever trying to fix the relationship first.

3. It's Friday afternoon and three volunteers just canceled for Saturday's shift. What do you do in the next hour?

This is the job in miniature. A strong answer has a real method: who they'd call first and why, what they'd do if no one's available, and how they'd communicate with whoever's depending on that shift being covered. A weak answer either claims they'd have it solved instantly with no real plan, or has no method beyond "I'd figure it out."

4. How do you keep volunteers coming back when there's no paycheck to hold over them?

You want a concrete answer, not a values statement. A strong answer names specific practices: real recognition, meaningful assignments instead of busywork, communication that makes people feel like their time mattered. A weak answer stays abstract ("I'd make sure they feel appreciated") with nothing behind it.

5. Tell me about a time you had to track and report volunteer hours or participation for a funder or grant.

Listen for whether they treat this as a real responsibility, not an afterthought. A strong answer describes an actual method: what they logged, how often, how they caught an error before it reached a report. A weak answer talks generally about "keeping records" without describing what the system looked like.

6. Two volunteers are in conflict, or a volunteer and a staff member are butting heads. Walk me through how you'd handle it.

A strong answer addresses it directly and early rather than hoping it resolves itself, and shows they can hold a boundary with a volunteer the same way they would with an employee. A weak answer avoids the conversation, or defers entirely to whichever side has more standing in the organization.

7. What draws you to [organization]'s mission specifically? Give me one concrete example, not a values statement.

This 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 mission and not just "helping people" generally. A weak answer could be copy-pasted into an application for a completely different cause without changing a word. Weight this less than the operational questions above if you're choosing between two strong candidates.

8. Describe how you'd build an onboarding process for a brand-new volunteer.

Listen for a real sequence: what they'd cover before the first shift, how they'd check understanding, what happens if a volunteer shows up undertrained anyway. A strong answer sounds like something they've actually built or run before. A weak answer is vague about the mechanics ("I'd walk them through everything") with no structure behind it.

9. Tell me about a volunteer who almost quit, and what you did.

This checks for retention instinct, not just recruiting instinct. A strong answer shows they noticed disengagement early, understood why (burnout, feeling unused, a bad experience), and did something specific about it. A weak answer either can't produce an example or shows they only noticed after the person had already stopped showing up.

10. Tell me about a volunteer who overstepped, with a participant, with staff, or with the scope of their role. How did you handle it?

Volunteers sometimes act like they have more authority than they do, and it's the coordinator's job to hold that line without alienating someone who's donating their time. A strong answer sets a clear, respectful boundary and explains the reasoning to the volunteer. A weak answer either lets it slide to avoid friction or handles it in a way that would make any reasonable volunteer feel humiliated.

11. What would you actually do in your first 30 days here, before anyone tells you what to do?

A strong answer names specific things: auditing the current volunteer list and who's actually active, sitting in on a shift, reviewing how onboarding currently works, meeting a handful of long-tenured volunteers directly. A weak answer is generic enough to apply to any job ("I'd get to know the team"), which suggests they haven't thought concretely about what this role involves.

A scorecard you can score candidates against

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

How to screen volunteer coordinator candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments. For a lean nonprofit with no HR function, screening a stack of applicants for a role this people-heavy, on top of actually running your volunteer program, is exactly the situation it's built for.

A workflow that fits a small nonprofit:

• Resume screening first, for the obvious mismatches. Not every applicant to a volunteer-facing posting has actually recruited or managed people before. Resume screening narrows the pile to candidates whose background includes recruiting, coordination, or people-management work, so you're not reading every application to find the handful worth a closer look.
• A leadership-oriented assessment before you spend interview time. This role is management, just management of people you can't pay or discipline in the usual ways. The leadership skills assessment gives you evidence on delegation, conflict handling, and follow-through before you've spent an hour on a live conversation.
• A short one-way video interview for the finalists. Ask 2 to 3 of the questions above, especially the recruiting example and the Friday-afternoon scheduling 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 can recruit, organize, and hold a boundary. Use the live conversation to talk through the actual volunteer base and its real quirks, 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.

Common hiring mistakes for this role

Hiring for mission passion alone. Enthusiasm for the cause is common among applicants to any nonprofit posting, and it's genuinely useful for recruiting other volunteers. But it's not the same skill as building a schedule that survives three cancellations or noticing a volunteer is about to quietly disappear. A candidate who talks beautifully about the mission and has no real recruiting or retention example will struggle the first time the roster gets thin.

No real plan for retention, just recruiting. A lot of postings for this role only describe finding volunteers, not keeping them. That mirrors how a lot of small nonprofits actually run the function: constant recruiting to backfill constant attrition, instead of a deliberate retention practice that would reduce how much recruiting is needed in the first place. Screen for retention thinking specifically, not just the ability to fill a roster once.

Treating it as an entry-level admin afterthought. Because the role doesn't run the program's core service, it's easy to underlevel it, low pay if any, no real authority, folded into someone else's job description as an extra duty. But this person is managing a workforce with zero built-in loyalty mechanism. That takes real judgment, not just someone with free time and a spreadsheet.

Blurring the job description with program coordinator. If your posting lists program delivery tasks and volunteer management tasks together without distinguishing them, you'll attract candidates who are strong at one and assume they're being hired for the other. Be explicit about which parts of the job are actually volunteer-facing.

Being vague about whether this is paid, and how much. Some small nonprofits run this as an unpaid or stipended lead-volunteer position, and that can work. What doesn't work is leaving it ambiguous in the posting. A candidate who can't tell whether they're applying for a paid job or a volunteer commitment will assume the worst and self-select out, often the strongest candidates first.

A volunteer coordinator and a nonprofit program coordinator get lumped together constantly because small organizations can't always afford to separate them, and because both roles sit close to the mission. But they're solving different problems. The program coordinator keeps the actual service from falling apart. The volunteer coordinator keeps the people who help deliver it from quietly walking away. Hire for the one you actually need, and if you need both, say so plainly in the job description rather than hoping one hire covers it by accident.