The Software Product Engineer (SPE) is a senior feature delivery leader within in-vehicle infotainment, responsible for translating product vision and design intent into executable software backlogs and driving end-to-end delivery across the in-vehicle digital experience.
\nThis includes the User Interface (UI) and User Experience (UX) layers, as well as supporting middleware, services, and vehicle integration,particularly for electrification-related features such as charging, energy management, range insights, and battery status.
\nOperating at the intersection of Product, Design, Engineering, and Electrification, the SPE plays a critical leadership role in aligning cross-functional teams and ensuring high-quality feature execution.
\nThis role requires a strong understanding of engineering systems and EV domain concepts, enabling effective translation of product, technical, UX/UI, and electrification requirements into clear, actionable work items and solutions.
\nThe SPE owns and drives backlog strategy and execution within Jira, including story creation, refinement, grooming, and triage.
\nBy incorporating Product Owner responsibilities, the SPE ensures well-defined acceptance criteria, alignment with program priorities, and readiness for implementation across multiple teams.
\nThis role is accountable for cross-team coordination, dependency and risk management, and integrated validation from concept through launch, ensuring predictable program execution and high-quality release outcomes.
\nWith broad organisational influence, the SPE partners closely with Product Management, Digital Product Design, Electrification teams, engineering scrum teams, and testing organisations to ensure seamless integration, feature readiness, and a consistent, customer-centric experience across vehicle platforms.
\nResponsibilities:
\nOwn the end-to-end engineering lifecycle for a set of features or digital experience domains from concept through release sign-off, including electrification-focused features
\nDefine the product execution path by answering: “What should we build, why does it matter, and how do we build it the right way?”,with consideration for both UX excellence and EV customer needs.
\nTranslate PRDs, design artifacts, system behaviour requirements, and electrification use cases into clear software deliverables,epics and sprint-ready user stories with well-defined acceptance criteria in Jira.
\nLead feasibility assessment, scope definition, and backlog readiness for PI planning; manage change/churn while protecting milestones.
\nDrive cross-functional alignment with Product, Digital Product Design, Architecture, Engineering, and Test teams to ensure shared understanding of intent, priorities, dependencies, and Electrification/EV-specific behaviours.
\nDefine and manage feature dependencies and blockers across HMI, services, platform, vehicle signals, and electrification systems.
\nValidate end-to-end feature behaviour on bench/vehicle through demos and product truth sessions; ensure implementation matches UX intent, functional expectations, and real-world EV usage scenarios.
\nLead defect triage and prioritisation for owned features; drive issues to closure through root-cause direction, retest strategy, and stakeholder communication.
\nMaintain clear execution visibility via epic status summaries, risk registers/mitigation plans, and regular stakeholder updates.
\nEnsure test coverage alignment by reviewing/confirming that test cases map to story acceptance criteria, edge cases, and electrification scenarios (e.g., charging interruptions, low battery states).
\nIdentify and define logworthies and analytics instrumentation required for each feature, including EV-specific telemetry (charging sessions, energy usage, range accuracy).
\nQualifications:
\nEducation: BS in Engineering, Computer Science, or related technical field
\nExperience: 5+ years delivering complex, cross-functional software features in embedded, automotive, or adjacent domains; demonstrated ownership across multiple teams and releases.
\nDirect experience with Android Automotive/QNX, infotainment HMIs, and automotive middleware/service architectures.
\nFamiliarity with electrification concepts such as battery state of charge (SoC), charging workflows (AC/DC fast charging), range estimation, and energy consumption modelling,without requiring deep hardware or electrical design expertise.
\nBacklog leadership: Proven ability to author high-quality epics and user stories (clear scope, testable acceptance criteria, dependency mapping) and drive Agile execution (grooming, PI planning, sprint delivery).
\nSystems integration mindset: Ability to reason about end-to-end behaviour across HMI ↔ middleware/services ↔ vehicle signal access (via API abstraction), including electrification data flows (battery, charging, energy systems), and drive integration/validation outcomes.
\nTechnical proficiency: Strong technical depth to lead engineers,comfortable with architecture discussions, interface contracts, and failure-mode thinking.
\nDiagnostics/triage: Experience leading defect triage using logs and traces (e.g., ADB/dev logs; CAN trace familiarity), defining diagnostic logging (logworthies), and driving disciplined prioritisation/closure.
\nTools: Proficiency with Jira and Confluence; comfortable creating traceability to requirements/design artefacts and managing dependencies.
\nCommunication/leadership: Strong cross-functional leadership skills,can drive decisions, align stakeholders, and communicate risks/status crisply to technical and non-technical audiences.
\nPreferred qualifications:
\nExperience with electrification-focused features such as charging experiences, route planning with charging stops, or energy insights within automotive or mobility platforms.
\nExperience with test management tools and reviewing test coverage against acceptance criteria.
\nKnowledge of automotive program cadence and release gating (launch milestones, OTA readiness, in-field defect handling).
\nProficiency with CAN-based feature behaviours and vehicle state modelling; exposure to tools such as CANalyzer/Wireshark (or similar).
\nExposure to EV ecosystem integrations such as charging networks, Plug & Charge, or mobile app–vehicle energy feature interactions.
\nXML job scraping automation by YubHub
","url":"https://yubhub.co/jobs/job_df6976bf-711","directApply":true,"hiringOrganization":{"@type":"Organization","name":"Ford Motor Company","sameAs":"https://www.ford.com/","logo":"https://logos.yubhub.co/ford.com.png"},"x-apply-url":"https://efds.fa.em5.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1/job/61784","x-work-arrangement":"hybrid","x-experience-level":"senior","x-job-type":"full-time","x-salary-range":"$80,000 - $154,000","x-skills-required":["Android Automotive","QNX","infotainment HMIs","automotive middleware/service architectures","electrification concepts","battery state of charge","charging workflows","range estimation","energy consumption modelling","Jira","Confluence","API abstraction","diagnostic logging","logworthies","analytics instrumentation","EV-specific telemetry","charging sessions","energy usage","range accuracy"],"x-skills-preferred":["electrification-focused features","charging experiences","route planning with charging stops","energy insights","test management tools","test coverage against acceptance criteria","automotive program cadence","release gating","CAN-based feature behaviours","vehicle state modelling","CANalyzer/Wireshark","EV ecosystem integrations","charging networks","Plug & Charge","mobile app–vehicle energy feature interactions"],"datePosted":"2026-04-24T12:22:10.082Z","jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Dearborn"}},"employmentType":"FULL_TIME","occupationalCategory":"Engineering","industry":"Automotive","skills":"Android Automotive, QNX, infotainment HMIs, automotive middleware/service architectures, electrification concepts, battery state of charge, charging workflows, range estimation, energy consumption modelling, Jira, Confluence, API abstraction, diagnostic logging, logworthies, analytics instrumentation, EV-specific telemetry, charging sessions, energy usage, range accuracy, electrification-focused features, charging experiences, route planning with charging stops, energy insights, test management tools, test coverage against acceptance criteria, automotive program cadence, release gating, CAN-based feature behaviours, vehicle state modelling, CANalyzer/Wireshark, EV ecosystem integrations, charging networks, Plug & Charge, mobile app–vehicle energy feature interactions","baseSalary":{"@type":"MonetaryAmount","currency":"USD","value":{"@type":"QuantitativeValue","minValue":80000,"maxValue":154000,"unitText":"YEAR"}}}]}