Interview practice plan

Z

Engineer - Engineering

ZEISS · Bengaluru

EngineeringMid level7 practice questions

Practice content written by LYDJ for interview preparation. These are common questions for this kind of role, not this employer's actual interview questions.

What this role asks for

The description doesn't name specific tools, so this plan focuses on the engineering function and behavioural rounds.

Sign in to see your gap areas first. We compare this role with the skills on your profile.

0 of 7 questions practised

Answer each one out loud, then tick it. Progress is saved in this browser only.

01Fundamentals0/3

Core programming

Engineering loops usually include a coding round. Practise talking through your approach before writing code.

  • Explain the difference between a process and a thread, and when you would use each.

    What good looks like

    Memory isolation versus shared memory, cost of creation and context switches, and the synchronisation problems that sharing introduces.

  • How would you find and fix a memory leak in a long-running service?

    What good looks like

    Confirm with memory metrics over time, take and compare heap snapshots, look for unbounded caches, listeners and global collections, then add a regression check.

  • What makes code testable? Show how you would refactor a function to make it easier to test.

    What good looks like

    Separate pure logic from I/O, inject dependencies instead of constructing them inside, and keep functions small with clear inputs and outputs.

02Every loop0/4

Behavioural

Every interview loop has a behavioural round. At mid level, expect questions on delivering independently, handling ambiguity and working through disagreement. Use the STAR structure.

  • Describe a piece of feedback that changed how you work.

    What good looks like

    State the feedback, your honest first reaction and the concrete behaviour you changed. Close with evidence that the change stuck.

  • Tell me about a time you worked with unclear or changing requirements.

    What good looks like

    Show how you reduced ambiguity: clarifying questions, writing down assumptions, small experiments and getting explicit sign-off.

  • Tell me about a time a project you owned was at risk of missing its date.

    What good looks like

    Show early detection, honest escalation and the scope, sequencing or resourcing levers you pulled. Avoid stories that end with "we all worked weekends".

  • Tell me about a time you worked closely with a team in another time zone or culture.

    What good looks like

    Mention concrete practices (async updates, overlap hours, written decisions) and a moment where a misunderstanding was caught and fixed.

Company research brief: ZEISS

From the roles we track on LYDJ, refreshed daily from the official careers page.

110

open roles

41

added in 30 days

28

in Engineering

Product & Software✦ New GCCGCC

Hiring most for

  • Other39
  • Engineering28
  • Sales & Marketing20
  • Data & AI8

Cities

Bengaluru · 91Delhi · 4Hyderabad · 2Gurugram · 1Kolkata · 1
See all 110 roles at ZEISS →

Read before the interview

Questions to ask them

  • ›There are several open Engineering roles at ZEISS right now. How is the team growing, and where does this role fit?
  • ›The company hires in Bengaluru, Delhi, Hyderabad. How do teams across locations work together day to day?
  • ›What does success look like in this role after six months?
  • ›What is the biggest challenge the team is facing this year?
  • ›What are the next steps in the process, and when should I expect to hear back?

Preparation checklist

0/8 done

Saved in this browser only.

Interview prep: Engineer - Engineering at ZEISS | LYDJ