Wind Turbine Mechanical Engineer Interview Questions

The interviewer wants to see that you can take a collector system from turbine layout to substation and explain the trade-offs. Walk through the design in order: gather the layout, turbine ratings and site conditions; choose the voltage, often 34.5 kV in the US; group turbines into feeder circuits; size cables or conductors for current, voltage drop and losses; and plan grounding, protection and the route to the substation. Say when you would choose overhead lines over underground cable.

Sample answer: "I start with the turbine layout and the substation location. I group turbines into radial feeders so each circuit stays within its cable rating, then size each segment for ampacity, voltage drop and losses, using soil thermal resistivity from the geotechnical report. Underground cable is my default for most of a site, but on long runs across rough ground I compare an overhead line, which can cost less but may need more permitting. I finish with grounding studies and protection coordination."

Pitfalls: listing steps with no reasons behind them; ignoring soil and thermal data for buried cable; forgetting losses over the project's life when choosing conductor size.

The interviewer wants to know how you keep layout documents accurate when the site changes under you. Use Situation, Task, Action, Result: what changed, what you owned, how you updated the layout and every drawing tied to it, and the outcome.

Sample answer: "Midway through design, the wetland survey came back with a larger boundary that took in two turbine pads and part of a road. I was responsible for the layout set. I moved the two turbines within the setback limits, rerouted the road and the collection line, and asked the energy analyst to check the effect on output. Then I updated the site plan, the cable schedule and the road profiles together, issued a new revision with the changes marked, and sent a short note to the civil and electrical leads. The permit package went in on time with drawings that agreed with each other."

Pitfalls: describing only the turbine move and not the drawings that depended on it; skipping version control or how others learned of the change; leaving out the effect on energy output or cost.

The interviewer wants to see that you weigh evidence, cost and risk before recommending a change. Name the factors you check, show how you balance them, then give a brief example.

Sample answer: "First I look at the data: SCADA trends, failure history and how many turbines the issue affects. Then I estimate the benefit, such as added energy or fewer repairs, against the full cost, including downtime and crew time. I check whether the change affects warranties, the turbine maker's limits or permit conditions, and I ask site technicians whether it is practical to carry out. For example, when one site had repeated yaw motor failures, I compared a parts upgrade with a change to the yaw settings, showed the payback of each, and recommended trying the settings change on a few turbines first."

Pitfalls: recommending changes based on one data point; ignoring warranty or permit limits; leaving out the people who will carry out the change.

The interviewer wants to learn how you use a model to choose a wind farm layout that balances cost and equipment access.

Use Situation, Task, Action, Result. Name the model's inputs, the routes you compared and the trade-off behind your choice. Explain how you checked the model and distinguish estimated benefits from results measured during construction.

Sample answer: "On a ridge-top project, the first road route crossed steep ground. I modeled alternatives in our GIS and civil design tools using terrain, setbacks, soil information and the crane's turning and slope limits. I compared earthwork, road grades and collection cable lengths using the same assumptions for each route. We chose a longer road around the slope because it avoided a tight crane turn. That meant accepting a longer cable run. The civil team checked the grades and turning clearances before we carried that option into detailed design."

Avoid describing only the software, overlooking crane or transport limits, or presenting modeled savings as proven construction savings.

The interviewer wants to see a structured, evidence-based method rather than a guess. Lay out your steps in order and name the tools you would use.

Sample answer: "First I make sure the site is safe and secure the evidence: the failed part, photos, and the SCADA and maintenance records from before the failure. Next I define the failure clearly, such as a cracked flange weld or loose tower bolts, and check whether other turbines show the same signs. Then I list possible causes with a fishbone diagram or fault tree, covering design, materials, installation such as bolt tensioning, and operating loads. I test each one against the evidence and send parts for lab analysis when needed. Once the cause is confirmed, I recommend a fix and an inspection plan for the rest of the fleet, and I write it up so the team can learn from it."

Pitfalls: jumping to a cause before collecting evidence; fixing one turbine without checking the others; leaving out safety.

The interviewer wants to know how you turn operating data into clear findings. Describe your method, the data and measures you use, and an example of what it found.

Sample answer: "I start with SCADA data and clean it first, separating curtailment, downtime and invalid readings according to the analysis method, while keeping those records available for reliability checks. For performance I compare each turbine's power curve with the specified curve and similar turbines under comparable conditions, using the agreed corrections and exclusions. For reliability I track availability, fault codes and time between failures, and I tie them to maintenance records. If a turbine falls below the expected curve, I check the operating conditions and maintenance history before suggesting a cause. I verify any proposed correction using comparable operating periods and the agreed performance specification."

Use a finding from your own work if you include a past example. Pitfalls: trusting raw data without filtering it; reporting site averages that hide single bad turbines; giving numbers with no action behind them.

The interviewer wants to see that you know the permit conditions and check them on site, not just on paper. Explain how you track requirements, check work in the field, and handle a problem.

Sample answer: "I start by turning the permits into a checklist: setbacks, wetland buffers, erosion control, wildlife timing limits and any noise or work-hour rules. I share it with the contractors at kickoff. During construction I walk the site regularly with the environmental monitor, check silt fences and staked boundaries, and log what I find with photos. When a crew once staged equipment inside a wetland buffer, I stopped that work, had them move it, and reported it as the permit required. We added the buffer to the daily briefing so it didn't happen again."

Pitfalls: relying only on contractor reports; not knowing which permits apply; hiding a problem instead of reporting it. Requirements vary by state and by permit, so name the ones you have worked with.

The interviewer wants to see that you check the test as carefully as the wind turbine component before reaching a conclusion.

Use Situation, Task, Action, Result. Identify the component, the failed requirement, your checks and the final decision. Explain how any change to the test method was checked against the agreed specification.

Sample answer: "We were qualifying a supplier's pitch bearing, and I ran the torque and stiffness tests. Friction torque was above the limit. I checked calibration, grease fill and rig setup, then repeated the test on another sample. The readings were still high. I sent the data and method to the supplier, and we found a difference in run-in procedures. Our test lead checked the agreed specification before we planned another test. We did not approve the bearing. The revised test plan stated the required run-in and the same acceptance limits, so the next test would answer the unresolved question."

Avoid blaming the part before checking the rig, changing acceptance limits to obtain a pass, or claiming the component passed when testing is unfinished.