Incidentally, ‘flipping non-EA jobs into EA jobs’ and ‘creating EA jobs’ both seem much more impactful than ‘taking EA jobs’. That could be e.g. taking an academic position that otherwise wouldn’t have been doing much and using it to do awesome research / outreach that others can build on, or starting an EA-aligned org with funding from non-EA sources, like VCs.

(excerpt from https://lydianottingham.substack.com/p/a-rapid-response-to-celeste-re-e2g) 

alignment is a conversation between developers and the broader field. all domains are conversations between decision-makers and everyone else:

“here are important considerations you might not have been taking into account. here is a normative prescription for you.”

“thanks — i had been considering that to 𝜀 extent. i will {implement it because x / not implement it because y / implement z instead}."

these are the two roles i perceive. how does one train oneself to be the best at either? sometimes, conversations at eag center around ‘how to get a job’, whereas i feel they ought to center around ‘how to make oneself significantly better than the second-best candidate’.