Hover over a name to see the position and date range. This table only
includes positions where at least the start date is known. The positions count
can count the same person multiple times if they held different positions.
For each year, a person is included if they were at the organization for any
part of the year; this means the actual staff count at any point during
the year can be lower.
Number of full-time staff at the beginning each year
The following table lists some dates and people who were at the organization
on the given date (namely, the start of the year). The table may not list every
person who worked for the organization (e.g. they could have joined and left in
the middle of a single year). This table excludes associates, interns,
advisors, and board members.
This table shows the full change history of positions. Each row corresponds
to at least one addition or removal of a position. Additions are in green and
subtractions are in red. If a position name changed,
it is listed simultaneously as an addition (of the new name) and removal (of
the old name) and colored yellow. Additionally there are faded variants of each
color for visited links.
A community blog about rationality, decision theory, AI, the rationality community, and other topics relevant to AI safety. This is a re-launch/modernization of the original LessWrong. For the launch date, the date of the welcome post  is used.
Jim Babcock, the fourth person to join LessWrong 2.0 (after Oliver Habryka, Ben Pace, and Raymond Arnold) describes why, after initially looking for a while for more developers to join the organization, they ultimately decided not to hire for now unless they found an exceptional candidate. The comment is in response to a post "Simultaneous Shortage and Oversupply" by Jeff Kaufman, noting that a lot of people are interested in applying to organizations related to effective altruism, but the organizations still take a long time to fill their job postings
Announcement that LessWrong 2.0 is looking for somebody to fill a Chief Technology Officer (CTO) role. Criteria are experience as a programmer and excitement about the long-term vision. The salary range is $70,000 to $120,000, though higher salaries are possible. The post and comments also reveal that the current employees are Oliver Habryka, Raymond Arnold, and Ben Pace, and they all make $60,000 a year. Comments also reiterate previously documented funding sources: Berkeley Existential Risk Initiative, EA Grants, and individual donors such as Eric Rogstad