Backend Engineer — Booking, Dispatch & Franchise Registry

https://drone-port.in/; Chennai District; On-site; INR 1,200,000 - 2,400,000; Full time

Benefits offered by this job

Ownership of two services from week 1

Evidence pack signing at end of Nov

Job summary

Drone Port in India is seeking a backend engineer to own critical booking and dispatch systems, as well as the franchise and fee registry. You will manage the entire lifecycle state machine, inventory, and system performance to ensure the network runs smoothly.

The role requires 4–6 years in backend engineering, proficiency with Spring, REST, queues, and strong PostgreSQL SQL skills. You will write tests proactively and influence the end-to-end order lifecycle and reliability.

Qualifications

• Four to six years in backend engineering with at least two production services.
• Experience with Spring framework, REST, and a queue or broker.
• Shipped order-lifecycle or payment-adjacent code; idempotency and retry semantics.
• Strong SQL on a Postgres-class database: transactions, indexes, and explain plans.
• You write tests without being asked.

Responsibilities

• Own booking and dispatch workflows: intake, slot/weather windows, 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; the order is fixed.
• Make every booking carry a verdict and a reason code for all ten gates; queryable/exportable.
• Guarantee that no booking can ever produce two assignments.
• Hold read paths under 300 milliseconds at the 99th percentile at proof volume.

Skills

Backend engineering

SQL

Spring framework

REST

Testing

Tools

PostgreSQL

Job description

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
• Strong 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