Hello,
Hope you’re doing well!!
Please find the requirement below. If you find yourself comfortable with the requirement, please reply with your updated resume or call me back at
Position :: Validation Engineer
Location:: Sunnyvael, CA Onsite
Duration :: 6+ Months(CTH)
Interview Process:
· Initial recruiter screen with Internal TA (15 min)
· 2 x 45-minute technical interviews
· Final 30-minute conversation
o Interview process can potentially be completed in one day for onsite candidates
o Scenario/problem-solving focused interviews
o Technical evaluation includes practical validation methodology and light Python scripting/automation questions
Must Have Linkedin profile
Job Description
What have you been running into:
· Candidates from OEM environments often struggle because they are used to validating complete end-to-end vehicle systems instead of partial ECU/signal-level systems.
· Many testers lack enough Python scripting/automation capability.
· Some candidates are too focused on manual QA vs true automotive validation/system-level reasoning.
· Need candidates who can logically reason through incomplete systems and independently execute testing.
· Need candidates comfortable in a fast-paced startup environment.
Intake Note:
· Mid-level candidates are acceptable/preferred. Do NOT send entry-level/fresh grads.
· Strong preference for candidates with infotainment/IVI validation backgrounds from OEMs or Tier-1 suppliers.
· Candidates do NOT need to be expert coders, but they must be able to read/modify/create Python automation scripts using existing frameworks/templates.
· They want engineers who understand systems behavior, CAN/signals, and ECU-level interactions.
· This is more validation engineering than pure QA and not a mobile or software QA.
· They are flexible on exact Bluetooth/WiFi experience if the candidate has strong automotive infotainment validation fundamentals.
· The environment is highly collaborative and fast paced.
· Local candidates strongly preferred, but relocation is possible.
· Multiple openings (2+ currently for HMI validation, likely growing).
· Candidates open to contract only OR contract-to-hire are acceptable.
Automotive IVI/HMI (Human Machine Interface) Validation Engineer:
We are looking for engineers with experience in Android-based HMI systems, including UI automation (Python/Appium), connectivity (Bluetooth, WiFi), and manual bench/vehicle testing.
What’s this team's overall project:
Team is working on Android-based in-vehicle infotainment/HMI systems that are approaching production release. The focus is accelerating validation and verification efforts across infotainment features, connectivity systems, ECU interactions, and automation coverage.
What will they be working on:
· Validation of Android-based IVI/HMI systems
· Manual and automated testing of infotainment features
· UI automation scripting using Python/Appium
· Connectivity validation (Bluetooth/WiFi)
· Bench-level and partial-system validation
· ECU/signal-level validation and troubleshooting
· Extending/modifying existing automation frameworks
· Working alongside developers and validation teams to execute existing test plans and build additional test coverage
What does their day to day look like:
· Executing manual and automated validation test cases
· Writing/modifying Python automation scripts
· Testing infotainment applications such as radio, phone, media, connectivity, etc.
· Performing bench testing on partial systems and ECUs
· Reviewing requirements and validating expected system behavior
· Debugging system/signal interactions
· Running validation scenarios independently using existing frameworks/tools
· Collaborating closely with developers and validation engineers onsite
What types of vehicles will they be working on:
Vehicle agnostic. Applied Intuition is not functioning as a traditional OEM in this environment. Candidates may be validating partial systems, ECUs, and infotainment modules rather than complete end-to-end production vehicles.
Must Have Skills:
· Automotive infotainment / IVI / HMI validation experience
· Android-based HMI systems
· Python scripting experience
· UI automation experience (Appium preferred)
· Validation engineering mindset vs pure QA testing
· Experience with manual bench testing
· Understanding of ECU/signal-level behavior
· Connectivity validation (Bluetooth/WiFi)
· Ability to work with partial systems/incomplete vehicle environments
· Automotive industry experience (OEM or Tier-1)
· Comfortable onsite 5 days/week
· ADB experience
· CAN/CAN bus familiarity
· Android Auto / Apple CarPlay exposure
· Experience extending existing automation frameworks
· Experience validating infotainment apps/features (radio, navigation, phone, media, HVAC controls, etc.)
· Prior startup or fast-paced engineering environment experience
· Strong troubleshooting/debugging mindset
· Prior embedded systems exposure
· Experience with automation frameworks and reusable test scripting
|
Acronym
|
Full Meaning
|
What it is
|
|
IVI
|
In-Vehicle Infotainment
|
Vehicle infotainment systems including radio, navigation, media, phone connectivity, etc.
|
|
HMI
|
Human Machine Interface
|
The screens/buttons/interfaces drivers interact with inside the vehicle.
|
|
ECU
|
Electronic Control Unit
|
Embedded computer/module inside the vehicle controlling specific functions.
|
|
OEM
|
Original Equipment Manufacturer
|
Automotive manufacturers like Ford, GM, Rivian, Tesla, Lucid, etc.
|
|
CAN
|
Controller Area Network
|
Main communication network/protocol inside vehicles.
|
|
CANoe
|
CAN Open Environment
|
Vector tool used for automotive network simulation/testing/validation.
|
|
CANalyzer
|
CAN Analyzer
|
Vector diagnostic and analysis tool for automotive communication networks.
|
|
Vector
|
Vector Informatik
|
Company that makes automotive validation/network testing tools.
|
|
dSpace
|
dSpace Simulation Platform
|
Industry-standard Hardware-in-the-Loop simulation/testing platform.
|
|
HiL / HIL
|
Hardware-in-the-Loop
|
Testing physical EChardware against simulated vehicle environments.
|
|
SiL / SIL
|
Software-in-the-Loop
|
Testing software in a simulated environment before physical hardware integration.
|
|
Autosar
|
Automotive Open System Architecture
|
Standardized automotive software architecture/framework used heavily in ECUs.
|
|
Classic Autosar
|
Traditional Autosar stack
|
Common embedded automotive software framework used across ECUs.
|
|
SWE.6
|
Software Qualification Testing
|
ASPICE software validation/testing process level.
|
|
SYS.4
|
System Integration & Integration Testing
|
ASPICE system-level validation/testing phase.
|
|
ASPICE
|
Automotive SPICE
|
Automotive software development/process quality standard.
|
|
Bench Testing
|
Hardware Bench Validation
|
Testing ECmodules outside a complete vehicle environment.
|
|
Signal-Level Validation
|
ECU Signal Validation
|
Verifying signals/messages change correctly when actions occur.
|
|
Partial System Testing
|
Subsystem Validation
|
Testing incomplete vehicle systems/modules instead of full vehicle integration.
|
|
Embedded Systems
|
Hardware + Software Systems
|
Low-level software running directly on automotive hardware/ECUs.
|
|
Device Driver
|
Hardware Interface Software
|
Software layer controlling communication between ECU hardware and software.
|
Thanks & Regards
Vinay Kumar
Senior Technical Recruiter
VISION INFOTECH INC
Phone:
Email:
368 Main Street, st #3, Melrose MA 02176
E-Verified Company