Most of this work is spent in polishing the grant and figuring out how to best present your research agenda. This is not writing code, so if you'd rather be writing code, this isn't really a good fit for you.
Most of this work is spent in polishing the grant and figuring out how to best present your research agenda. This is not writing code, so if you'd rather be writing code, this isn't really a good fit for you.
Many people who are good at whatever activity the grant is supposed to support are terrible writers or at least terrible grant writers (which isn't surprising because grant writing can often be extraordinary boring).
From what I can gather, most scientists in the sense of working at universities as profs aren't selected for their ability as writers until they actually become profs, or at least post-docs. Which means that many will be something like 30 before they realize writing grants is important, but that they may not be well-suited to doing so, since few people are.
My family's consulting business does grant writing for nonprofit and public agencies (you can read more about this at http://blog.seliger.com if you're curious), and many of our clients hire us precisely because they're not good at grant writing but are often good at providing whatever service they're providing. We mostly write human services grants but sometimes do technical work. I'm actually surprised that more profs don't find ways to outsource or partially outsource grant writing; they could do for in the neighborhood of $5 – $10K / proposal, which is relatively small relative to the value of their time.
It is like raising VC capital: an agency is likely to be more friendly, if it sees another take some of the initial funding risk. So you sell your idea, and manage the project -- not unlike a feudalistic landlord.