The bigger problem here is treating a research problem as if it was a product problem. In 2025, no one knew what an automated alignment researcher should look like, and at that point it’s very counterproductive to spend time on product concerns like accounts, cloud infra, frontend/backend, etc. You need to start a research project by finding experiments which could get meaningful results quickly, and sprinting towards those results. I’m basically repeating what Ethan Perez said here. I actually also worked on automated alignment research in this same period (I made RE-Bench) and I tried making a multi agent product for 1 month in early 2025 before realizing that it (making the product too soon) was a bad idea
The bigger problem here is treating a research problem as if it was a product problem. In 2025, no one knew what an automated alignment researcher should look like, and at that point it’s very counterproductive to spend time on product concerns like accounts, cloud infra, frontend/backend, etc. You need to start a research project by finding experiments which could get meaningful results quickly, and sprinting towards those results. I’m basically repeating what Ethan Perez said here. I actually also worked on automated alignment research in this same period (I made RE-Bench) and I tried making a multi agent product for 1 month in early 2025 before realizing that it (making the product too soon) was a bad idea