Application choices
Before you apply
Preparation by function
Interview preparation should start with one project you can defend in detail. Be ready to explain the initial specification, what you personally owned, the first failure, the measurement or data used to isolate the problem, the trade-off in the final design, and what you would change with another week. For a hardware or process role, expect questions that test whether you understand measurement error and physical constraints. For software, explain interfaces, tests, observability and failure handling. For business roles, explain the operating mechanism behind the number you modeled.
Work, teams and company background
Jump to a section
Company brief and operating context
Onto is a useful student target for optical/metrology engineering, algorithms, machine vision, mechanical/electrical systems, applications, software, manufacturing and EHS. The business value is often a measurement: detect a defect earlier, quantify a structure more accurately, or turn factory data into a process decision.
For application purposes, map the employer to the semiconductor value chain first: configurable silicon, power devices, materials, wafer-processing equipment, process control, test, photonics or equipment subsystems. That map changes what an intern actually does and what prior evidence is persuasive. The report does not assume that a prestigious company name compensates for a weak project or an unclear manager.
Applications Engineering
Applications work sits near the customer process. Prepare to explain how a measurement result changes a fab decision and how you would debug disagreement between the tool and another metrology method.
Candidate fit and offer diligence
Evaluate the internship on project ownership, manager access, technical learning, location burden, conversion path and compensation rather than employer name alone. For equipment and manufacturing employers, on-site work may be the source of learning rather than a drawback: the lab, cleanroom, factory or test floor may contain the actual problem. Conversely, relocation without housing support can materially change effective compensation. Build a simple after-tax and housing budget if the offer requires a move.
A strong offer should make the work legible. You should know the team, likely project class, manager or mentor structure, physical location, schedule, pay basis and whether the work is expected to continue after the internship. If the recruiter cannot answer those questions before acceptance, treat that uncertainty as part of the offer rather than assuming the best-case version.
Optical / Metrology Engineering
Show an experiment where optical measurement quality, calibration or uncertainty matters. Candidates should understand that better resolution is not useful if the measurement is unstable or too slow for process control.
Turn the preparation into a compact work sample. State the problem, constraints, data or measurements, decision rule, result and one limitation. For technical work, include the failure or mismatch that forced you to revise the design. For business work, include the assumption that most changes the recommendation. This makes the artifact useful in an interview rather than decorative.
Computer Vision / Algorithms
Inspection systems generate images and signals that must separate defects from background variation. A strong project reports false positives/negatives, robustness and data limitations, not just model accuracy.
Mechanical / Systems Engineering
Precision stages, optics, thermal stability and vibration can all affect measurement. Candidates should show cross-disciplinary troubleshooting rather than treating mechanical subsystems in isolation.
Distinguish the defect from the detection process
Create synthetic inspection results with one false alarm and one missed issue. Explain the decision cost of each and the measurement needed to investigate it. Keep the analysis tied to a defined process or user. Do not imply that an educational classification result is sufficient to release real production material.
Hypothetical preparation exercise, not an employer assessment or a verified internship assignment.
Interview preparation
Do not memorize a generic company description. Pick one product or process area relevant to the team and form a point of view about the engineering or operating problem it solves. Then prepare questions that reveal the internship's actual quality: What deliverable is expected by the end? Who reviews the work weekly? What lab, fab, codebase or data access will the intern receive? How is a project scoped when equipment or customer dependencies slip? What happened to last year's intern project? These questions produce more decision-useful information than asking whether the culture is 'collaborative.'
Questions to resolve before accepting
- Which product, module, process or customer problem will the intern own?
- What does the final deliverable look like and who signs off on it?
- How much work occurs in a lab, fab, factory, cleanroom or customer site?
- What training is required before the intern receives tool or data access?
- What are the exact pay, overtime, housing and relocation terms?
- Does the role have export-control or work-authorization restrictions?
- How many prior interns returned, and was return conversion formal or ad hoc?
- What is the biggest reason last year's intern project got delayed?
Research context
Onto Innovation provides semiconductor process-control solutions in inspection, metrology, lithography and software. Its systems are used to find defects, measure structures and materials, control processes and improve yield across wafer fabrication and advanced packaging.
The recruiting observations below retain the dates in the underlying research. They are not a live vacancy list.