Celestica interview questions

Tech / SWE · 4 questions · last reported Apr 2026
Report an interview →

Browse 4 Celestica interview questions for software engineering and software development interview preparation. Questions in this collection are tagged for new graduate, internship roles. Explore the topics and stages below and filter the collection to plan your practice.

Interview stages in this collection
Onsite, Phone screen
Practice topics
Internship (2), Problem Solving (2), Ambiguity (1), Behavioral (1), Data Sources (1), Data Structures (1), Debugging (1), DNS (1)

Questions come from candidate contributions and online research. Reports reflect past experiences and do not guarantee what Celestica will ask. Locked question details require points. Public examples below are free to read.

Read 2 free Celestica interview question examples

Browse all Celestica questions

4 questions

Free Celestica interview question examples

Read the full problem statements and use the links to revisit or share a specific example.

Midpoint Pointers

Easy · Onsite · New graduate

They asked me to find the middle element of a linked list in the most optimized way during the campus technical round. I explained the slow and fast pointer approach instead of counting the list length first, and they seemed to appreciate that I went straight to the efficient solution. The interviewer pushed on what happens when the list has an even number of nodes and which middle I'd return. I clarified the difference and showed how adjusting the loop condition changes which one you land on. This came after an MCQ-style online assessment and group discussion, so it was the first real coding question in the process.

URL Flow

Medium · Onsite · New graduate

One technical round asked what happens after typing a URL into the browser and pressing enter. I had to walk through DNS lookup, establishing the TCP connection, sending the HTTP request, and how the response gets rendered. Since the round was explicitly about computer networks, they went deeper than the usual browser question and asked about TLS handshakes and what happens if a DNS record is cached versus not. I also had to explain the difference between HTTP and HTTPS at the transport layer. It was more about explaining the full flow clearly than writing any code. The interviewer seemed to care about whether I could connect each step to the next logically rather than just listing buzzwords.