The company has excellent people and a genuinely supportive culture that's perfect for starting your career in wafer-level testing. The corporate values create a friendly, welcoming environment where you feel valued from day one. What's peculiar of the job is the sense of impact: Your work will directly impact production: with the high volume products that you'll manage you can really have a massive impact on yield and profitability, Your work truly matters here, and they will let you know about it.
If you want to get some hands-on experience with ATE test equipment such as Advantest/Teradyne/Cohu ATE Machines and TEL Probers, this is an ideal place to acquire it and build expertise.
Beyond the work itself, the atmosphere is pleasant and collaborative, and the food is a nice bonus!
You are the eyes of the company on production's output and the hand that decides what to keep and what to discard. Your test code will directly define product Yield, profitability and testing cost: optimizing testing time while keeping the data reliable and smooth enough ("Normal" enough) will be your highest priority, when no new product development or Emergency priority or Reliability/Failure Analysis is at hand.
Since you're working with production-impacting hardware and code, there are drawbacks: volumes are huge and so when problems come, they're also huge and super-high priority.
You're basically technical-electronics ER (emergency response), you need to be available on short notice to jump on critical issues, at any moment anything can happen and you could be ending up spending Christmas time debugging something, but it will still be considered "normal" and inside your duties.
This is an intense, high-stakes environment that requires significant commitment. Expect long hours and time-critical issues with serious consequences that need immediate resolution.
The role comes with constant pressing priorities, and tape-out periods can be extremely stressful.
You'll need to quickly connect, analyze data, diagnose problems, modify testing code, and push fixes to production, often under significant time pressure.
Work-life balance can be challenging, especially during critical periods.
If you value predictable hours or protected personal time, this may not be the right fit.
That said, if you thrive under pressure and want to work on mission-critical problems where your contributions have immediate, tangible impact, the intensity can be rewarding, and the impact is huge, not many jobs have the same possibility to have such an impact, even though for management, it's considered as nothing out of the ordinary and basically all you efforts are inside your standard remuneration package.
Please consider reviewing the responsibilities and tasks of the team and design a reward strategy for the good work.
DFT, new test code for new products development, testing hardware design, ATE software libraries development, existing products test code optimization, Reliability testing, Failure Analysis testing, Tape-out madness and above all always constant Data Analysis and Emergency development include the tasks to consider splitting and giving proper recognition for the good work, that quite often is not evident and presented and it passes un-noticed.
It was an online interview. I was joined by the HR, a senior software engineer and the manager. I was asked some coding question by the sr. software engineer, general questions by the manager about my background. The HR arrived late to the call as t
There were some questions about C, bash commands, statistics, and basic electronics. Nothing overly complex or advanced. Following the technical interview, there was an introductory interview with HR and some managers.
First I had an introductory interview with Human Resources, then I had a first technical interview with the area manager, and then I had another less in-depth technical interview with the area manager and his superior.
It was an online interview. I was joined by the HR, a senior software engineer and the manager. I was asked some coding question by the sr. software engineer, general questions by the manager about my background. The HR arrived late to the call as t
There were some questions about C, bash commands, statistics, and basic electronics. Nothing overly complex or advanced. Following the technical interview, there was an introductory interview with HR and some managers.
First I had an introductory interview with Human Resources, then I had a first technical interview with the area manager, and then I had another less in-depth technical interview with the area manager and his superior.