Extras · 1 of 4

A typical day

Start with whether last night's training run finished and whether the numbers moved. Most of the morning is data: finding it, cleaning it, working out why a chunk of it is wrong. Then a code review, a meeting with the product team about what the model is supposed to do, and an argument about how to measure that. Afternoon might be writing an evaluation, or chasing why the deployed model got slower this week. Actual model architecture work is a small slice of the whole thing.