> Markdown version of [/jobs/ext/3940955-adas-diagnostic-systems-engineer](https://www.wearedevelopers.com/jobs/ext/3940955-adas-diagnostic-systems-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). --- # ADAS Diagnostic Systems Engineer - **Company:** Ford Motor Company - **Location:** Dearborn, MI, United States - **Experience:** Experienced - **Salary:** $14,560.0 - $16,640.0 - **Contract:** Permanent contract - **Skills:** Agile Methodology, Systems Engineering, Communications Protocols, Ethernet, Failure Mode Effects Analysis, Requirements Management, Software Engineering, Software Requirements Analysis - **Published:** October 26, 2026 - **Apply:** https://www.techcareers.com/job.asp?id=3467287930&tx=VT5954TYZ&pt=1&aff=0B19D771-A501-4A5E-8338-2A822B784D54&utm_source=Job%20Feed&utm_medium=textkernel&utm_campaign=DE&utm_term=0B19D771-A501-4A5E-8338-2A822B784D54 ## About the Role * Bachelor's degree in Electrical, Mechanical, Computer, Software Engineering, Data Science, or a related field * 2+ years of experience in vehicle systems engineering, including architecture development, requirements definition and authoring, and failure mode analysis (DFMEA) * 2+ years of experience with automotive diagnostics development (DTCs, DIDs, diagnostic strategy/architecture) * Familiarity with diagnostic communication standards (e.g., UDS/ISO 14229, OBD) * Experience translating stakeholder needs or problem statements into technical requirements or design proposals * Strong learning agility, adaptability, and systems thinking * Excellent analytical, problem-solving, and troubleshooting skills * Proven ability to lead and collaborate within cross-functional teams * Effective verbal and written communication skills, * Master's degree in Electrical, Controls, Computer, Mechanical, or Systems Engineering or a related field * 5+ years of experience in vehicle systems engineering, including architecture development, requirements definition and authoring, and failure mode analysis (DFMEA) * 5+ years of experience with automotive diagnostics development and architecture (DTCs, DIDs, diagnostic strategy) * Experience authoring diagnostic specifications or behavioral models (e.g., state diagrams, sequence diagrams, DTC maturation/healing logic) * Experience with electrical module design, in-vehicle communication protocols (CAN, LIN, Ethernet, UDS), and power distribution * Experience with requirements management tools and model-based systems engineering * Experience with systems engineering or electronic component release engineering during major vehicle build launch milestones * Experience leading root-cause analysis (e.g., 8D, 5-Why) with cross-functional or supplier teams * Experience with Agile methodologies ## Description * Architect and own diagnostic strategy for assigned ADAS features/subsystems, as part of a broader diagnostics team responsible for the overall ADAS diagnostic architecture - defining diagnostic requirements, fault detection logic, DTC set structure, and failure response strategy for your area of responsibility from concept through production, using systems engineering principles, and ensuring alignment with the team's overall diagnostic strategy and architecture. * Author diagnostic specifications and behavioral models (e.g., state diagrams, sequence diagrams, DTC maturation/healing logic) that translate system-level failure modes into implementable diagnostic requirements for software and hardware teams. * Design diagnostic architecture in alignment with UDS (ISO 14229), OBD, and corporate diagnostic standards . * Serve as the intake and technical owner for enhanced diagnostics requests from internal customers - eliciting and clarifying the underlying problem statement or customer need, assessing priority and feasibility against the overall diagnostics scope of work in partnership with the diagnostics team, developing design proposals, and incorporating approved changes into diagnostic specifications. * Collaborate directly with software/controls engineers during feature development to define fault detection thresholds, enable conditions, and failure mode responses before code is written - not after issues surface in validation. * Lead or support root-cause investigations for diagnostic anomalies identified during development - Working with internal engineering functions and suppliers, identify defect source, feed findings back into diagnostic architecture and DTC strategy updates (continuous improvement, not just issue closure). * Develop troubleshooting guides and diagnostic documentation to enable engineering, manufacturing, and service teams to act on the diagnostics you designed. * Define and execute validation criteria for diagnostic specifications you author , ensuring diagnostic behavior meets intent - validation as the final checkpoint of a strategy you built, not a standalone verification task. * Manage diagnostic issue triage and DTC lifecycle management across the product lifecycle , with a focus on identifying architecture-level fixes rather than one-off patches.