Interview experience
Siemens interview experiences covering Online Assessment, Technical MCQ Round, Technical Interview, HR Interview. Round-wise notes, common questions, and what candidates report clears each stage.
Siemens Interview Questions and Answers (2026)
Real Siemens interview questions for campus software, GTE core-engineering and Siemens EDA tracks - process, C++/OOP depth, and HR prep in one hub.
Siemens is a global industrial technology leader founded in 1847, building automation, energy, and digitalization solutions. In India, it hires graduate engineer trainees and software engineers across hubs in Bengaluru, Pune, and Gurugram. Siemens offers careers spanning industrial software, smart infrastructure, and engineering R&D.
Explore: Interview experience · HR interview questions · Overview · Placement papers · Preparation guide
Overview
Siemens runs a 4-round fresher loop with an unusually time-compressed aptitude section, splitting technical content across software (C++/OOP/DSA), core engineering (GTE), and Siemens EDA (VLSI) tracks depending on the role.
HR interview questions
Siemens HR interview questions with sample answer frameworks - motivation, relocation, STAR stories, and culture-fit prompts.
Siemens interview process at a glance
| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 45-60 min | Aptitude/logical/verbal MCQs (time-compressed) + 2 coding problems |
| Technical MCQ Round | 30-40 min | C++/OOP fundamentals, output prediction |
| Technical Interview | 30-45 min | CS fundamentals (OS/DBMS), puzzles, easy-medium DSA, project deep-dive |
| HR Interview | 20-30 min | Fit, offer discussion |
Siemens online assessment: quick answers
These answers are compiled from public candidate reports and prep guides, not from an official Siemens notice. Siemens hires through several entities (Siemens Technology/GTE, Siemens EDA, Siemens Healthineers, Siemens Ltd), each with its own test, so the instruction screen of your own test is the final word.
| Question | Answer |
|---|---|
| How many questions and how long? | It depends on the entity. FACE Prep’s software-oriented pattern is 30 technical questions in 30 minutes plus 24 aptitude questions in 18 minutes. A Siemens EDA intern test had 25 MCQs and 2 coding problems in 1 hour; a 2024 EDA software test had 42 MCQs in 1.5 hours; a 2021 Healthineers test had MCQs plus 2 coding problems in 60 minutes. |
| Does it have negative marking? | FACE Prep says there is none, but advises checking; no candidate report we read describes a penalty. Read your instruction screen. |
| Is there a sectional cutoff? | Not published. The aptitude block is very tight on time (about 24 questions in 18 minutes on the cited pattern), so accuracy under time pressure decides more than any single section. |
| What is the eligibility cutoff? | Reports differ. FACE Prep’s guide cites 7.5 CGPA with 60% in 10th and 12th and no active backlogs; other campus reports cite 7.0 CGPA or 70%, and a Siemens EDA intern drive asked for 7.0 CGPA and above. |
| Which platform is it on? | HackerEarth, in reports from Siemens GTE Pune (2024), a Siemens EDA intern drive and Siemens Healthineers. |
| Is there coding? | Usually 2 problems. Siemens GTE Pune (2024) had 2 medium problems on strings, bit manipulation and DP; the EDA intern test had one medium and one hard problem. |
| How many get through? | Few. One 2021 Healthineers drive shortlisted 35 and selected 7; a 2024 Hyderabad drive shortlisted 20 of 200 and selected 5. |
Siemens interview questions by track
The interview follows the entity and track. These are questions candidates have reported on GeeksforGeeks, LeetCode Discuss and Glassdoor; they show the level and style, not a fixed list.
| Track | Reported questions and topics |
|---|---|
| Siemens Healthineers (SDE) | Show OOP in practice using code from your own GitHub. A recursive phone-charging-time function. Largest number from digits without repetition, including the leading-zero edge case. Abstract classes in Java. Volatile vs non-volatile memory. Multithreading in practice. The clock-hands angle formula. |
| Siemens EDA (Noida, Bengaluru) | Reverse a linked list. Right view of a linked list. C++ STL hash map internals and collision handling. Binary search and array traversal. Design a buffer for a continuous data stream when the receiver accepts only 100 units. |
| Siemens Technology / GTE (Bengaluru, Pune) | A written test on your branch plus medium coding, then technical and HR rounds (2022). Array and string OA problems, DSA and aptitude (2026). Pune 2024 combined the technical and HR interviews. |
| Siemens Ltd core (electrical, ECE) | Measurement, electrical machines and power systems; core digital and analog electronics for ECE. |
Asked across every track: a project deep-dive, C/C++ pointers and virtual functions, OS, DBMS and networks basics, “Why Siemens?”, strengths and weaknesses, and your five-year plan.
Eligibility and locations (candidate-reported)
Public campus reports commonly mention 7.0+ CGPA as a baseline; some Siemens EDA drives shortlist higher (8.0 posted, 9.0+ actually interviewed on competitive campuses). Software and EDA loops often restrict to CSE/IT/ECE; GTE roles open to mechanical, electrical and automation branches. Interview hubs cited repeatedly include Bengaluru, Pune, Gurugram, Hyderabad and Noida; HR panels also ask about plant-site relocation (Nashik, Aurangabad and similar) for core-engineering paths. Confirm branch, CGPA cut-off and entity (STS, EDA, DISW) in your invite mail before you pick a prep track.
Online Assessment
A standard aptitude/logical/verbal section is paired with 2 coding problems, but candidate reports consistently flag the aptitude portion as unusually tight on time - some drives give as little as ~18-20 minutes for around 24 questions, so accuracy under time pressure matters more than in a typical campus OA.
Common questions
- Quantitative aptitude and logical reasoning under a tight per-question time limit
- Verbal ability - reading comprehension, sentence correction
- 2 coding problems, typically easy-medium difficulty (arrays, strings, basic logic)
Technical MCQ Round
A dedicated MCQ round on C++ and object-oriented programming, heavy on output-prediction questions rather than open-ended coding.
Common questions
- Predict the output of a C++ snippet involving constructors/destructors or operator overloading
- Polymorphism, virtual functions, and inline functions in C++
- Differences between compile-time and run-time polymorphism
Technical Interview
Covers CS fundamentals (OS, DBMS), logic puzzles, easy-medium DSA, and a detailed walkthrough of your resume project - the role and technology you actually used, not just the outcome. Core-engineering (GTE) drives substitute domain engineering topics for some of this; Siemens EDA drives add VLSI/digital-design questions.
Common questions
- OS fundamentals - process scheduling, memory management, deadlock
- DBMS basics - normalization, joins, transactions
- Easy-medium DSA - queues, binary search, and similar patterns
- Classic logic puzzles
- Detailed questions on your project’s technology stack and your specific contribution
- Domain-engineering fundamentals for your discipline (GTE/core-engineering drives) or VLSI/digital-design basics (Siemens EDA drives)
Round-by-round candidate write-ups are on the Siemens interview experience page.
HR Interview
A closing 20-30 minute round on fit, motivation, and offer discussion.
Common questions
- Tell me about yourself and why Siemens
- Siemens hires across both software and core engineering roles - how would you explain your project to someone from a different engineering background?
- Tell me about a time you had to debug or troubleshoot a technical issue under time pressure
- Location flexibility and long-term career plans
Sample answer frameworks for each of these are on the Siemens HR interview questions page.
Why the track split (software vs GTE vs EDA) matters
Siemens hires across genuinely different businesses in India - software/IT, core engineering (Graduate Trainee Engineer roles in mechanical, electrical, and automation), and Siemens EDA (semiconductor design-software, a track closer to a chip company than an industrial one). The C++/OOP/DSA loop described above is the software-track default; GTE and EDA drives swap parts of that content for domain engineering or VLSI/digital-design questions respectively. Confirm which track your specific drive or req falls under before deciding where to focus prep time.
Common technical interview questions and answers
Q: What is the difference between compile-time and run-time polymorphism in C++?
Compile-time polymorphism is resolved by the compiler and covers function overloading, operator overloading, and templates - the correct function is chosen from the static types of the arguments, so there is no dispatch cost at run time. Run-time polymorphism uses virtual functions: the compiler gives each polymorphic class a vtable of function pointers and each object a hidden vptr, so a call through a base pointer or reference jumps to the derived override decided by the object’s dynamic type. Overloading differs in signature within the same scope; overriding keeps an identical signature in a derived class and requires the base function to be virtual. Marking the override with the override keyword makes the compiler catch a mismatched signature that would otherwise silently create a new function.
Q: Why does a base class with virtual functions need a virtual destructor?
If you delete a derived object through a base-class pointer and the base destructor is not virtual, the behaviour is undefined and in practice only the base destructor runs, so derived members leak. Declaring the base destructor virtual makes deletion dispatch through the vtable, running the derived destructor first and then the base destructor in reverse construction order. The rule of thumb is that any class intended to be used polymorphically needs either a public virtual destructor or a protected non-virtual one. The cost is that adding the first virtual function gives every object a vptr, so a tiny value type used in a large array should not be made polymorphic casually.
Q: What does the inline keyword actually do in C++?
inline is a request, not a command - it hints that the compiler may substitute the function body at the call site to avoid call overhead, and modern compilers make that decision on their own based on size and call frequency. Its real, guaranteed effect is on linkage: it relaxes the one-definition rule so an identical function definition can appear in multiple translation units without a duplicate-symbol error, which is why header-defined functions and member functions defined inside a class body are implicitly inline. Aggressive inlining of large functions bloats the instruction cache and can make code slower. Debugging is also harder because inlined frames may not appear in a stack trace.
Q: Implement binary search and state its complexity and its classic bug.
Keep two indices low and high over a sorted array, compute mid, and compare the element at mid to the target: if equal you return mid, if the element is smaller you set low to mid plus one, otherwise you set high to mid minus one, looping while low is at most high. Time is O(log n) and space is O(1) for the iterative form. The classic bug is computing mid as (low + high) / 2, which overflows a 32-bit int for large indices - write low + (high - low) / 2 instead. The second common bug is an off-by-one that makes the loop condition never terminate, which is why you should trace a two-element array out loud.
Q: How would you implement a queue using two stacks?
Keep an input stack and an output stack. Push always goes onto the input stack in O(1). For pop or peek, if the output stack is empty, move every element from input to output one at a time, which reverses the order so the oldest element ends up on top, then pop from output. Each element is pushed and popped at most twice across its lifetime, so the amortised cost per operation is O(1) even though a single pop can cost O(n). Total space is O(n), and the mistake to avoid is transferring elements back on every operation, which makes it O(n) per call.
Q: Explain 1NF, 2NF, and 3NF with an example.
1NF requires atomic column values and no repeating groups - a single phone_numbers column holding a comma-separated list violates it, so the phone numbers move to their own table. 2NF applies when the primary key is composite and requires every non-key column to depend on the whole key, not part of it: in an OrderItem table keyed on order_id plus product_id, storing product_name breaks 2NF because the name depends only on product_id. 3NF removes transitive dependencies - keeping both employee_dept_id and dept_name in the Employee table breaks it, since dept_name depends on dept_id rather than on the employee key. Normalisation removes update anomalies, but production reporting schemas often denormalise deliberately to avoid join cost.
Q: What are the ACID properties of a transaction?
Atomicity means a transaction either commits fully or leaves no trace, implemented by an undo log or rollback segment. Consistency means the database moves from one valid state to another with all constraints, keys, and triggers satisfied. Isolation means concurrent transactions do not observe each other’s partial work, controlled by isolation levels - READ COMMITTED still permits non-repeatable reads, REPEATABLE READ still permits phantoms in some engines, and SERIALIZABLE prevents both at higher locking cost. Durability means a committed transaction survives a crash, which engines achieve by write-ahead logging that flushes the log record to disk before acknowledging the commit.
Q: What is the difference between paging and segmentation in an operating system?
Paging splits the virtual address space into fixed-size pages mapped to equally sized physical frames through a page table, so external fragmentation disappears but the last page of each region wastes space internally. Segmentation splits memory into variable-length logical units such as code, stack, and heap, which matches program structure and eases protection but reintroduces external fragmentation. A page fault occurs when a referenced page is not resident, and the OS picks a victim frame using a replacement policy such as LRU or clock, writing it back if it is dirty. Thrashing is the pathological case where the working set exceeds physical memory and the system spends nearly all its time on page faults.
Frequently asked questions about Siemens interviews
Does the Siemens online test have negative marking?
FACE Prep says there is no negative marking, and no candidate report we read describes one, but the test changes by Siemens entity, so check the instruction screen; the cited software pattern is 30 technical questions in 30 minutes plus 24 aptitude questions in 18 minutes.
Which platform does Siemens use for its online test?
HackerEarth, according to candidate reports from Siemens GTE Pune (2024), a Siemens EDA intern drive and Siemens Healthineers. Most of these tests pair MCQs with 2 coding problems.
What is the Siemens interview process for freshers?
Siemens typically runs 4 rounds for freshers: 1. An Online Assessment (45-60 minutes) - aptitude, logical reasoning and verbal MCQs (often ~24-28 questions with tight per-question time limits) plus 2 coding problems. 2. A Technical MCQ round (30-40 minutes) on C++/OOP fundamentals and output prediction. 3. A Technical Interview (30-45 minutes) covering CS fundamentals (OS, DBMS), puzzles, easy-medium DSA, and project discussion. 4. An HR round (20-30 minutes) on fit and offer discussion. Timeline: 1-3 weeks, sometimes with rounds 3-4 on the same day.
Is Siemens’s interview different for software roles vs core engineering (GTE) roles?
Yes. Software-track candidates get the standard OA-plus-C++/OOP-plus-DSA loop described above. Graduate Trainee Engineer (GTE) roles for core disciplines (mechanical, electrical, automation) substitute domain engineering questions for some of the CS-heavy content, while Siemens EDA (its semiconductor design-software arm) roles lean further into VLSI and digital-design fundamentals instead of general software DSA. Confirm which track your drive covers before you prep.
What questions are asked in Siemens interviews?
Expect aptitude/logical/verbal MCQs, C++/OOP questions (polymorphism, inline functions, output prediction), CS fundamentals (OS, DBMS), puzzles, easy-medium DSA (queues, binary search), and detailed questions about your role and the technology used in your projects. Core-engineering drives (Graduate Trainee Engineer roles) substitute domain engineering questions for some CS topics, and Siemens EDA roles lean into VLSI/digital design instead.
How many rounds are there in the Siemens interview?
Most freshers go through 4 rounds: Online Assessment, Technical MCQs, a Technical Interview, and an HR round. The exact mix depends on whether you’re interviewing for a software role, a core engineering (GTE) role, or Siemens EDA. Some drives compress rounds 3 and 4 into the same day.
How should I prepare for Siemens interviews?
Revise C++/OOP fundamentals and output-prediction style questions, practice easy-medium DSA and puzzles, and be ready to discuss your project’s technology stack and your specific contribution in detail. Since Siemens hires across both software and core engineering (mechanical/electrical/automation) roles, practice explaining your project to someone from a different engineering background.
How time-pressured is Siemens’s online assessment?
Very tight. Candidate reports describe an aptitude section - as few as ~18-20 minutes for around 24 questions in some drives - so speed and accuracy under pressure matter more than depth here. The coding portion (typically 2 problems) is comparatively more generous on time; treat the aptitude section as a speed drill and practice it under a strict timer beforehand.
What Siemens interviewers score
Industrial software / embedded / digitalization roles mix domain fundamentals with coding depth that varies by BU. Interviewers score:
- Role-correct technicals - embedded/C, automation, or full-stack per the posting.
- Safety and quality mindset - testing, standards awareness at fresher depth where relevant.
- Global-delivery logistics - relocation, German/India hub clarity, long-term learning plan.
Soft fail modes: generic IT-services answers for an engineering BU, or resume tools you cannot explain.
How do Siemens EDA software interviews differ from industrial automation roles?
Siemens EDA / software campus loops emphasise C/C++ OOP, DSA, OS/DBMS, and project depth (sometimes without a separate HR round). Automation or core engineering postings lean toward PLC/SCADA/control fundamentals and troubleshooting. Read your invite’s BU name before you over-prep the wrong syllabus.
How to prepare for Siemens interviews
- Loop map: Online Assessment; Technical MCQ Round; Technical Interview; HR Interview. Confirm timings from the drive mail.
- Technical depth: Drill the Q&A section until answers are spoken, not read. Know every resume project cold.
- Experiences: Study round-wise notes on the interview experience page - real prompts beat generic lists.
- HR: Three STAR stories + a specific “Why Siemens?” on the HR page.
Who usually fits and who struggles
Good fit: You can dry-run C on paper (software) or defend 2-3 branch domains (GET), and you have a 60-second Why Siemens that names a division, not “I like Germany.”
Harder path: You only practiced CAT; you freeze without an IDE; you refuse the city on the letter after ticking “any location.” A high CGPA with weak pointers dies in 30 minutes. A mid CGPA with clean tracing and one project sketch often survives.
A practical Siemens prep plan
Use this as a default four-week loop before a Siemens drive. Adjust to your invite timeline.
- Week 1: Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Siemens previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
- Week 2: Most Siemens drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
- Week 3: Technical interviews at Siemens usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Siemens?” with one concrete product, lab, or business line - not a slogan.
- Week 4: Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
10-day crash version: Days 1-4 timed DSA, days 5-7 resume projects + CS fundamentals, days 8-9 mock interviews out loud, day 10 HR STAR stories on the HR page.
Compensation notes
Candidate-reported fresher/early-career packages for Siemens often cite ₹7-14 LPA. Treat forum numbers as ranges, not guarantees - confirm the written offer letter for your team and location.
Sources
Interview process details and sample questions on this site are editorially organized from public candidate reports and hiring write-ups, with round structure, prep notes, and company-specific framing added by our team. For round-by-round stories, see the Siemens interview experience page. For OA papers and coding drills, use Siemens on placementpapers.app. OA quick answers and track-wise questions draw on FACE Prep’s Siemens recruitment guide, GeeksforGeeks interview experiences for Siemens EDA SDE intern and Siemens Healthineers 2021 drives, LeetCode Discuss posts on Siemens GTE and EDA, and Glassdoor candidate reviews.
Also prepare for
Guides often searched alongside this page: bosch interview questions · honeywell interview questions · abb interview questions · larsen-toubro interview questions.