At Onto Innovation, a Software Engineer plays a critical role in shaping the future of semiconductor manufacturing. The company is a global leader in process control, combining high-precision 3D metrology, defect inspection, and advanced software analytics to help semiconductor manufacturers optimize their yields. As a software engineer, you are not just writing isolated code; you are building the software engines, control systems, and data pipelines that interface directly with multi-million dollar hardware systems operating at sub-nanometer scales. The impact of this position is immense. Your code directly influences the throughput, accuracy, and reliability of metrology and inspection tools used by the world's leading microchip fabrication plants (fabs). Whether you are optimizing real-time hardware control loops, designing complex algorithms to analyze wafer images, or developing robust desktop and cloud-based analytical applications, your work enables the continuous scaling of semiconductor technology. This role is highly collaborative and intellectually stimulating. You will work at the intersection of software engineering, physics, electrical engineering, and systems design. This cross-functional environment requires software engineers to possess a unique blend of deep computer science fundamentals and a strong curiosity about physical hardware and manufacturing processes.
Recruiter Screen
reportedInitial screening call with a recruiter to evaluate basic qualifications and fit.
What to demonstrate
- Initial screening call with a recruiter to evaluate basic qualifications and fit
- Depth in C# programming
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Screening Call
reportedA technical call with the hiring manager to assess technical capabilities.
What to demonstrate
- A technical call with the hiring manager to assess technical capabilities
- Depth in C# programming
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Panel Interview
reportedA series of interviews with peer engineers, stakeholders, and leadership to evaluate coding skills, system design, and behavioral alignment.
What to demonstrate
- A series of interviews with peer engineers, stakeholders, and leadership to evaluate coding skills, system design, and behavioral alignment
- Depth in C# programming
How to prepare
- Answer aloud and timed: Explain the concept of dependency injection and how it improves code maintainability.
- Answer aloud and timed: Given an array of integers, write an algorithm to find the peak element where the element is greater than its neighbors.
Final Decision Phase
reportedThe concluding phase where the final decision regarding the candidate's application is made.
What to demonstrate
- The concluding phase where the final decision regarding the candidate's application is made
- Depth in C# programming
How to prepare
- Answer aloud and timed: How would you design an algorithm to detect defects on a simulated 2D wafer grid?
- Answer aloud and timed: Explain the time and space complexity of your proposed sorting algorithm.
PracHub editorial advice for the preparation topics above.
Highlight your hardware-adjacent projects
If you have ever worked on robotics, IoT, embedded systems, or software that controls physical devices, make sure this is prominent on your resume and discuss it during your interviews.
Prepare for cross-functional panel dynamics
You may find yourself speaking with engineers from other departments, such as systems or applications engineering. Tailor your communication so that you can explain complex software architectures to non-software engineers.
Never running a concrete value through the code
Trace one small input and one edge input by hand, index by index, out loud. Re-reading your own code catches design mistakes; walking a real value through it catches the off-by-one, the uninitialised accumulator and the loop that never advances.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain the difference between interface and abstract classes in C#, and when you would use each.
Explain the difference between interface and abstract classes in C#, and when you would use each.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
How does garbage collection work in.NET, and how can you manage memory efficiently when dealing with large dat
How does garbage collection work in.NET, and how can you manage memory efficiently when dealing with large datasets?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Describe your experience with multi-threading and asynchronous programming in C#. How do you prevent race cond
Describe your experience with multi-threading and asynchronous programming in C#. How do you prevent race conditions?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
What are the main principles of Object-Oriented Programming (OOP), and how have you applied them in your past
What are the main principles of Object-Oriented Programming (OOP), and how have you applied them in your past projects?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Explain the concept of dependency injection and how it improves code maintainability.
Explain the concept of dependency injection and how it improves code maintainability.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Given an array of integers, write an algorithm to find the peak element where the element is greater than its
Given an array of integers, write an algorithm to find the peak element where the element is greater than its neighbors.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain the time and space complexity of your proposed sorting algorithm.
Explain the time and space complexity of your proposed sorting algorithm.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Describe how you would implement a queue using two stacks, and analyze its operational efficiency.
Describe how you would implement a queue using two stacks, and analyze its operational efficiency.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain your familiarity with control systems or algorithms used to process physical measurements.
Explain your familiarity with control systems or algorithms used to process physical measurements.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
Explain why the owner filter ignores the listing index
The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.
Approach
- Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
- For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
- Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
- Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.
Follow-up
- 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
- A dashboard runs this for 40 owners in one page load. What changes about the design?
How would you design an algorithm to detect defects on a simulated 2D wafer grid?
How would you design an algorithm to detect defects on a simulated 2D wafer grid?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you optimize a search algorithm when querying massive datasets generated by high-throughput sensors?
How do you optimize a search algorithm when querying massive datasets generated by high-throughput sensors?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you approach writing software that interfaces directly with physical sensors, motors, or optical system
How do you approach writing software that interfaces directly with physical sensors, motors, or optical systems?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you ensure high reliability and zero-downtime in software running in a continuous manufacturing environ
How do you ensure high reliability and zero-downtime in software running in a continuous manufacturing environment?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you handle a scenario where physical hardware returns noisy or inconsistent data to your software?
How would you handle a scenario where physical hardware returns noisy or inconsistent data to your software?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Exports duplicate a row range about once a week
Roughly once a week an export writes a file containing a duplicated range of rows. The affected job_run rows show attempt = 1, status = succeeded, one started_at, and a lease_owner naming a different host from the one whose logs show the job starting. Leases last 30 seconds and are heartbeated every 10 from inside the handler; lease_expires_at is computed on the worker and compared against the database's now(). Find the mechanism, and give a fix that holds even if you cannot fix the clocks.
Approach
- Start from the fact that eliminates the obvious answer. attempt = 1 means no retry was recorded, so this is not a re-run after failure; two workers ran the same row concurrently and the takeover path never touched the counter. lease_owner naming a host other than the one that started the job is the same statement from the other side.
- Enumerate the mechanisms that cause a premature takeover, then find the signal that separates them. Either the lease genuinely expired because the heartbeat did not fire, which is what happens when the heartbeat runs on the handler's own thread and the handler makes a long blocking call, or it only appeared expired because two clocks disagree, since lease_expires_at is written from the worker's clock and evaluated against the database's. The discriminator is the distribution: incidents clustered on the longest exports indict the heartbeat, incidents clustered on one host indict skew. Measure both, and measure each host's offset against the database directly.
- Read the reclaim query precisely. In PostgreSQL now() is transaction start time, not statement time, so a reclaimer holding a long transaction compares against an older timestamp than expected; clock_timestamp() is the statement-time function. This is worth ruling in or out before you redesign anything, because it changes which rows look expired.
- Remove the second clock rather than trying to synchronise it. Issue and extend the lease in the database, with lease_expires_at = now() + interval '30 seconds' in both the claim and the heartbeat, so exactly one clock is ever compared and worker skew stops mattering to this predicate.
Follow-up
- The displaced worker has already streamed half the file to object storage. What makes that side effect safe to repeat?
- You now count takeovers. What alert fires on that counter, and at what threshold?
Built from the rounds and topics Onto Innovation candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Onto Innovation loop
- Write out the reported sequence: Recruiter Screen, Technical Screening Call, Panel Interview, Final Decision Phase.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
02Work C# programming
- Spend the session on C# programming, which Onto Innovation candidates report being tested on.
- Write one worked example in C# programming and time yourself on it.
Deliverable: One timed worked example in C# programming.
03Work Algorithm/DS problem solving (coding questions)
- Spend the session on Algorithm/DS problem solving (coding questions), which Onto Innovation candidates report being tested on.
- Write one worked example in Algorithm/DS problem solving (coding questions) and time yourself on it.
Deliverable: One timed worked example in Algorithm/DS problem solving (coding questions).
04Work Behavioral interview skills (career planning, past experiences)
- Spend the session on Behavioral interview skills (career planning, past experiences), which Onto Innovation candidates report being tested on.
- Write one worked example in Behavioral interview skills (career planning, past experiences) and time yourself on it.
Deliverable: One timed worked example in Behavioral interview skills (career planning, past experiences).
05Answer out loud: Technical and Language-Specific Questions
- Answer aloud, timed: Explain the difference between interface and abstract classes in C#, and when you would use each.
- Answer aloud, timed: How does garbage collection work in.NET, and how can you manage memory efficiently when dealing with large datasets?
Deliverable: Spoken answers to 2 reported Technical and Language-Specific Questions question(s), under time.
06Answer out loud: Algorithms and Problem-Solving
- Answer aloud, timed: Given an array of integers, write an algorithm to find the peak element where the element is greater than its neighbors.
- Answer aloud, timed: How would you design an algorithm to detect defects on a simulated 2D wafer grid?
Deliverable: Spoken answers to 2 reported Algorithms and Problem-Solving question(s), under time.
07Answer out loud: Domain, Hardware, and Manufacturing Processes
- Answer aloud, timed: How do you approach writing software that interfaces directly with physical sensors, motors, or optical systems?
- Answer aloud, timed: What is your experience with manufacturing methodologies such as Lean, Kanban, or Agile software development?
Deliverable: Spoken answers to 2 reported Domain, Hardware, and Manufacturing Processes question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
What is your experience with manufacturing methodologies such as Lean, Kanban, or Agile software development?
What is your experience with manufacturing methodologies such as Lean, Kanban, or Agile software development?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Why do you want to work at Onto Innovation, and how does your background align with semiconductor process cont
Why do you want to work at Onto Innovation, and how does your background align with semiconductor process control?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a time when you had to work with a cross-functional team (e.g., systems, electrical, or applications
Describe a time when you had to work with a cross-functional team (e.g., systems, electrical, or applications engineers) to solve a complex issue.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle a situation where project requirements change midway through a development cycle?
How do you handle a situation where project requirements change midway through a development cycle?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell me about a time you had to learn a complex technical domain or tool quickly on the job.
Tell me about a time you had to learn a complex technical domain or tool quickly on the job.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Are you comfortable supporting field service environments, which may include occasional weekend standby duties
Are you comfortable supporting field service environments, which may include occasional weekend standby duties or direct customer interaction?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
What is your experience with manufacturing methodologies such as Lean, Kanban, or Agile software development?
- 02
Why do you want to work at Onto Innovation, and how does your background align with semiconductor process control?
- 03
Describe a time when you had to work with a cross-functional team (e.g., systems, electrical, or applications engineers) to solve a complex issue.
- 04
How do you handle a situation where project requirements change midway through a development cycle?
How difficult are the technical interviews at Onto Innovation?
The difficulty is generally rated as average. The technical questions are highly practical and focused on your actual coding ability, resume experiences, and software engineering fundamentals, rather than highly abstract, competitive-programming-style brainteasers.
Onto Innovation Software Engineer candidate reports ↗Do I need a background in semiconductors or metrology to get hired?
No, it is not strictly required for all roles, but it is highly valued. If you do not have a semiconductor background, you can stand out by showing a strong interest in physical hardware, industrial automation, and demonstrating how your software engineering skills can be applied to complex physical systems.
Onto Innovation Software Engineer candidate reports ↗What is the company culture like for software engineers?
The culture is highly collaborative, engineering-focused, and supportive. Teams are typically laid-back and knowledgeable, with an emphasis on taking engineering challenges seriously while maintaining a respectful and flexible working environment.
Onto Innovation Software Engineer candidate reports ↗How much preparation time should I plan for?
Candidates typically spend one to two weeks preparing. Focus your time on brushing up on C# fundamentals, multi-threading, object-oriented design patterns, and practicing a few medium-level algorithm and data structure problems.
Onto Innovation Software Engineer candidate reports ↗What topics does Onto Innovation test in interviews?
Onto Innovation interviews most often cover Semiconductor domain knowledge, Cost Accounting, C# programming, SEC Reporting, and Algorithm/DS problem solving (coding questions). The exact emphasis depends on the specific role you apply for.
Onto Innovation Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Onto Innovation Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.