ZEISS Group Software Engineer Interview Experiences 2026
Real, anonymous reports from people who interviewed for Software Engineer at ZEISS Group, newest first and distilled into what to expect across the loop.
Get your personalized ZEISS Group Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter conversation, the process quickly moved into a structured technical flow. I remember being told the overall sequence up front and then, around a week later, I joined a technical stage where the questions were closely tied to the role. Depending on the day, it either felt like a straightforward screen or a small assessment—either way, the vibe was professional and responsive, with quick communication between steps.
Across the technical parts, I mostly dealt with fundamentals and applied thinking. I was asked about things like manual testing, company/product knowledge, and basic problem-solving. Some rounds leaned into coding-style questions (JavaScript topics such as OOP concepts, hash maps, and comparing approaches for efficiency), while others stayed more role-adjacent—like test design, and even hands-on work involving a microscope and how to think through measurement. Interviewers stayed friendly and let the conversation stay clear rather than overly adversarial.
> 1 year
Difficult Neutral Oberkochen
My process started with a task that felt like it required real depth rather than a quick screening exercise. I was instructed to prepare a detailed presentation based on an assignment I’d recently received. When I finally joined the longer online meeting to discuss it, the questions went deep and got very specific, as if they were trying to pressure-test both my understanding and how I structured the thinking behind the work. It was demanding in a way that made the prep feel like the real “interview,” and the meeting felt like a follow-through to that.
After the presentation discussion, the flow continued into more traditional rounds that still leaned technical. One stage included an online screening followed by an on-site interview that went well overall, but it wasn’t light—one round involved a case-style scenario where I had to form and explain my views on a business situation. Then, I moved through another path that included puzzles on an app and mind-tickler style questions before reaching a coding round that touched JavaScript and Node.js.
> 1 year
Average Negative Oberkochen
At the start, I joined a digital first call with several people from the company. I could see that the conversation was active, but two of the intervi…
> 1 year
Easy Negative Paris
My first step with the recruiter was immediately jarring. The interaction felt cold and impersonal, and I didn’t see much professionalism in how the c…
> 1 year
Average Negative Lisbon, Lisbon District
The process dragged in a way that set the tone early. Feedback took a long time and sometimes felt barely existent, and I got the sense that the coord…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter call, followed by a series of technical and behavioral interviews, often escalating in complexity. Candidates reported varied timelines, with some experiencing delays and others noting quick feedback.
Technical rounds often include coding questions, problem-solving scenarios, and discussions on practical applications related to the role, such as JavaScript and system design. Candidates noted a mix of formats, including presentations and case studies.
Coding questionsJavaScriptCase studies
Behavioral & Cultural Fit
Later stages of the interview process focus on assessing cultural fit and alignment with team values, often through discussions about past experiences and how they relate to the company's work environment. Candidates found these discussions to be important but sometimes misaligned with initial expectations.
Cultural fitTeam valuesExperience alignment
Communication & Clarity
Candidates reported mixed experiences with communication throughout the process, with some feeling well-informed while others experienced vague or unclear expectations, especially regarding job details and language requirements.
CommunicationExpectationsJob details
Interview Difficulty & Pressure
Overall, candidates described the interview difficulty as high, with a focus on thoroughness and clarity under pressure rather than just correctness. This created a demanding atmosphere that some found challenging.
Interview difficultyPressureThoroughness
Outcome & Candidate Reflection
Most candidates did not receive offers, leading to reflections on the overall experience, with many expressing disappointment over the lack of closure or feedback after the process. This left a lingering sense of frustration despite positive interactions during interviews.