Interview practice plan

Z

Data Engineer

ZEISS · Bengaluru

Data & AIMid level22 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

Skills we found in the job description. The plan below is built around them.

ETLDatabricksSQLAzureSparkData warehousingData modelingGitCI/CDTerraformKafkaIAMSupply chainProcurement

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.

01Required skill0/3

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 like

    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 like

    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 like

    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.

02Required skill0/3

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 like

    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 like

    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 like

    Read the execution plan, check stale statistics, missing or unused indexes, data growth and skew, parameter-sensitive plans, and locking.

03Required skill0/3

Azure

This role asks for Azure.

  • How would you organise Azure management groups, subscriptions and resource groups for several teams?

    What good looks like

    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 like

    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 like

    Compare operational effort, scaling model, execution limits, cost profile and team skills, and give a workload that fits each.

04Required skill0/3

Spark

This role asks for Spark.

  • What causes a shuffle, and how do you reduce its cost?

    What good looks like

    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 like

    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 like

    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.

05Required skill0/3

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 like

    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 like

    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 like

    A secrets manager or the platform's secret store, short-lived federated credentials, masking in logs, and never committing secrets to the repo.

06Required skill0/3

Kafka

This role asks for Kafka.

  • Explain topics, partitions, consumer groups and offsets in Kafka.

    What good looks like

    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 like

    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 like

    A schema registry with compatibility rules, optional fields with defaults, never changing a field's meaning, and versioned topics for breaking changes.

07Every 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 mistake you made at work and what happened next.

    What good looks like

    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 like

    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 like

    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

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 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 done

Saved in this browser only.

Interview prep: Data Engineer at ZEISS | LYDJ