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 design a pipeline that can be safely re-run for a past date?

    What good looks like

    Idempotent writes via partition overwrite or merge on keys, deterministic inputs, no side effects outside the target, and a backfill procedure.

  • 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.

  • What is incremental loading, and how would you implement change data capture?

    What good looks like

    Load only new or changed rows using watermarks or log-based CDC, handle deletes and updates, and reconcile counts periodically.

02Required skill0/3

SQL

This role asks for SQL.

  • Find users who were active on at least three consecutive days.

    What good looks like

    A gaps-and-islands pattern: subtract ROW_NUMBER() from the activity date, group by user and that difference, and count.

  • 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.

  • Compute a 7-day rolling average of daily revenue, including days with no sales.

    What good looks like

    Build a calendar of dates, LEFT JOIN the sales, fill missing days with zero, then AVG over ROWS BETWEEN 6 PRECEDING AND CURRENT ROW.

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.

  • How would you build a secure pipeline that deploys infrastructure and apps to Azure?

    What good looks like

    Federated workload identity instead of stored secrets, Key Vault, environment approvals, infrastructure as code with Bicep or Terraform, and policy checks.

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.

  • Blue-green, canary or rolling deployment: how do you choose?

    What good looks like

    Blast radius, rollback speed, infrastructure cost and how good your metrics are for judging a canary. Give a case for each.

  • The build takes 40 minutes. How do you bring it down?

    What good looks like

    Measure where time goes, cache dependencies, parallelise and shard tests, only build what changed, and fix or quarantine the slowest tests.

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.

  • A consumer group is lagging badly. How do you diagnose and fix it?

    What good looks like

    Check lag per partition, slow processing versus too few partitions or consumers, rebalancing storms, and batching or scaling out.

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.

  • Tell me about a time you had to learn something new quickly to deliver on a deadline.

    What good looks like

    Name the specific gap, show how you learned (sources, people, practice) and quantify what you shipped. Interviewers want a repeatable learning method, not heroics.

  • 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.

  • Describe a time you had several urgent priorities at once. How did you decide what to do first?

    What good looks like

    Explain your criteria (impact, deadlines, dependencies), how you communicated the trade-offs, and what you deliberately dropped or delayed.

  • Describe the most complex technical or analytical problem you have solved.

    What good looks like

    Explain why it was hard, the options you considered, how you de-risked the chosen approach, and what you would do differently now.

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