Hi Emily-- I enjoyed and took inspiration from your previous post on your pivot journey. This inquiry on freelancing and atomization of tasks is a smart follow up.
As an experienced grantmaking generalist currently working for a non-EA foundation, I think there is a useful distinction between generalist tasks that can be projectized vs longer-term functions that are harder to separate from deep-seated organizational context.
Tasks that lend themselves well to freelance work have a clear end state and a well defined standard of quality:
- creative-forward projects like web design (traditionally left to freelancers given lack of continuity)
- clearly scoped writing projects like research memos, due diligence, landscape scans, or grant applications (assuming the org has heavily documented their own priorities and context)
- one-time database hygiene checks, workflow documentation, template creation
- bounded process analysis and automation projects (when the org knows how to define its desired end state-- difficult / not a given!)
- surge capacity for proposal review, event logistics, heavy reporting
All of this scoping and documentation that (I feel) is required to hire a freelancer responsibly requires significant internal capacity to spin up. If those conditions are missing, the freelancer may be set up to fail.
It is also common for any of the above tasks to overflow their clean deliverable scoping and brush at deeper matters of prioritization judgment, internal inconsistencies, informal or unwritten context, org chart tensions, etc. One piece of the value of a full-time generalist is their ability to notice and take initiative to address these kinds of problems, which may require deep, long-term, and emotionally aware engagement. They can be especially prevalent for orgs with a startup culture or those that scale rapidly. Freelancers may notice these deep issues but tend not to be in a good position to address them out of fear of overstepping or creating relational friction that a full-time employee is far more incentivized to tackle.
I've also observed that EA orgs are extremely discerning about their hires, and rationally so. Freelancers occupy an awkward position where it is not cost-effective to conduct a similar vetting process given short project timelines and expected turnover, but the risk surface for the org is still fairly high if this person turns out to deliver subpar work: the deficiency needs to be identified, the contract reassigned, and the work repeated.
This very cost-benefit tension is the kind of issue that a high-level, embedded operations person could identify and solve. When do we take on the risk of a freelancer to power through something urgent in the short-term, and when is it more sustainable to take time to solve the underlying capacity issue?
I do love the idea of a freelance generalist directory. It may benefit from some scaffolding: tips on turning organizational pain points into scoped projects and perhaps some sort of pre-vetting process. Either way, I'd love to support!
Emily, this is really interesting to me, particularly your observation that there seems to be a need for generalist skills that isn't necessarily visible in the job market.
I wonder whether a source of operational freelancers could be a useful resource for EA—and potentially AI safety organizations specifically. A pool of experienced people who could come in for defined projects, fractional work, or short-term operational capacity could lower the barrier on both sides.
But I'm also wondering whether the bottleneck is actually less about a lack of talent and more about talent recognition and organizational design.
A lot of what you're describing sounds very familiar from the startup and growth environments I've worked in. Organizations know they have too much to do, but they don't always know exactly what role they need, how to structure it, or what capabilities should sit together. That's an organizational design problem as much as a recruiting problem.
I'm particularly curious about the emphasis on “context.” Obviously, there is domain-specific context that matters enormously for technical research and policy work. But for operations, I'm less convinced the amount of context required is as high as it sometimes seems to be.
The basic building blocks of building and scaling an organization—clarifying priorities, designing roles and decision rights, establishing processes, creating operating rhythms, improving systems, identifying bottlenecks, managing projects, building capacity—have a remarkable amount of commonality across industries.
So I keep wondering: how much context is actually necessary before an experienced operator can start producing useful work, when that work is neither technical nor research in nature?
I've actually started considering offering myself as a freelancer into the ecosystem for exactly this reason—not necessarily to arrive knowing what the organization needs, but to help an organization figure that out. Come in, understand the work and the bottlenecks, help define what capacity is missing, determine what the roles should look like, and then either help build that capacity or hand off a much clearer hiring plan.
It seems like that could be a useful bridge between “we need more capacity” and “we have a perfectly defined job description for you.”
And your point about the amount of unpaid work required to establish credibility makes me wonder whether we're inadvertently filtering out some of the very experienced people the field needs. Not everyone who has valuable operational expertise is going to be able—or willing—to spend six months proving that they belong before they're allowed to use it.
Anyway, I'm still thinking this through, but I really appreciated you articulating the problem so clearly. It has me looking at the generalist bottleneck less as a talent-supply problem and more as a possible talent-routing + organizational-design problem.