I had an interview scheduled by a consultancy via Naukri.com.
After confirming, the interview was scheduled for three days later.
It was a face-to-face technical round and started on time.
This felt like an interview for someone with 5+ years of experience, heavily focused on C# syntax. There was no discussion of:
I could sense the nature of the work based on the interview, but life is like that.
What is your daily routine in the office and your roles/responsibilities?
Do you know design patterns?
Which tools do you use for design and architecture? What types of diagrams are there, and what are the differences between Sequence diagrams and Use Case diagrams?
Write a Singleton class.
Surprisingly, there were no further design principles or OOPs concepts. Back to C# syntax, I was like, "Are you kidding me?"
One array problem: remove an item from the first position and add it to the last, five times.
The following metrics were computed from 1 interview experience for the Siemens .NET Lead role in Bengaluru, Karnataka.
Siemens's interview process for their .NET Lead roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Siemens's .NET Lead interview process in Bengaluru, Karnataka.