Overview
Feast connects customers with vetted personal chefs who prepare fresh meals in the customer’s kitchen — weekly meal prep, special dinners, and menus designed around dietary or medical needs. Feast: Chef Experiences is the customer app; Feast Chef is the chef app; eatwithfeast.com is the public site.
Problem
Hiring a personal chef is high-friction: finding someone trusted, agreeing on a menu, buying groceries, and coordinating payments. Chefs spend that same energy on admin instead of cooking.
My role
Senior Software Engineer at Feast (2025 – Present). Engineering the two-sided Feast product: Feast Customer and Feast Chef on iOS, plus the eatwithfeast.com marketing site. Shipping live App Store listings for both sides of the marketplace so customers can book and chefs can run a personal-chef practice from one pair of apps.
Technical approach
The product is a pair of iOS apps plus a marketing site. The customer side covers booking, menu customization, messaging, and meal-prep flows. The chef side covers weekly bookings, earnings, and grocery logistics so chefs can focus on cooking.
Architecture
- Customer surface: Feast: Chef Experiences on the App Store
- Chef surface: Feast Chef on the App Store
- Public site: eatwithfeast.com
Technology stack
Key features
- Customer app for booking chefs, customizing menus, and in-home meal prep
- Chef app for weekly bookings, earnings, menus, and grocery logistics
- In-app messaging between customers and chefs
- Menus designed around dietary and medical needs
Challenges
Two-sided booking
Customers need a trusted way to book in-home cooking; chefs need a way to run recurring work without assembling schedule, menu, groceries, and payments by hand.
Keeping logistics off the cook
Grocery handling, scheduling, and chat have to live in the product so the in-home meal is the thing people show up for — not the admin around it.
Solutions
Separate apps for each side
Feast Customer is the booking and menu surface. Feast Chef is the operations surface. The website introduces the service and sends people into the iOS apps.
In-home cooking as the product
The documented flows are chef booking, customized menus, dietary needs, messaging, meal prep, earnings, and grocery logistics — not a generic food-delivery marketplace.
Outcome
Feast is live at eatwithfeast.com, with Feast: Chef Experiences and Feast Chef on the App Store — a two-sided product for in-home chef experiences.