(click "see more")
Link to my coaching post.
(apparently I'm doing some of this?)
I'm not sure how to answer this so I'll give it a shot and tell me if I'm off:
Because usually they take more time, and are usually less effective at getting someone hired, than:
- Do an online course
- Write 2-3 good side projects
For example, in Israel pre-covid, having a CS degree (which wasn't outstanding) was mostly not enough to get interviews, but 2-3 good side projects were, and the standard advice for people who finished degrees was to go do 2-3 good side projects. (based on an org that did a lot of this and hopefully I'm representing correctly).
There is more that I can say about this, but I'm not sure I'm even answering the question.
Also note that the main point of this post is to recommend people do side projects, as opposed to recommending they don't get a CS degree. Maybe another point is "don't try to learn all the topics you heard about before you apply to any job", which is also important.
My own intuition on what to do with this situation - is to stop trying to change your reputation using disclaimers.
There's a lot of value in having a job board with high impact job recommendations. One of the challenging parts is getting a critical mass of people looking at your job board, and you already have that.
Hey Conor!
Regarding
we don’t conceptualize the board as endorsing organisations.
And
contribute to solving our top problems or build career capital to do so
It seems like EAs expect the 80k job board to suggest high impact roles, and this has been a misunderstanding for a long time (consider looking at that post if you haven't). The disclaimers were always there, but EAs (including myself) still regularly looked at the 80k job board as a concrete path to impact.
I don't have time for a long comment, just wanted to say I think this matters.
Paul Graham agrees that building something you're excited about is a top way to get good at technology:
Paul Graham about getting good at technology (bold is mine):
How do you get good at technology? And how do you choose which technology to get good at? Both of those questions turn out to have the same answer: work on your own projects. Don't try to guess whether gene editing or LLMs or rockets will turn out to be the most valuable technology to know about. No one can predict that. Just work on whatever interests you the most. You'll work much harder on something you're interested in than something you're doing because you think you're supposed to.
If you're not sure what technology to get good at, get good at programming. That has been the source of the median startup for the last 30 years, and this is probably not going to change in the next 10.
From "HOW TO START GOOGLE", March 2024. It's a talk for ~15 year olds, and it has more about "how to get good at technology" in it.
Linking to Zvi's review of the podcast:
https://thezvi.wordpress.com/2024/04/15/monthly-roundup-17-april-2024/
Search for:
Will MaCaskill went on the Sam Harris podcast
It's a negative review, but opinions are Zvi's, I didn't hear the podcast myself.
do you have a rough guess at what % this is a deal breaker for?
It's less of "%" and more of "who will this intimidate".
Many of your top candidates will (1) currently be working somewhere, and (2) will look at many EA aligned jobs, and if many of them require a work trial then that could be a problem.
(I just hired someone who was working full time, and I assume if we required a work trial then he just wouldn't be able to do it without quitting)
Easy ways to make this better:
Also, some candidates will WANT a work trial to see how the job actually is. I asked for a work trial in my current job.
Also, CEA does work trials. You could ask them how it goes. (But they won't hear about people who didn't even apply, I guess)
Any idea if these capabilities were made public or, for example, only used for private METR evals?