When I recently cracked my Siemens interview, I knew I didn’t want to just list questions and answers. I wanted to share the entire experience — the atmosphere, the type of conversations that happen, and the lessons I carried from it.
This post is not a “cram before your interview” guide. It’s a reflection from one student to another — an honest look at what the process felt like and what really matters.
Technical Interview — Round 1
The first round was conducted by a panel of three interviewers, two of whom were actively involved in asking questions. What stood out immediately was how conversational it felt. It wasn’t an interrogation but a genuine discussion around what I knew and how I thought.
- The Introduction
The interview began with a simple “Tell me about yourself.”
It’s a standard question, but it sets the tone. I made sure to keep it real — confidently walking them through my journey rather than memorizing a script.
- Project Discussion
Next, they asked me to explain the project I was most proud of. I shared my screen and walked them through the architecture, workflow, and challenges.
What they really looked for wasn’t how big or complex the project was, but how deeply I understood it. They checked whether I had actually built it, explored alternatives, and thought through real-world use cases.
It was clear that depth mattered more than breadth.
- Database Management
Since I had used MongoDB in my project, the questions went in that direction.
They asked about the difference between authentication and authorization, ACID properties, how MongoDB handles transactions, and how I connected it to the backend in JavaScript.
We also discussed HTTP request types and how I implemented them within my project.
- Object-Oriented Programming
They shifted to OOP concepts next — asking me to first explain OOP to a non-technical person, and then to a technical one. From there, they dived deeper into inheritance, polymorphism, abstraction, and encapsulation.
To make it more relatable, I used an analogy of a College–Department–Student structure, which they appreciated.
- Data Structures and Algorithms
This section began with the Leetcode “Two Sum” problem. I first described the brute-force approach, then optimized it with the two-pointer technique, and finally presented the O(N) solution using a hashmap.
We also discussed sorting algorithms and their complexities. I went a bit further to explain how the STL sort function works internally — and that caught their attention since few candidates talk about library internals.
- Aptitude Questions
Then came a few logical and aptitude problems. These tested reasoning more than formulas:
Using 3-liter and 5-liter buckets to measure exactly 4 liters.
A scooter running on 2 tyres at a time with 3 tyres available, each lasting 5 km — finding the maximum distance.
Converting 600 meters in 5 minutes to km/h.
Finding how many small cubes remain unpainted when a 3×3×3 cube painted white on the outside is divided into 27 smaller cubes.
Each problem was less about math and more about structured problem-solving.
- General Questions
Finally, they asked about my family, background, and hobbies. When they asked if I had any questions for them, I made sure to ask about Siemens’ tech stack and the structure of their internship program.
What I Learnt from the Technical Round
This round taught me several key lessons:
Turn interviews into conversations, not monologues.
Interviewers are there to select, not reject.
Don’t hesitate to ask for hints or clarifications.
Stay calm and composed — outcomes follow preparation.
Be honest if you don’t know something; never bluff.
Perfect English is not the goal — clarity and confidence are.
Let them see your thought process, not just your memory.
HR Round — The Techno-HR Mix
The final round was a blend of technical and HR discussions. There were two interviewers: one focused on technical details while the other explored my personality, opinions, and background.
Topics Covered
Self-Introduction
They revisited my academic journey — JEE/CET scores, why I chose engineering, and specifically why I opted for IT/CS. They also asked about my college and future plans, including whether I planned to pursue an MS.
Project Discussion
They cross-examined my projects again, questioning my design choices and asking whether my project could scale across multiple pages. They also pushed me to think about why I chose certain tools and whether I had considered alternate solutions.
General Questions
The questions shifted toward general awareness and personality:
My opinion on AI and whether it will replace developer jobs.
Differences between Python and C++.
Whether Python is compiled or interpreted.
My projects in C++, Java, and Python.
Finally, they asked if I had any questions for them. I asked about their internal tech stack and the skills I should work on before joining.
Their last question was direct: “Are you confident you’ll be selected?”
I answered honestly and confidently — and that was the end of the process.
What They Were Really Looking For
Looking back, the qualities they seemed to value most were:
Authenticity: Are you genuine or rehearsed?
Reliability: Can they trust you to deliver what you promise?
Confidence: Do you back your ideas without arrogance?
Depth: Do you understand your work beyond surface-level?
Teamwork: Can you collaborate effectively?
Learnability: Are you open to feedback and growth?
Attitude: Do you display a growth mindset?
Character: Do you take responsibility for mistakes and learning?
My Final Takeaways
If you’re preparing for Siemens or any similar company, here’s what I’d emphasize:
Be trainable — companies look for potential more than perfection.
Prepare a clear system architecture diagram for your full-stack projects.
Always understand the “why” behind your answers and projects.
Remember, they can teach you technology, but not attitude.
It’s okay to think differently — stand out by being yourself.
Above all, be real.
Every interview is a chance to learn, not just to get selected. The more honest and curious you are, the better impression you leave.
This was my Siemens interview experience. I hope it helps others preparing for their interviews. If you have questions or want to share your journey, feel free to drop a comment below — I’d love to hear your story too.
You can also read the original Medium version of this article here:
👉 My Siemens Interview Experience — Honest Reflections, Learnings & Tips (on Medium)
Top comments (0)