Transmission Controls Engineer

Position Description

Own and manage multiple automatic transmission software components (features): manage changes and requirements, coordinate validation with HIL and calibration teams, act as SPOC for issue triage and resolution, bookshelf and release updates using software development and software quality processes, including all necessary deliverables (e.g. test reports, DVMs, calibration guides, etc.).

• Transmissions:
  Experience having worked on automatic transmissions either in software design or calibration. Approximately 5 years of experience in this area is sufficient.
• Agile Software Development:
  Knowledge of agile principles. 1 year of working in an Agile environment is sufficient.
• Software Testing:
  Experience using software testing tools to generate and evaluate standard software quality metrics like decision coverage, MC/DC and line coverage. 2 years of software testing experience.
• MATLAB: 2 years using MATLAB.
• Software Development Lifecycle: 2 years working with lifecycle products like IBM Clear Case or Git Hub.
• C: 2 years of writing or modifying c-code.
• Simulink: 2 years working with Simulink models. This includes modifying, designing, and simulating.

• Powertrain:
  Developing powertrain controls (engine or transmission) software within the OEM/Client powertrain software environment.
• Artificial Intelligence & Expert Systems:
  Knowledge of AI tools (like Copilot) and having used AI to assist in the creation, or completion, of work related tasks and objectives.

4+ years developing automatic transmission controls using c-code and MATLAB/Simulink and State flow.

Experience with automotive calibration tools like ATI Vision, Vector CANOE.

Bachelor's Degree.

HYBRID / 4 days per week in the office.

• Use MATLAB/Simulink/State flow to model feature functions and autogenerate quality c-code directly from the model.
• Develop and execute unit tests to fully verify the functionality of the software with respect to requirements.
• Use issue management tools (JIRA) to manage and document software feature change requirements, emphasizing customer (SP&I, calibration, program) needs and timing considerations.
• Develop interface specifications for interfaces that cross functional boundaries including across organizations, subsystems and feature.
• Participate in, and communicate with, cross-functional teams to optimize solutions weighing software complexity, tune ability, testability and OEM/Client SW modeling guidelines.