Hotplate Backend Engineer at Hotplate owning backend systems that support thousands of chefs and bakers. Build reliable, fast, and scalable APIs, data models, and services for high-demand food drops and customer interactions.
Responsibilities
As a backend and infrastructure engineer at Hotplate, you'll own the systems that thousands of chefs and bakers run their businesses on, and that their customers buy from. When a popular chef opens a drop, customers arrive at once and compete for limited items, and every order has to be right: the inventory, the payment and the pickup.
Some of the problems you'll work on:
Make high demand drops fast and reliable. Keep inventory accurate and checkout responsive when customers arrive at once and compete for limited items.
Build the backend foundation for our consumer app. Design the APIs, data models, and services behind discovery, feeds, and every other customer facing surface to get people relevant results and make interactions fast and data rich to drive ordering.
Make critical workflows dependable. Build reliable systems for notifications, background jobs, and third party integrations.
Keep Hotplate getting faster and more stable. Find bottlenecks, improve observability, and own production issues through lasting fixes.
You'll work directly with the founders, ship features alongside the rest of the team, and make decisions about how our backend evolves. This is a hands on role with broad ownership and a direct connection between your work and the experience of chefs and their customers.
This role is based in San Francisco, and we are 5 days a week in-person. We move fast.
What you will need to be successful
Deep experience building and running backend systems in production: APIs, data models, background jobs and queues
Strong PostgreSQL skills: schema design, indexing, query performance, and transactions and locking under concurrency
You've kept a system fast and correct through real traffic spikes, and you know where they break first
Qualification
Design for retriesOur philosophy of engineeringHotplate's engineering team is smallWe are a leanWe operate with high ownershipWe’re a tight knit crewThis role probably isn't for you ifYou hand systems off once they ship
Required
Deep experience building and running backend systems in production
Strong PostgreSQL skills including schema design, indexing, query performance, transactions, and locking under concurrency
Experience maintaining system performance and correctness through traffic spikes
Design for retries, partial failures, and duplicate requests especially around payments and inventory
Ownership of production deployments including monitoring and alerting
Experience building SMS and notification systems that deliver reliably at scale
Preferred
Our philosophy of engineering
Hotplate's engineering team is small, and as we scale we want to keep it that way. Features are owned by individuals, and every engineer pushes code to whatever layer of the app the work needs. Your focus will be the backend: the systems that have to hold up when a drop sells out in minutes. We'd rather build simple systems that stay correct under pressure than clever ones that are hard to debug at the worst moment.
We are a lean, mission driven team. We exist to enable the next million chefs and bakers to scale local food businesses outside the brick & mortar model.
We operate with high ownership, laser focus on the impact we have for our chefs and bakers, and commitment to take on projects that push us out of our comfort zones.
We’re a tight knit crew. We jam with a daily shared playlist, often hang for team lunch and happy hours, and always have snacks on the table (made by the team or a Hotplate Chef). We love working in a place where we all have a connection, and think it helps us work better as a team.
This role probably isn't for you if
You want the problem scoped and prioritized for you. You'll often be the one finding which bottleneck or failure matters most, then scoping the fix yourself by digging into the data.
You hand systems off once they ship. You own what you build in production, including when something breaks in the middle of a big drop.