Interview practice plan
Data Engineer
ZEISS · Bengaluru
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
Skills we found in the job description. The plan below is built around them.
Also named in the description, not covered below: IAM, Supply chain, Procurement. Review these on your own.
Sign in to see your gap areas first. We compare this role with the skills on your profile.
0 of 22 questions practised
Answer each one out loud, then tick it. Progress is saved in this browser only.
ETL & data pipelines
This role asks for ETL, Databricks, Data warehousing and Data modeling. These ETL & data pipelines questions cover the ground they share.
Explain slowly changing dimensions, especially Type 1 versus Type 2.
What good looks likeHide hint
Type 1 overwrites history, Type 2 adds a new row with effective dates and a current flag; choose based on whether reports need history.
Star schema or one wide denormalised table: what are the trade-offs for analytics?
What good looks likeHide hint
Star schemas keep dimensions consistent and reusable; wide tables are simpler and faster for specific use cases but duplicate logic. Many teams use both layers.
What is incremental loading, and how would you implement change data capture?
What good looks likeHide hint
Load only new or changed rows using watermarks or log-based CDC, handle deletes and updates, and reconcile counts periodically.
SQL
This role asks for SQL.
Explain INNER, LEFT and FULL OUTER joins. When does a LEFT JOIN accidentally behave like an INNER JOIN?
What good looks likeHide hint
Filtering the right-hand table in WHERE removes the NULL rows; put that condition in the ON clause instead.
Write a query that returns the second-highest salary in each department.
What good looks likeHide hint
Use DENSE_RANK() over a partition by department, and say how you treat ties, NULLs and departments with a single employee.
What is an index, how does a B-tree index speed up a query, and when does adding an index hurt?
What good looks likeHide hint
Sorted structure enabling seeks instead of scans; costs on writes and storage; low-selectivity columns and functions on columns can stop it being used.
Azure
This role asks for Azure.
How would you organise Azure management groups, subscriptions and resource groups for several teams?
What good looks likeHide hint
Management groups for policy inheritance, subscriptions as billing and isolation boundaries, resource groups per workload lifecycle, and consistent tagging.
When would you pick App Service, Azure Functions or AKS?
What good looks likeHide hint
Compare operational effort, scaling model, execution limits, cost profile and team skills, and give a workload that fits each.
How would you build a secure pipeline that deploys infrastructure and apps to Azure?
What good looks likeHide hint
Federated workload identity instead of stored secrets, Key Vault, environment approvals, infrastructure as code with Bicep or Terraform, and policy checks.
Spark
This role asks for Spark.
Explain transformations versus actions and lazy evaluation in Spark.
What good looks likeHide hint
Transformations build a plan, actions trigger execution, which lets the optimiser combine steps; know narrow versus wide transformations.
What causes a shuffle, and how do you reduce its cost?
What good looks likeHide hint
Wide operations like joins and groupBy; reduce with broadcast joins for small tables, partitioning on join keys, filtering early and adaptive query execution.
One task in a Spark stage runs far longer than the rest. What is happening and how do you fix it?
What good looks likeHide hint
Data skew on a key. Salt the hot keys, enable adaptive skew-join handling, or process the hot keys separately.
CI/CD & IaC
This role asks for Git, CI/CD and Terraform. These CI/CD & IaC questions cover the ground they share.
Design a CI/CD pipeline for a service with many contributors. Which gates would you put before production?
What good looks likeHide hint
Fast unit tests on every PR, integration and security scans, build once and promote the same artifact, staged environments, and automated rollback.
How do you manage infrastructure as code safely across environments and a team?
What good looks likeHide hint
Remote state with locking, reusable modules, plans reviewed in pull requests, separate state per environment, drift detection and least-privilege CI credentials.
How should secrets be handled in a CI/CD pipeline?
What good looks likeHide hint
A secrets manager or the platform's secret store, short-lived federated credentials, masking in logs, and never committing secrets to the repo.
Kafka
This role asks for Kafka.
Explain topics, partitions, consumer groups and offsets in Kafka.
What good looks likeHide hint
Partitions are the unit of parallelism and ordering, each partition is consumed by one member of a group, and offsets track progress per group.
Explain at-most-once, at-least-once and exactly-once delivery. How would you get effectively-once processing?
What good looks likeHide hint
Idempotent producers and transactions, committing offsets after processing, and idempotent consumers keyed on a business id.
How do you evolve message schemas without breaking consumers?
What good looks likeHide hint
A schema registry with compatibility rules, optional fields with defaults, never changing a field's meaning, and versioned topics for breaking changes.
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.
Tell me about a mistake you made at work and what happened next.
What good looks likeHide hint
Own it without blaming others, explain how you contained the impact, and what you changed so it would not happen again.
Tell me about a time you worked with unclear or changing requirements.
What good looks likeHide hint
Show how you reduced ambiguity: clarifying questions, writing down assumptions, small experiments and getting explicit sign-off.
Describe the most complex technical or analytical problem you have solved.
What good looks likeHide hint
Explain why it was hard, the options you considered, how you de-risked the chosen approach, and what you would do differently now.
Tell me about a time you worked closely with a team in another time zone or culture.
What good looks likeHide hint
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
8
in Data & AI
Hiring most for
- Other39
- Engineering28
- Sales & Marketing20
- Data & AI8
Read before the interview
Questions to ask them
- ›There are several open Data & AI 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?
- ›How does the team use ETL and Databricks today, and what would you like to change?
- ›What does success look like in this role after six months?
- ›What is the biggest challenge the team is facing this year?
Preparation checklist
0/7 doneSaved in this browser only.