This is a special post for quick takes by a guy named josh. Only they can create top-level comments. Comments here also appear on the Quick Takes page and All Posts page.
Sorted by Click to highlight new quick takes since:

I tried doing this a while back. Some things I think I worried about at the time:

(1) disheartening people excessively by sending them scores that seem very low/brutal, especially if you use an unusual scoring methodology (2) causing yourself more time costs than it seems like at first, because (a) you find yourself needing to add caveats or manually hide some info to make it less disheartening to people, (b) people ask you follow-up questions (3) exposing yourself to some sort of unknown legal risk by saying something not-legally-defensible about the candidate or your decision-making.

(1) turned out to be pretty justified I think, e.g. at least one person expressing upset/dissatisfaction at being told this info. (2) definitely happened too, although maybe not all that many hours in the grand scheme of things (3) we didn't get sued but who knows how much we increased the risk by

Jamie, I've been contemplating writing up a couple of informal "case study"-type reports of different hiring practices. My intention/thought process would be to allow EA orgs to learn about how several different orgs do hiring, to highlight some best practices, and generally to allow/encourage organizations to improve their methods. How would you feel about writing up a summary or having a call with me to allow me to understand how you tried giving feedback and what specific aspects caused challenges?

Unfortunately this was quite a while ago at the last org I worked at; I don't have access to the  relevant spreadsheets, email chains etc anymore and my memory is not the best, so I don't expect to be able to add much beyond what I wrote in the comment above. 

Regarding "disheartening people," I once got feedback for a hiring round and the organization shared what scores I got, and even shared scoring info for the other (anonymized) candidates. It was the best and most accurate data I have ever been given as feedback.

I scored very low, much lower than I had expected. Of course I felt sad and frustrated. I wish that I knew more details about their scoring methodology, and part of me says that it was  an unfair process because they weren't clear on what I would be evaluated on. But I draw a analogies to getting rejected from anything else (such as a school application or a romantic partner): it sucks, but you get over it eventually. I felt bad for a day or two, and then the feelings of frustration faded away.

(I run hiring rounds with ~100-1000 applicants) agree with Jamie here. However, if someone was close to a cutoff, I do specifically include "encourage you to apply to future roles" in my rejection email. I also always respond when somebody asks for feedback proactively.

