Back to Jobs
Recently postedTechnology

Senior Software Validation Engineer

MY RECRUE LLCPalo Alto, CA🇺🇸United States

Quick overview

SeniorityMid-Senior
Work modeOn-site
LocationPalo Alto, CA, United States
Embedded SystemsAndroid

Job description

Title: Senior Software Validation Engineer
Location: Palo Alto, CA, 5 days onsite (Local Only)
Duration: 12+ Months Contract
Client: FORD
Interview: Video

Job Description:

Scope Summary

  1. Senior Software Validation Engineer
  2. Domain: Automotive Software Validation / HIL / System-Level & Vehicle Validation
  3. Responsible for validating software and vehicle features at the system level, understanding the interaction between vehicle hardware, ECmodules, embedded software, features, and the HIL/test environment.
  4. Troubleshoot failures across the full vehicle → hardware → software → feature → validation chain rather than focusing only on isolated software test execution.
  5. Support HIL and vehicle-level validation, root-cause analysis, test execution, issue investigation, and overall system maturity.
  6. One resource may operate at a Lead level, providing technical direction and helping drive validation activities across the team.

What to Look For

  1. Target 10+ years of directly relevant software testing/validation experience, ideally within automotive, aerospace, or another complex physical system environment. This should be 10+ years of relevant validation experience, not simply 10+ years of total career experience.
  2. 15–20 years of experience is completely acceptable, particularly for someone capable of functioning as a technical lead.
  3. Strong background in one or more of the following:
    • Automotive software validation
    • Vehicle-level validation
    • System-level validation
    • HIL validation/testing
    • ECU/system integration
    • Embedded software testing
    • Vehicle systems integration
  4. Candidates should understand the relationship between vehicle hardware, embedded software, ECmodules, features, and validation without needing significant training on how vehicle systems operate.
  5. Must be comfortable troubleshooting beyond the test result. When a validation test fails, they should be able to investigate whether the problem originates from software, hardware, configuration, vehicle electrical behavior, an ECU/module, communication, or the test/HIL environment itself.
  6. Look for engineers with experience working with physical HIL hardware or real vehicle/system environments, not candidates whose careers have primarily consisted of executing tests inside pre-existing simulation environments.
  7. Automotive is strongly preferred. Aerospace system validation can also translate well when the candidate has worked with embedded software, physical hardware integration, system-level testing, and complex electrical/electronic systems.
  8. Experience with lab cars, HIL benches, ECUs, vehicle networks, automotive diagnostics, system integration, or vehicle electrical systems is highly valuable.
  9. Lead-level candidate: Look for someone who can independently drive validation activities, troubleshoot complex cross-domain issues, guide other engineers, and quickly understand a new vehicle/system architecture.
  10. Big plus: Previous automotive OEM experience involving vehicle programs, HIL, system integration, software maturity, vehicle-level validation, or launch activities.

Profiles to Be Careful With

Silicon / Semiconductor Validation

Heavy semiconductor or silicon-validation experience is not directly transferable by itself. Someone may have significant validation experience but still require too much ramp time if that validation primarily involved chips rather than vehicles, ECUs, embedded systems, physical hardware, and end-to-end system behavior.

“10+ years of validation” alone should not qualify the candidate.


ADAS-Heavy Candidates

ADAS experience is not an automatic rejection, but candidates whose experience is predominantly ADAS simulation are likely not the target.

Be cautious when most experience centers around:

  • ADAS simulation
  • Lane departure/collision avoidance testing
  • Virtual test environments
  • Executing predefined scenarios
  • Simulation environments that someone else already built

The issue is whether they can move outside the simulation and troubleshoot a physical HIL/system environment.


Infotainment-Only Candidates

Infotainment exposure can be useful, particularly at the broader vehicle/system level.

However, candidates whose experience is primarily Android Auto, UI/interface validation, display behavior, or narrow infotainment feature testing may not have enough underlying systems depth.

Thanks and regards

AMIT DUBEY

Technical Recruiter
Email:
Cell:

Will your resume get past this employer's screening? Check your resume against this job, free

Similar jobs