Ful stack developer

About CuraCura is a travel concierge that plans, books and looks after your trips. You tell it where you are going. It builds the trip, books it, and handles it when something breaks at 2am in Bangkok. Every trip ends with a receipt showing exactly how many hours and rupees it saved you, including what Cura earned on the booking.We are pre-seed, based in Bengaluru, and we are opening our first cohort now. We are a travel business that uses AI. We are not an AI company that does travel. The difference shows up in every decision we make.The roleFull-time, on-site in Bengaluru.You are an early engineer on a small team. There is no backlog to pick from and nobody to hand you a spec. You will own whole surfaces end to end, from the database to the screen a member is looking at on a train platform in a country they have never been to.We ship weekly. The product is live with real members and real money, so nothing you build is a prototype.This role is weighted toward the app. If you like being three layers away from the person using the thing, this is the wrong job.What you will build• The app. iOS and Android, in the same sprint. Offline-tolerant, because members open it in airports and on hotel wifi that barely works.• Gmail import. Rebuild a member's travel history by parsing their inbox across hundreds of booking platforms, and render it back to them. This is the first thing a member ever sees.• The agent surface. LLM orchestration over real supplier inventory with a human in the loop. The model drafts, a person approves, then money moves. There is no code path from a model output to a payment.• Supplier integrations. Flights, hotels, trains, visas. Every supplier API is different and several of them are bad. Normalising them is most of the work.• Payments and split. Four people paying four shares of one trip, with the money landing correctly every time.• The operator console. The internal tool that decides whether a trip takes 30 minutes of human time or 90. Unglamorous and the most commercially important thing in the codebase.StackTypeScript across client and server. Node, Postgres, LLM orchestration over Anthropic and OpenAI. Mobile is cross-platform with native modules where we need them. Hosted in ap-south-1. We are not precious about tools and we will not rewrite anything for taste.What we are looking for• 2 to 3 years building products that real people used.• You have shipped a mobile app to the App Store and Play Store, and you were still there for what happened afterwards. Review rejections, a crash on a device you do not own, a release you had to pull. If you have only worked on apps someone else submitted, this is not the same thing.• Comfortable in Flutter, React Native or Swift. We care that you have shipped, not which framework you shipped in.• You can own a surface end to end: schema, API, client, and the bug someone reports on a Sunday.• Opinions about latency and app size. A concierge that takes eleven seconds to reply is not a concierge.• You have integrated third-party APIs that were poorly documented and worked around it rather than complaining about it.• You write code a stranger can read in six months.What we are not looking for• Someone who wants a well-specified ticket. There are none.• Someone who wants to work on the model rather than the product. We are not training anything.• Anyone who needs the problem to be technically interesting before it is worth solving. Most of the highest-value work here is plumbing.• Agency or services-only backgrounds where the app shipped and you never saw it again.Nice to have• Travel, fintech or logistics. Anything with real inventory, real money and real failure states.• Payments work, especially UPI and cards in the same product.• You have built an internal tool that an operations team actually used every day.How to applySend us one app you built and shipped, with the store link. Then two sentences on what broke after it went live and what you did about it. Skip the cover letter.