Associate Engineer – Engineering Change Management

HireSetu's note

The chasing is the real work

On paper the job reads like data entry: create part numbers, create AVL, release part lists. The weight sits in the ECOs. A part changes, you work out which products, drawings and sites it touches, route it through Agile, chase approvals, then make sure every plant gets the updated list. Miss one site and a line builds with the old part.

The listing asks for conflict resolution and coaching skills, which tells you where the friction lives. Engineers want their changes pushed through fast; you need them complete and correct first. English is mandatory because the requestors, customers and site teams you'll be emailing and calling are spread across time zones, not sitting in Chennai.

One oddity worth knowing before you apply: the title says Associate Engineer, the job summary says Technician. Treat it as a change analyst seat with an engineering-flavoured title, and ask which customer program you'd sit on.

Where two years of this leads

Agile PLM is used by hardware and electronics companies well beyond Chennai, so ECO and BOM experience travels: NPI coordination, PLM analyst or administrator roles, supply chain and program roles inside EMS. Baan is an older ERP. Knowing it helps here, but the Agile side is what the next employer will ask about.

EMS work runs many customer programs under one roof, so you'll see change processes across different product types and customer requirements in a shorter time than a single-product company would give you. That range is the thing to describe on your CV later: how many ECOs you handled a week, how many sites you released to, and what process metric you were measured on.

Drafted with AI from Flex's job posting and checked by Prashanth Jakkula before publishing. See our Editorial Policy.