Check out this video to see what we’re all about:
https://www.instagram.com/p/DayEOOsRlSG/
Magic (makers of Loyalist) · New York, NY · In-office 4 days/week · $150k-$200k + equity
Hi! I’m Niky, a founding engineer. Before joining Magic, I was working at a clinical data AI startup while reading every hospitality book I could find. The half-formed product in my head turned out to already exist: Magic, which Maggie was building. Exhilarated, I jumped at the opportunity. A year down the line, we’re yet again looking for a foundational piece of our team (…you?)
Loyalist is the operating system that powers how our favorite restaurants remember you.
We ingest live data from ~30 third-party systems during service (reservations, POS, reviews, private events, marketing, e-commerce). We turn that data into guest profiles and automated actions: a server hands a VIP a comped glass of wine because the system flagged that she’s been posting five-star reviews over the last year. A marketing manager sends a happy-birthday offer to 2,000 guests at once, each message referencing the specific dish that guest ordered last time. A sommelier gets a heads-up that a two-top walking in tonight are repeat 2018 Barolo drinkers. We’re also actively moving beyond restaurants into the full span of hospitality: hotels, casinos, spas, and more, so that Loyalist becomes a full‑fledged system for hospitality service everywhere.
800+ restaurants run on Loyalist today, from neighborhood favorites to Carbone, Momofuku, Le Bernardin, and Daniel Boulud’s group. Some of the biggest have 5-10 million guests each and hundreds of millions of visits and orders going back 15 years, and we process more than 10 million guest interactions every year.
You’d be a fullstack engineer shipping end-to-end features for restaurants. Engineers own the full arc here: talking to the customer, scoping the work, and shipping it.
An example feature I shipped recently is Journeys, our system for designing multi-step guest experiences across multiple venues and integrations. Operators define what should happen across a guest’s lifecycle (welcome, post-visit, lapsed-regular, anniversary), and Loyalist orchestrates it across reservations, POS, marketing, and reviews.
The biggest strategic direction right now is moving onboarding from engineer-led to operator-led. We’ve historically configured each customer’s Loyalist instance by hand (which is how I learned the industry). We want operators to drive most of that themselves. That’s a lot of UI work with real consequences, and much of it is what you’d be working on.
You’ll probably do well if:
You probably won’t thrive here if you want direction to come from above. Here it comes from you and the customer, and the failures of last Saturday's dinner service. Also if you’re not curious about restaurants, hospitality, or the physical-world data layer.