Frontend Engineer (React)Dukaan · Remote (India)

Careers · Bengaluru & remote Small team. Enormous surface. Every Dukaan store runs on what this team ships. Payments, logistics, a pricing engine, the API the dashboard runs on, and a storefront that has to be fast on a phone that is not. There is more surface here per person than almost anywhere you could work. See open roles Before you apply The honest version Read this part before the perks. Most careers pages describe a company nobody works at. Here is the actual shape of the job, including the parts you might not want. You will own more than is comfortable. There is no layer of people between you and the decision. That means the interesting problems land on your desk, and so does the pager when your change breaks a merchant's checkout on a Saturday. Some people find this the best thing about working here. Some find it exhausting. Both reactions are reasonable. The stakes are real money, immediately. A bug in the pricing engine is not a failed test — it is a seller in Surat being paid less than they were owed. That focuses the mind, and it means we are conservative about certain things in a way that fast-moving startups usually are not. We ship most days. Not because velocity is a value on a poster, but because small changes shipped often are easier to reason about than a quarterly release. If you like long design phases and detailed specifications signed off before code, this will feel chaotic. The constraints are unusual. Your user is on a mid-range Android with two bars of signal. Most modern web engineering assumes the opposite. A lot of received best practice simply does not apply here, and you will have to think from first principles more often than you are used to. What you get for it: your work is in front of tens of thousands of real businesses within days, you can see the effect in the numbers, and nobody has to ask permission to fix something that is obviously broken. How we workFour things we mean 01 Ship like it's yours Ownership over hierarchy. You make the call and you carry the consequence — including writing the postmortem when it goes wrong. We do not blame people for outages; we do expect them to be understood and written down. 02 Speed is a feature Both kinds. We launch in days rather than quarters — and the product itself has to be fast, because the merchant on the other end is losing an order every time a page hangs. Latency is a product decision here, not an infrastructure detail. 03 Allergic to dogma We left the public cloud when everyone said not to, because it was right for our workload and our users. "That's how it's done" is not an argument here. Neither is "we've always done it that way" — that one cuts both directions. 04 The merchant is in the room Everyone talks to sellers, not just support. Engineers read support tickets. Designers watch a real seller set up a store on a real phone. It is very hard to build the wrong thing when you have watched someone struggle with the last thing you built. The process How we actually hire Four steps, usually two to three weeks end to end. No unpaid multi-day take-homes, no whiteboard algorithms you will never use, and no ghosting — you get an answer at every stage even when it is a no. STEP 1 · 2–3 DAYS We read it properly A person reads your application, not a keyword filter. Tell us what you built and what broke — a paragraph about something that went wrong and what you did next tells us more than a list of technologies. STEP 2 · 45 MIN A conversation With the person you would work alongside, not a recruiter reading a script. What you have built, what you want to build, and what the job is actually like. Ask hard questions — we would rather you find out now. STEP 3 · 90 MIN A real problem Something from our actual backlog, worked through together. Engineers get real code; designers get a real screen a merchant struggles with. If it needs work outside the session, it is scoped to a couple of hours and we pay for your time. STEP 4 · SAME WEEK Decision and offer A short conversation with a founder, then a decision within the week. The offer has the cash, the equity and the band written down. If it is a no, you get a reason you can use. On compensation We pay competitively for the Indian market and we do not negotiate against your current salary — the band is set by the role, and we will tell you the band before you interview if you ask. Every full-time role includes ESOPs, and we will explain the strike price, the vesting schedule and what the equity is plausibly worth in plain numbers rather than letting you imagine one. If someone here cannot explain your own offer to you clearly, that is our failure. The practicalsBenefits, unembellished 🏝️Flexible time offNo fixed allowance. Take what you need, tell your team, and hand over properly. Founders take leave too — an unlimited policy nobody uses is just a lie. 💻The machine you wantPick your hardware. Plus a cheap Android test phone on your desk, because that is what your users are holding. 🩺Health coverMedical insurance for you, your partner, your children and your parents. The last one matters more in India than most policies admit. 📈ESOPs, explainedReal equity for every full-time role, with the strike price, vesting and dilution walked through in numbers before you sign. 📚Learning budgetCourses, books, conferences. No approval theatre — if it makes you better at the job, buy it. 🏠Remote that worksSeveral roles are fully remote within India. Decisions are written down so remote people are not permanently a step behind the room. 🍱Meals in officeLunch and snacks at the Bengaluru office. Not a substitute for going home at a reasonable hour. 🐶LeoChief Entertainment Officer. Attends more meetings than most of us and contributes about as much. We're hiringOpen rolesWhat each role actually does in the first ninety days, rather than a list of required frameworks. Senior Backend Engineer Engineering · Bengaluru or remote Go and Postgres, on the order and payments path. In your first quarter you will touch the checkout pricing engine, the order state machine, or the courier integration layer — code where a mistake costs a real merchant real money. We care that you can reason about correctness under concurrency far more than which frameworks you have used. Apply → Product Designer Design · Bengaluru Designing for someone running a business from a phone, often in their second or third language, frequently while doing something else. Fewer taps beats more features every time. You will spend real time watching sellers use what you designed, and you will change your mind about it. Apply → Frontend Engineer (React) Engineering · Remote The seller dashboard and the storefront themes. Performance is the feature: your target device is a mid-range Android on a weak connection, and a bundle-size regression is treated as a bug, not a trade-off. If you enjoy making things fast on hardware you would not choose, this is unusually satisfying work. Apply → Growth Marketer Marketing · Bengaluru Getting Dukaan in front of sellers who have never heard of it, mostly in languages other than English. Content, partnerships, community and paid, measured on activated stores rather than sign-ups. A vanity metric will get argued with here. Apply → Merchant Support Lead Operations · Bengaluru Owning the 4–6 hour response promise, and — more importantly — turning what sellers keep asking into product changes that stop them having to ask. The best support lead makes their own queue shorter. Fluency in Hindi plus one more Indian language is a real advantage. Apply → Nothing here that fits? Write to careers@mydukaan.io anyway and tell us what you would want to own. We have created roles for people who made a convincing case for one. Come buildSee yourself here?Tell us what you have built and what you broke learning to build it. That is the part we read first. careers@mydukaan.io