Grant Writer
Researches funding programmes and writes proposals, milestone plans, budgets, and reports that connect a project's work to an ecosystem's stated goals.
New to this area? Learn the foundations before building proof.
Also listed as
Grant Consultant · Ecosystem Grants Specialist · Proposal Writer
What this role actually does
Most days, the practitioner has to research programmes, draft sections, collect evidence, clarify scope, and manage application requirements.
Its decision rights usually cover grant research, proposal narrative, and milestones, while guaranteeing funding and owning programme selection decisions remain outside the default remit.
Where the role sits
Grant Writer usually sits inside Governance, Foundation Operations, Legal, Compliance, People, Grants, or Education teams. Common reporting lines include General Counsel, Compliance Lead, People Lead, Governance Lead, Foundation COO, or Ecosystem Program Lead. Core-team roles coexist with outside counsel, recruiters, educators, consultants, grant contractors, and contributor-led governance work. The role usually collaborates with Governance Coordinator, Ecosystem Researcher, Operations Associate, Ecosystem Partnerships Manager.
Core responsibilities
- Research programme scope, eligibility, evaluation criteria, deadlines, and reporting requirements
- Interview project owners and turn their plan into a credible proposal
- Define milestones, deliverables, dependencies, budget, risks, and measurement
- Coordinate evidence, technical input, legal or finance review, and submission
- Track reviewer questions, revisions, approval, and reporting
- Maintain an honest record of what changed after funding
Daily, weekly, and reactive work
A typical day
Research programmes, draft sections, collect evidence, clarify scope, and manage application requirements.
Weekly or monthly
Review pipeline, improve proposals, prepare reports, and coordinate milestone evidence.
When conditions change
Respond to deadline changes, reviewer requests, rejected milestones, budget changes, team delivery problems, or an application that no longer matches reality.
Deliverables
How success is judged
- Eligibility fit
- Credible milestones
- Clear budget
- Successful review
- On-time reporting
- Funded work delivered as described
Read signals in context. Read eligibility fit together with credible milestones. Neither signal is meaningful without the relevant launch, incident, market, workload, or attribution context.
Tools in practice
- Notion or Google Docs
- Draft, review, and maintain grant opportunity brief and proposal, with owners, source links, and change history.
- spreadsheets
- Structure the records behind grant opportunity brief and proposal and make review status visible.
- grant portals
- Check eligibility, submit the proposal and attachments, answer reviewer questions, and track milestone and reporting status.
- governance forums
- Publish or track proposals, voting windows, delegate discussion, quorum, and execution status while preserving the official record.
- CharmVerse or Gitcoin where relevant
- Review programme requirements, submit milestones, attach evidence, and track reviewer feedback in grant ecosystems that use these platforms.
- project management tools
- Track proposal owners, attachments, milestones, reporting dates, reviewer questions, and delivery dependencies.
Skills and prerequisite knowledge
Hard skills
- Proposal writing
- Programme research
- Milestone design
- Budget basics
- Evidence and reporting
Working skills
- Discretion
- Clear documentation
- Fair process
- Stakeholder sensitivity
- Ability to explain constraints without creating false certainty
Prerequisite knowledge
Understand the project's actual delivery capacity, ecosystem priorities, grant terms, governance process, and reporting obligations.
Expectations by level
Entry level
At entry level, a candidate should be able to complete a scoped assignment with review. That includes the ability to research programme scope, eligibility, evaluation criteria, deadlines, and reporting requirements, to interview project owners and turn their plan into a credible proposal, and to produce reviewable artifacts such as a grant opportunity brief and a proposal.
Mid level
At mid level, the practitioner normally owns grant research, proposal narrative, and milestones without constant supervision. They can coordinate adjacent teams and improve the workflow behind a grant opportunity brief and a proposal, including when the role must respond to deadline changes, reviewer requests, rejected milestones, budget changes, team delivery problems, or an application that no longer matches reality.
Senior
At senior level, the work shifts toward standards, decision rights, and review quality. A senior Grant Writer defines how grant research, proposal narrative, and milestones are handled, reviews high-risk cases, and builds systems that do not depend on one person.
Proof of work and portfolio
Reviewers should be able to inspect a grant opportunity brief and a proposal, trace the inputs or decisions behind the work, and understand what the candidate personally owned.
Strong proof
- A sample grant proposal
- A milestone and budget model
- A reviewer-response memo
- An impact report template
Weak evidence
- A generic project pitch reused for every programme
- Inflated impact claims
- Milestones that describe activity rather than verifiable output
Common mistakes and misconceptions
- Taking responsibility for guaranteeing funding and owning programme selection decisions without the mandate or approval to do so
Common misconception
Grant Writer may overlap with Governance Coordinator, but the hiring evidence is different. This role is judged on grant research, proposal narrative, and milestones, not on ownership of guaranteeing funding and owning programme selection decisions.
Scope boundaries
Usually owns
- Grant research
- Proposal narrative
- Milestones
- Budget rationale
- Application coordination
- Reporting
Usually does not own
- Guaranteeing funding
- Owning programme selection decisions
- Financial audit
- General company operations
- Inventing impact
Interview focus
Expect questions about proposal writing, programme research, and milestone design, plus a scenario where the role must respond to deadline changes, reviewer requests, rejected milestones, budget changes, team delivery problems, or an application that no longer matches reality. Interviewers are looking for evidence that the candidate knows where grant research and proposal narrative stop and guaranteeing funding and owning programme selection decisions begin.
How do you turn an ambitious roadmap into credible grant milestones?
When should you recommend not applying?
How do you report a milestone that changed after funding?
Compensation and role risks
Grant writing is often freelance, fractional, contract-based, or combined with ecosystem or operations work. Use project, retainer, success-fee, or salary evidence only when the model is explicitly sourced; avoid unsupported percentages or ranges.
No reliable role-specific range
KRAFT did not find a reliable role-specific range that meets the evidence standard. Compensation may still exist through salary, contract fees, retainers, grants, commissions, token or equity packages, creator revenue, or business economics. These models are described separately rather than compressed into an invented number.
Wider Web3 market, for scale
Typical advertised averages $65,000 – $200,000 / year
Individual postings run from about $40,000 to $350,000.
Across the role categories this index tracks, advertised averages sit between roughly $65,000 and $200,000 per year, with individual postings from about $40,000 to $350,000. This is whole-market scale from advertised roles - not a figure for this specific role, and not verified paid compensation.
Role risks
- Funding dependence
- Pressure to overpromise
- Success-fee conflicts
- Delayed programme decisions
- Responsibility for reporting after the original writer leaves
Compensation can change materially by geography, seniority, employment model, company stage, market cycle, and the mix of cash, bonus, commission, equity, token, vesting, royalties, or fees. A published range is useful only when those dimensions match the role being considered.
How to read compensation evidence
- Direct
- Evidence from the same or a materially equivalent role.
- Adjacent
- Evidence from a neighbouring occupation, used only for context.
- Broad market
- Category-level Web3 or labour-market evidence.
- Unverified
- Estimates without enough source or methodology detail.
Confidence reflects the quality and comparability of the evidence, not the value or legitimacy of the role.
Career path and role fit
Common progression
May fit people who
People who can turn messy plans into verifiable commitments and are willing to tell a team its proposal is not ready.
May not fit people who
People who mainly enjoy persuasive writing but dislike budgets, evidence, follow-up, and reporting.
Practical next steps
How this guide is built. Role content is drawn from current first-party hiring material and reputable industry evidence, with compensation labelled by confidence and evidence tier rather than a single number.
Turn this role into evidence.
Choose a proof-of-work project, package the result, and practice the questions this role is likely to ask.