Here, the “Testing Engineer” we’re talking about is the one in a manufacturing plant responsible for product testing. We usually refer to the R&D engineers responsible for testing as EEs (Electronic Engineer). This role, along with the “Process/Product Engineer” we mentioned earlier, is one of the must-have positions in a factory. Another key role is the “Quality Engineer.” Together, they form what’s often called the “iron triangle” of a factory’s engineering department.

We’re focusing here on Testing Engineers in electronics assembly plants, not software-only testing engineers—that’s a different topic.

Since the job title includes “testing,” all product-related testing work falls under this role. The Testing Engineer is responsible for setting up the testing processes on the production line. If it’s a PCB assembly plant, they need to handle MDA (Manufacturing Defect Analysis) / ICT (In-Circuit Test) and functional testing, as well as analyzing defective boards. If it’s a final product assembly line, they need to arrange testing for all product functions—so customers don’t end up receiving defective products.

A Testing Engineer generally needs a background in electronics, electrical engineering, or automation, and ideally some programming skills. In some factories, they may even be asked to write product testing software. From Workingbear’s experience, some companies have R&D write the testing software in advance, so the Testing Engineer just follows the given procedures—an easier job, but with fewer learning opportunities.

MDA, ICT, and FVT fixtures usually use pin-based testing, also called bed-of-nails testing. These fixtures are often outsourced, but the Testing Engineer must define the required functions for them. Ideally, the list of tests should be decided during the product’s R&D phase, and R&D should be asked to keep the necessary test points. Otherwise, there may be no usable points later. While some modern smartphone boards skip MDA/ICT, FVT still requires test points.

We generally hope the factory’s Testing Engineer gets involved during the R&D phase. Early involvement helps them understand the product, assist R&D in deciding which test points or functions should be reserved, and provide input on the factory’s testing capabilities for design reference. The later you try to add test points, the harder it gets—space is limited, and changes may even affect RF performance. The earlier R&D reserves test points, the better.

Since manufacturing plants often run three shifts, 24/7, but engineers rarely rotate shifts, if a testing problem happens off-hours, the Testing Engineer must be on call. If the issue can be solved by phone, great. If not, they may have to rush to the production line—even in the middle of the night—because many people are waiting to resume production, and downtime losses can be huge.

I’ve heard that at TSMC, on-duty engineers must keep their phones on at all times—even while sleeping—and be able to reach the production line within an hour if needed. That’s why they live close to the factory. Of course, large companies have more engineers to rotate shifts, but smaller companies… well, good luck.

Speaking of downtime, a Testing Engineer must be able to handle stress. When the line stops, all the managers will come asking what went wrong. You must do everything possible to find the problem and get production running again. The pressure is no joke. Having a strong engineering team helps ease the burden—much better than fighting the battle alone.

That’s why, during normal days, it’s best to keep sharpening your technical skills. Know your products inside and out, and use effective methods to pinpoint problems quickly. This not only reduces your stress but also earns you more recognition within the company.

Related Posts:

• The Role of Process Engineers and Product Engineers in a Company