Grant writer: job description, interview questions, and screening workflow

The generic advice for this hire is "find a great writer." At a small nonprofit, that's necessary and nowhere near sufficient. Good grant writing isn't a creative writing exercise. It's translating a program's real outcomes into the exact format and language a funder's rubric is scoring against, on a deadline that doesn't move because the writing took longer than expected. What actually sinks a grant writer hire is someone who writes beautifully but can't get a straight number out of a busy program director, or who misses a submission window because they were still polishing a sentence. This guide is built to screen for the researcher and project manager behind the prose, not the writing sample alone.

What a grant writer actually does at a small nonprofit

At a large foundation or a nonprofit with a full development department, grant writing might be one narrow lane: someone else handles the funder relationships, someone else pulls the program data, and a writer assembles the final document. At a small mission-driven organization, one person usually owns the entire calendar, from research to submission to post-award reporting, often alongside other duties. The core responsibilities, in practice:

• Researching new funding opportunities across foundations, government agencies, and corporate giving programs
• Maintaining a grant calendar that tracks every deadline, from letters of intent through final reports
• Writing letters of intent and full proposals that translate program work into a funder's specific format and priorities
• Working directly with program staff to gather accurate outcomes, budget, and impact data
• Managing post-award compliance reporting so the organization stays in good standing for future cycles
• Maintaining a boilerplate or case-for-support library so the same background section isn't rebuilt from scratch every time

The writing itself usually isn't the hardest part for someone with real experience. The hard part is everything around the writing: getting a program director to hand over real numbers instead of a vague summary, judging whether a new funder is actually a fit before spending days on a proposal, and keeping a dozen deadlines in different stages from colliding into the same week. Funder fit matters because the odds are real: Candid's Foundation Center research found that among grantmakers surveyed, larger foundations receiving over 1,000 proposals a year funded at least half of what they received only 11% of the time, while smaller foundations funded at that rate far more often. A grant writer who researches fit before writing is protecting the organization's time against those odds.

Job description you can post today

Copy this, then adjust the specifics (your funding mix, your reporting tools, your program areas) to match your organization.

Grant writer
[Organization name] is looking for a grant writer to research funding opportunities, write compelling proposals, and manage our grant calendar from first research to final report. You'll work closely with our program team to translate real outcomes into proposals that win funding and keep our programs running.

What you'll do
Research and evaluate new foundation, government, and corporate funding opportunities. Maintain a grant calendar tracking every deadline across letters of intent, proposals, and reports. Write clear, compelling proposals grounded in real program data. Work directly with program staff to gather outcomes, budget, and impact information. Manage post-award compliance reporting on time, every time. Maintain and update our case-for-support materials and boilerplate language.

What we're looking for
A real system for tracking multiple deadlines in different stages at once, not just a claim of being organized. Strong writing that's grounded in specific evidence, not general appeals. Comfort following up persistently but professionally with program staff who are busy and hard to pin down. Judgment about which funding opportunities are worth pursuing and which aren't a fit.

Schedule
[Insert hours, e.g. full-time with flexibility around deadline crunches, or part-time depending on your grant volume]

