The role is a systems‑focused ADAS ECU position, with an emphasis on change point analysis, requirements development, and validation rather than pure development. Honda operates in a lean structure, meaning the same engineer is responsible for activities across the V‑model, including both requirements/specification work and downstream verification and validation. The consultant will take systems originally developed in Japan and support their integration into North American vehicle models by analyzing what remains the same versus what must change. This includes coordinating closely with Japan counterparts and U.S. cross‑functional teams to understand change impacts, define updated requirements, and modify system, diagnostic, or CAN communication specifications as needed
The consultant will own gap analyses and requirements updates, documenting changes in tools such as Excel, PowerPoint, PDFs, and internal CAN/change‑point tools. They are not responsible for software implementation or ECU hardware design but will create the requirements and specifications that are delivered to suppliers. Once suppliers return software releases, the consultant will support validation activities, including bench and on‑vehicle testing. This includes developing test plans, executing select tests personally, sending requirements to technicians for vehicle testing, analyzing results, making preliminary judgments, and presenting findings for evaluator approval. The team uses Vector tools and VT system benches for automated testing.
In addition, the role carries light project execution responsibility. The consultant is expected to understand software schedules, manage requirement submission timing, support milestone events (including system verification and MARU‑Q milestones), and contribute status and documentation for formal reviews. The work is focused on ADAS components such as BSW, diagnostics, communication, and ECU validation—not ADAS performance algorithms.
Honda would ideally like someone with 3–5 years of automotive systems engineering experience supporting ADAS, ECU, FICU, or related systems. Strong co‑op experience could offset less full‑time experience. This is not intended to be a senior (10+ year) role but can flex up or down for the right person at the right rate.
High‑Level Responsibilities Snapshot