MCP Software Engineer

Note - Please apply with external profile.

The Module Configuration and Programming (MCP) Diagnostic Designer Engineer is primarily responsible to design and develop, validate, and implement, programming applications and delivers software files and configuration data to the dealer/aftermarket network to support vehicle. The MCP Diagnostic Design Engineer will be using the OTX / Grade X authoring software and other XML scripting tools to develop the programming applications

Main responsibilities include:

· Develop diagnostic solutions for Over the Air (OTA) supported connected vehicles.

· Interface with Product Engineering regarding new control system technologies requiring new diagnostics service procedures and support.

· Use Rally to document Features and User Stories to add new content to FDRS.

· Design, Develop, Test, Release, all features of MCP that relate to software compatibility (for example, operating system, vehicle protocol / communication drivers, databases, libraries) on the two diagnostic service tools using OTX/Grade X programming, XML scripting tools and software programming tools

· Manage and understand data, process data requests and data concerns, maintain templates.

· Interface with Software/Hardware Designer/Supplier to assure design intent is met.

· Design and implement new tools for dealership diagnostic support.

· Validation will be performed with both simulation tools and on vehicle validation.

Experience and Skills Required:

Minimum experience - 2 - 5 years

· Bachelors in Computer Science, Computer Engineering, Electrical Engineering, or Automotive Technology preferred.

· Dealership field experience working Service Departments and Repair Technicians is a plus.

· Strong desire to enhance and improve the technician’s diagnostic experience.

· Project development experience with Ford Agile/Rally/JIRA is a plus.

· Strong Program Management skills.

· Strong verbal and written communication skills.

· Ability to work close with global teams to communicate and agree on desired outcomes.

· Ability to communicate with tool owners to drive changes that relate to both HMI and UX