Engineering talent in India: how to judge a team, not a CV

What engineering capability actually means

An Indian supplier can have a hundred engineers and still be unable to support your part. Capability is not headcount. It is the ability to read a drawing, challenge a tolerance, choose a process, prove a measurement and close a problem without being told each step.

That distinction matters because design support is often the reason a buyer chooses one supplier over another. The price difference between two quotes may be small, but the cost of a supplier that cannot answer a drawing query for a week is large. It shows up in tool corrections, late first articles and changes that arrive after the die is cut.

The practical test is to give the team a small piece of your work and watch how it thinks. A team that asks good questions before it quotes is usually a team that will flag a problem before it ships.

The roles that decide a programme

Most supplier teams are built around five functions. The titles vary, and one person may cover two roles in a smaller plant. Map the functions before you meet the people.

Test the work, not the vocabulary

A conversation about Industry 4.0 tells you very little. A drawing exercise tells you a lot. Send a real part with two difficult features, a general tolerance and a finish call, and ask for a short DFM note with a process route and the three risks the team sees.

Read the answer for specifics. Does it name a datum, a gauge, a fixture or a heat treatment step? Does it say which feature will drive the cost? Does it ask about volume and handling? A generic reply that lists capabilities without touching your geometry is a sales reply.

Follow with one tolerance stack and one root cause. The stack shows whether the team understands how features accumulate. The root cause shows whether it can work from evidence. Ask for a past corrective action, then ask what changed in the process, not only in the document.

Retention: the risk that does not appear in a quote

Engineering knowledge walks out of the door. A plant can have a strong team at the audit and a different team at the launch. Ask for tenure by function over the last two years, not a company average that mixes the founder with the shop floor.

Look for a training log, an apprenticeship route and a named deputy for the key role. A plant where one engineer holds all the customer drawings is a single point of failure. A plant that rotates work and documents its decisions can absorb a departure.

Pay is part of the story but not all of it. Engineers stay for interesting work, a clear path and a manager who defends the engineering view. Ask how a process change is approved. If the answer is only commercial, the engineering team will not stay long.

Protecting the work

Design work creates intellectual property before a part is ever made. The drawing, the CAD model, the tool design and the process know-how all have value. A confidentiality clause is a starting point, but it is enforced after the event, and enforcement in any jurisdiction is slow.

Use practical controls. Share drawings on a need-to-know basis, watermark them with the recipient and the date, and keep a register of who received which revision. Ask where the CAD files are stored, who can copy them and what happens when an engineer leaves. A personal cloud account is not a controlled store.

In India, confidentiality is supported by the Indian Contract Act, 1872, registered designs by the Designs Act, 2000 and inventions by the Patents Act, 1970. Copyright in drawings arises under the Copyright Act, 1957. The legal route exists, but prevention is cheaper. Put the ownership of tooling and drawings in the purchase order, not only in a separate agreement that nobody reads.

Build a working model

The best supplier engineering team will underperform without a routine. Name one counterpart on each side, set a weekly review and keep a single issue log with an owner and a date. Minutes should record decisions, not attendance.

Give the supplier the reason behind a tolerance. A team that knows the part is a safety stop will treat a burr differently from a team that sees only a dimension. Share the assembly context where confidentiality allows, because it turns a drawing into a problem to solve.

Review the engineering performance at the same time as the quality and delivery metrics. Track drawing queries answered on time, first article pass rate and the number of changes after tool freeze. Those three numbers say more about capability than a slide about the team.

• One named engineering counterpart on each side
• Weekly review with written decisions and owners
• Single issue log shared with the supplier
• Drawing query response time measured
• Changes after tool freeze reviewed at every programme gate

Warning signs on a visit

The signals are usually small and easy to explain away one at a time. Together they describe a plant that executes but does not think.

• The sales engineer answers every technical question without calling a colleague
• No one can show a drawing review record for a recent part
• The CAD station is shared and the files sit on a personal drive
• A first article is signed by the same person who set the machine
• Corrective actions repeat the same root cause with a new date
• The team cannot name the last change made to a process
• Training records stop at induction