Transmission Controls Engineer/ Powertrain Controls Engineer (W2 Position)- 328530

Role: Transmission Controls Engineer/ Powertrain Controls Engineer (W2 Position)- 328530
Location: Dearborn, MI (HYBRID)
Duration: 12+ Months
Experience: 5+ Years
Client: Ford Motors
JD:
Skills Required:
Transmissions, Agile Software Development, Software Testing, Matlab, MATLAB modeling, Software Development Lifecycle, C, Simulink
Transmissions – I''''m looking for experience having worked on automatic transmissions. Either in software design or calibration. I think 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
MATLAB modeling – 2 years
Software Development Lifecycle – 2 years working with lifecycle products like IBM Clearcase or Github
C – 2 years of writing or modifying c-code.
Simulink - 2 years working with simulink models. This include modifying, designing, and simulating.
Skills Preferred:
Ford powertrain, Artificial Intelligence & Expert Systems
Ford powertrain – developing powertrain controls (engine or transmission) software within the Ford powertrain software enivroment.
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.
Experience Required:
4+ years developing automatic transmission controls using c-code and Matlab/sSimulink and Stateflow
Experience Preferred:
Experience with automotive calibration tools like ATI Vision, Vector CANOE.
Additional Information :
HYBRID / 4 days per week in the office
Use Matlab/Simulink/Stateflow 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, tuneability, testability and Ford SW modeling guidelines