Feature System Engineer at Ford

The role title 'Feature System Engineer' carries no explicit seniority level, but the 5+ years requirement and breadth of ownership (cross-functional leadership, supplier governance, regulatory compliance) support a Senior classification.

SOC classification is a judgement call: the role is primarily requirements definition, architecture governance, and systems analysis rather than software development, pointing to 15-1211 (Computer Systems Analysts). However, the depth of cloud/connectivity architecture work and supplier technical leadership could also support 15-1299 (Computer Occupations, All Other) as a connected-vehicle systems specialty not cleanly captured elsewhere.

The degree requirement accepts 'a combination of education and experience' as an alternative to a Bachelor's degree, so no minimum degree is hard-gated.

Several skills listed under 'You'll have…' are framed as knowledge/understanding rather than hands-on tool experience (e.g. cybersecurity principles, privacy governance); they are captured as required given their placement in the required qualifications section.

Skills listed under 'Even better, you may have…' are marked preferred throughout, including OTA/MMOTA, FordPass/TMC/TCAM, Android Automotive OS, Google Automotive Services, EV charging, SIM provisioning, and API design.

The posting is hybrid (not fully remote); candidates near a Ford hub may be required onsite four or more days per week.

Ignored 7 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): systems engineering, requirements management, vehicle-to-cloud architecture, privacy/consent management, supplier management, API design, SIM provisioning.