Is revealing scores useful to candidates for some other reason not covered by that? It seems to me the primary reason (since it sounds like you aren't asking for qualitative feedback to also be provided) would be to inform candidates as to whether applying for future similar roles is worth the effort.

revealing scores useful to candidates for some other reason not covered by that

Honestly, I hadn't even thought of encouraging them to apply for future roles. My main thought regarding feedback is to allow them to improve. If you assess my work and then tell me the ways in which it falls short, that allows me to improve. I know that to work on. An example would be something like "Although your project plan covered a lot of the areas we requested, you didn't explain your reasoning for the assumption you made. You estimated that a [THING] would cost $[AMOUNT], but as the reader I don't know where you got that number. If you had been transparent about your reasoning, then you would have scored a bit higher." or "We were looking for something more detailed, and your proposal was fairly vague. It lacked  many of the specifics that we had requested in the prompt."

Quantitative scoring doesn't really give you that, though!

I suppose I'm skeptical that quant scores in an auto-sent email will actually give you a nuanced sense - but I do see how, e.g., if over time you realize it's always your interview or always your quant question that scores poorly, that is a good signal

I do think being kind is an underrated part of hiring!

Have also tried this, although most our applicants aren't EAs. People who reapply given detailed feedback usually don't hit the bar.

We still do it, in part because we think it's good for the applicants, and in part because people who make a huge improvement attempt 2 usually make strong long-term hires

That actually seems like a really strong signal of something important: can people improve, if given a modest amount of guidance/support. I'd certainly be interested in hiring someone who does rather than someone who doesn't.

But I'm also impressed that you provide feedback to candidates consistently. I've always thought that it would be something fairly time-consuming, even if you set up a system to provide feedback in a fairly standardized way. Would you be willing to share a bit about how you/your team does feedback for rejected job applicants?

I view our hiring process as a constant work in progress, and we look back at the application process of everyone after their time with us, the best and worst performers alike, and try figure out how we could have told ahead of time. Part of that is writing up notes. We use chatgpt to make the notes more sensitive and send them to the applicant. 

Caveat: We only do this for people who show some promise of future admission. 

Curated and popular this week
 ·  · 6m read
 · 
I am writing this to reflect on my experience interning with the Fish Welfare Initiative, and to provide my thoughts on why more students looking to build EA experience should do something similar.  Back in October, I cold-emailed the Fish Welfare Initiative (FWI) with my resume and a short cover letter expressing interest in an unpaid in-person internship in the summer of 2025. I figured I had a better chance of getting an internship by building my own door than competing with hundreds of others to squeeze through an existing door, and the opportunity to travel to India carried strong appeal. Haven, the Executive Director of FWI, set up a call with me that mostly consisted of him listing all the challenges of living in rural India — 110° F temperatures, electricity outages, lack of entertainment… When I didn’t seem deterred, he offered me an internship.  I stayed with FWI for one month. By rotating through the different teams, I completed a wide range of tasks:  * Made ~20 visits to fish farms * Wrote a recommendation on next steps for FWI’s stunning project * Conducted data analysis in Python on the efficacy of the Alliance for Responsible Aquaculture’s corrective actions * Received training in water quality testing methods * Created charts in Tableau for a webinar presentation * Brainstormed and implemented office improvements  I wasn’t able to drive myself around in India, so I rode on the back of a coworker’s motorbike to commute. FWI provided me with my own bedroom in a company-owned flat. Sometimes Haven and I would cook together at the residence, talking for hours over a chopping board and our metal plates about war, family, or effective altruism. Other times I would eat at restaurants or street food booths with my Indian coworkers. Excluding flights, I spent less than $100 USD in total. I covered all costs, including international transportation, through the Summer in South Asia Fellowship, which provides funding for University of Michigan under
 ·  · 7m read
 · 
My new book, Altruismo racional, is now on presale. It is my attempt at presenting a compelling case for a particular strand of "classical EA"[1]: one that emphasizes caring deeply about global health and poverty, a rational approach to giving, the importance of cost-effectiveness, and the 🔸10% Pledge. In this post, I provide some context on my reasons for writing this book and what I hope to achieve. If “new EA-themed book in Spanish” was all you needed to know, feel free to skip to How you can help or preorder now. Why write a book Imagine you wake up one morning and discover the world has changed in a few peculiar ways. There has been no 10th anniversary edition of Peter Singer's The Life You Can Save—it was last edited more than a decade ago and has been out of print for years. Will MacAskill has not written Doing Good Better nor any of his pieces for The Guardian. And that’s not all. You ask around about EA and get mostly confused looks. Someone mentions a blog called “Codice Stellare Something” that later changed its name. You look it up but it's written in some foreign language that's hard to understand. “Toby who?” He seems to be associated with something called Geben Was Wir Können that you cannot pronounce, let alone remember. Welcome to Spain—or, I dare say, the Spanish-speaking world—where language friction[2] curbs the potential of most of the ways people first hear about EA. This is true for many other topics, of course. In Spain, people usually don't hear directly from those doing cutting-edge work in the English-speaking world, but rather from local explainers or commentators. Top non-fiction books like Sapiens or Antifragile are read, overwhelmingly, in translation. I have been close to some attempts to translate key EA-themed books into Spanish. The problem? Publishers are quite uninterested because only a handful of English-speaking public intellectuals have the global name recognition to guarantee sales. The Scout Mindset and What We Owe T
 ·  · 3m read
 · 
Summary * 🤰🏽 A randomized study in Kenya found that giving families a $1,000 GiveDirectly cash transfer immediately cut infant deaths by 48%. → * 🏥 Deaths dropped most for mothers living near physician-staffed health facilities and those who received cash in the weeks before they gave birth. → * 🩺 GiveDirectly is launching a new program to maximize these life-saving impacts, partnering with a Kenyan community health provider to get cash to more expectant mothers. → ---------------------------------------- In rural Kenya, giving poor families a one-time $1,000 transfer cut infant deaths nearly in half, one of the largest reductions ever recorded for a poverty program. With global aid budgets shrinking and funders under pressure to do more with less, the findings point to cash as a powerful, underused tool to reduce preventable deaths. Cash cut infant deaths by 48% The study, led by researchers at UC Berkeley and Oxford, tracked over 100,000 births and found that infant mortality fell by 48% in the years families received a one-time $1,000 transfer from GiveDirectly. It’s a striking result, reinforcing what decades of research have already shown: poverty itself is one of the biggest risk factors for a child’s survival. As the researchers note, “infant and child mortality appears highly sensitive to economic conditions.” Cash saved lives by helping new moms rest, eat, and deliver safely The biggest gains were among newborns: deaths within the first 30 days of a baby’s life fell by 63%, with drops in maternal and newborn causes of death accounting for more than half of the overall decline in infant deaths.  This drop was driven by a 45% increase in hospital deliveries and a 51% drop in work (often physically strenuous) during the third trimester and postpartum. Less work in late pregnancy coincided with fewer deaths from complications at birth.  When mothers have cash, they get care, proving that sometimes, the best way to save a child’s life is to simp