You own three of the seven services, and together they are the platform’s evidence layer. Your telemetry code produces the artefact that the farmer’s payment, the insurer’s record and the franchisee’s defence all rest on.
Key responsibilities
- Own telemetry ingest, the compliance and registration registry, and notifications
- Pass the September telemetry gate: a real flight, a real track, overlaid on a real booked polygon, at ninety-two per cent overlap or better
- Build the handset-relay fallback in parallel, as insurance
- Ship the dead-man timer that marks a silent stream incomplete and blocks a job from closing
- Hold transactional Tamil messages at ninety-eight per cent delivery, measured from delivery receipts rather than assumed
- Produce a compliance export for any registered airframe in one action
- Guarantee zero farmer personal data in any log sink, proven by a test that seeds a name, a number and a coordinate and fails if any appears
Eligibility
- Four to six years in backend engineering, with production services carrying high-volume ingest
- Time-series storage on a Postgres-class database or a purpose-built store
- You understand at-least-once delivery, windowing and clock skew — and have been bitten by at least one of them
- Three or more live third-party integrations with real error handling: rate limits, circuit breakers, backoff
- Comfortable with asynchronous Python, Linux and containers
What you get
- Three services owned outright, each with a named backup
- Work whose output is the evidence everybody else relies on
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.