Executive summary: In this personal reflection, the author shares how they transitioned from software engineering to an impactful AI policy operations role within just three months, arguing that entry into the field is more accessible than commonly believed—especially for proactive individuals willing to leverage community connections, volunteer experience, and financial flexibility.
Key points:
Surprisingly quick career switch: The author expected to need years to break into AI safety but instead secured a job in international AI policy operations within three months of leaving software engineering.
Nature of the job: Their role involved logistical and project management work for high-level AI policy events, where AI safety knowledge was primarily useful during initial planning.
Path to getting hired: Volunteering at CeSIA led to a personal referral for the role, which was pivotal; being embedded in a local EA/AI safety community also opened up opportunities.
Key enabling factors: Unique fit for the role (e.g., fluent in French, available on short notice), financial flexibility, and prior freelance experience made it easier to accept and succeed in the position.
Lessons learned: The author emphasizes the difficulty of learning on the job without mentorship and recommends future job-seekers seek structured guidance when entering new domains.
Encouragement and offer to help: They invite others interested in AI safety to reach out for career advice and signal openness to future opportunities building on their recent experience.
This comment was auto-generated by the EA Forum Team. Feel free to point out issues with this summary by replying to the comment, and contact us if you have feedback.
Executive summary: In this personal reflection, the author shares how they transitioned from software engineering to an impactful AI policy operations role within just three months, arguing that entry into the field is more accessible than commonly believed—especially for proactive individuals willing to leverage community connections, volunteer experience, and financial flexibility.
Key points:
Surprisingly quick career switch: The author expected to need years to break into AI safety but instead secured a job in international AI policy operations within three months of leaving software engineering.
Nature of the job: Their role involved logistical and project management work for high-level AI policy events, where AI safety knowledge was primarily useful during initial planning.
Path to getting hired: Volunteering at CeSIA led to a personal referral for the role, which was pivotal; being embedded in a local EA/AI safety community also opened up opportunities.
Key enabling factors: Unique fit for the role (e.g., fluent in French, available on short notice), financial flexibility, and prior freelance experience made it easier to accept and succeed in the position.
Lessons learned: The author emphasizes the difficulty of learning on the job without mentorship and recommends future job-seekers seek structured guidance when entering new domains.
Encouragement and offer to help: They invite others interested in AI safety to reach out for career advice and signal openness to future opportunities building on their recent experience.
This comment was auto-generated by the EA Forum Team. Feel free to point out issues with this summary by replying to the comment, and contact us if you have feedback.