Startup Interviews: OpenReview

Revolutionize peer review.

The impact that the project causes in the scientific community along with the team's enthusiasm.

I think I was very inexperienced for a startup. No company or university really prepared me for OpenReview, so I had to learn a lot. However, it was thanks to the preparation I received at UMass and my previous jobs that taught me how to keep a mind open and learn from my mistakes and peers.

This could be a really long list.

• Because we are in a small team, one mistake has a big impact. In moments like this, being pragmatic can be very useful. Not always do we have the time to think of the optimal solution, sometimes we just need to fix something as soon as possible.
• Continuous learning is essential. New technologies arise all the time, libraries are updated every week and we have to keep up. Sometimes, an implementation made a few months back is no longer optimal and we need to learn how to use the new one.
• Better coding practices. In a small team, a lot of your code will be in production, so having good code is necessary.
• Sharing ideas with others. Sharing ideas and problems with my team has brought the best solutions.

• The things I do are in production.
• Everything moves fast. You don't have to wait months for something to be approved.
• We do not have time for meaningless meetings, so we have none of those.

That it was going to be a lot of fun. I think this is more related to me, but startups usually have a very specific goal in mind and if you believe in that goal, I think you'll have a blast and learn a LOT in the process.