Siemens Interview Experience | Set 2 (For System Engineer)
Interview Experience
Applied through college. The process took 2 days. I was interviewed at Siemens (Chennai) in October 2016.The hiring process was done in four rounds:Round 1 (Programming Ap...
Full Details
Applied through college. The process took 2 days. I was interviewed at Siemens (Chennai) in October 2016. The hiring process was done in four rounds: Round 1 (Programming Aptitude) - This was completely based on C++, easy enough. Knowledge of other languages won't be enough as the questions were very specific. Round 2 (General Aptitude) - 3 sections consisting of 15 questions each (Numerical, Verbal and Logical). All sections were quite challenging given the limited time (time limit for every question). The numerical section required some knowledge of statistics. Round 3 (Technical Interview) - Tests your basic knowledge of computer science concepts (be prepared to write moderate algorithms). Topics consists mainly OOPs concepts, UML, SDLC, Puzzles. The interview went on for 50 mins(approx.) Round 4 (HR interview) - The HR asked about projects, other interests, family background. He specifically inquired about my plans for further studies. He also asked how I viewed the tech industry and current challenges. Went on for 25 mins(approx.)
About This Question
This is a candidate experience report from a siemens interview for a swe role during the phone screen round reported in 2016.
It covers the following topics: Probability Stats .
Difficulty rating: Easy
Topics
More Siemens Interview Questions
About Siemens Interview Reports
This question was reported by a candidate who interviewed at Siemens. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Siemens are the higher-signal extractions to take from this report.
For broader preparation context, the Siemens interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Siemens reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Siemens Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Siemens reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.