[Insert pay range, per your organization's policy and any applicable state salary transparency requirements]

12 interview questions, and what a good answer sounds like

1. Walk me through how you'd track ten grant deadlines that are all in different stages, so nothing slips.

You're checking for a real system, not a vague claim. A strong answer names something concrete: a shared calendar with stage tracking, standing check-ins tied to deadline proximity, a habit of working backward from a submission date. A weak answer is some version of "I'm good with deadlines," with nothing you could actually observe.

2. Tell me about a time you had to get outcomes data from a program staffer who wasn't responsive. What did you do?

This tests the part of the job that isn't writing at all. Listen for a real story: a specific follow-up approach, escalating appropriately if a deadline was at risk, finding an alternate source for partial data if needed. A candidate who can't produce a real example, or who just says they'd "keep asking," hasn't yet owned this part of the process.

3. A funder's rubric asks a question your program's data doesn't cleanly answer. What do you do?

Good answers show honest problem-solving: clarifying what's actually being asked, finding the closest available proxy data, or being direct with the funder or your team about a genuine gap rather than fabricating a number to fit. A candidate who suggests rounding up or guessing to make the numbers look better is a real flag.

4. Tell me about a proposal you're proud of. What made the case compelling, beyond the writing itself?

Listen for a real answer grounded in evidence: a specific outcome, a clear alignment with the funder's priorities, a strong theory of change, not just "I wrote it well." A candidate who can only describe the prose, not the substance behind it, may be treating grant writing as a purely creative exercise.

5. Walk me through your process for researching whether a new funder is actually a good fit before you spend time writing to them.

This should come out as a real filtering process: reviewing a funder's past grantees and giving priorities, checking alignment with your program areas, confirming eligibility requirements before investing hours. A candidate who says they'd apply to anything that seems plausible is describing a process that wastes time on long-shot proposals.

6. Describe how you'd handle a reporting deadline for one grant landing the same week as a new proposal deadline for another.

Good answers describe real triage: understanding which deadline has less flexibility, communicating early with a funder if a report might need a short extension, and not letting the "exciting" new proposal quietly crowd out a compliance obligation that keeps existing funding intact.

7. Tell me about a time a proposal was rejected. What did you do with the feedback, if you got any?

You want a real story with real reflection, not one where the rejection is entirely attributed to the funder's budget or timing. A candidate who sought out feedback when it wasn't automatically offered, and can name something they'd do differently, shows real growth instinct.

8. How do you keep a boilerplate or case-for-support library updated so you're not rewriting the same background section every time?

Strong answers describe an actual habit: a living document updated after each major program change or new outcomes report, organized so pieces can be pulled into a new proposal quickly. "I just start from an old proposal each time" suggests drift and outdated numbers creeping into new submissions.

9. What's your process for making sure the numbers in a proposal match what's actually in the program's data, not just what sounds good?

This tests integrity and rigor together. Listen for a real verification habit: checking a number against its source before it goes in, not relying on memory or an old figure from a previous proposal. A candidate who's vague here is a risk in a role where a wrong number can become a funder-facing claim.

10. How would you handle being told, two days before a deadline, that the program budget numbers you used are now wrong?

Good answers stay calm and practical: confirming the correct numbers immediately, updating every place they appear in the document, and flagging to a supervisor if the change is significant enough to need a second look. A candidate who describes panicking or blaming whoever gave them the original numbers is telling you how they'll handle the next crunch too.

11. Why are you interested in grant writing at a small nonprofit, where you're likely the only person doing this, instead of a larger development team?

This surfaces whether they understand what they're signing up for. A strong answer names something real: full ownership of the funding strategy, direct relationships with program staff, seeing a proposal's real-world impact up close. A candidate who can't articulate a reason beyond "it was the job that was open" may be underprepared for doing this alone.

12. Tell me about a time you had to say no to writing a proposal, or push back on leadership about a funding opportunity that wasn't a good fit.

This tests judgment and backbone. A strong answer describes a specific opportunity that looked appealing on the surface (maybe a large dollar amount) but wasn't actually aligned with the organization's mission or capacity, and how they made that case. A candidate who says they'd write to any opportunity leadership wants may struggle to protect the organization's time and credibility later.

A scorecard you can score candidates against

Twelve questions are only useful if everyone on your team is listening for the same signals. Score every candidate on the same six, so you're comparing evidence instead of comparing whose writing sample read the smoothest. Copy this into a doc and fill in a row per candidate.

How to screen grant writer candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you can build a screening process around what actually predicts success in this role: deadline discipline and the ability to extract real data from busy colleagues, not just a polished writing sample.

A workflow that fits a small nonprofit hiring one grant writer to run the whole calendar:

• Resume screening first. Look for real grant research, writing, and calendar management experience, not just general nonprofit or communications background.
• A short one-way video interview for your first real look. Ask 2 to 3 of the scenario questions above, like the unresponsive-staffer question or the funder-fit research question, so you hear how someone actually reasons through the parts of the job a writing sample can't show you.
• A short, relevant skills check instead of a long take-home. Our communication assessment tests the exact behaviors this role runs on: clarifying a vague ask under a deadline, and documenting a decision so it doesn't get lost, without asking someone to burn an evening on a project.
• A real, live conversation only for the candidates who clear the first three steps. By the time you're on a call, you already know they can manage deadlines, extract data, and communicate clearly under pressure. The live conversation is for fit and judgment, not for finding out for the first time whether they can do the job.

Our resume screening and one-way video interview tools handle the first two steps in one place, with AI that surfaces your strongest matches against the criteria you set. You review the evidence and decide. It doesn't pick for you. If you're building out the rest of a small program team, our nonprofit program coordinator hiring guide and volunteer coordinator hiring guide cover those roles specifically.

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

A skills check only helps if it tests the judgment the job actually needs, not generic writing trivia. These three are pulled straight from Truffle's communication assessment, the screen we'd point you to for this role. Try them yourself before you decide what "strong communicator" means for your organization.

The point isn't these three questions specifically. It's that a short, job-relevant skills check like this tells you in ten minutes what a writing sample alone can't: whether someone handles ambiguity, documentation, and friction the way this role actually requires. Truffle's AI scores and surfaces the results against the bar you set. You still make the call on who clears it.

Common hiring mistakes for this role

Over-indexing on writing samples alone. A beautiful writing sample tells you someone can write well with unlimited time. It doesn't tell you whether they can hit a real deadline or extract accurate numbers from a busy colleague. Weight the process questions above at least as heavily as the sample itself.

Not testing how someone handles unresponsive program staff. This is one of the most common, underestimated parts of the job at a small nonprofit, where program staff are stretched thin and grant deadlines aren't their top priority. Ask directly how a candidate has handled it before.

Assuming any nonprofit background transfers directly. A program coordinator or a communications generalist may have real, relevant skills, but running a live grant calendar with hard external deadlines is a different job than most adjacent nonprofit work. Test for it directly instead of assuming it from a resume.

Underestimating the cost of a missed deadline. A late or unfinished proposal isn't a minor miss. Since most funding cycles only open once or twice a year, it can mean losing access to that money for six months to a year. Treat this hire with the seriousness the downside actually deserves.

Letting one grant writer's calendar grow past what any system can track. Even a strong hire with a real process will start missing deadlines if your funding volume outpaces what one person can reasonably run. Watch for the warning signs in the interview questions above before a missed deadline tells you about it the hard way.