As of February 01, 2025, the average annual salary for an Electrical Controls Engineer in Indianapolis, IN is $96,301. Salary.com reports that pay typically ranges from $81,501 to $113,101, with most professionals earning between $68,026 and $128,397.
| Annual Salary |
Monthly Pay |
Weekly Pay |
Hourly Wage |
|
| 75th Percentile | $113,101 | $9,425 | $2,175 | $54 |
| Average | $96,301 | $8,025 | $1,852 | $46 |
| 25th Percentile | $81,501 | $6,792 | $1,567 | $39 |
An entry-level Electrical Controls Engineer with under 1 year experience makes about $90,791. With less than 2 years of experience, a mid-level Electrical Controls Engineer makes around $91,232. After 2-4 years, the Electrical Controls Engineer pay rises to about $96,881. Those senior Electrical Controls Engineer with 5-8 years of experience earn roughly $103,794, and those Electrical Controls Engineer having 8 years or more experience are expected to earn about $104,288 on average.
| Levels | Salary |
|---|---|
| Entry Level Electrical Controls Engineer | $90,791 |
| Intermediate Level Electrical Controls Engineer | $91,232 |
| Senior Level Electrical Controls Engineer | $96,881 |
| Specialist Level Electrical Controls Engineer | $103,794 |
| Expert Level Electrical Controls Engineer | $104,288 |
| Entry Level | 6% |
| Mid Level | 5% |
| Senior Level | 1% |
| Top Level | 8% |
| Experienced | 8% |
Not the salary data you are looking for? Choose the city salary you want to see.
Salary.com job board provides millions of Electrical Controls Engineer information for you to search for. Click on search button below to see Electrical Controls Engineer job openings or enter a new job title here.
Each competency has five to ten behavioral assertions that can be observed, each with a corresponding performance level (from one to five) that is required for a particular job.
Troubleshooting: Troubleshooting is a form of problem solving, often applied to repair failed products or processes on a machine or a system. It is a logical, systematic search for the source of a problem in order to solve it, and make the product or process operational again. Troubleshooting is needed to identify the symptoms. Determining the most likely cause is a process of elimination—eliminating potential causes of a problem. Finally, troubleshooting requires confirmation that the solution restores the product or process to its working state. In general, troubleshooting is the identification or diagnosis of "trouble" in the management flow of a system caused by a failure of some kind. The problem is initially described as symptoms of malfunction, and troubleshooting is the process of determining and remedying the causes of these symptoms. A system can be described in terms of its expected, desired or intended behavior (usually, for artificial systems, its purpose). Events or inputs to the system are expected to generate specific results or outputs. (For example, selecting the "print" option from various computer applications is intended to result in a hardcopy emerging from some specific device). Any unexpected or undesirable behavior is a symptom. Troubleshooting is the process of isolating the specific cause or causes of the symptom. Frequently the symptom is a failure of the product or process to produce any results. (Nothing was printed, for example). Corrective action can then be taken to prevent further failures of a similar kind.
System Integration: The process of creating a complex information system that may include designing or building a customized architecture or application, integrating it with new or existing hardware, packaged and custom software, and communications.
Systems Architecture: A system architecture or systems architecture is the conceptual model that defines the structure, behavior, and more views of a system. An architecture description is a formal description and representation of a system, organized in a way that supports reasoning about the structures and behaviors of the system. A system architecture can consist of system components and the sub-systems developed, that will work together to implement the overall system. There have been efforts to formalize languages to describe system architecture, collectively these are called architecture description languages (ADLs).
