Three candidates describe ZF software and engineering interviews with technical screens on C, Python, embedded or control concepts, and Kubernetes, and two also report an HR conversation. All three report receiving offers.
$113K
Avg. Base Comp
$130K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
ZF software interviews appear to vary by team, so match your preparation to the job description. One candidate for a Software Engineer role in the automotive braking division reports a two-round process over Teams: a technical screen, then a short HR call. The technical round covered C and Python coding questions, including when to choose one over the other and why C matters in embedded work. It also included logic and mathematical reasoning questions. That candidate says interviewers cared more about how they reasoned than about a perfect answer, and rated the difficulty as intermediate.
A second candidate, whose listing was a junior role, describes a more control-systems-oriented path. It began with an online multiple-choice assessment of about an hour on C fundamentals, electronics, open-loop versus closed-loop systems, and timers and counters. A web-call interview followed, which included an English self-introduction and questions about hands-on work with vibration and acceleration measurements. This candidate also reports long waits between stages.
A third candidate, on a more cloud and infrastructure-focused team, reports a recruiter call, a conversation with the team leader, and two further rounds with team members and a product manager. The technical questions covered writing and explaining a Python script, Kubernetes, cloud providers, and Git. The HR round asked why they wanted to leave their current role and about salary expectations.
All three report offers. Practice explaining your code aloud, prepare concrete examples of hardware or infrastructure work, and have a thoughtful answer to why you want to move.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Zf Group process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Zf Group
Design a data warehouse for a new online retailer
| Question | |
|---|---|
| Bagging vs Boosting | |
| The Brackets Problem | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Ticket Agent Analysis | |
| Target Indices | |
| Transformer Encoder Layer | |
| FAQ Matching | |
| Duplicate Rows | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Search Timeout | |
| Matrix Multiplication | |
| Cloud-Agnostic Deployments | |
| String Palindromes | |
| Client Solution Pushback | |
| Testing Constraints | |
| International e-Commerce Warehouse | |
| Why Do You Want to Work With Us | |
| Decreasing Tech Debt | |
| Payment Data Pipeline | |
| Your Strengths and Weaknesses | |
| Processing Large CSV | |
| Evaluate News | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a LinkedIn recruiter reaching out the day after posting a resume, followed by an introductory call that covered the role. Other candidates do not describe this step, so it may depend on the team and how you are sourced.
One candidate for an embedded and control-systems role reports an online multiple-choice test of roughly an hour. It covered C fundamentals, electronics, open-loop versus closed-loop control, and timer and counter functionality. Other candidates did not mention an assessment, so it may not apply to every role.
Candidates report technical conversations tied to the job description. Topics include comparing C and Python for embedded work, logic and math reasoning, hands-on vibration and acceleration experience, and writing a Python script, plus Kubernetes, cloud providers and Git. Interviewers reportedly valued reasoning and concrete experience over perfect answers.
One candidate reports meeting the team leader, then team members and a product manager in two further rounds, where the team's activities and areas of work were explained. This structure is reported by only one candidate, so confirm your own schedule with your recruiter.
Candidates report an HR conversation covering background, interests, culture fit, why they were leaving their current role, and salary expectations. All three candidates report receiving offers, and one describes the offer coming shortly after the HR call. Timing between stages varied by candidate.
