Turning research into a product is a separate job at Sakana AI, and the lab has now published who does it and how they are hired.
Sakana AI published an FAQ-style look inside the product team that carries its research into shipped software. It describes two roles: the Applied Research Engineer, who turns a result into something that runs, and the Software Engineer, who builds that into a product. For each it walks through a typical day, how the team is organised, how hiring proceeds, and what the company looks for. The account is drawn from interviews with current members, and it notes that the team works without a block of hours when everyone is required to be present.
The striking part is the split itself. Making a model better and making it usable are treated as two jobs with two titles and two different days, rather than as one role a researcher gradually grows into. Read as an org chart, it suggests that whether a lab ships depends less on model quality than on who carries the translation, and how. What the piece does not show is the consequence: it describes the structure that exists now, not what that structure has produced.
Which of the two roles the open positions actually fill first. The count that settles this is not papers, but products that reach users.