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.
How do you detect and handle bad data arriving from an upstream source?
What good looks likeHide hint
Schema and data-quality checks (nulls, ranges, row counts, freshness), quarantining bad rows, alerting, and a data contract with the producer.
Batch or streaming: how do you decide for a new use case?
What good looks likeHide hint
How fresh the data must be, cost and operational complexity, late data handling, and whether micro-batches are good enough.
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.
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.
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.
A query that used to take 2 seconds now takes 2 minutes. How do you debug it?
What good looks likeHide hint
Read the execution plan, check stale statistics, missing or unused indexes, data growth and skew, parameter-sensitive plans, and locking.
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.
How do managed identities work, and why are they better than storing connection strings?
What good looks likeHide hint
Azure issues and rotates credentials for the resource, removing secrets from config; grant the identity least-privilege roles on targets.
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.
Spark
This role asks for Spark.
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.
When would you use repartition versus coalesce?
What good looks likeHide hint
repartition does a full shuffle to increase or rebalance partitions; coalesce merges partitions without a full shuffle, useful before writing fewer files.
How do you choose file format and partitioning for a large data lake table?
What good looks likeHide hint
Columnar formats such as Parquet or Delta, partition by commonly filtered low-cardinality columns, avoid small files with compaction, and use clustering for selective filters.
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.
Describe a piece of feedback that changed how you work.
What good looks likeHide hint
State the feedback, your honest first reaction and the concrete behaviour you changed. Close with evidence that the change stuck.
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.
Walk me through a project you are proud of and your specific role in it.
What good looks likeHide hint
Separate "we" from "I". Cover the problem, the decisions you personally made, the trade-offs, and a measurable result.
Tell me about a time you disagreed with a teammate or your manager. How did it resolve?
What good looks likeHide hint
Show that you disagreed on substance with evidence, listened properly, and committed once a decision was made, even if it went the other way.
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.