A Software Engineer at Corning plays a critical role at the intersection of deep tech software, materials science, and advanced manufacturing. Unlike traditional pure-SaaS companies, Corning relies heavily on software engineers to design, build, and optimize systems that control precision glass manufacturing, high-speed optical communications networks, display technologies such as Gorilla Glass, and AI data center interconnect solutions. You will work on software that directly controls physical hardware, analyzes complex manufacturing sensor data, and powers automated optical inspection. The software engineering domain at Corning spans multiple specializations, ranging from embedded C/C++ firmware and process control systems (PLCs, HMIs) to computer vision, machine learning platforms, and high-performance computing tools. You will collaborate closely with process engineers, optical scientists, mechanical designers, and plant operators to translate physical and mathematical models into production-ready code. Because Corning products power global infrastructure and consumer electronics, the code you write directly impacts yield, quality, and real-time operations across international manufacturing facilities. The role offers a unique challenge: delivering low-latency, mission-critical software solutions operating under strict real-world constraints where system downtime or algorithmic bugs carry immediate physical and financial consequences.
Phone Screen
reportedA recruiter will gauge your interest and qualifications.
What to demonstrate
- A recruiter will gauge your interest and qualifications
- Depth in C++
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 Interview
reportedIn-depth interview that may include coding challenges or problem-solving scenarios.
What to demonstrate
- In-depth interview that may include coding challenges or problem-solving scenarios
- Depth in C++
How to prepare
- Answer aloud and timed: "What is a PLC, how does it interface with HMIs, and what communication protocols do you use to stream telemetry from equipment?"
- Answer aloud and timed: "How do you apply image processing techniques like PCA or PLS for defect detection in optical inspect systems?"
Onsite Interviews
reportedComprehensive interviews involving multiple rounds with various team members.
What to demonstrate
- Comprehensive interviews involving multiple rounds with various team members
- Depth in C++
How to prepare
- Answer aloud and timed: "Describe your experience with memory management, pointer manipulation, and multithreading in real-time software development."
- Answer aloud and timed: "Walk us through the core architectural decisions you made on your flagship project and explain why you chose those specific technologies."
Project Presentation
reportedPresent a project or work experience to the interviewers.
What to demonstrate
- Present a project or work experience to the interviewers
- Depth in C++
How to prepare
- Answer aloud and timed: "What was the most challenging bug or system failure you encountered during this project, and how did you debug it under pressure?"
- Answer aloud and timed: "If you had to scale this project for a high-throughput plant environment, what changes would you make to the pipeline?"
One-on-One Interviews
reportedInterviews focused on both technical and behavioral questions.
What to demonstrate
- Interviews focused on both technical and behavioral questions
- Depth in C++
How to prepare
- Answer aloud and timed: "How did you validate your software performance against real-world hardware constraints?"
- Answer aloud and timed: "What trade-offs did you make between software execution speed and algorithmic precision during implementation?"
PracHub editorial advice for the preparation topics above.
Structure your technical presentation with clarity
Treat the candidate presentation like a professional design review. Define the problem, state your constraints, highlight your specific technical decisions, and present clear outcome metrics.
Master your resume details
Every interviewer in your panel loop will likely pick a different section of your resume to interrogate. Ensure you can comfortably explain the underlying code and architectural mechanics of any project listed.
Prepare for cross-disciplinary interviewers
Remember that not every interviewer on your panel will be a software engineer; you may be interviewed by plant managers, mechanical engineers, or HR partners. Tailor your communication style accordingly.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
"How would you approach fixing and optimizing a C++ codebase containing broken memory allocations and ineffici
"How would you approach fixing and optimizing a C++ codebase containing broken memory allocations and inefficient loop logic?"
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 memory management, pointer manipulation, and multithreading in real-time softwa
"Describe your experience with memory management, pointer manipulation, and multithreading in real-time software development."
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 trade-offs did you make between software execution speed and algorithmic precision during implementation
"What trade-offs did you make between software execution speed and algorithmic precision during implementation?"
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?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
"Explain the difference between PID control and Model Predictive Control in automated manufacturing systems."
"Explain the difference between PID control and Model Predictive Control in automated manufacturing 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?
"What is a PLC, how does it interface with HMIs, and what communication protocols do you use to stream telemet
"What is a PLC, how does it interface with HMIs, and what communication protocols do you use to stream telemetry from equipment?"
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 apply image processing techniques like PCA or PLS for defect detection in optical inspect systems?
"How do you apply image processing techniques like PCA or PLS for defect detection in optical inspect 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?
"Walk us through the core architectural decisions you made on your flagship project and explain why you chose
"Walk us through the core architectural decisions you made on your flagship project and explain why you chose those specific technologies."
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?
"If you had to scale this project for a high-throughput plant environment, what changes would you make to the
"If you had to scale this project for a high-throughput plant environment, what changes would you make to the pipeline?"
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 did you validate your software performance against real-world hardware constraints?"
"How did you validate your software performance against real-world hardware constraints?"
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?
"What was the most challenging bug or system failure you encountered during this project, and how did you debu
"What was the most challenging bug or system failure you encountered during this project, and how did you debug it under pressure?"
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Corning candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Corning loop
- Write out the reported sequence: Phone Screen, Technical Interview, Onsite Interviews, Project Presentation, One-on-One Interviews.
- 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 5 reported rounds, with the weakest marked.
02Work C++
- Spend the session on C++, which Corning candidates report being tested on.
- Write one worked example in C++ and time yourself on it.
Deliverable: One timed worked example in C++.
03Work Code Debugging
- Spend the session on Code Debugging, which Corning candidates report being tested on.
- Write one worked example in Code Debugging and time yourself on it.
Deliverable: One timed worked example in Code Debugging.
04Work Performance Optimization
- Spend the session on Performance Optimization, which Corning candidates report being tested on.
- Write one worked example in Performance Optimization and time yourself on it.
Deliverable: One timed worked example in Performance Optimization.
05Answer out loud: Technical & Domain Knowledge
- Answer aloud, timed: "How would you approach fixing and optimizing a C++ codebase containing broken memory allocations and inefficient loop logic?"
- Answer aloud, timed: "Explain the difference between PID control and Model Predictive Control in automated manufacturing systems."
Deliverable: Spoken answers to 2 reported Technical & Domain Knowledge question(s), under time.
06Answer out loud: Project Presentation & Architecture Defense
- Answer aloud, timed: "Walk us through the core architectural decisions you made on your flagship project and explain why you chose those specific technologies."
- Answer aloud, timed: "What was the most challenging bug or system failure you encountered during this project, and how did you debug it under pressure?"
Deliverable: Spoken answers to 2 reported Project Presentation & Architecture Defense question(s), under time.
07Answer out loud: Behavioral & Team Collaboration
- Answer aloud, timed: "Tell me about a time you had to work with a cross-functional engineer who had a different technical opinion on how to solve a problem."
- Answer aloud, timed: "Describe a situation where a project deliverable was delayed due to unexpected technical roadblocks. How did you communicate this to leadership?"
Deliverable: Spoken answers to 2 reported Behavioral & Team Collaboration 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.
"Tell me about a time you had to work with a cross-functional engineer who had a different technical opinion o
"Tell me about a time you had to work with a cross-functional engineer who had a different technical opinion on how to solve a problem."
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 situation where a project deliverable was delayed due to unexpected technical roadblocks. How did
"Describe a situation where a project deliverable was delayed due to unexpected technical roadblocks. How did you communicate this to leadership?"
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 are you interested in working at Corning, and how do you feel about working near manufacturing or researc
"Why are you interested in working at Corning, and how do you feel about working near manufacturing or research facilities?"
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?
"Give an example of a time when you received constructive feedback on your code or design architecture and how
"Give an example of a time when you received constructive feedback on your code or design architecture and how you handled it."
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 adapt when project requirements change rapidly during mid-development?"
"How do you adapt when project requirements change rapidly during mid-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?
- 01
"Tell me about a time you had to work with a cross-functional engineer who had a different technical opinion on how to solve a problem."
- 02
"Describe a situation where a project deliverable was delayed due to unexpected technical roadblocks. How did you communicate this to leadership?"
- 03
"Why are you interested in working at Corning, and how do you feel about working near manufacturing or research facilities?"
- 04
"Give an example of a time when you received constructive feedback on your code or design architecture and how you handled it."
How difficult are the technical interviews at Corning compared to traditional software companies?
The technical complexity at Corning stems from practical software engineering, low-level architecture, and physical domain constraints rather than obscure algorithmic puzzles. You are more likely to be evaluated on code debugging, project architecture, and system integration than on complex LeetCode algorithms.
Corning Software Engineer candidate reports ↗What is expected in the candidate technical presentation?
You should prepare a well-structured slide deck (typically 30 to 45 minutes of content, leaving 15 minutes for questions) highlighting 1 to 2 major technical projects or research topics you led. Focus on the core engineering problem, your specific code/architectural contributions, key technical challenges overcome, and the measurable results.
Corning Software Engineer candidate reports ↗How long does the hiring process take from start to finish?
The process typically takes between 3 weeks to 2 months. Due to the involvement of multiple cross-functional managers and panel schedules, response times between initial screening and the panel interview can occasionally take several weeks.
Corning Software Engineer candidate reports ↗Is relocation or on-site presence required for Software Engineers at Corning?
Most engineering roles at Corning are tied directly to primary R&D centers (like Corning, NY) or regional manufacturing facilities (such as Hickory, NC or Fairport, NY). While some hybrid flexibility exists, roles closely tied to process controls or hardware testing generally require on-site presence.
Corning Software Engineer candidate reports ↗How important is industry experience in glass or optics?
Domain experience in optics or glass is not required for general software roles. What matters most is your core software engineering capability, your ability to learn specialized physical domains quickly, and your capacity to communicate effectively with physical scientists and process engineers.
Corning Software Engineer candidate reports ↗What topics does Corning test in interviews?
Corning interviews most often cover Stakeholder Management, Problem Solving, Requirements Gathering, Java, and Communication (Professional/Interpersonal). The exact emphasis depends on the specific role you apply for.
Corning 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.
- 01Corning 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.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave 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.
Aerospike Software Engineer Interview Questions & Guide 2026
Aerospike database-engine preparation through an original single-owner Python key-value store with bounded logical index accounting, disk-offset reads, conditional writes, tombstones, process-restart recovery and 3,240 checks. Existing 14 p