> Markdown version of [/jobs/ext/1099840-hmi-software-product-engineer](https://www.wearedevelopers.com/jobs/ext/1099840-hmi-software-product-engineer). 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). --- # HMI Software Product Engineer - **Company:** Ford Motor Company - **Location:** Dearborn, MI, United States - **Experience:** Expert - **Salary:** $14,560.0 - $16,640.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Agile Methodology, Systems Engineering, JIRA, Code Coverage, Middleware, Design of User Interfaces, Health Information Management, Human-Computer Interaction, Interaction Design, Scrum Methodology, Software Requirements Analysis, Systems Integration, Wireshark, Information Technology, Atlassian Tools, Figma, Win CC - **Published:** June 13, 2026 - **Apply:** https://www.juju.com/job/00000000gbxwbv ## About the Role + **Experience:** 5+ years (or equivalent) delivering complex, cross-functional software features in embedded, automotive, or adjacent domains; demonstrated ownership across multiple teams and releases. + **Backlog 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). + **Systems integration mindset:** Ability to reason about end-to-end behavior across **HMI * middleware/services * vehicle signal access (via API abstraction)** and drive integration/validation outcomes. + **Technical proficiency:** Strong technical depth to lead engineers-comfortable with architecture discussions, interface contracts, and failure-mode thinking. + **Diagnostics/triage:** Experience leading defect triage using logs and traces (e.g., ADB/dev logs; CAN trace familiarity) and driving disciplined prioritization/closure. + **Tools:** Proficiency with **Jira and Confluence** ; comfortable creating traceability to requirements/design artifacts and managing dependencies. + **Communication/leadership:** Strong cross-functional leadership skills-can drive decisions, align stakeholders, and communicate risks/status crisply to technical and non-technical audiences. + **Education:** BS in Engineering, Computer Science, or related technical field (or equivalent practical experience). Even better, you may have... + Direct experience with **QNX/Android Automotive** , infotainment HMIs and **Figma** . + Familiarity with **CAN-based feature behaviors** and vehicle state modeling; exposure to tools such as CANalyzer/Wireshark (or similar). + Background in driver-focused feature areas. + Experience with test management tools and reviewing test coverage against acceptance criteria. + Knowledge of automotive program cadence and release gating (launch milestones, OTA readiness, in-field defect handling). ## Description The HMI 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. This includes the **User Interface (UI)** and **User Experience (UX)** layers, as well as supporting middleware, services, and vehicle integration. Operating at the intersection of Product, Design, and Engineering, the SPE plays a critical leadership role in aligning cross-functional teams and ensuring high-quality feature execution. This role requires a strong understanding of engineering systems and artifacts, enabling effective translation of product, technical, and **UI/UX** requirements into clear, actionable work items. The SPE owns and drives backlog strategy and execution within Jira, including story creation, refinement, grooming, and triage. By incorporating **Product Owner** responsibilities, the SPE ensures well-defined acceptance criteria, alignment with program priorities, and readiness for implementation across multiple teams. This 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. With broad organizational influence, the SPE partners closely with Product Management, Digital Product Design, engineering scrum teams, and testing organizations to ensure seamless integration, feature readiness, and a consistent, customer-centric **UI/UX** experience across vehicle platforms. In this role, the SPE leads delivery of Driver Information HMI, owning **UI and UX** elements such as layouts, animations, themes, drive modes, and feature integration across Build, Thrill, and Adventure domains. This includes ownership of Welcome and Farewell screen experiences, ensuring a seamless, engaging, and high-quality **User Experience** across all in-vehicle displays. The SPE ensures design intent is accurately realized through execution while maintaining consistency and performance across domains and vehicle platforms. What you'll do... - Own the end-to-end delivery for a number of vehicle features sets from concept through release sign-off. - Translate PRDs, design artifacts, and system requirements into epics and sprint-ready user stories with clear acceptance criteria in Jira. - Lead feasibility assessment, scope definition, and backlog readiness for PI planning; manage change/churn while protecting milestones. - Drive cross-functional alignment with Product, Digital Product Design, Architecture, Engineering, and Test to ensure shared understanding of intent, priorities, and dependencies. - Define and manage feature dependencies and blockers across HMI, services, platform, and validation. - Validate end-to-end feature behavior on bench/vehicle through demos and product truth sessions; ensure implementation matches UX intent and functional expectations. - Lead defect triage and prioritization for owned features; drive issues to closure through root-cause direction, retest strategy, and stakeholder communication. - Maintain clear execution visibility via epic status summaries, risk registers/mitigation plans, and regular stakeholder updates. - Ensure test coverage alignment by reviewing/confirming that test cases map to story acceptance criteria and key edge cases. ## Related Videos - [For the Cars and the Curious: Android Drift](https://www.wearedevelopers.com/videos/499-for-the-cars-and-the-curious-android-drift) - [Boost Productivity with AI: Figma & Playwright MCP Workflows - Aris Markogiannakis](https://www.wearedevelopers.com/videos/1768-boost-productivity-with-ai-figma-playwright-mcp-workflows-aris-markogiannakis) - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [Agile work at CARIAD – Creating a customer web application for controlling the vehicle ](https://www.wearedevelopers.com/videos/200-agile-work-at-cariad-creating-a-customer-web-application-for-controlling-the-vehicle) - [Designing the Future of Human<>Agent Collaboration](https://www.wearedevelopers.com/videos/1447-designing-the-future-of-human-agent-collaboration) - [Collaboration Quantified: Lessons from Open Source Developer Networks](https://www.wearedevelopers.com/videos/1422-collaboration-quantified-lessons-from-open-source-developer-networks) ## Related Articles - [How software is steering vehicle technology](https://www.wearedevelopers.com/magazine/515-how-software-is-steering-vehicle-technology) - [7 Important Tips That Every Software Developer Should Know](https://www.wearedevelopers.com/magazine/101-7-important-tips-that-every-software-developer-should-know) - [Dev Digest 107 - And the OSScar goes to…](https://www.wearedevelopers.com/magazine/405-dev-digest-107-and-the-osscar-goes-to) - [Résumé-Driven Development: How IT trends affect the job market for software developers](https://www.wearedevelopers.com/magazine/59-resume-driven-development-how-it-trends-affect-the-job-market-for-software-developers) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer)