Verdict: A tight set of 44 interview questions built for small nonprofits hiring without an HR department.
What works: Behavioral and situational questions that surface real operational skill, a 2-round process that respects a lean team's time, and role-specific questions for EDs, board members, volunteers, development officers, and comms staff.
What doesn't: Generic "tell me about yourself" openers, five-round corporate interview processes, and culture-fit screening that smuggles in bias.
Best for: Small nonprofits (2 to 15 staff) hiring their first or second staffer, filling a key vacancy, or formalizing a process that's been ad hoc.
Worth considering if: You're a solo staffer doing the hiring yourself, or a board member leading a search without a dedicated HR team.
Table of contents
Hiring at a small nonprofit isn't really hiring. It's a 20-50% capacity decision. Most small nonprofits run on one solo staffer plus a board, so a single new hire either lifts the load off the person already holding everything together, or quietly adds to it for the next six months.
That changes what your interview is for. You're not screening for the "best candidate" in the abstract. You're screening for someone who can function as a 1.5-person operation, with no specialist backup, no separate HR, and tools they'll set up themselves. The interview's real job is to filter out anyone whose first 90 days will burn out the staffer you're trying to help.
These 44 questions are organized for that reality. You'll get sample answers (so you know what "good" sounds like), red flags (so you can cut in round 1, not round 3), questions candidates should ask you, and a 2-round process tuned for a 2-person hiring panel. Use them whether you're hiring your third employee or filling a key vacancy on a lean team.
Why nonprofit interviews require a different approach
At a 3- to 10-person nonprofit, the person you're hiring isn't joining a team. They're becoming 20-50% of it. There's no HR partner to onboard them, no senior peer to shadow, and no specialist team to back them up when something they've never done before lands on their desk in week two.
Most small nonprofits we hear from are running on a solo staffer (often 30 hours a week) doing donor management, communications, and reporting alone, plus a board chair juggling the role with a day job and family. That's the panel doing your hiring. That's also the panel that pays the price if the hire doesn't work. A single mishire at a five-person nonprofit can absorb months of program capacity, because the work doesn't pause: it falls back on the person already holding everything together.
So your interview has to answer a different question than the corporate version. Not "is this person qualified?" but "will this person reduce or add to the load on the one person already running this?" That means screening for three things you don't see on a rsum:
- Resourcefulness under constraint. Can they set up the tool, write the email, and run the event without a vendor, a contractor, or a manager telling them how?
- Self-direction with minimal management. Will they ship work in week three without you building them a task board first?
- Real mission fit, not rehearsed mission fit. Do they actually want to do the unglamorous version of this job, or are they pattern-matching to "nonprofit = meaningful"?
General HR research from SHRM puts the cost of replacing an employee at 50% to 200% of annual salary, depending on level. For a small nonprofit, the dollar number undersells it. The real cost is the staff member who quits trying to manage a bad hire. You don't get to absorb that the way a 200-person org does.
One operational decision before you start: pick the stack the new hire will inherit. If you're hiring a development or comms role and they'll need a donor database or an email tool on day one, set that up in advance on a free fundraising platform that won't eat your new hire's first-year budget. The candidate shouldn't be evaluating you on whether they have to procure software in week one.
For a small nonprofit: the goal of every question below is to figure out, before you sign the offer, whether this person reduces the load or adds to it. If a question doesn't help you answer that, cut it.
Mission alignment questions (with sample answers)
Mission alignment is the easiest area for candidates to coach themselves through. Generic answers ("I care deeply about giving back") are almost always rehearsed. You're looking for specific details that show they've actually done the work to understand your cause.
1. What do you know about our mission, and which part of it pulled you to apply?
A strong answer might sound like: the candidate names a specific program, references something they saw on your site or in a recent report, and connects it to something concrete in their own life or work. Bonus points if they mention a limitation or trade-off your org makes ("I noticed you focus on X rather than Y, and that resonated because…").
What to listen for: specifics. Program names, populations served, geographies. If they only repeat your tagline back to you, they haven't done the homework.
2. Tell me about a moment when you saw the problem we work on up close.
A strong answer might sound like: a concrete story, not a statistic. They describe a person, a situation, or a system they encountered, and what it changed in their thinking.
What to listen for: emotional specificity. People who genuinely connect to a cause can describe one moment. People who don't will describe the issue in the abstract.
3. What's a nonprofit (ours or another) you think gets this work right, and why?
A strong answer might sound like: they name an org, describe one specific practice they admire, and can articulate a trade-off that org makes.
What to listen for: nuanced opinions, not just praise. Mature candidates can admire an org and still see what it sacrifices to operate that way.
4. We have to make hard choices about what we don't do. How do you think about scope?
A strong answer might sound like: they accept that small orgs can't serve everyone, and they describe a framework (need, capacity, mission fit, funder alignment) they'd use to make the call.
What to listen for: comfort with constraint. Candidates who can't say no to anything will run your team into the ground in six months.
5. Where do you draw the line between "stretching to serve the mission" and "burning out"?
A strong answer might sound like: they describe a personal practice (boundaries, sleep, a specific routine) and a professional one (saying no, setting expectations with stakeholders).
What to listen for: self-awareness. The candidate who says "I never burn out, I just love the work" is the candidate who burns out fastest.
6. If our funding got cut 30% next year, which programs would you protect and which would you pause?
A strong answer might sound like: they ask clarifying questions first (what's restricted, what's our reserve?), then propose a framework, then name a tentative answer.
What to listen for: they don't dodge the question, but they also don't answer it without information. Both extremes are concerning.
For a small nonprofit: mission alignment is the easiest thing to fake and the most expensive thing to get wrong. Trust specifics, not enthusiasm.
Experience and behavioral questions (with sample answers)
Behavioral questions ask candidates to describe what they actually did, not what they would do. The best answers follow the STAR pattern: Situation (what was happening), Task (what they were responsible for), Action (what they did), Result (what happened). Train yourself to listen for all four.
7. Tell me about a time you did a job that wasn't yours.
A strong answer might sound like: "Our communications person left mid-campaign. I picked up the email schedule, learned the tool over a weekend, and shipped the next two sends. Open rates dropped about 8%, but we didn't miss a deadline."
Red flag answer: "I always pitch in wherever needed." That's a value statement, not a story.
8. Describe a project where you had no clear playbook. What did you do first?
A strong answer might sound like: they describe how they scoped the unknown (who they asked, what they read, what they tested first), then how they made a call and adjusted.
Red flag answer: "I'd ask my manager what they wanted." At a small nonprofit, you ARE the manager. You need someone who can scope ambiguity, not escalate it.
9. Walk me through a time you had to work with a very limited budget.
A strong answer might sound like: a specific dollar figure or constraint, the trade-offs they made, the free or low-cost tools they used, and the outcome.
What to listen for: they treat budget as a design constraint, not a complaint.
10. Tell me about a failure. What did you do the next day?
A strong answer might sound like: they name a specific failure, take real ownership (not the fake kind), and describe the concrete change they made.
Red flag answer: "I'm a perfectionist" or any version that flips the failure into a humble brag.
11. Describe a time you disagreed with your boss or board. How did it land?
A strong answer might sound like: they describe the disagreement professionally, name what they did to make their case, and accept the outcome (even if they lost).
What to listen for: they can disagree without contempt. At a small org, you'll disagree with this person regularly. You need to know they can hold a position and still keep working.
12. Tell me about a time you built a relationship with a donor, partner, or major stakeholder.
A strong answer might sound like: a slow story. They describe the early outreach, the follow-up cadence, what they learned about the person, and how the relationship evolved.
Red flag answer: "I closed the deal in one meeting." Donor relationships at small nonprofits are long. Anyone who treats them like a transaction will burn them.
For a small nonprofit: behavioral answers are the highest-signal part of the interview. If a candidate can't tell you a real story with names, numbers, and trade-offs, they probably don't have one.
Situational questions to test problem-solving
Situational questions ask what a candidate would do in a scenario they haven't faced. They're less reliable than behavioral questions (people are great at imagining themselves as competent), but they reveal how someone thinks when there's no playbook. For a lean team, you want candidates who can operate without specialist backup.
13. A major donor pulls their pledge two weeks before your gala. What do you do in the first 48 hours?
A strong answer might sound like: they triage. Confirm the loss in writing, assess gala economics, brief the ED and board chair, identify two or three backup asks, and decide whether to adjust the gala (smaller venue, lower target) or hold the line.
What to listen for: they don't panic and they don't oversimplify. They ask questions you'd want them to ask.
14. A program participant tells you, in confidence, something that contradicts what we've been telling funders. How do you handle it?
A strong answer might sound like: they protect the participant's confidence first, escalate the discrepancy to leadership, and propose how to course-correct with the funder without throwing anyone under the bus.
Red flag answer: they immediately propose telling the funder "for transparency" without thinking about the participant, or they propose hiding it.
15. The board wants you to launch a new program in 60 days. You think it'll fail. What do you do?
A strong answer might sound like: they write down the specific reasons it'll fail, propose a smaller pilot or a different timeline, and bring data, not just opinion.
What to listen for: they push back constructively. Candidates who say "I'd just do what the board wants" are not the candidates you want in week 12.
16. You inherit a process you'd never set up that way. Walk me through your first month.
A strong answer might sound like: they don't tear it down on day one. They document the current state, ask who set it up and why, find the one or two changes with the highest leverage, and propose those before the bigger overhaul.
Red flag answer: "I'd rebuild it from scratch." That's how you blow up a small team in your first month.
17. Two volunteers are in a conflict that's affecting the team. You have 45 minutes before your next meeting. What do you do?
A strong answer might sound like: they triage the urgency (does this need to be fixed today?), have a short individual conversation with each, and schedule a longer joint conversation if needed.
18. A reporter calls about a sensitive issue at the org. The ED is on vacation. What's your move?
A strong answer might sound like: they buy time professionally ("I want to give you a thoughtful response, can I call you back in two hours?"), reach the ED, and don't speak on the record without alignment.
What to listen for: they don't freelance. Small-org reputations are fragile.
For a small nonprofit: bias toward candidates who can operate without specialist backup. The "perfect" answer matters less than the structure of their thinking.
Role-specific questions by position
The questions above work for any role. These add a layer of specificity for the five hires small nonprofits make most often.
Executive director
At a small org, the ED is the CEO, the development director, the comms lead, and the operations manager. Boards interviewing for this role should screen for breadth and judgment, not just leadership.
19. How would you balance fundraising, program leadership, and board management in your first 90 days?
A strong answer might sound like: they propose a sequence (listen first, stabilize cash and key relationships next, then strategy), name the trade-offs, and ask what the board's biggest fear is.
20. Walk us through how you'd build a fundraising plan if our biggest grant doesn't renew.
A strong answer might sound like: they propose a diversified mix (individual giving, events, smaller grants, recurring donors), with realistic timelines and dollar targets.
21. What's your relationship with a board when you disagree with them?
A strong answer might sound like: they describe a healthy partnership, not a power struggle. They bring data, they listen, and they accept the board's final authority on governance questions.
Need a written role definition before you interview? Use this executive director job description template to align your board on what you're actually hiring for.
For a small nonprofit: the ED role at a small org is four jobs in one. Screen for breadth first. Deep expertise in one area, at the cost of the others, is a risk you can't absorb.
Board members
Board interviews are different. You're not evaluating skills, you're evaluating commitment, judgment, and what they'll add to the room.
22. What's your understanding of the difference between governance and management?
A strong answer might sound like: governance sets direction, hires and supports the ED, ensures fiduciary health. Management runs the work. They don't blur the two.
23. Tell us about a board you served on that did this well. What did the chair do differently?
A strong answer might sound like: a specific example with named practices (consent agendas, clear committee work, an annual board self-evaluation).
24. If you saw the ED making a decision you disagreed with, but it was clearly within their authority, what would you do?
A strong answer might sound like: they raise the concern privately, accept that it's the ED's call, and don't litigate it in the full board.
For a small nonprofit: a board member who blurs governance and management is more disruptive than a vacant seat. Screen for that line before you vote anyone in.
Volunteers
Volunteer interviews are short, but they matter. Volunteers are the face of your cause to your community.
25. Why this organization, specifically?
A strong answer might sound like: they can name something specific. Not "I want to give back," but "I read about your work with X and it connected to Y in my life."
26. How many hours a month can you actually commit, honestly?
A strong answer might sound like: a specific number, with caveats (busy season at work, etc.). Volunteers who overpromise are volunteers who ghost.
27. Tell me about a time you committed to something and couldn't follow through. What did you do?
A strong answer might sound like: they communicated early, made a plan to make it right, and learned from it.
If you're building your volunteer pipeline from scratch, our guide on recruiting volunteers for your nonprofit covers sourcing, screening, and onboarding.
For a small nonprofit: a volunteer who ghosts after two shifts costs you more in re-recruitment time than a vacancy you held longer. Screen for realistic commitment, not enthusiasm.
Development officers
The development officer is often the first hire that pays for itself. Screen hard for relationship skills, follow-through, and comfort with a donor database they may need to set up themselves.
28. Walk me through your last major-gift close. What happened in the six months before the ask?
A strong answer might sound like: they describe the cultivation arc (touches, what they learned, who else was involved, the moment they knew the donor was ready). Metrics-focused candidates name the gift size, the prior giving, the soft credit attribution.
29. What's your donor retention rate, and how do you talk about it?
A strong answer might sound like: a number (industry average for small orgs hovers in the 40s), an honest read on what drives it, and specific practices they use to lift it.
30. What donor database have you used, and what would you do if we didn't have one yet?
A strong answer might sound like: they've used something (Salesforce, Little Green Light, or a free tool), they can talk about its limits, and they're comfortable setting one up if needed.
That last question is the one to weight. A development officer who can't operate a database is going to ask you to procure one in week two. If you want them productive on day one, set up a free donor management tool your new development officer can own on day one before the offer goes out.
For a small nonprofit: a development officer who needs a full tech stack handed to them before they can prospect is a liability, not a hire. Make sure the tools are ready before they start, and make sure they can use them.
Communications specialists
At a small org, the comms hire is also the email marketer, the social media manager, the event flyer designer, and the website editor. Screen for range, not just one channel.
31. Walk me through a campaign you ran end to end. What was the brief, and what shipped?
A strong answer might sound like: they describe the goal, the audience, the channels, the creative decisions, and the result. They can tell you what they'd do differently.
32. How do you write differently for a donor email vs. an Instagram post vs. a grant report?
A strong answer might sound like: they understand audience and channel. Donor emails are personal and specific. Instagram is visual and short. Grant reports are structured and outcome-focused.
33. What email tool have you used, and what would you do if we didn't have one yet?
A strong answer might sound like: they've used Mailchimp, Constant Contact, or a built-in nonprofit tool. They can audit a list, segment, and run a basic A/B test.
Same logic as development: don't make your new comms hire procure software in week one. Built-in newsletter and email tools mean they can ship their first send before they've even finished onboarding.
For a small nonprofit: range matters more than depth. A comms hire who excels at one channel but can't write an email, update the website, and design a flyer in the same week isn't built for a lean team.
Questions candidates should ask you
The questions a candidate asks tell you more than the ones they answer. Thoughtful candidates ask things that signal they're seriously evaluating whether the job will work, not just whether they'll get it. Here are the questions you want to hear, and what each one reveals.
- 1. "What does success look like in this role at six and twelve months?" They're thinking about outcomes, not just inputs. They want to know what "good" actually means here.
- 2. "Who would I work most closely with day to day?" They're mapping the actual team, not the org chart. They know the difference matters at a small org.
- 3. "What's the biggest open challenge I'd be walking into?" They want to know the real job, not the pitched one. Candidates who don't ask this haven't worked in a small org before.
- 4. "What tools and systems are already in place, and which ones would I need to build?" They're evaluating onboarding load. This is the single best signal of operational maturity.
- 5. "How does the board engage with this role?" Especially for ED, development, or senior roles. They understand governance matters.
- 6. "What's the team's working style on remote, hybrid, or in-person?" They're surfacing logistics before the offer, not after.
- 7. "How do you handle disagreement on the team?" Strong candidates probe culture by asking how conflict goes, not whether the culture is "great."
- 8. "What's your retention story? Why have people stayed, and why have people left?" A sharp question. The answer tells them (and you) a lot.
- 9. "What's the funding picture for the next 18 months?" They want to know if the role will still exist in year two.
- 10. "Is there anything in my background that gives you pause?" Confident candidates invite the objection. It gives you a chance to raise concerns and them a chance to address them.
For a small nonprofit: a candidate who doesn't ask any of these is a candidate who hasn't actually thought about the job. Treat the absence of good questions as a signal.
Red flags: answers that should concern you
Use this list to disqualify in round 1, not round 3. Every item below is a pattern that shows up before the offer and gets louder after it.
- 1. Vague answers about why they left previous roles. "It just wasn't the right fit" repeated for three jobs in a row is a pattern. Ask follow-ups.
- 2. Inability to name specific accomplishments. If they can't tell you one project with a name, a number, and a result, they probably didn't drive one.
- 3. Treating nonprofit work as "easier" or "less stressful" than corporate. Anyone who thinks this hasn't done the work. It will end in burnout.
- 4. No questions about the mission itself. If they don't ask about who you serve or how, they're applying to "a nonprofit," not yours.
- 5. No plan for operating without specialist backup. When you ask "what would you do if we don't have a database yet?" and they look stuck, that's the answer.
- 6. Complaints about every previous manager. One bad manager is a story. Three is a pattern.
- 7. Salary as the first or only question. Compensation matters. It shouldn't be the only thing they ask about across three rounds.
- 8. Overpromising on capacity. "I can absolutely run all of that with the budget you described" is concerning, not reassuring. Realistic candidates push back.
- 9. Buzzwords without examples. "Strategic," "innovative," "passionate," "data-driven": any of these without a story underneath is filler.
- 10. No curiosity about the team they'd join. At a small org, "who am I working with" is the most important question they can ask. If they don't, they don't get it.
For a small nonprofit: trust the red flags. The patterns you see in the interview get louder, not quieter, after the offer.
How to structure your nonprofit interview process
The five-round corporate interview is what burns out the staffer you're trying to help. For a small org, run a tight 2-round process with a 2-person panel. That's it.
Round 1: 30-minute structured screen with the ED or founder. Pick 5-7 of the must-ask questions above (mission, behavioral, and one situational). Score each answer 1-5 using a simple shared rubric. Don't freestyle. Take notes. Decision in 48 hours.
Round 2: 60-minute working session with one board member or the closest teammate. Skip the "culture panel." Instead, give the candidate a slice of the real job:
- Development hire: draft a 250-word thank-you email to a $500 first-time donor, or sketch a donor segmentation for your top 50 supporters.
- Comms hire: rewrite an existing email of yours, or storyboard a three-post Instagram series for an upcoming program.
- Program hire: walk through how they'd intake a new participant, or critique a current program with two improvements.
- ED candidate: mock a three-minute board update on a current challenge.
You're hiring for someone who can do the actual work. The working session shows you. A polished rsum does not.
References: ask different questions than you asked the candidate. Don't ask references to confirm what the candidate said. Ask: "What did you have to manage closely with them?" "What's one thing they'd need to grow in their next role?" "Would you rehire them today, knowing what you know now?" Those three questions give you more signal than ten "tell me about a time" questions.
Skills assessment, by role:
- Development: a writing sample (an actual thank-you note or grant intro) and a 10-minute "walk me through your last major gift" verbal.
- Comms: a portfolio review and a short live edit.
- Program: a case study walk-through. "Here's a real situation we faced last year. Talk me through how you'd handle it."
- ED: a written 90-day plan, 1-2 pages max, due before round 2.
Reject candidates within a week, by email, with one specific reason if you can. Small-sector reputation is a real thing. The candidate you reject this quarter might be your funder's program officer in two years. Be the org that closes the loop.
Set up the new hire's stack before they start. The single best thing you can do in week one is hand the new hire a working set of tools, not a procurement list. Donations, ticketing, donor management, and email can all sit on the same free platform, which means a development or comms hire can ship work on day one without a budget conversation. Zeffy is free for 100K+ nonprofits: no platform fee, no transaction fee, no credit card fee. Ever.
For a small nonprofit: the goal of the process isn't to be thorough. It's to be fast, structured, and decisive, so the staff member already holding everything together gets relief in week three, not week thirteen.
How long should a nonprofit interview last?
For most roles at a small org, a 30-minute first round and a 60-minute working second round is plenty. Anything longer is usually the interviewer's anxiety, not the candidate's depth. Senior roles (ED, director-level) can justify a third conversation with the board chair, but the total should rarely exceed 3 hours of the candidate's time before the offer.
Should we include a skills test or working session?
Yes, for any role where output matters more than credentials, which is most small-nonprofit roles. Keep it tight (60-90 minutes), keep it real (a slice of the actual job, not a hypothetical), and pay for it if it exceeds 90 minutes. Asking a candidate to do four hours of unpaid work is a red flag for them, not just for you.
How do we interview for culture fit without bias?
"Culture fit" is the term that smuggles in the most bias. Replace it with "values alignment" and operationalize it. Instead of "would I want to grab a beer with this person?" (the bias version), ask "does this person handle disagreement the way we need our team to?" or "can this person own work without me building scaffolding for them?" Those are observable behaviors, not vibes.
How can small nonprofits without formal HR teams conduct effective interviews?
Small nonprofits can run a solid interview process without dedicated HR staff. The key is structure without complexity. Form an interview committee of 2-3 team members and a board member. Assign clear focus areas: skills, values, and capacity to operate independently. Use a simple 1-5 scoring system so everyone is comparing notes on the same criteria. Document feedback with basic shared notes or a free online form. Research similar roles at other nonprofits and adapt their questions for your context. Include a practical exercise that reflects real job responsibilities.
How can nonprofits ensure their interviews are inclusive?
Start by removing logistical barriers. Offer flexible scheduling and multiple formats (video, phone, in-person). Share clear details about the process and what to prepare. During the interview, use plain language and avoid jargon. Don't make assumptions about candidates' backgrounds. Train your panel to recognize unconscious bias and aim for diverse representation among interviewers when possible. Give candidates enough time to respond and offer breaks during longer sessions. Focus evaluation criteria on core competencies, not just traditional credentials. Inclusive hiring is about creating conditions where all candidates can show what they're actually capable of.
What are common mistakes nonprofits make during interviews?
The most common ones: asking questions that aren't specific to the role, relying on the rsum instead of probing the experience behind it, forgetting to explain the mission and what you stand for, skipping practical questions about real challenges, rushing through without follow-up questions, leaving out team members who'd work with the hire, overlooking volunteer or unpaid experience, not asking about motivation, giving a vague job description, and only focusing on current skills instead of growth potential.
Should we ask about salary expectations in round 1?
Yes. Post the range publicly if you can, and confirm it in round 1. A small org can't afford to spend three rounds with a candidate who's $20K above your top of band. It wastes their time and yours. Transparency on compensation is a small but real recruiting advantage in a sector where it's still rare.
.webp)
