> Markdown version of [/jobs/ext/4030403-feature-systems-engineer-partner-programs](https://www.wearedevelopers.com/jobs/ext/4030403-feature-systems-engineer-partner-programs). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Feature Systems Engineer - Partner Programs

- **Company:** Ford Motor Company
- **Location:** Dearborn, MI, United States (Remote available)
- **Experience:** Expert
- **Salary:** $86,600.0 - $166,200.0
- **Contract:** Permanent contract
- **Skills:** Systems Engineering, Cloud Computing, Cyber Security, Data Integrity, Data Sharing, Data Flow Control, Design of User Interfaces, Package Management Systems, Cloud Services, Systems Architecture, Systems Integration, Privacy Controls, Backend, Cloud Integration
- **Published:** October 30, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=c5d83c3969872ad1

## About the Role

* Bachelor's degree in Engineering
 * 5+ years of systems engineering experience, including experience in telematics or cloud-connected product program.
 * 5+ years of experience supporting complex products development or service launches, integrations or validation cycles, coordinating across internal organizations & external suppliers integration issues through resolution or documented disposition
 * 5+ years of experience defining or reviewing the architecture of connected products or services, including system interfaces and architecture deliverables, such as interface specifications, sequence diagrams, or data-flow diagrams.

Even better, you may have...

 * Master's degree in relevant Engineering / technical field.
 * Experience supporting OEM / vehicle program through integration and launch, including coordinating vehicle, cloud/backend, and supplier teams; managing integration issues through resolution or formal disposition; and contributing to release-readiness evidence or post-launch issue resolution

## Description

Serves as Ford's technical authority for connected vehicle features, responsible for defining requirements, governing cloud-to-vehicle interfaces, ensuring supplier implementation alignment, and validating compliance with Ford architecture, cybersecurity, privacy, and customer experience expectations.

What you'll do...

The Ford FSE acts as the system owner for connectivity features and cloud-integrated services. The role bridges product requirements, vehicle engineering, cloud services, privacy compliance, provisioning, telematics, fleet services, OTA updates, and supplier integration activities. The FSE establishes Ford-defined behavior and interfaces while ensuring supplier implementations are aligned with Ford standards and customer experience requirements.

Requirements & Systems Architecture

 * Define connected vehicle technical, security, privacy, safety, and regulatory requirements.
 * Own Ford cloud interface definitions and connectivity architecture requirements.
 * Define Ford Well-Known Signals, event models, signal mappings, enumerations, units, and expected vehicle behavior
 * Maintain requirements through change-control and legal-review processes.

Supplier Integration & Technical Leadership

 * Communicate Ford feature expectations and technical requirements to suppliers.
 * Drive closure of feature gaps identified between Ford and supplier implementations.
 * Review supplier sequence diagrams, implementation proposals, and architectural responses.
 * Ensure supplier solutions remain aligned with Ford architecture and interfaces.

Cloud & Backend Systems Ownership

 * Define and govern Ford cloud integration requirements
 * Own customer authorization, account-linking, and VIN association workflows.
 * Define backend activation and deactivation requirements for connected services.
 * Govern fleet-management, feature-package, and remote-command cloud services

Customer Experience & HMI Definition

 * Define customer authorization and onboarding experiences.
 * Define connected services disclaimers and setup wizard behavior.
 * Establish Ford UI/UX expectations for privacy, account management, and connected services.
 * Define profile synchronization and user-management expectations.

Privacy, Cybersecurity & Regulatory Compliance

 * Define privacy controls, consent requirements, and data-sharing behaviors.
 * Ensure connected features comply with cybersecurity, privacy, and ePrivacy requirements.
 * Define regional compliance and regulatory reporting requirements.
 * Establish governance for fleet-privacy and dual-consent frameworks.

OTA & Software Update Governance

 * Define OTA/MMOTA deployment requirements and strategies.
 * Own software-update content, rollout policies, and version governance.
 * Define cloud deployment requirements for emissions, battery-health, and regulatory data reporting.

Provisioning & Manufacturing Integration

 * Define End-of-Line (EOL) provisioning requirements and cloud registration processes.
 * Govern Sync key allocation and supplier-feed integration requirements.
 * Define cloud-triggered carrier provisioning and SIM activation processes.

Connected Feature Governance

 * Define operational behavior for remote climate control, remote start, lock/unlock, vehicle health alerts, vehicle location, EV charging, panic alarms, and stolen vehicle services.
 * Establish expected command responses and status-reporting requirements.
 * Define fleet telematics signals, events, and command capabilities.

Verification & Validation

 * Verify supplier implementation compliance with Ford-defined architectures and requirements.
 * Validate signal mappings, telemetry behavior, status reporting, and cloud integrations.
 * Confirm regulatory, privacy, and customer experience requirements are satisfied.

Fleet & Telematics Services

 * Define fleet enrollment and feature-package management requirements
 * Govern telematics payload definitions, data integrity requirements, and reporting expectations. Define fleet remote-command authorization and lifecycle management requirements.
*