The role

You are the person every merge goes through. You own the service contracts that the whole team builds against, you sign the contract freeze, and you command incidents from your first week. In your third week you induct nine engineers who all arrive on the same morning, having yourself been in the building for ten working days.

Key responsibilities

Own the seven API service contracts, draft them by the end of August and sign the freeze with all fifteen seats present
Approve every merge to main — no exceptions, not for a one-line fix, not at eleven at night
Require two-person review on settlement and payments, with no exception for hot fixes
Hold review turnaround at 24 hours, and at 6 hours on the money and dispatch paths
Own the architecture decision log, release and rollback calls, incident triage and post-incident reviews
Run the engineering track of the induction week and get all nine joiners to a merged commit by the Friday
Share the on-call rota with DevOps — one week on,



two weeks off

Eligibility

Eight to ten years in backend engineering, at least three of them leading a team or owning a critical service
Depth in Java and solid SQL on a Postgres-class database, plus enough Python to review it
You have designed and versioned API contracts that other teams built against
You have run real incidents and written the reviews afterwards
You have onboarded a group, not just an individual — this seat inducts nine people in its third week

What you get

Seven services and fifteen engineers, from the first line of code
A daily working relationship with the CTO, and the authority that goes with the seat

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.

📌 Technical Lead (Chennai)
🏢 https://drone-port.in/
📍 Chennai