Job Description:
Status: 01 Open Position | Experience Requirement: 3 - 5 Years| CTC: 10-12 LPA
What Tiffexx is
We deliver home-style tiffin meals on a daily subscription. A customer subscribes to a plan — say, weekday lunch. Every morning the system turns active subscriptions into that day's orders, assigns each order to a delivery rider, moves it through its lifecycle, and settles payment, all before the lunch window closes.
Riders work from a phone, in traffic, in basements and stairwells, on a connection that drops constantly. That last detail is the whole job.
What you would own
• The delivery rider app — go online, claim the next order, move it through pickup and delivery, share live location. Built first, because operations run on it.
• The customer app — browse plans, subscribe, pause and skip days, change address, pay, track today's delivery.
• The vendor app — kitchen-side order visibility and status updates.
• A shared React Native codebase and component library across all three, so we build once and reuse rather than maintaining three unrelated apps.
You will also touch the web side — the ops dashboard and customer web flows are React, and we would rather you were comfortable there than hand off at the boundary. That is why this is a full-stack role and not a pure mobile one.
The hard part — please read this properly
Building the screens is not the difficult bit. Keeping the app correct on a bad connection is. These are the problems you would actually spend your time on:
• A rider taps “Delivered”, the network dies before the response comes back, and they tap again. Nothing may happen twice.
• Two riders tap “Claim” on the same order in the same second. Exactly one gets it, and the other gets a clean, honest answer.
• A rider marks an order delivered while completely offline. Meanwhile the office reassigned it. On reconnect, that conflict has to be detected and resolved — never silently overwritten.
• The app is killed in the background mid-delivery. L
📌 Full Stack Developer (Noida)
🏢 Tiffexx
📍 Noida