Candidates describe Siemens software engineer interviews as three to four stages: technical rounds on OOP and language fundamentals, a managerial conversation, and HR. Resume and project depth come up often.
$128K
Avg. Base Comp
$160K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Siemens software engineer roles describe a process that tests fundamentals more than heavy algorithms. Object-oriented programming is the most common topic. Reports mention polymorphism, design patterns and class design for related shapes such as a rectangle and a square. One candidate also got a SOLID question: name the principle a code snippet violated and explain how to fix it.
The language focus depends on the team. Individual candidates report Java with Spring Boot and Hibernate, including a question on handling a Spring Boot migration. Others report C++ with small programs to explain concepts, C# for OOP and SOLID questions, and Python scripting for a testing-oriented role. Coding questions are usually described as easy to medium, such as string and array problems, finding the second-largest number in an array, and LeetCode-style questions. One candidate's second technical round was more demanding, with three coding problems plus Docker, Kubernetes and SQL queries.
Project discussion appears in many accounts. Interviewers asked candidates to walk through resume projects and probed what they had actually built and why they made certain choices, so be ready to explain your own work in detail. Some reports also mention aptitude and logic puzzles, an estimation question about piano tuners, and core topics such as DBMS, networks and data structures.
Most reports describe a managerial round and an HR round after the technical stage. The managerial round was conversational in some accounts, covering past experience and expectations for the role. One candidate cleared the technical rounds but was not selected after the managerial conversation. In one account, the HR call covered salary, availability and a pre-employment medical checkup. Outcomes in the reports are mixed, so preparing for both fundamentals and project depth is the safest approach.
Synthesized from 57 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 Siemens process.
My whole interview was a single 30-minute behavioral conversation, and it was far more about me than about code. Most of the time went to my background and the items on my resume, along with the question of why I was interested in engineering in the first place. I'd recommend preparing a clear, concise walkthrough of your past projects and being ready to explain your decisions in plain language. There were only a couple of technical questions, and they were open-ended rather than hard. The overall feel was casual, so I went in focused on telling my story well rather than cramming problems. I accepted the offer after that.
Prep tip from this candidate
Be ready to walk through your resume and explain your projects and your interest in engineering, since that made up most of the conversation. The technical questions were light and open-ended, so focus on explaining fundamentals clearly instead of memorizing problems.
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 Siemens
Given an integer N, write a function that returns all of the prime numbers up to N
| Question | |
|---|---|
| Size of Joins | |
| The Brackets Problem | |
| Real-Time Transaction Streaming | |
| Find Duplicate Numbers in a List | |
| Hurdles In Data Projects | |
| Multi-Reaction | |
| RAG Strict Source Control | |
| Worker Distribution Dilemma | |
| The Pirate’s Hunt | |
| Gas Station Counting | |
| Safe Deployments | |
| Fixed-Length Arrays: Deletion | |
| Text Editor With OOP | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Bagging vs Boosting | |
| Level Of Rain Water In 2D Terrain | |
| Cyclic Detection | |
| Longest Increasing Subsequence | |
| Term Frequency | |
| Merge N Sorted Lists | |
| Seller Type Modeling | |
| Offer Matching API Design | |
| Search Timeout | |
| Loan Model | |
| Solo ML Deployment | |
| String Palindromes |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. Some describe an online or on-site test covering aptitude and topics such as DBMS, networks and OOP, with one reporting same-day results. Another describes a short video screen about their background, projects and scripting experience. The opening may depend on the team and hiring route.
Candidates typically describe easy-to-medium coding alongside OOP and language fundamentals. Reported topics include Java, Spring Boot, Hibernate, C++, C# and data structures. Interviewers often tie questions to projects on the resume, so expect to explain design decisions and what you personally built.
One candidate describes a second technical interview that was broader than the first, with three coding problems, Docker and Kubernetes, and writing database queries. Another reports two technical rounds focused on OOP, SOLID principles and string and array coding. The focus varies by team and role.
Several candidates report a manager conversation after the technical stage. Reported topics include previous job experience and what you expect from the new role. Tone was described as conversational rather than a technical drill. One candidate cleared the technical rounds but was not selected after this round.
Candidates typically describe a final HR conversation. Reported topics include salary negotiation, availability date and a pre-employment medical checkup. One candidate described the process as moving smoothly from one stage to the next.
