The role

You build the service that turns a farmer’s demand into a pilot’s job, and the register that decides which franchisee owns which territory. If booking and dispatch stops, the whole network stops earning. If the exclusivity register is wrong, the mistake is not recoverable at any price.

Key responsibilities

Own booking and dispatch: intake, slot and weather windows, the ten-gate evaluation, catchment resolution, pilot round-robin and airframe selection
Own the job lifecycle state machine, plus custody, maintenance and inventory
Own the franchise and fee registry: territory exclusivity, the agreement state machine, token register and commissioning status
Build the exclusivity register before the funnel screen — that order is fixed, not a preference
Make every booking carry a verdict and a reason code for all ten gates, queryable and exportable
Guarantee that no booking can ever produce two assignments




Hold read paths under 300 milliseconds at the ninety-ninth percentile at proof volume

Eligibility

Four to six years in backend engineering, with at least two services live in production for two years or more
A Spring-class framework, REST, and a queue or broker
You have shipped order-lifecycle or payment-adjacent code — idempotency and retry semantics are not new words
Solid SQL on a Postgres-class database: transactions, isolation levels, indexes, and reading a query plan
You write tests without being asked

What you get

Two of the seven services owned outright from week one, with a named backup
Your service named in the evidence pack that is signed at the end of November

How the process runs

Fill in the short form on this page.
We read it ourselves. Every application is read.
If we want to meet you, we call you.

📌 Backend Engineer — Booking, Dispatch (Chennai)
🏢 https://drone-port.in/
📍 Chennai