Owner Staff Software Engineer at Owner responsible for owning and evolving the Orders Platform core system for independent restaurants. Works on event-sourced data storage, data reconciliation, and Kotlin Multiplatform code distribution.
Responsibilities
Owner is the leading all-in-one platform for independent restaurants. Orders Platform is the system that takes, tracks, and settles every order a restaurant handles with the upmost reliability (even through internet outages).
We're looking for a Staff Engineer to help own and evolve the core of that platform as we scale to more and more restaurants. You'll work on problems that look very different from a traditional backend role: event-sourced data storage, data reconciliation, cost-effective observability, code distribution across thousands of devices via Kotlin Multiplatform, and restaurant workflows that must behave correctly even when part of the system disappears halfway through an operation.
This is a high-ownership, hands-on role. You'll be a technical anchor for the Orders Platform team, setting platform direction, raising the bar on correctness, and helping the team move fast on a system restaurants depend on every day.
Why we’re looking for you
Orders are the heartbeat of a restaurant. Our tier zero platform is built on patterns such as event sourcing and conflict-free replicated data types (CRDTs) to support an offline-first point of sale and ordering via Owner’s online and white-labeled app experiences. It relies on a small group of people, with high agency, who understand those patterns deeply.
We need another Staff-level engineer who can reason about this kind of system quickly, share the architectural load with the rest of the team, and make the platform more resilient as the team and the business grow.
Core patterns: Event sourcing, Fog/cloud distribution (we run a version of our server code in every restaurant on a point of sale device), caching of critical data to support offline mode, app distribution, and device configuration.
Act as an architect within the Orders Platform team, setting technical direction for how orders are modeled, stored, replicated, and reconciled
Design and build event-sourced and replicated-state systems that stay correct under retries, network partitions, concurrent edits, and partial failure
Qualification
Required experienceHands-on experience with event sourcingExperience with idempotencyClear written and verbal communicationCustomer Obsession & Empathy
Required
Required experience
Hands-on experience with event sourcing, CRDTs, or comparable approaches to replicated and offline-first data (for example, sync engines or conflict resolution layers)
Experience with idempotency, optimistic concurrency, event replay, projections, and reconciliation
Comfort reasoning about "what happens if this node disappears halfway through the operation?" and designing for it
Ability to pick up a specialized technology quickly and make it more robust
Staff-level experience leading technical direction without losing touch with the code
Clear written and verbal communication, and a habit of making complex systems easier for others to understand
Payments and ordering backend experience preferred
Backend experience in payment or ordering systems
Ability to partner with our payments and reporting team while owning the order side of money-moving flows
Customer Obsession & Empathy
Being unafraid to work directly with restaurants to solve their needs (including in person visits, phone/text communication, and more).
