About the role
Who we are In the past, to be a successful restaurateur, you simply had to have a passion for food and a passion for people - but to succeed as a digital restaurateur you also need to have a passion for technology. We believe in the joy of serving others, and that's why we created Otter – to help restaurateurs succeed in online food delivery. Restaurants around the world, both large and small, including Chick-fil-A, Ben & Jerry’s, KFC, and Eataly trust our software to power their delivery business. We increase sales, reduce order issues, and decrease delivery headaches.
What you'll do As Product Manager for the Orders domain, you own the system of record for every order that flows through Otter in real time and over time. Your goal is to review a fragmented landscape of third-party delivery platforms, multiple POS systems, kitchen printers, and downstream analytics consumers as it relates to Orders domain and turn it into a dependable, structured order data layer that every team in the company builds on. You will: Own the order state machine: Define and maintain the canonical order lifecycle from ingestion through acknowledgment, in-preparation, modification, completion, and cancellation including the edge cases that may happen hundreds of times per day: late cancellations after food is made, partial fulfillments, mid-rush item voids, delivery platform state conflicts etc Build a reliable multi-platform ingestion layer: Lead the strategy for normalizing order events from DoorDash, Uber Eats, Grubhub, Google, and first-party channels into a single structured order schema, accounting for the fact that each partner has a different webhook format, retry model, cancellation API, and SLA and changes them unilaterally Drive POS integration quality: Own the
requirements for order injection across POS partners such as Toast, Square, NCR etc understanding that each has a different injection model, menu mapping dependency, and failure acknowledgment signal Own post-creation mutation flows: Build logic that handles order modifications, cancellations, and item-level updates after an order is already in flight coordinating changes across the POS, print layer, delivery platform, and reporting in real time without creating duplicate orders, ghost tickets, or reconciliation gaps Improvise order data contract: Own the canonical order schema and the SLAs that govern it such as ingestion latency, delivery completeness, time-to-BI-visibility etc and make explicit prioritization calls when multiple opportunities conflict with each other Set the reliability metrics: Instrument the platform around missed order rate, duplicate order rate, p99 ingestion latency, kitchen acknowledgment SLA, and end-of-day report completeness and hold