Senior Fullstack Engineer – CargoX
About CargoX
CargoX is a UAE-based autonomous logistics company running driverless delivery vans, bots and drones. Our fleet orchestration platform coordinates the full delivery journey, from order creation and dispatch through live vehicle tracking, customer handoff and incident recovery, connecting delivery partners, operators and vehicle makers.
Role overview
We are looking for a Senior Fullstack Engineer to own features end to end, from the backend API to the screens our operations teams and field workers use. You'll join one of two squads (see Squad differences below), each a sub-team of two to three engineers owning one product with a business owner.
What you'll do
- Build features across the stack: API and data model, backend logic, and the web or mobile interface.
- Stream live vehicle, order and task updates from backend to screen with low latency.
- Make the client reliable on poor connections (offline-first sync, conflict handling).
- Contribute to the backend that coordinates long-running workflows and vehicle and partner integrations.
- Implement security and monitoring across the stack (multi-tenancy, access control, secure token handling).
How we build
Kotlin and Spring Boot modular monolith on PostgreSQL/PostGIS, Redis and Kubernetes. Web console in TypeScript and Next.js/React; field apps in TypeScript, React Native and Expo. Vehicle and partner integrations via REST, webhooks and MQTT.
Qualifications
- 5+ years building complex production systems, owning features across backend and frontend or mobile; CS degree or equivalent.
- TypeScript with React/Next.js (web) or React Native/Expo (mobile).
- Backend: Java/Kotlin and Spring Boot preferred; distributed systems, concurrency and API design.
- PostgreSQL and real-time communication (WebSockets, MQTT).
- Real-time state management and offline-first sync on the client.
- Automated testing (unit, integration, end-to-end).
- Fluent business English.
Squad differences
Both roles are fullstack and share the same backend. The big difference is the screen: a web app on a desk vs a mobile app in someone's hand.
LiveOps Console (Orchestration): the "mission control screen"
- Builds the web app that operations agents use to watch the whole fleet live on a map and deal with problems, like a stuck robot or a late delivery. Alerts, an incident queue, a supervisor dashboard. Goal: automate most of it so a few hundred agents can run thousands of vehicles.
- Works with: the Head of LiveOps and the agents in the control room.
Runner App (RMS & Apps): the "app in the runner's pocket"
- Builds the phone app human runners use on every shift: their tasks, scanning a QR code to unlock a robot, proof-of-delivery photos, maps, chat and earnings.
- Works with: the Head of Operations and the runners themselves.
