Ford Motor Company logo

Mechatronics Fuel Subsystem Engineer - Propulsion

Ford Motor Company

  • Dearborn, MI
  • 7 days ago

    Highlights

    You will be laser-focused on bridging the gap between Electronics, Mechanical Hardware (VHE), Features, Controls & Software (CVS) and others, acting as the central integration lead to ensure flawless physical-to-electrical execution. Drive the cross-skill team delivery with the use of design guardrails-preventing direct Feature-to-Electronic DR handoffs and ensuring strict traceability from feature intent down to component execution.

    Numbers & Facts

    LocationDearborn, MI

    Description

    Enterprise Technology plays a critical part in shaping the future of mobility. If you're looking for the chance to leverage advanced technology to redefine the transportation landscape, enhance the customer experience and improve people's lives, this is the opportunity for you. Join us and challenge your IT expertise and analytical skills to help create vehicles that are as smart as you are., We're in the midst of the biggest change the automotive industry has ever seen. Just as cars changed the world over the last century, new technologies such as self-driving cars, electric powertrains, and connected vehicles will radically reshape how we live, work, and play in the next hundred years. As a member of the Experience Design (XD) Team, you'll be at the heart of creating that future. Every day, Ford's vehicles, and services support millions of people around the world. You'll craft every touchpoint our customers encounter, designing people and society's needs into the heart of our next generation of out-of-vehicle products, services, and experiences., Ford's Electric Vehicles, Digital and Design (EVDD) team is charged with delivering the company's vision of a fully electric transportation future. EVDD is customer-obsessed, entrepreneurial, and data-driven and is dedicated to delivering industry-leading customer experience for electric vehicle buyers and owners. You'll join an agile team of doers pioneering our EV future by working collaboratively, staying focused on only what matters, and delivering excellence day in and day out. Join us to make positive change by helping build a better world where every person is free to move and pursue their dreams.

    Mechatronics Fuel Subsystem Engineer - Propulsion We made history and now we work to transform the future - for our customers, our communities and our families. You'll see your work on the road every day, helping people move freely and pursue their dreams. At Ford, you can build more than vehicles. Come build what matters.

    In this position...

    You will be part of a newly formed team that will execute cross-domain Mechatronics Subsystem integration across all vehicle programs. You will be laser-focused on bridging the gap between Electronics, Mechanical Hardware (VHE), Features, Controls & Software (CVS) and others, acting as the central integration lead to ensure flawless physical-to-electrical execution.

    While the Mechatronics Core Team works in the background to design enterprise standards, mathematical models, and templates,. This role will focus on owning specific mechatronic subsystems (fuel systems) and intercepting feature intent before component design begins. The team will manage the physical-to-electrical transfer functions, ensuring that system performance meets subsystem requirements such as the physical realities of mechanical hardware (torque, thermal limits, kinematics).

    What you'll do...

    • You will demonstrate a passion for changing Ford's approach to systems engineering-shifting from isolated component delivery to holistic, synchronized mechatronic subsystem execution.

    Why This Role is Critical…

    • Define electro-mechanical requirements and interfaces
    • Define subsystem electrical Architectures (that include hardware software and electrotechnical requirements and system performance specification

    Enables true software-hardware co-development

    • Drives Ford's transition to subsystem-based engineering execution
    • Test and validate electro- mechanical subsystems
    • Improves first-time quality at launch

    Lead Subsystem-Level Execution: Take the standardized templates, math models, and engineering frameworks developed by the Mechatronics Core team and apply them to your specific vehicle program to ensure the subsystem performs flawlessly on the assembly line.

    • Drive the new working interaction model by ingesting Feature level or system level requests and decomposing them into synchronized mechanical, electrical, and software requirements.

    Interface with Feature, System, VHE (Hardware), and CVS (Software) teams ensuring system-level performance and timing are physically achievable before code is written or parts are tooled.

    • Coordinate cross-functionally to take Core templates and develop program-specific Subsystem Boundary Diagrams, Interface Control Documents (ICDs), and Subsystem Electrical Block Diagrams for your assigned domain.
    • Be part of the solution to deliver exceptional experiences by leading active vehicle build issue triage (Breadboard, HIL, and plant floor). You will investigate data logs, identify root causes, and define real-time containment plans for complex cross-domain failures.
    • Partner with software and hardware teams to perfectly align Agile software sprints (Jira) with Waterfall mechanical hardware timelines (GPDS), ensuring code is ready when physical parts arrive.
    • Hold the standard with partnering D&R teams to subsystem timelines, risk mitigation plans, and integration readiness to ensure on-time and on-target delivery prior to key program milestones (e.g., FDJ).
    • Drive the cross-skill team delivery with the use of design guardrails-preventing direct Feature-to-Electronic DR handoffs and ensuring strict traceability from feature intent down to component execution.
    • Develop complete plans for Subsystem-level Verification and Sign-off across current and future vehicle programs.

    Key Deliverables:

    • Subsystem Boundary Diagrams (program-specific)
    • Component Design specification (CDS) with validated signals and constraints
    • Physical-to-electrical transfer function models
    • Integration readiness reviews aligned to GPDS milestones
    • Root cause + containment plans for cross-domain issues
    • Subsystem verification & sign-off plans

    In this position...

    You will be part of a newly formed team that will execute cross-domain Mechatronics Subsystem integration across all vehicle programs. You will be laser-focused on bridging the gap between Electronics, Mechanical Hardware (VHE), Features, Controls & Software (CVS) and others, acting as the central integration lead to ensure flawless physical-to-electrical execution.

    While the Mechatronics Core Team works in the background to design enterprise standards, mathematical models, and templates,. This role will focus on owning specific mechatronic subsystems (fuel systems) and intercepting feature intent before component design begins. The team will manage the physical-to-electrical transfer functions, ensuring that system performance meets subsystem requirements such as the physical realities of mechanical hardware (torque, thermal limits, kinematics).

    What you'll do...

    • You will demonstrate a passion for changing Ford's approach to systems engineering-shifting from isolated component delivery to holistic, synchronized mechatronic subsystem execution.

    Why This Role is Critical…

    • Define electro-mechanical requirements and interfaces
    • Define subsystem electrical Architectures (that include hardware software and electrotechnical requirements and system performance specification

    Enables true software-hardware co-development

    • Drives Ford's transition to subsystem-based engineering execution
    • Test and validate electro- mechanical subsystems
    • Improves first-time quality at launch

    Lead Subsystem-Level Execution: Take the standardized templates, math models, and engineering frameworks developed by the Mechatronics Core team and apply them to your specific vehicle program to ensure the subsystem performs flawlessly on the assembly line.

    • Drive the new working interaction model by ingesting Feature level or system level requests and decomposing them into synchronized mechanical, electrical, and software requirements.

    Interface with Feature, System, VHE (Hardware), and CVS (Software) teams ensuring system-level performance and timing are physically achievable before code is written or parts are tooled.

    • Coordinate cross-functionally to take Core templates and develop program-specific Subsystem Boundary Diagrams, Interface Control Documents (ICDs), and Subsystem Electrical Block Diagrams for your assigned domain.
    • Be part of the solution to deliver exceptional experiences by leading active vehicle build issue triage (Breadboard, HIL, and plant floor). You will investigate data logs, identify root causes, and define real-time containment plans for complex cross-domain failures.
    • Partner with software and hardware teams to perfectly align Agile software sprints (Jira) with Waterfall mechanical hardware timelines (GPDS), ensuring code is ready when physical parts arrive.
    • Hold the standard with partnering D&R teams to subsystem timelines, risk mitigation plans, and integration readiness to ensure on-time and on-target delivery prior to key program milestones (e.g., FDJ).
    • Drive the cross-skill team delivery with the use of design guardrails-preventing direct Feature-to-Electronic DR handoffs and ensuring strict traceability from feature intent down to component execution.
    • Develop complete plans for Subsystem-level Verification and Sign-off across current and future vehicle programs.

    Key Deliverables:

    • Subsystem Boundary Diagrams (program-specific)
    • Component Design specification (CDS) with validated signals and constraints
    • Physical-to-electrical transfer function models
    • Integration readiness reviews aligned to GPDS milestones
    • Root cause + containment plans for cross-domain issues
    • Subsystem verification & sign-off plans

    Similar Jobs

    See more jobs