טל כהן — ספרינט למשרה

"Networking ICs are large, high-power, high-frequency parts — that puts real stress on the test equipment, so uptime and stability of the ATE directly gate production capacity."

"For seven years at Tower I worked hands-on with production test on a high-volume line — operating and troubleshooting test equipment, debugging hardware and software issues, and keeping test cells running. I sat on the manufacturing side, so I understand exactly what a test house needs from its equipment and its vendors: fast recovery, clear procedures, and stable uptime. The vocabulary of equipment engineering — OEE, acceptance, PM — is something I'll formalize quickly, because in practice I've been doing the work the whole time."

"I'm an electrical engineer with seven years at Tower Semiconductor's Fab2. My day-to-day is hands-on production test — operating and troubleshooting test equipment, debugging hardware and software issues, optimizing test flows, and keeping a high-volume line running. I completed my EE degree at the Technion while working full-time. What draws me to this role is that it's exactly the work I do best, but on the equipment side: owning ATE uptime, acceptance, and reliability for high-volume production. I've sat on the manufacturing floor for seven years, so I know what keeps a test line healthy."

"Seven years gave me deep hands-on experience with production test and equipment debug, but the scope at a foundry is fixed. I want to own test equipment end-to-end — uptime, acceptance, vendor and OSAT relationships — for leading-edge products at the scale NVIDIA runs."

"NVIDIA's networking products are some of the most demanding parts to test — large, high-power, high-frequency. That makes equipment engineering genuinely matter: uptime on those test cells directly drives capacity. I want to own that challenge at a company shipping at this volume and pace."

"I'd start with data — break OEE into availability, performance, and quality and find the weakest one; usually it's availability. Then chase recurring downtime: pull the failure history, find the top repeat offenders, and attack them two ways — raise MTBF with targeted preventive maintenance, and cut MTTR with stocked spares, documented recovery procedures, and trained operators. Every fix gets verified against the data, not assumed."

"Throughput against the spec, measurement correlation to a reference system, stability over time, spare-parts availability, and a clear, documented acceptance procedure with the vendor. I don't sign off until the equipment proves it can hold its targets on the floor, not just at install."

"Clear documentation, data-driven debug before I ask anyone to touch hardware, time-zone-aware handoffs, and defined escalation criteria so the line never sits idle waiting on a decision. I've been on the manufacturing side at Tower, so I know what a test house actually needs from the company it supports."

"My formal title was test engineer, not equipment engineer, so some of the equipment-engineering vocabulary — OEE targets, formal acceptance processes — is something I'm formalizing rather than something I've owned by name. The mitigation is that I've done the underlying work for seven years: troubleshooting equipment, cutting recovery time, keeping cells running. And I ramp fast — I finished a Technion degree while working full-time."

"Three things. Seven years of hands-on equipment and silicon debug on a real production line. A manufacturing-side perspective — I know what a test house needs because I've been one. And proven fast learning under load — a Technion degree completed while working full-time. The equipment-engineering framing is a short ramp; the hands-on foundation is already there."

S: "A test cell at Fab2 started failing intermittently on [equipment/flow], causing repeated downtime and threatening line throughput."

T: "I owned getting the cell back to stable production fast."

A: "I reproduced the fault across [N runs], isolated variables one at a time — [mechanical / contact / measurement / a specific lot] — and traced it to [root cause]. I fixed [the recovery step / the procedure / the setting] and verified stability over [M] lots."

R: "Downtime on that cell dropped by [X%], and I documented a recovery procedure so the next occurrence is resolved in minutes instead of hours."

S: "[A piece of test equipment / a flow] had recurring failures that kept pulling down availability."

T: "Raise uptime without adding headcount."

A: "I pulled the failure history, found the top repeat offenders, and attacked them — [tuned a measurement sequence / standardized a recovery routine / adjusted a maintenance interval]."

R: "Availability improved by [X%], recurring escalations dropped, and the routine became the team standard."

S: "[A new test program / setup / capability] needed to enter production with no clear acceptance process."

T: "Bring it in and prove it was production-ready."

A: "I defined the criteria — [throughput, correlation to reference, stability] — validated against [characterization data / golden units], and documented the steps."

R: "It released to production on schedule and ran reliably on [Z lots/wafers]; the acceptance checklist became reusable."

S: "I completed my Technion EE degree while working full-time at Tower — years of parallel load."

T: "Keep full performance on a production line while finishing an engineering degree."

A: "I ran a strict system and routed coursework into work value — [device physics / data analysis] fed directly into how I debug equipment and silicon."

R: "Graduated June 2024 with zero performance issues at work. When the role asks for fast learning and agility under production pressure, this is the proof."

S: "[A test area / piece of equipment] had recurring issues and no clear owner."

T: "Nobody assigned it. I took it."

A: "I documented the failure history, fixed [N issues], wrote the missing procedures, and became the point of contact."

R: "Escalations dropped [X%] and the documentation became the team reference. I don't wait for ownership to be handed to me."

S: "Test time on [flow] was a bottleneck — [N units/hour] on a loaded line."

T: "Increase throughput without losing coverage — and prove it."

A: "I profiled the flow, found [inefficient sequencing / redundant steps], restructured it, and validated against [historical datalogs] that detection was unchanged."

R: "[X%] throughput improvement with documented proof of equivalent quality. Efficiency only counts if quality is provably untouched."

Electrical engineer with 7 years at Tower Semiconductor (Fab2), working hands-on with production test equipment — operation, troubleshooting, uptime, and high-volume manufacturing support. I've spent my career on the manufacturing floor, so I understand what keeps a test line healthy: fast recovery, stable equipment, clear procedures. Technion EE graduate (earned while working full-time). Targeting test-equipment / production-engineering roles where ATE uptime and reliability drive real capacity. Strengths: equipment debug, OEE/uptime improvement, vendor and test-house collaboration.

Hi [Name], I'm an electrical engineer with 7 years at Tower Semiconductor — hands-on test equipment operation, troubleshooting, and high-volume production support, plus a Technion EE degree. I'm very interested in the Equipment Engineer role in Yokneam (JR2019367). Is it still open? Happy to send my resume. Thanks, Tal

Hi [Name], I saw you're on the [team] at NVIDIA in Yokneam. I'm a test engineer at Tower Semiconductor — 7 years of hands-on equipment debug and production support, Technion EE. I'm really interested in the Equipment Engineer role (JR2019367) and would value 2 minutes of your perspective on the team — and if it seems like a fit, a referral would mean a lot. Happy to send my resume. Thanks! Tal