The role

You own what finished means. You build the test architecture, you command the two field test engineers, you own the severity label on every defect, and your signature is one of only two on the acceptance at the end of November. You are the person who says the release is not ready.

Key responsibilities

Own test architecture across service, web and mobile, running in the pipeline on every commit and gating every merge
Hold critical-path coverage above ninety per cent on booking, settlement, telemetry and compliance export
Seed every integration run with a random station count between ten and two hundred, and record the seed
Publish the station commissioning scripts a month before the first station opens
Command the two field test engineers and the commissioning programme at the four proof stations
Bank twelve clean acceptance runs in the second half of November, with zero severity-one defects open at signature
Run acceptance testing with real farmers,



pilots and station staff — not engineers testing engineers

Eligibility

Five to seven years in quality and automation, at least two of them leading
You have built service, web and mobile frameworks from zero and run them in a pipeline — including killing the flaky tests
Real acceptance testing with non-technical people: recruiting them, running sessions in silence, turning reactions into defects
Defect triage authority earned rather than assigned
Comfortable being the person who says the release is not ready

What you get

Authority that is real — including the authority to stop the next phase when production needs it
Your signature on the acceptance, beside the CTO’s

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.

📌 QA & Automation Lead (Chennai)
🏢 https://drone-port.in/
📍 Chennai