Epistemic status: Tentative and personal. I'm somewhat biased by the frustration of unemployment and repeated rejections and very open to being corrected, especially by people with access to hiring data. Still, this is a pattern I've noticed over several years, and I thought it was worth articulating.
TL;DR
- I live in Rome and, since 2019, I’ve sent ≈70 applications to EA-aligned roles, receiving only 3 first-round interviews.
- I suspect that being physically and socially distant from core EA hubs (SF, Oxford, Berlin) may reduce candidate visibility.
- My background is atypical (founder, content creator, few institutional references), which might make me harder to evaluate.
- Over-reliance on public writing (e.g. Forum posts) may disadvantage those better at execution than exposition.
- I propose testing a two-step blind screening: evaluate anonymized work first, then review full profiles. Curious to hear thoughts.
Intro
Over the course of the years (dating back to 2019), I’ve applied to a high (≈70) number of EA-aligned jobs - from research assistant positions to operational roles, mostly in organizations based in SF, New York, Loxbridge, and the usual hotspots. I rarely make it to a first-round interview (≈3 times max)[1]
Now, let me be clear up front: this could very well be because I’m not a strong candidate. Maybe my experience isn’t quite relevant. Maybe my writing isn’t that great. Maybe I’m just not what these orgs are looking for. That’s completely plausible, and I don’t want to fall into the classic trap of “if they didn’t pick me, the system must be broken.”
But I do wonder if there’s another contributing factor that’s worth considering—namely, the effect of not being physically or socially present within the EA ecosystem.
I’ve mostly worked independently—startup founder, content creator, occasional freelancer. I don’t have institutional affiliations or high-prestige references. I’ve never co-worked at Trajan House[2] or attended a fellowship. I live in Rome, which doesn’t have a strong EA presence.
As a result, my applications often go out into the void. There’s almost no mutual contact who can vouch for me. No familiar name in my CV that resonates with someone on the hiring panel. Mostly friends, not professional referees, who could at best say, “yeah, I’ve met him, he seems thoughtful and capable.”
And that makes me suspect that a kind of proximity bias might be quietly operating in the selection processes. Not in a malicious or intentional way—just as a natural byproduct of how humans process uncertainty. When two candidates have similar profiles on paper, it’s easier to trust the one whose context you understand, who lives nearby, or who’s been seen around. Legibility becomes a tiebreaker.
Now, one might argue—and reasonably so—that context should matter. Understanding where someone comes from, how they operate, and who can vouch for them is part of evaluating culture fit and collaborative potential. And from a hiring manager’s perspective, that makes sense: you want to reduce downside risk.
But the downside of this is that we may be filtering out potentially strong candidates before we ever see what they can actually do.
"But Just Write on the Forum Bro"
I’m aware that visibility doesn’t just come from physical presence. One common suggestion—especially within the EA community—is to build credibility by posting on the Forum. And to be fair, that can be a great way to showcase your thinking, signal alignment, or get feedback[3]
But it's also worth asking: how strongly should we weigh public posting as a proxy for value-add?
For many roles—especially operational, logistical, or execution-heavy ones—public writing isn't always relevant. Some people don’t enjoy writing. Others are better at doing than explaining. Still others may be older, working full-time, parenting, or living in places with low EA density and few incentives to write for an audience they don’t naturally engage with.
Relying too much on Forum visibility can subtly bias us toward a certain personality type: analytically expressive, cognitively extroverted, and culturally fluent in EA-speak. That’s not bad per se—but it might lead us to overlook different but equally valuable kinds of contributors.
A modest proposal
What I’m suggesting is something fairly lightweight: more experimentation with two-step blind screening in EA hiring.[4]
- Step one: strip out names, locations, university names, and references from the initial application. Evaluate candidates based on short, role-relevant tasks—writing samples, spreadsheets, case responses, whatever best matches the role.
- Step two: only after shortlisting based on the anonymized task do reviewers gain access to the full CV, location, and references. Then you proceed as normal with interviews and contextual evaluation.
This doesn’t eliminate the value of context—it just shifts it later in the funnel, after you've already had a chance to assess actual work. In many cases, that might mean giving a chance to people whose backgrounds initially seem unfamiliar, but whose output is surprisingly strong.
Sure, this process adds a little complexity. It might be marginally more time-consuming, especially for small orgs. And yes, it might occasionally let through candidates who “perform well on paper” but don’t integrate well in practice. But those costs may be outweighed by the benefits of broadening our talent discovery radius—especially in a movement that cares so much about cause neutrality, evidence-based thinking, and impartiality.
More importantly, this is a testable claim. If this hasn't been done already it is possible to run a pilot: take a round of applications, evaluate half through the standard process and half via a blind-first pipeline. Compare which candidates make it to final interviews, and how satisfied the hiring managers are with each group. It’s a small empirical question with potentially large implications.
I don’t want to overstate the case. Maybe I’m wrong (please reach out to me if you want to discuss in details why you think I am), and the impact of proximity bias is negligible. Or maybe it’s real, but not fixable in practice. But from my personal experience—and from conversations with others outside the core hubs—it feels like there’s something here worth investigating.
EA has built its reputation on doing what works, even when it’s unintuitive or effortful. If we suspect our current filters are systematically excluding certain types of valuable talent, shouldn’t we at least be curious enough to check?
If nothing else, blind hiring would finally spare hiring panels from mispronouncing my very Italian surname.
Appendix - Why this might actually be worth it
Back-of-the-envelope, ±1 order of magnitude.
Say a typical hiring round receives around 100 applications. Implementing a two-step blind process—where the first phase strips identifying information and evaluates anonymized work samples—might add about 3 hours of extra work in total: anonymizing CVs, reviewing short tasks, and matching candidates back to their identities. Assuming a fully loaded staff cost of $100/hour, the added cost per round would be around $300.
Now, suppose that just 1 in 100 applicants—filtered in by this process but who might otherwise have been overlooked due to lack of visibility, proximity, or social capital—turns out to be a genuinely high-impact hire. Let’s conservatively estimate that such a person produces $200,000 more impact (over 3–5 years) than the median hire, whether through better execution, lower coordination costs, or more initiative. That gives an expected benefit of $2,000 per round, for a cost of $300—a benefit-to-cost ratio of almost 7 to 1.
Even under more pessimistic assumptions—say, only 1 in 200 applicants yields such upside, and the marginal impact is just $100,000—the expected benefit is still $500, which exceeds the cost. In fact, the intervention only becomes net-negative if the probability of surfacing a high-impact hire drops below ~0.15% or if the marginal value of such a hire is below $45,000—both of which seem implausibly low given the known variance in individual employee performance.
In short, the upside is asymmetric: even if we surface just one overlooked high-performing candidate every few rounds, the total value gained far exceeds the operational cost. And all of this is testable: a few pilots would be enough to assess whether blind-first screening meaningfully improves talent discovery.
- ^
To be fair I've had some success in the past, by getting a few grants. But getting a grant is a different story compared to getting a job.
- ^
Well, I've been there one afternoon in 2022, but just for lunch
- ^
And I'm planning to do it more myself
- ^
I’m aware that some research already exist on blind hiring. I’ve skimmed a few but haven’t read them carefully enough to cite them responsibly here. If you have links to relevant data or case studies, I’d be grateful.
I've done a lot of partially blind hiring processes both within EA and outside it [1]. And as much as I like them (and feel like I've benefited from them), I think there's good reasons why they aren't done more.
Applied seriously to a software engineer role at a prestigious tech firm and had a final stage interview that far exceeded my abilities, which was painful for everyone involved. Applied on a whim to the Charity Entrepreneurship incubation program and got rejected after the second (third?) stage. Accepted the job offer to my current credentialed non-EA job after two blind stages and a final in-person. Applied seriously to Charity Entrepreneurship Research Training program and got rejected after second stage. Applied as a long shot to a GiveWell Senior Researcher role and got rejected after second stage.
I am sorry that you have to deel with kind of frustration. At Successif we have done double blind work tests for the first round of the hiring interviews for advisor applications and had good results.
On the other hand we recently hired for an operation associate and didn’t do this. I’ve become less excited about written work tests given LLM capabilities and I think work tests can cover only parts of what I’m looking for. I’d rather have people describe what they did before in their application so I can talk with them about the details in the interview.
In this case we hired someone with several years of experience doing the kinds of things we were looking for in a another organization without having been involved in EA. I don’t know how representative that is, but I do nudge organizations to hire for experience before alignment when asked.
I can’t comment on your situation as there is not enough information but if people ask me about operations roles I typically recommend to upskill outside the impact space in organizations which can provide mentorship and good operational procedures - something which is sadly sometimes missing in our space.
In terms of counterfactuals I would suspect that we are sometimes seeing negative values by only hiring within the community and often very small ones for many of the competitive operation positions. For our recent hiring round we received 70 applications in four days before closing the applications. We had many brilliant and purpose driven people apply who were affected by USAID cuts.
So what could you do in addition to upskilling? Volunteer roles can be a great way to get into roles which will never be publicly announced. Similarly networking, doing small scale side projects, being around people in organizations and helping them (for example helping the local or national community) can help to stand out.
Sometimes it can also be the most impactful thing to have a solid career, donate a be the person to help others in the community. Imagine a strong hub of people in Rome* doing impactful work together because you were there to consistently support them and fill the gaps in the local space. This could be awesome.
*I don’t know anything about EA in Rome so only speculating
I'd ask a question here as well. I'm a budding EA, and well, I want to be an effective altruist one day, and I have been following the advice given so far: I am studying Economics and Philosophy; trying to explore various fields, etc. Coming from a fairly humble background, I don’t have the kind of personal connections that many of my peers rely on to secure internships or work opportunities. I’ve been applying to roles, especially in more quantitative or research-based areas, because I want to build relevant skills and gain hands-on experience. But often, I'm turned down due to my lack of experience — which I’m trying to gain in the first place.
So, if you’ve been involved in hiring for EA-aligned roles, I’d really appreciate your thoughts:
How can someone like me break out of this cycle — where I need experience to get opportunities, but need opportunities to gain experience?
(I'm sorry if this sounds like I'm complaining, but this is rather the truth, honestly)
I think SHOW can be a helpful framework.
Hey Ben, thank you so much for responding! I'd be sure to check this out :)
This is a very real issue, and it is a bit of a catch-22. The core of the advice is really to start with little steps.
You need to have experience with projects, employers, or volunteer opportunities. These needs to be good enough that you can describe them on a resume or in a cover letter and they sound decently impressive. They also need to give you stories that you can use to answer questions like "what is the most logistically complex event or project you've been involved in" and "a time when you had to solve a difficult problem." Ideally, these experiences will be at least somewhat relevant to the context/industry of the organization you are applying for, such as if you volunteered for a vegan advocacy organization and later you apply to the Good Food Institute.
Basically, you need to be able to (honestly) appear as an impressive candidate. The details of what 'impressive' means will vary in different contexts: an impressive candidate for event management for existential risk organizations will be different than an impressive candidate for a researcher role focused on animal welfare. But there are general commonalities (clear communication, time management, teamwork, etc.) that exist for almost all roles.
There are also some limited opportunities for building a network if you aren't located in New York, San Francisco, London, or some other city with a good EA network. CEA runs some online programs, I run a couple of book clubs, and many EAG and EAGx conferences offer heavy discounts for people who are students, unemployed, travelling, etc. I think that it isn't as good as living in an EA hub, but there are some options that help a bit. I also perceive a big location-focused bias.
There might also be other skills that could be helpful for professional growth:
Finally, I want to argue that a large number of small steps are more realistic than a small number of big steps. Rather than getting some experience, then getting an impressive job, think of it like an incremental process in which you get a little experience, and then you get a low-quality job, and that job allows you to build your experience a little more, which allows you to get a slightly better job, etc. Here is my sloppy attempt at a visualization from MS Paint.
Hey Joseph, thank you so much for your thoughtful reply. I'm having trouble joining the book club that you host; could you please help me? Moreover, I wanted to ask when you say that I may benefit from taking an online training bootcamp, is there something specific I should look out for, something in the project bit? Thanks again for your guidance! It means a lot :)
I don't think I can help you, because I don't know what sort of a problem or difficulty you are encountering. 😂 This is the link to the Google Doc, which has all of the information: descriptions, links and instructions on how to join, links to lists of books, etc.
The appropriate advice would depend on what your career goals are.
Most online courses (such as through Coursera, EdX, or other platforms) will involve some level of projects, but these will usually be very small and somewhat artificial projects. I suggest that you search for ways to combine the skills you are learning/developing with real world situations. Maybe your sister runs a bakery and you can use your new CSS and HTML skills to make a little website. Maybe you can use the spreadsheet skills for a class project in your Anthropology 101 in college to display the word frequency of a religious text and compare two different translations. So as you do these things, think of two different ideas: 1) am I learning a useful skill, and 2) how will I be able to describe this in a job interview or in a cover letter or in a resume so that it sounds impressive.
Thank you Joseph! I just messaged you a doubt :)
Having done a lot of this advice in my 20s, I'd recommend just getting started with an online training program you find interesting, seems career relevant, and also not too pie-in-the-sky as a near-term plan. Throughout my life, I think there were one or two that felt unusually good or bad all-things-considered. Even then, training programs are short (~6 weeks) and have no stakes if you stop them.
(The exception is if the training somehow includes hands-on training from someone actively trying to progress in one of your desired career paths. Good mentorship is a scarce resource and you should prioritize it above a lot of other things.)
It's dramatically more important what you do after the online training program. It's extremely rare that these programs set people up to to do the "impressive project" that hiring managers want from less prestigious candidates. If they did, everyone would be doing them.
As for the program, if you feel like you're at least passing the course (whatever than means) and it seems promising, then I'd pair that with some informational interviews. You can ask "Hey I've been doing X training course and feel like it might be a good career path. Would you be willing to chat about how you got to where you were?".
That will help you identify directions to take for your "career ladder", which I put in quotes since it's really more of a fog-of-war. Unfortunately, it's usually the things between "Step 1" and "desired job" where steps are the least clear and the most consequential. So I would save your energy for when you get there.
I'm sorry you've had a hard time applying! Your BOTEC misses the costs for candidates, which is also important for EA orgs (eg I appreciate most work tests are paid).
Many jobs get 100+ initial applications. They usually have form questions that take less than 20 minutes to fill in - this is very much by design, as some of the most promising applicants are indeed not full-time job hunting but working, often outside the impact space. On the other hand, the shortest work tests I've had so far were capped at 1h. Assuming 50% of 100 applicants are filtered out at the initial stage, we have wasted 50h of applicant time vs ~17h. (Conservatively not counting the 49 people who will be eliminated later)
Adding: you might be right that the reason is your lack of social proximity. But it could also be that you express yourself suboptimally in the written questions, or your CV doesn't present your skills well enough. One way more proximity to the community could help is by finding someone with hiring experience in the space who can give you feedback. :)