Home › Company › Careers
Careers

Build the register that never stops.

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.

Why this team

What working here actually means.

Production on day one

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.

You own what you ship

The person who wrote it answers the ticket — direct ownership from first commit to field deployment, end to end.

Field over conference rooms

Site visits are how you learn the product. A queue clearing on a Kashmir kitchen's register teaches more than any internal wiki.

Where the work happens

Eight bases. Remote-native.

DarjeelingMumbaiBangaloreOhioDrammenDubaiLondonAucklandNovosibirsk — soonRemote — India · UAE

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.

Open roles

Six seats. All of them ship.

Every role touches production within the first week — you own what you ship, from commit to field.

Senior POS EngineerC++ / Qt · offline sync · register UXOwn the surface a cashier touches four hundred times a shift — across 97-terminal networks and an air-gapped canteen.Remote — India · Full-time →Applied AI EngineerRAG pipelines · MCP tooling · cost controlsGrounded RAG answers and MCP agents that act inside audit ceilings — AI that shows its working.Remote — India / UAE · Full-time →Security EngineerCode signing · PCI-DSS · role isolationSigned runtimes, role isolation and the append-only trail auditors actually read.Remote — India · Full-time →Implementation LeadMulti-site rollouts · migration playbooksSandbox pilots to multi-site cutovers — the person who lands a 100-terminal rollout.Mumbai / Dubai · Full-time →Support EngineerTier-2 escalation · edge diagnosticsEdge deployments across eight bases — follow-the-sun coverage from Auckland to Ohio.Darjeeling · Full-time →Product DesignerERP UX · register flows · dashboardsFlows a first-week cashier uses without a manual — ERP design that disappears into the shift.Remote · Full-time →

Don't see your seat? careers@retailda.com →

How hiring works

Three steps. No theatre.

The process is the product — you work on a real ticket, we see how you think, you see what shipping here feels like.

Step 01The technical conversation

30 minutes with the person who owns the lane — not a recruiter screen. We talk about real systems, not riddles.

Step 02The paid working session

Half a day on an actual ticket, paid. You work on the product, in the codebase, with the team you'll join.

Step 03The founder call

Direct conversation about the work, the terms and where the company is going — then a decision. No committees.

Questions

The ones you were going to ask.

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.

Don't see your exact title? Write anyway.

Send your GitHub, portfolio or a note on the hardest system you've shipped — an engineer reads every application directly.