You should be hiring scientists who straddle the line between software and bio, care about the quality of their code, and inspire good code, data and communication.

This cheat sheet provides you with the questions you should ask any scientist you interview, and what to look for in their answers.

You should equip your team with the resources to build software and data practices that allow you to outcompete others. This means establishing responsibilities, communicating priorities, and setting metrics to measure how well you're doing.
‍
This cheat sheet provides you with the questions you should be regularly asking your team.‍