Typical process:
First, talk with a recruiter, then the hiring manager over the phone, followed by an on-site interview with 4-5 engineers. It was an easy interview compared to other tech companies that ask Google-style algorithms and coding questions. However, it may have been too easy – there was no way to showcase my technical breadth and depth, or my full capabilities. It felt like they just wanted to hire based on resumes and pick someone who could code and fit their "flavor."
They offered me the position after a week or two with a below-market salary and hoped I would accept right away. I tried to negotiate for a higher level and waited. After a week, they said "no" and judged that I didn't like the team. Actually, I feel I could contribute a lot to their ongoing projects and augment their current skill set, but unfortunately, there was no deal.
On my interview day, I talked with each of the senior engineers on the team for about half an hour. There was no chance to speak with the hiring manager, nor a follow-up phone interview with the director of engineering. It felt like the interviews were not organized very well; I wasn't getting enough information about them, and they didn't get to know my depth.
Does program execution go through the finally block if there is a return statement in the try block?
The following metrics were computed from 1 interview experience for the Siemens Staff Software Engineer role in United States.
Siemens's interview process for their Staff Software Engineer roles in the United States is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very negative feelings for Siemens's Staff Software Engineer interview process in United States.