Source.ag · Amsterdam
Every week, a tomato grower tells their buyers how many kilos they’ll deliver three weeks from now. Contracts, trucks, and prices are set on that number. Source builds AI software that greenhouse growers in Europe and North America use for decisions like this, and our Harvest Forecast for tomato, pepper, and cucumber is one of the inputs to that weekly number.
Getting an average week right isn’t the hard part. The value is in the weeks when the crop does something unusual: a heat wave, a sharp drop after a peak, the start and end of the season. Those are the weeks when growers need a forecast most, and when forecasts, ours included, are trusted least.
Why this is hard:
We’re looking for a Staff Data Scientist who has done this before: taken a forecast of a physical system that people didn’t trust, and turned it into a number a business commits money on.
The difficulty isn’t one clever model. It’s the whole system: data quality, how plants are sampled, growers changing their harvest plans, and then the model. There may be ten things to fix before the forecast is good, and only some of them are in the model. You look at the whole system end to end, find the places that matter, do the hardest work yourself, and carry it all the way to something growers use.
This is a senior individual contributor role, technical all the way, with no people management. You report to our Director of Engineering and join our staff engineers, the senior group that works across teams with the CTO and sets the technical bar. Day-to-day, you work with our data scientists, crop scientists, and directly with growers. Harvest forecasting is the first problem. The same kind of problem shows up across our other crop models, and we expect your work to reach those too.
The role is based in Amsterdam, because you can’t see the whole system from a distance. You need to be in the room with the data scientists, the crop scientists and the people who talk to growers every week.