Interview practice plan
Senior Software 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.
Sign in to see your gap areas first. We compare this role with the skills on your profile.
0 of 16 questions practised
Answer each one out loud, then tick it. Progress is saved in this browser only.
Agile
This role asks for Agile.
The team carries over stories every sprint. What do you do?
What good looks likeHide hint
Look at story size, work in progress, interruptions and dependencies, agree retro actions with owners, and track flow metrics such as cycle time.
How do you make retrospectives actually lead to change?
What good looks likeHide hint
Vary the format, focus on one or two actions with owners and dates, review last retro's actions first, and make it safe to speak honestly.
How do you coordinate several agile teams working on one product?
What good looks likeHide hint
A shared roadmap and dependency view, joint planning on a regular cadence, clear ownership boundaries, and lightweight rituals rather than heavy process.
CI/CD & IaC
This role asks for Git. These CI/CD & IaC questions cover the ground it builds on.
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.
The build takes 40 minutes. How do you bring it down?
What good looks likeHide hint
Measure where time goes, cache dependencies, parallelise and shard tests, only build what changed, and fix or quarantine the slowest tests.
Cybersecurity
This role asks for Cybersecurity.
Walk me through your response to a suspected compromised user account.
What good looks likeHide hint
Contain (revoke sessions and keys), scope using logs, eradicate, recover, communicate to the right people, and run a blameless review.
A scanner reports thousands of vulnerabilities. How do you prioritise them?
What good looks likeHide hint
Exploitability and exposure, asset criticality, known-exploited lists, compensating controls, and remediation SLAs by risk rather than raw severity.
How would you run a penetration test on a web application, from scoping to report?
What good looks likeHide hint
Rules of engagement and scope, reconnaissance, testing for auth, access control and injection issues, safe exploitation, and a report with clear risk and fixes.
System design
Senior engineering roles almost always include a design round. State requirements and rough numbers first, then walk through trade-offs.
Design a rate limiter for a public API.
What good looks likeHide hint
Compare token bucket, fixed and sliding windows; decide where it lives (gateway or service), how counters are shared across nodes, and how clients learn they are limited.
Design a payment service that must never charge a customer twice.
What good looks likeHide hint
Idempotency keys, a payment state machine, reconciliation with the provider, and at-least-once delivery with de-duplication rather than hoping for exactly-once.
Your service's p99 latency doubled after a release. Walk me through how you investigate.
What good looks likeHide hint
Check what changed, compare dashboards and traces, isolate by endpoint and dependency, roll back first if users are hurting, then find the root cause with profiling.
Behavioural
Every interview loop has a behavioural round. For senior roles, expect probing on influence without authority, judgement under pressure and raising the bar for others. 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.
Describe a time you had several urgent priorities at once. How did you decide what to do first?
What good looks likeHide hint
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 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
28
in Engineering
Hiring most for
- Other39
- Engineering28
- Sales & Marketing20
- Data & AI8
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?
- ›How does the team use Agile and Git 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/8 doneSaved in this browser only.