I'm Karim, a talent and operations strategy leader based in Sarasota, Florida.
My background centers on building systems that position talent and hiring operations as proactive growth drivers rather than reactive support functions. I have extensive experience with workforce planning, hiring process design, and passive/non-obvious talent discovery.
I've been interested in AI for quite a while, but became far more curious about AI safety earlier this year... And the more I learned, the more that curiosity transformed into conviction. From that emerged a commitment to transition into the field, and I've spent the majority of this year strengthening my understanding of the risks and exploring where my experience could create the most impact. I've been particularly interested in the constraints that may limit an organization's ability to scale and how those can be addressed.
I was accepted into the BlueDot AGI Strategy Course and the CEA Bootcamp, and I've been connecting with SPAR Fellows to contribute to projects related to my expertise. I've also taken a particular interest in gradual disempowerment and recently published an essay exploring it through a framing I believe deserves deeper examination.
On a more personal level, I'm a father of two young boys, a humanist, and someone who has always been drawn toward existential questions - not only what kind of future we're building but also what any of it ultimately means. AI safety has given me a reason to bring those interests together with the skills I've spent my career developing.
Plan T vibes...
This post does a great job of highlighting why I'm compelled to start an org, and the TLDR summarizes it really nicely: Figure out what needs doing and do it, don't wait on approval from fellowships or jobs. I see gaps, I'm confident I can fill them, and I'd rather use my capabilities to contribute than continue trying to demonstrate that I have those capabilities in the first place.
I've also learned far too much about the hiring practices of AI safety orgs to justify the cost-benefit of pursuing roles through applications. Most orgs don't have adequate processes in place to evaluate inbound talent, so they lean heavily on referrals and candidates whose alignment is easily recognized. Gergő and Aaron highlight how much they value context and worldview, but neither address the difficulty of identifying outsiders who have developed those qualities. There's also a substantial opportunity cost if that alignment is weighted more heavily than deep functional expertise, which I've expanded on previously in comments on other posts about this subject.
The org concept I'm working on ties into what I wrote about in this post: new ways to engage with the public and drive support for the AI safety cause. There's much more to it than just that, but the primary outcome I'd be looking to achieve is to make AI safety a priority for everyone rather than just those working within AI safety. I'd also look to hire heavily from the talent pipeline rather than pull from other orgs, and I think that's an approach that should be welcomed considering the staggering mismatch between capable external talent and available opportunities for them.
Spot on. I agree with your points, and ultimately they can keep working on x-risks while using more immediate threats as a way to build awareness and support. They don't need to change where they apply their focus, but messaging around more accessible entry points for public engagement could be a great move.
However, my ideas go beyond just fear-based messaging. That's one way to get buy-in, but it's not the only way, and I think there are other approaches worth exploring. That's a big part of what I've been thinking about and the org concept I'm working on.
I definitely see your perspective! Getting rejected from the course the first time I applied (back in June) largely influenced my assumption that I needed to strengthen my understanding if I wanted to get in. For all I know, I could have applied a week later and been accepted back then, and had I done so I'm sure the experience would have been very different.
On coursemates being less alarmed, I agree. A lower level of concern doesn't necessarily mean someone is less informed. I'm sure there are plenty of people that know far more than I do and simply disagree with my perspectives. That said, in the discussions I participated in, many of my peers shared that this was their first time encountering some of the arguments or even that they hadn't done all of the readings. That's not a knock on them - many are still working full-time roles, and there's a lot of literature to engage with in order to develop a solid foundation of understanding. Not everyone can stop what they are doing and commit full-time to learning about a field they want to enter, and, to me, that's largely why these context/worldview gaps exist in the first place.
And no, I haven't secured a role, but I also haven't applied to any since September. My focus has shifted toward developing a concept for a new organization aimed at addressing some of the gaps I see in the field. The types of roles I was initially targeting are fairly senior level and relatively few and far between, and I think there are plenty of meaningful areas of impact that a new org could pursue.
I agree that this is a great post and with your point that the opportunity cost is often underweighted. I also think that cost may extend beyond slower organizational growth, particularly when trust and familiarity are valued over deep functional expertise. Many organizations seem to favor insiders with demonstrated alignment over external candidates who have spent years developing relevant skills. This may be especially consequential for generalist functions, where competent execution can conceal unrealized potential.
I don't mean to discredit the people in those roles as I imagine they're highly capable, but there is a meaningful difference between maintaining a function and elevating its effectiveness. As you said, developing the skills for the latter can take years. The challenge is not simply the time it takes to learn, but whether they are in a position to develop those capabilities at all. They may not be aware of what they need to learn, have limited exposure to experts they can learn from, or even do an excellent job maintaining the function, making unrealized potential difficult to recognize. This type of opportunity cost is self-concealing and can compound across an organization as it scales without adapting its hiring practices.
I'm also not arguing that orgs should prioritize outsiders over insiders, but rather that they would benefit from addressing the constraint Patrick highlights: assessing outsiders is costly, and many orgs don't have the systems in place to do so effectively. And unfortunately, building those systems may itself require bringing in someone from the outside with deep experience doing exactly that.
Appreciate these insights, especially because I've been thinking about opportunity costs a lot recently, albeit from a different perspective that I think deserves more consideration.
As someone who's been exploring opportunities to enter the AI safety field and learning a lot about the ecosystem along the way, I wonder if orgs are adequately accounting for the opportunity cost of not bringing in external expertise. My exposure is limited so I could be wrong, but I've gotten the impression that existing access and familiarity within the community are weighted more heavily, especially for generalist roles.
There's an obvious focus on attracting talent, and plenty of programs and resources committed to that. But is that matched with a willingness to hire outsiders with deep functional experience over insiders with demonstrated alignment?
Prioritizing the latter may create a particularly self-concealing opportunity cost: someone can be perfectly capable of keeping a function running without having the experience to recognize how much more effective it could be. If those in leadership don't have that expertise either, any resulting inefficiencies and unrealized value can be difficult to identify. And when the people in those roles are otherwise brilliant, trusted, and deeply mission-aligned, their ability to keep things running may obscure what the organization is missing out on: expertise in developing high-impact strategies, optimizing processes, and addressing constraints that could be limiting their ability to scale.