Who Will Thrive in This Role?
You have been the technical anchor on a modelling team before. You’ve owned the hardest problems, set the standards others worked to, and been the person the team turned to when an approach needed a call. You did it hands-on, as a senior IC, not by moving into management, and that’s the path you want to keep on.
You think in interconnected systems. A demand forecast isn’t just a number; it drives how many shifts are opened, how many vans are dispatched and how routes are planned, and it feeds a downstream planning decision and the network’s expansion models. You care about how your models connect to the models around them, and you design their interfaces deliberately.
A deep track record of building and delivering models from ambiguous starting points. You understand the problem, build something useful, validate it against real operations, and iterate. You evaluate models well beyond standard offline metrics, connecting outputs to downstream applications and business KPIs and measuring how improvements translate into operational impact.
Strong Python and SQL, and depth across the full modelling lifecycle - from data extraction and feature engineering through training, validation and production deployment. You’ve worked with time-series forecasting across classical statistical approaches, gradient boosting and deep learning, and you understand the trade-offs well enough to make and defend the choice for a given problem. You’ll be supported by a dedicated ML Engineer, but you set the standard for how the area’s models are built.
At least 8 years in a data science or quantitative modelling role, with clear examples of models you built that informed operational or commercial decisions, and of methodology or technical direction you set for a team. You know a model isn’t done when it trains well; it’s done when it’s running, monitored, and trusted.
You communicate with non-technical stakeholders with authority. The squads that consume the forecasts need to trust them, and that trust comes from explaining what the models do, where they’re reliable, and where they’re not, without hiding behind the maths.
You’re comfortable using AI tools - LLMs, code assistants, and similar - to accelerate your workflow, from exploratory analysis to code generation, and you’re curious about where these tools can augment the modelling process itself.
This role suits someone who wants to see whether their models made a real difference to how the network operates. There is a direct feedback loop between your work and operational outcomes, and as the Staff DS you own the most consequential end of it.
Logistics or delivery network experience is a plus, but what matters more is the ability to learn a complex operational domain quickly and model it well.