| Basically ran a macro to adjust how far restaurants would deliver by time of day / day of week. The goal was to balance supply and demand of restaurants and orders. Eats product didn't have any demand shifting levers at that time yet restaurants were getting blown up with demand at peak times (ex. top pizza restos at 7pm on a Friday). The product did however allow ops teams to manually set a delivery radius for a given restaurant. Clever ops teams scripted shrinking / expanding this delivery radius to encourage demand at non-peak times and reduce it during period where restaurants were overloaded and likely to ignore / cancel orders. This laptop ran scripts for all cities in Canada to adjust delivery radii for each restaurant until a few different levers were built into product. Ian (who is a _super nice_ guy) owned this process which kept things working smoothly while Eats was experiencing explosive growth. Another fun fact - Eats Marketplace, which is the current Eats you see today, was built and launched in Toronto - SF engineers / product / design supported by Toronto ops teams. Quickly eclipsed the Instant Eats product which was the 3rd (and most successful to date) try by Uber at food delivery. |