Python & Fellowship Tests Repost from blog (I’d appreciate any feedback)
This Autumn has been a bit of a mix of continuing with Arena, being sick, and applying for half a dozen fellowships and courses.
Claude and Astra’s fellowships both required code signal’s industry coding assessments. I did a week of preparation for both of them before taking the test but did a lot worse than I thought I would. Being relatively new to Python and not being able to code at high speed without making mistakes was my downfall with these. I’m generally not great at thinking fast be it coding or chess.
I did enjoy practising Python. It’s very valuable given most the career switches I’m considering use it. It was refreshing to see this kind of test instead of algorithm and data structure tests, which I feel involve revising something you’re not going to need for the job. I created some mock practice tests using LLMs that were excellent preparation for the real deal. I’ve also picked up some Anki flashcards for the most common Python functions, which should come in handy for next time.
I also did tests that involved writing essays about papers for Cooperative AI Research fellowship, MARS, LASR, Deepmind, ERA, and the 2nd stage of Astra. With the exception of the ERA test (really interesting paper on LLM coding capabilities), I didn’t enjoy these. But they were probably valuable for fit testing; if I’m not enjoying reading papers and writing about them, AI safety research probably isn’t going to be my cup of tea.
I’ve decided, for the time being, to stop applying for new fellowships. Joining a fellowship would be a great fit test in itself, but it’s quite a large time commitment, especially when you include the x number of applications you’ll need before getting accepted to one. I have limited time to do fit tests this year, so my priority now that I’m getting a sense that pure research isn’t my thing, is to focus on finishing ARENA, start to explore career paths other than AI safety, and contribute to more open-source projects. I need to be careful not to use up all my time doing applications rather than getting my hands dirty with projects that will give a much better indication of my fit for a given career path.
Python & Fellowship Tests
Repost from blog (I’d appreciate any feedback)
This Autumn has been a bit of a mix of continuing with Arena, being sick, and applying for half a dozen fellowships and courses.
Claude and Astra’s fellowships both required code signal’s industry coding assessments. I did a week of preparation for both of them before taking the test but did a lot worse than I thought I would. Being relatively new to Python and not being able to code at high speed without making mistakes was my downfall with these. I’m generally not great at thinking fast be it coding or chess.
I did enjoy practising Python. It’s very valuable given most the career switches I’m considering use it. It was refreshing to see this kind of test instead of algorithm and data structure tests, which I feel involve revising something you’re not going to need for the job. I created some mock practice tests using LLMs that were excellent preparation for the real deal. I’ve also picked up some Anki flashcards for the most common Python functions, which should come in handy for next time.
I also did tests that involved writing essays about papers for Cooperative AI Research fellowship, MARS, LASR, Deepmind, ERA, and the 2nd stage of Astra. With the exception of the ERA test (really interesting paper on LLM coding capabilities), I didn’t enjoy these. But they were probably valuable for fit testing; if I’m not enjoying reading papers and writing about them, AI safety research probably isn’t going to be my cup of tea.
I’ve decided, for the time being, to stop applying for new fellowships. Joining a fellowship would be a great fit test in itself, but it’s quite a large time commitment, especially when you include the x number of applications you’ll need before getting accepted to one. I have limited time to do fit tests this year, so my priority now that I’m getting a sense that pure research isn’t my thing, is to focus on finishing ARENA, start to explore career paths other than AI safety, and contribute to more open-source projects. I need to be careful not to use up all my time doing applications rather than getting my hands dirty with projects that will give a much better indication of my fit for a given career path.