Siemens Gamesa logo

Siemens Gamesa Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 10 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
70% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Siemens Gamesa.

Showing 3 of 10
Siemens Gamesa logo
Siemens Gamesa

Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Behavioral

It was campus Recruitment with 3 stages Written +Technical+HR Written consists of Basic Aptitude questions with Respective Engineering questions Technical interview went around 1hour30 minutes and HR went around 45-50 minutes

Confirmed questions8 questions
  • Could you start with a basic introduction about yourself?
  • If you have prior job experience, could you explain it?
  • Tell me about your course projects.
Siemens Gamesa logo
Siemens Gamesa

Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Behavioral

firstly data acquestion send to me a email and then lead engineer and manager with interview and operational question and then my answer generally this type. some problems for my information about grid and wind turbine. and generally this type.

Confirmed questions3 questions
  • Can you tell me about your knowledge of grids and wind turbines?
  • Could you describe some electrical issues you have dealt with?
  • What operational topics are you familiar with?
Siemens Gamesa logo
Siemens Gamesa

Lead Engineer

Engineering · more than a year ago

Lead Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Coding

I was contacted by a recruiter for a loads position. They confirmed twice that it was for load physics/calculations, not software development. I was surprised there was no preliminary phone interview as I had requested. I was asked to come to the Bangalore office. Within the first 5 minutes of arriving, I found out the role was actually for tools and software development, not loads platform/physics, which is not my area of expertise or interest. I decided to withdraw my candidacy immediately. I asked why this discrepancy happened and why I was shortlisted when my resume doesn't show a development background. It seemed like they just needed to conduct interviews. I learned it was a new team with new leadership, so these mistakes might be expected. They made me sit for an hour to answer questions with little engineering impact, which is not typical for a senior role. The discussion covered many disciplines, which I could handle. Their objective seemed to be to find fault with my interview, which felt like a condescending approach. It didn't make sense to waste everyone's time. I've never interviewed anyone like that; it reflects poorly on leadership, unlike my current company. My current manager is a great leader, and I was only looking to switch for other reasons. Two months later, I'm still chasing the HR person for travel reimbursement, which is guaranteed for interviewees who travel. They keep giving excuses like the Siemens-Gamesa merger is causing delays. Such a weak reason. I can handle rejection, but this whole process was strange. It seems I dodged a bigger bullet.

Confirmed questions1 question
  • Given 10 coding questions in C/C++

Siemens Gamesa Engineer Interview Questions

Quoted word for word from Siemens Gamesa interview reports.

What are the electrical standards and grid codes used in North America?

Read reports

Can you answer questions about battery requirements in substations?

Read report

Can you tell me about your knowledge of grids and wind turbines?

Read report

Formats, difficulty and experience

Across all 10 Siemens Gamesa interview reports.

Interview formats

Technical 42.1%
Behavioral 42.1%
Presentation 5.3%
Group 5.3%
Coding 5.3%

Interview difficulty

Easy 0%
Average 80%
Difficult 20%

Candidate experience

Negative 30%
Positive 70%