Senior Software Engineer, Revenue Recapture

<p><strong>Who we are&nbsp;</strong></p> <p>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 &amp; Jerry’s, KFC, and Eataly trust our software to power their delivery business. We increase sales, reduce order issues, and decrease delivery headaches.&nbsp;</p> <p>&nbsp;</p> <p><strong>What you’ll do</strong></p> <ul> <li>Own and evolve Revenue Recapture—our highest revenue‑producing product. Revenue Recapture is an automated tool designed for restaurants to recover funds lost to third-party delivery platform errors, unwarranted refunds, and chargebacks.</li> <li>Design and build end‑to‑end automation to improve dispute effectiveness and drive toward a fully “no humans in the loop” process—from data ingestion and decisioning to filing, tracking, and resolution.</li> <li>Develop scalable, reliable backend services in Java and build intuitive, maintainable front‑end experiences that surface dispute status, outcomes, and insights.</li> <li>Increase automation and win rates through experimentation and define and track success metrics.</li> <li>Ensure reliability and quality via sound architecture, automated testing, observability, and a focus on high service uptime and resilience.</li> <li>Collaborate with Product, Data, Operations, and Support to incorporate customer feedback and turn insights into product and engineering improvements.</li> </ul> <p>&nbsp;</p> <p><strong>What we’re looking for</strong></p> <ul> <li>A customer‑obsessed engineer who optimizes for the best outcomes for restaurant owners and measures impact by real results (e.g., dollars recovered, issues prevented).</li> <li>Someone who demonstrates radical ownership—taking accountability from design through long‑term support—and continuously improves systems and processes.</li> <li>An engineer who can context‑switch quickly, handle ambiguity, and deliver in a fast‑moving environment with evolving priorities.</li> <li>Strong backend experience in Java building reliable, distributed systems and integrations, with the ability to work across the stack, including front‑end development.</li> <li>A clear, concise communicator who can explain ideas, trade‑offs, and plans to both technical and non‑technical audiences; strong at writing design docs.</li> <li>Independent and self‑directed, capable of prioritizing and delivering with minimal supervision while