Vehicle Software Integration Test Engineer
Stefanini Group · Dearborn, MI · 1 mo ago
On-siteQuality AssuranceFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Skills, Experience, Education), Benefits, Pay, Schedule only if present. The posting includes: About Stefanini Group (company description). Also "About the role" maybe not explicit but we can treat "Job Description" as about the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. So we need to extract content.
We have:
- About the role: The description includes "We are seeking a detail-oriented and technically versatile Vehicle Software Integration Test Engineer..." That's about the role. Could be a paragraph.
- Responsibilities: bullet list of duties.
- Requirements: Could combine Skills Required, Experience Required, Education Required. Could separate into Skills, Experience, Education. But we can combine into Requirements? The instruction says we can use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide.
We have Skills Required list, Skills Preferred list, Experience Required, Experience Preferred, Education Required, Education Preferred.
We could create sections: Responsibilities, Skills, Experience, Education. Or combine Skills and Experience into Requirements. But better to follow typical: Responsibilities, Requirements (which includes Skills, Experience, Education). However they said we can use multiple headings. We'll include separate sections for Skills, Experience, Education if there is specific content.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. The page already shows it, so we don't add heading for Vehicle Software Integration Test Engineer.
We must not put Job ID/requisition numbers as headings; none.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About the role paragraph: "We are seeking a detail-oriented and technically versatile Vehicle Software Integration Test Engineer to join our team focused on Human-Machine Interface (HMI), user experience (UX), and user interface (UI) validation for next-generation vehicle systems. In this role, you will bridge hardware and software domains, working hands-on with in-vehicle systems and TDKs by utilizing debugging tools and performing software updates to support pre-production HMI quality validation initiatives. You will play a key role in ensuring our setups are ready to perform HMI validation testing reliably."
That's the role description.
Responsibilities: list items:
- Set up testing validation requests for HMI, UX, and UI features across vehicle infotainment systems on TDKs and vehicles.
- Utilize in-house diagnostic tools and Android Debug Bridge (ADB) to debug and set up testing environments on vehicles and TDKs.
- Work cross-functionally with software teams to set up and execute Python scripts to enable simulations supporting HMI testing and the software download process.
- Support hardware and software integration efforts through seamless communication between embedded control units by ensuring the correct software levels are flashed and appropriate DIDs are enabled for HMI testing in vehicle and TDK setups.
- Apply working knowledge of CAN hardware used for feature signal simulation, including recording CAN information to support the deployment and monitoring of CAN signals across vehicle networks.
- Break down complex system issues into fundamental root causes; troubleshoot concerns spanning both hardware and software layers; then retest to confirm resolution and enablement of HMI testing.
- Maintain an overall understanding of vehicle architecture and communication.
- Adapt quickly to shifting priorities, evolving test environments, and changing management or project demands in a fast-paced development setting.
- Perform HMI validation testing and report quality assurance concerns.
- Document software methodologies and procedures by working cross-functionally.
- Travel occasionally between Mexico and California.
Skills Required list:
- User Acceptance Testing – Perform HMI testing and validate software implementation against design releases.
- Software Documentation – Document processes and procedures related to updating vehicles and benches.
- Analytical Skills – Ability to break down configurations and simplify testing procedures and setup.
- Technical Troubleshooting – Utilize the ADB debugging bridge and general system integration debugging to solve testing requirements.
- Troubleshooting / Problem Solving – Review ECU configurations and identify root causes related to HMI testing.
- Test Integration Testing – Set up vehicles and TDKs with the appropriate hardware and software to test prototype designs and evaluate HMI content displayed on the screen.
- Hardware Experience – Basic understanding of SOA communication and the ability to read wiring diagrams and connectors.
- Software Communications – Other – Ability to utilize in-house debugging tools to set configuration bits and send CAN messages over a CAN bus to support HMI evaluation.
Skills Preferred list:
- User Experience – Understanding of Difficult to Use (DTU) experiences within the digital space.
- User Interface – Understanding of how interactions within the digital space trigger and activate features, as well as their purpose.
- HMI Design – Understanding of how designs are created in the digital space and their influence on UX and UI.
- Prototyping – Ability to swap ECUs and manipulate wire harnesses to integrate prototype hardware.
Experience Required:
- 5+ years in the automotive industry, 3 years of software testing experience.
- Experience with ADB (Android Debug Bridge) for in-vehicle system debugging, or strong aptitude to quickly learn.
- Proficiency in Python for scripting, automation, and test tooling.
- Solid understanding of hardware-software integration principles in embedded or automotive systems.
- Experience with CAN bus interfacing hardware and CAN network signal deployment and monitoring, such as CAN analyzers, Vector tools, or similar platforms.
Experience Preferred:
- Strong analytical and root-cause troubleshooting skills, with the ability to systematically break problems down to fundamentals.
- Excellent adaptability, communication, and time-management skills in a dynamic, deadline-driven environment.
- Prior experience in HMI, UX, or UI validation testing for automotive or embedded consumer products preferred.
Education Required:
- Bachelor's Degree
Education Preferred:
- Master's Degree
About Stefanini Group paragraph:
"The Stefanini Group is a global provider of offshore, onshore and near shore outsourcing, IT digital consulting, systems integration, application, and strategic staffing services to Fortune 1000 enterprises around the world. Our presence is in countries like the Americas, Europe, Africa, and Asia, and more than four hundred clients across a broad spectrum of markets, including financial services, manufacturing, telecommunications, chemical services, technology, public sector, and utilities. Stefanini is a CMM level 5, IT consulting company with a global presence. We are a CMM Level 5 company."
We need to include sections only when posting has real, specific content. All sections have content.
We should not include "About Stefanini Group" as a heading? The instruction list includes "About the role" but not "About the company". However we could treat "About Stefanini Group" as "About the company" but not in list. Might be better to include as a paragraph under a heading like "About the company" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real, specific content. So we need to extract content.
We have:
- About the role: The description includes "We are seeking a detail-oriented and technically versatile Vehicle Software Integration Test Engineer..." That's about the role. Could be a paragraph.
- Responsibilities: bullet list of duties.
- Requirements: Could combine Skills Required, Experience Required, Education Required. Could separate into Skills, Experience, Education. But we can combine into Requirements? The instruction says we can use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide.
We have Skills Required list, Skills Preferred list, Experience Required, Experience Preferred, Education Required, Education Preferred.
We could create sections: Responsibilities, Skills, Experience, Education. Or combine Skills and Experience into Requirements. But better to follow typical: Responsibilities, Requirements (which includes Skills, Experience, Education). However they said we can use multiple headings. We'll include separate sections for Skills, Experience, Education if there is specific content.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. The page already shows it, so we don't add heading for Vehicle Software Integration Test Engineer.
We must not put Job ID/requisition numbers as headings; none.
We must preserve all substantive information.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About the role paragraph: "We are seeking a detail-oriented and technically versatile Vehicle Software Integration Test Engineer to join our team focused on Human-Machine Interface (HMI), user experience (UX), and user interface (UI) validation for next-generation vehicle systems. In this role, you will bridge hardware and software domains, working hands-on with in-vehicle systems and TDKs by utilizing debugging tools and performing software updates to support pre-production HMI quality validation initiatives. You will play a key role in ensuring our setups are ready to perform HMI validation testing reliably."
That's the role description.
Responsibilities: list items:
- Set up testing validation requests for HMI, UX, and UI features across vehicle infotainment systems on TDKs and vehicles.
- Utilize in-house diagnostic tools and Android Debug Bridge (ADB) to debug and set up testing environments on vehicles and TDKs.
- Work cross-functionally with software teams to set up and execute Python scripts to enable simulations supporting HMI testing and the software download process.
- Support hardware and software integration efforts through seamless communication between embedded control units by ensuring the correct software levels are flashed and appropriate DIDs are enabled for HMI testing in vehicle and TDK setups.
- Apply working knowledge of CAN hardware used for feature signal simulation, including recording CAN information to support the deployment and monitoring of CAN signals across vehicle networks.
- Break down complex system issues into fundamental root causes; troubleshoot concerns spanning both hardware and software layers; then retest to confirm resolution and enablement of HMI testing.
- Maintain an overall understanding of vehicle architecture and communication.
- Adapt quickly to shifting priorities, evolving test environments, and changing management or project demands in a fast-paced development setting.
- Perform HMI validation testing and report quality assurance concerns.
- Document software methodologies and procedures by working cross-functionally.
- Travel occasionally between Mexico and California.
Skills Required list:
- User Acceptance Testing – Perform HMI testing and validate software implementation against design releases.
- Software Documentation – Document processes and procedures related to updating vehicles and benches.
- Analytical Skills – Ability to break down configurations and simplify testing procedures and setup.
- Technical Troubleshooting – Utilize the ADB debugging bridge and general system integration debugging to solve testing requirements.
- Troubleshooting / Problem Solving – Review ECU configurations and identify root causes related to HMI testing.
- Test Integration Testing – Set up vehicles and TDKs with the appropriate hardware and software to test prototype designs and evaluate HMI content displayed on the screen.
- Hardware Experience – Basic understanding of SOA communication and the ability to read wiring diagrams and connectors.
- Software Communications – Other – Ability to utilize in-house debugging tools to set configuration bits and send CAN messages over a CAN bus to support HMI evaluation.
Skills Preferred list:
- User Experience – Understanding of Difficult to Use (DTU) experiences within the digital space.
- User Interface – Understanding of how interactions within the digital space trigger and activate features, as well as their purpose.
- HMI Design – Understanding of how designs are created in the digital space and their influence on UX and UI.
- Prototyping – Ability to swap ECUs and manipulate wire harnesses to integrate prototype hardware.
Experience Required:
- 5+ years in the automotive industry, 3 years of software testing experience.
- Experience with ADB (Android Debug Bridge) for in-vehicle system debugging, or strong aptitude to quickly learn.
- Proficiency in Python for scripting, automation, and test tooling.
- Solid understanding of hardware-software integration principles in embedded or automotive systems.
- Experience with CAN bus interfacing hardware and CAN network signal deployment and monitoring, such as CAN analyzers, Vector tools, or similar platforms.
Experience Preferred:
- Strong analytical and root-cause troubleshooting skills, with the ability to systematically break problems down to fundamentals.
- Excellent adaptability, communication, and time-management skills in a dynamic, deadline-driven environment.
- Prior experience in HMI, UX, or UI validation testing for automotive or embedded consumer products preferred.
Education Required:
- Bachelor's Degree
Education Preferred:
- Master's Degree
About Stefanini Group paragraph:
"The Stefanini Group is a global provider of offshore, onshore and near shore outsourcing, IT digital consulting, systems integration, application, and strategic staffing services to Fortune 1000 enterprises around the world. Our presence is in countries like the Americas, Europe, Africa, and Asia, and more than four hundred clients across a broad spectrum of markets, including financial services, manufacturing, telecommunications, chemical services, technology, public sector, and utilities. Stefanini is a CMM level 5, IT consulting company with a global presence. We are a CMM Level 5 company."
We need to include sections only when posting has real, specific content. All sections have content.
We should not include "About Stefanini Group" as a heading? The instruction list includes "About the role" but not "About the company". However we could treat "About Stefanini Group" as "About the company" but not in list. Might be better to include as a paragraph under a heading like "About the company" but not in allowed headings. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can add other headings if appropriate, but better to stick to those. Could we put company description under "About the role"? No, that's not accurate. Perhaps we can omit the company description? But we must preserve ALL substantive information. So we need to include it somewhere. Could we put it under a heading like "About Stefanini Group" as an ? The instruction didn't forbid other headings, just gave examples. So we can add About Stefanini Group
. That seems fine.
We must not include boilerplate like EEO etc. None.
Now produce HTML:
About the role
? The instruction didn't forbid other headings, just gave examples. So we can add About Stefanini Group
. That seems fine.
We must not include boilerplate like EEO etc. None.
Now produce HTML:
About the role
We are seeking a detail-oriented and technically versatile Vehicle Software Integration Test Engineer to join our team focused on Human-Machine Interface (HMI), user experience (UX), and user interface (UI) validation for next-generation vehicle systems. In this role, you will bridge hardware and software domains, working hands-on with in-vehicle systems and TDKs by utilizing debugging tools and performing software updates to support pre-production HMI quality validation initiatives. You will play a key role in ensuring our setups are ready to perform HMI validation testing reliably.
Responsibilities
- Set up testing validation requests for HMI, UX, and UI features across vehicle infotainment systems on TDKs and vehicles.
- Utilize in-house diagnostic tools and Android Debug Bridge (ADB) to debug and set up testing environments on vehicles and TDKs.
- Work cross-functionally with software teams to set up and execute Python scripts to enable simulations supporting HMI testing and the software download process.
- Support hardware and software integration efforts through seamless communication between embedded control units by ensuring the correct software levels are flashed and appropriate DIDs are enabled for HMI testing in vehicle and TDK setups.
- Apply working knowledge of CAN hardware used for feature signal simulation, including recording CAN information to support the deployment and monitoring of CAN signals across vehicle networks.
- Break down complex system issues into fundamental root causes; troubleshoot concerns spanning both hardware and software layers; then retest to confirm resolution and enablement of HMI testing.
- Maintain an overall understanding of vehicle architecture and communication.
- Adapt quickly to shifting priorities, evolving test environments, and changing management or project demands in a fast-paced development setting.
- Perform HMI validation testing and report quality assurance concerns.
- Document software methodologies and procedures by working cross-functionally.
- Travel occasionally between Mexico and California.
Skills
We could split into Required and Preferred but maybe just one Skills section with both? Better to have two subheadings? Not allowed? Could useSkills Required
andSkills Preferred
. That's okay. Let's do:Skills Required
- ...
Skills Preferred
- ...
Experience Required
- ...
Experience Preferred
- ...
Education Required
Bachelor's Degree
Education Preferred
Master's Degree
About Stefanini Group:About Stefanini Group
The Stefanini Group is a global provider of offshore, onshore and near shore outsourcing, IT digital consulting, systems integration, application, and strategic staffing services to Fortune 1000 enterprises around the world. Our presence is in countries like the Americas, Europe, Africa, and Asia, and more than four hundred clients across a broad spectrum of markets, including financial services, manufacturing, telecommunications, chemical services, technology, public sector, and utilities. Stefanini is a CMM level 5, IT consulting company with a global presence. We are a CMM Level 5 company.
Check for any duplicated lines: none. Now ensure we didn't include any boilerplate like "For quick apply, please reach out to Saurabh Kapoor at 248-582-6559/[email protected]" That's application instructions; we must remove application instructions. So we need to drop that line. Also "Stefanini Group is hiring! Stefanini is looking for Vehicle Software Integration Test Engineer, Dearborn, MI" maybe considered job title and location; we should not repeat job title as heading, but we can keep location? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. The location "Dearborn, MI" is minor metadata; we