|June 20th, 2017|
|giving, work, switching_jobs|
I was laid off from Wave yesterday: they've decided that having engineers build a mobile money system in East Africa while living in the US has a lot of drawbacks, and I (and my family) aren't up for moving to Africa. So now I need to figure out what I should do next.
I'm looking at this from primarily an EA perspective: for each of my options, how much better will the world be than if I didn't do it?
First, some constraints:
I probably need to earn some money: Julia works at a non-profit and doesn't earn enough for us to live on alone. We could maybe reduce our expenses to where we could live on her salary, but that would be challenging with housing and childcare.
I want to stay in Boston: I really like it here. My relatives live here, my friends are here, I have roots in several different communities here. And the same with Julia.
I don't want to work all the time. I want to spend time with my kids, and have time for music other things that matter to me. Something like 45hr/week would be good.
I want to work in the same place as coworkers. I don't enjoy remote work very much: I get lonely and feel disconnected. I waited to join Wave until there were three other engineers working from Boston (who were interested in coworking).
My default here would be going back to earning to give as a programmer. I liked Google a lot and would be happy to go back there, though I if I'm considering going that direction I should also interview at some competitors to see if someone would pay me more or have work that was better in some respect. It looks like there are openings at Google, Facebook, Amazon, and Microsoft here; are there others I should be thinking about?
On the other hand, earning to give may not be my best option. The EA movement as a whole has been moving away from seeing the main bottleneck being funding to seeing it as being talent, as more money has become available (summary). What else might make sense?
Starting some sort of organization: people who can organize and run things independently are in relatively short supply, and this is something I'm pretty good at. The main downside of this is that running things involves a lot the aspects of jobs that I like less: more exposure to uncertainty, more hassle, hard to limit hours.
Working in AI: over the past couple years many people I respect have moved to thinking of AI risk as the most valuable place to focus EA efforts. I'm less convinced, but I should put more time into learning about it. If I did think this was the direction to go, options include trying to get a machine-learning related software engineering role (ex: this Amazon role, for a combination of earning to give and working in ML), or working on a PhD (MIT and Harvard are options here).
Working in Biotech: biotech is a strong industry here (Boston), and there might be something there that's a good fit? Maybe some sort of safety-related influencing? On the other hand my expectation is that as a software engineer I'd primarily be there to support bio PhDs, and any views I had on safety etc wouldn't get much consideration.
Working for an EA organization: CEA is looking for a full-stack developer, though working at the same organization as my spouse is probably not a good idea. Pretty much any EA organization role is likely to be remote work if I'm living in Boston, which I'm not keen on.
Something else: there are an enormous number of things I could be doing, and I'm probably not thinking of all of them. What else should I look into?
Update 2017-07-03: for the next few weeks I'm planning to work on understanding why there are such different views on superintelligence risk.
Update 2017-08-17: I'm going back
More Posts: Older Post: Newer Post: