An engineering-led team across Darjeeling, Mumbai, Bangalore, Ohio, Drammen, Dubai, London and Auckland — Novosibirsk soon — shipping code that runs a 97-terminal retail network, air-gapped defence & PSU canteens and SCADA water plants. No layers between you and the deployment.
Your first ticket runs on the same binaries behind defence & PSU canteens, a 97-terminal network and industrial SCADA lines. There is no sandbox career track.
The person who wrote it answers the ticket — direct ownership from first commit to field deployment, end to end.
Site visits are how you learn the product. A queue clearing on a Kashmir kitchen's register teaches more than any internal wiki.
Coverage follows the sun — Auckland opens the retail day and Ohio closes it; the queue doesn't sleep, so the team doesn't sit in one timezone.
Every role touches production within the first week — you own what you ship, from commit to field.
Don't see your seat? careers@retailda.com →
The process is the product — you work on a real ticket, we see how you think, you see what shipping here feels like.
30 minutes with the person who owns the lane — not a recruiter screen. We talk about real systems, not riddles.
Half a day on an actual ticket, paid. You work on the product, in the codebase, with the team you'll join.
Direct conversation about the work, the terms and where the company is going — then a decision. No committees.
Three steps: a 30-minute technical conversation, a paid half-day working session on a real ticket, and a founder call. No whiteboard puzzles — you work on the product.
Yes. The codebase, the field deployments and the ticket queue are all remote-native. Site visits happen — a register in a Kashmir kitchen beats a conference room for understanding the product.
C++ / Qt on the register, offline sync engines, RAG pipelines and MCP tooling, plus the dashboards and consoles around them. The role card names the lane.
No — the field teaches it. Site visits are part of onboarding; you'll watch a real queue clear before your second week.
Send your GitHub, portfolio or a note on the hardest system you've shipped — an engineer reads every application directly.