Pipelines don’t just fail by being absent they lose talent by being outcompeted. Right now, policy organizations, governance think tanks and for profit businesses are winning the generalist talent competition by default, simply because they have job listings, defined roles, and an onboarding infrastructure. AI safety and impact organizations have tremendous potential and a broken front door and that asymmetry has a cost that compounds quietly.
The post identifies a real bottleneck, but I don’t think this risk gets named or measured sharply enough in the ecosystem. The field isn’t just failing to attract generalist talent, it’s actively losing those who are aligned and passionate about working to adjacent pipelines that have clearer entry points.
Policy organizations, governance think tanks, and corporate AI teams are hiring. They post on LinkedIn and Indeed. Some add the term “ethics or safety” to the job title. They have defined roles, recognizable credentials, and onboarding infrastructure. For someone with strong mission alignment but no research or technical background, “AI safety-adjacent” becomes the path of least resistance. The person has the conviction, but easier and legible paths exist that are nuanced and harder to identify in the AI safety space.
The counterfactual isn’t that person staying in marketing. It’s that person doing meaningful work on AI, outside the ecosystem, in structures that don’t share the same stakes or threat models and that is a compounding loss.
I’m raising this from inside of the problem as I’m a strategic communications executive, with 20+ years of experience and a non-technical background. I found AI safety last August through the standard rabbit hole that began with a YouTube talk by Tristan Harris, AI 2027, BlueDot, 80,000 Hours, Successif, and now the CEA Career Bootcamp. As of this writing I’m asking my bootcamp advisor for referrals to people who’ve made this pivot from generalist or strategic communications to AI safety organization. From networking and taking courses I respond to every job or connection. I show up to events where I’m often the eldest person in the room and routinely the only one without a research or technical background.
EA members tell me the ecosystem needs communicators and generalists. As the writers suggest searching the 80000 Hours job listings or fellowship opportunities it’s hard to see the need for those of us with these skills. The credentialing infrastructure or pathway doesn’t exist outside of Blue Dot or the CEA Bootcamp. There is an implicit hierarchy where research is the real work and it is legible even when it’s unintentional. I have enough context and drive to push through that friction but I shouldn’t have to rely on referrals and my tenacity.
The Generator Residency is a meaningful signal and I plan to apply. But the deeper fix is making the pipeline visible enough that alignment-minded generalists don’t have to stumble into AI safety and sturdy enough that they don’t get routed elsewhere while they’re looking for the door.
Credit to the authors for naming this clearly. The Generator Residency is a good first move and the pipeline problem is bigger than one program and worth continued pressure.
Thanks for engaging with our post. To be clear, do you think that there’s a problem related to how much we signpost the roles we need publicly? It’s my impression that the majority of vacant generalist roles are indeed posted and circulated through job boards and LinkedIn, it’s just that most of the applicants don’t meet the criteria orgs are searching for.
That’s a helpful distinction and honestly it sharpens my thinking. If the roles are out there, then the real gap isn’t that people can’t find the door, it’s that most people don’t yet have what it takes to walk through it or understand the pathway to get there.
That’s the part I was really trying to name. Someone who genuinely cares about this work but can’t yet meet the bar for an AI safety role isn’t going to wait around. They’re going to take the governance, policy, or corporate “ai ethics” job that’s hiring right now because that path exists and this one is harder to navigate. By the time the ecosystem builds the infrastructure to develop that person, it’s already lost them.
So I’ll refine what I said: the front door may be more visible than I implied. The pathway to being ready to walk through it is what’s missing.
What you and your colleagues are building with the Generator Residency is exactly the kind of infrastructure this ecosystem needs. Creating a structured pathway that develops, credentials, and places generalists is the missing piece. I’m excited to see it and share it with my cohort team members.
I’ll add one more data point from where I’m sitting right now. In my CEA bootcamp cohort there are several talented, mission-aligned generalists actively searching for roles in AI safety organizations. The consistent challenge isn’t motivation or alignment, it’s access. Without a technical background, breaking into this ecosystem often comes down to who you know or who referred you.
I hope the Generator Residency is the first of many programs like it. The talent is out there and it is mission aligned.
Karen, your reply appears to be AI-generated. I recommend avoiding using LLMs in job applications and EA Forum conversations—the prose isn’t good and (most) people still prefer talking with humans.
It’s extremely intimidating to write in the EAForum. Normally I write my thoughts and ask Google or Claude to edit for mistakes or clarity.
This is such an important conversation that I am living through now. I wanted to add not detract from the conversation. I will go back to lurking on the EA Forum.
I made an account here so I can post this comment.
I wanted to thank you for raising these issues. Similar to you, I’m a senior professional. I’m part of Bluedot and CEA cohorts which also include other senior professionals (20-30 years experience). These professionals (and myself) have already had impactful careers, and are looking to pivot into new impactful roles where our skills and experience can be applied.
With my personal background, it would be much easier (and probably better financially) for me to pivot into corporate AI Governance rather than AI safety. I’d prefer not to do this since it seems less impactful.
I also find the distinction in these discussions between technical / researcher roles and ‘generalist’ (ie non-technical) roles to be an interesting framing. It seems to me that there are other ways of assessing mission alignment, and there is a risk of overweighting on technical expertise, as HannahGB questions below.
To give a concrete (but invented) example:
Scenario 1: Lets imagine that we have an AI safety organisation doing wonderful research. The researchers take their results, and present at a technical conference. Attendees are very impressed, and this inspires other researchers to continue to develop the research pathway.
Scenario 2: Lets imagine the same research at a different AI safety organisation. The researcher briefs the executive leadership of the organisation on their results. The organisation works with their policy lead to tease out the implications of the research results. The policy and communications leads work together to define an advocacy position and their proposals, supported by a strong briefing deck with talking points that are understandable by a semi-technical government audience. A lawyer helps prepare zero draft text for inclusion in regulation. The policy lead links the organisation with regulators from their network, to present the research and advocate for improved governance. The Comms lead arranges publicity and advocacy for the discussion through their comms networks. And the researcher still gets to present the research at a technical conference.
It seems to me like there’s a lot of Scenario 1 work happening in the field. And then some separate organisations working on AI governance and oversight from a legislative and policy perspective. My question is whether there is also opportunity for more of the Scenario 2 type approach?
Pipelines don’t just fail by being absent they lose talent by being outcompeted. Right now, policy organizations, governance think tanks and for profit businesses are winning the generalist talent competition by default, simply because they have job listings, defined roles, and an onboarding infrastructure. AI safety and impact organizations have tremendous potential and a broken front door and that asymmetry has a cost that compounds quietly.
The post identifies a real bottleneck, but I don’t think this risk gets named or measured sharply enough in the ecosystem. The field isn’t just failing to attract generalist talent, it’s actively losing those who are aligned and passionate about working to adjacent pipelines that have clearer entry points.
Policy organizations, governance think tanks, and corporate AI teams are hiring. They post on LinkedIn and Indeed. Some add the term “ethics or safety” to the job title. They have defined roles, recognizable credentials, and onboarding infrastructure. For someone with strong mission alignment but no research or technical background, “AI safety-adjacent” becomes the path of least resistance. The person has the conviction, but easier and legible paths exist that are nuanced and harder to identify in the AI safety space.
The counterfactual isn’t that person staying in marketing. It’s that person doing meaningful work on AI, outside the ecosystem, in structures that don’t share the same stakes or threat models and that is a compounding loss.
I’m raising this from inside of the problem as I’m a strategic communications executive, with 20+ years of experience and a non-technical background. I found AI safety last August through the standard rabbit hole that began with a YouTube talk by Tristan Harris, AI 2027, BlueDot, 80,000 Hours, Successif, and now the CEA Career Bootcamp. As of this writing I’m asking my bootcamp advisor for referrals to people who’ve made this pivot from generalist or strategic communications to AI safety organization. From networking and taking courses I respond to every job or connection. I show up to events where I’m often the eldest person in the room and routinely the only one without a research or technical background.
EA members tell me the ecosystem needs communicators and generalists. As the writers suggest searching the 80000 Hours job listings or fellowship opportunities it’s hard to see the need for those of us with these skills. The credentialing infrastructure or pathway doesn’t exist outside of Blue Dot or the CEA Bootcamp. There is an implicit hierarchy where research is the real work and it is legible even when it’s unintentional. I have enough context and drive to push through that friction but I shouldn’t have to rely on referrals and my tenacity.
The Generator Residency is a meaningful signal and I plan to apply. But the deeper fix is making the pipeline visible enough that alignment-minded generalists don’t have to stumble into AI safety and sturdy enough that they don’t get routed elsewhere while they’re looking for the door.
Credit to the authors for naming this clearly. The Generator Residency is a good first move and the pipeline problem is bigger than one program and worth continued pressure.
Hi Karen,
Thanks for engaging with our post. To be clear, do you think that there’s a problem related to how much we signpost the roles we need publicly? It’s my impression that the majority of vacant generalist roles are indeed posted and circulated through job boards and LinkedIn, it’s just that most of the applicants don’t meet the criteria orgs are searching for.
Agustin,
That’s a helpful distinction and honestly it sharpens my thinking. If the roles are out there, then the real gap isn’t that people can’t find the door, it’s that most people don’t yet have what it takes to walk through it or understand the pathway to get there.
That’s the part I was really trying to name. Someone who genuinely cares about this work but can’t yet meet the bar for an AI safety role isn’t going to wait around. They’re going to take the governance, policy, or corporate “ai ethics” job that’s hiring right now because that path exists and this one is harder to navigate. By the time the ecosystem builds the infrastructure to develop that person, it’s already lost them.
So I’ll refine what I said: the front door may be more visible than I implied. The pathway to being ready to walk through it is what’s missing.
What you and your colleagues are building with the Generator Residency is exactly the kind of infrastructure this ecosystem needs. Creating a structured pathway that develops, credentials, and places generalists is the missing piece. I’m excited to see it and share it with my cohort team members.
I’ll add one more data point from where I’m sitting right now. In my CEA bootcamp cohort there are several talented, mission-aligned generalists actively searching for roles in AI safety organizations. The consistent challenge isn’t motivation or alignment, it’s access. Without a technical background, breaking into this ecosystem often comes down to who you know or who referred you.
I hope the Generator Residency is the first of many programs like it. The talent is out there and it is mission aligned.
Karen, your reply appears to be AI-generated. I recommend avoiding using LLMs in job applications and EA Forum conversations—the prose isn’t good and (most) people still prefer talking with humans.
It’s extremely intimidating to write in the EAForum. Normally I write my thoughts and ask Google or Claude to edit for mistakes or clarity.
This is such an important conversation that I am living through now. I wanted to add not detract from the conversation. I will go back to lurking on the EA Forum.
Hi Karen,
I made an account here so I can post this comment.
I wanted to thank you for raising these issues. Similar to you, I’m a senior professional. I’m part of Bluedot and CEA cohorts which also include other senior professionals (20-30 years experience). These professionals (and myself) have already had impactful careers, and are looking to pivot into new impactful roles where our skills and experience can be applied.
With my personal background, it would be much easier (and probably better financially) for me to pivot into corporate AI Governance rather than AI safety. I’d prefer not to do this since it seems less impactful.
I also find the distinction in these discussions between technical / researcher roles and ‘generalist’ (ie non-technical) roles to be an interesting framing. It seems to me that there are other ways of assessing mission alignment, and there is a risk of overweighting on technical expertise, as HannahGB questions below.
To give a concrete (but invented) example:
Scenario 1: Lets imagine that we have an AI safety organisation doing wonderful research. The researchers take their results, and present at a technical conference. Attendees are very impressed, and this inspires other researchers to continue to develop the research pathway.
Scenario 2: Lets imagine the same research at a different AI safety organisation. The researcher briefs the executive leadership of the organisation on their results. The organisation works with their policy lead to tease out the implications of the research results. The policy and communications leads work together to define an advocacy position and their proposals, supported by a strong briefing deck with talking points that are understandable by a semi-technical government audience. A lawyer helps prepare zero draft text for inclusion in regulation. The policy lead links the organisation with regulators from their network, to present the research and advocate for improved governance. The Comms lead arranges publicity and advocacy for the discussion through their comms networks. And the researcher still gets to present the research at a technical conference.
It seems to me like there’s a lot of Scenario 1 work happening in the field. And then some separate organisations working on AI governance and oversight from a legislative and policy perspective. My question is whether there is also opportunity for more of the Scenario 2 type approach?