Role: Lead - MBD Validation (EV Controls)

Location: Mohan Estate, Delhi

Technical Skills Required

Responsibilities

- About the role
- We design our vehicle controllers in-house, so no Tier-1 supplier validates the software for us. That makes validation our own quality gate between a Simulink model and a vehicle in a customer's fleet.
- You will build and run that gate: the test strategy, the MIL/SIL/PIL/HIL infrastructure, the automation, and the release sign-off. Our vehicles run 150–250 km a day in commercial duty, so a field fault means lost revenue for a fleet operator, not just a warranty claim.
- Key responsibilities
- Validation strategy and process
- • Define the V-model validation strategy for each controller: what is proven at MIL, SIL, PIL, HIL and vehicle level, and what exit criteria each stage needs.
- • Derive test cases from system and software requirements, with bidirectional traceability (requirements ↔ model ↔ test ↔ result).
- • Set and enforce model quality gates: MAAB/JMAAB modelling guidelines, Model Advisor checks, and structural coverage targets (decision, condition, MC/DC as needed).
- • Own software release sign-off: no controller build ships to production or fleet without a validation report from your team.
- Model and code-level testing
- • Run unit and integration testing on Simulink/Stateflow models using Simulink Test, Test Manager and harnesses.
- • Run back-to-back (MIL vs SIL/PIL) equivalence testing on auto-generated Embedded Coder / TargetLink code.
- • Drive static analysis and run-time error checks on generated and handwritten C (Polyspace or equivalent, MISRA C).
- • Build and maintain plant models (motor, inverter,



battery, charger, vehicle dynamics) fit for closed-loop testing.
- HIL and test infrastructure
- • Own the HIL benches (dSPACE SCALEXIO or equivalent): architecture, I/O and CAN configuration, fault-injection, and commissioning of new rigs.
- • Build test automation (Python, AutomationDesk / ECU-TEST or equivalent) with nightly regression runs integrated into CI (Jenkins/GitLab).
- • Cover fault-injection and edge cases the vehicle can't safely reproduce: sensor failures, CAN loss, thermal derating, over/under-voltage, contactor faults.
- Vehicle and field validation
- • Plan and support vehicle-level validation with the T&V; team, using CAN logs (CANoe/CANalyzer) to close the loop between bench and road.
- • Triage field and fleet issues back to root cause in model or code, and add a regression test for every escaped defect.
- Team and cross-functional leadership
- • Hire, lead and mentor a team of 4–6 validation engineers.
- • Work with controls, embedded, electrical, charging and service teams, plus suppliers for sensors, cells and chargers.
- • Support functional safety (ISO 26262) and cybersecurity (ISO/SAE 21434) work products for validation, and prepare for ASPICE-style process audits.
- Must-have qualifications
- • B.E./B.Tech in Electrical,



Electronics, Instrumentation or Mechanical Engineering; M.Tech in automotive electronics or controls preferred.
- • 8–12 years in automotive controls, with at least 5 years hands-on in MBD testing and validation.
- • Deep MATLAB/Simulink/Stateflow skills, including Simulink Test and Embedded Coder or TargetLink generated code.
- • Proven MIL and unit testing of production controller models, with coverage and traceability reporting.
- • Hands-on HIL experience on dSPACE, NI or Vector platforms, including fault-injection testing.
- • Working knowledge of at least two EV controllers (VCU, MCU, BMS or charger) and how they interact over CAN.
- • CAN tools fluency: CANoe/CANalyzer, DBC management, log-based debugging.
- • Test scripting in Python for automation and log analysis.
- • Has taken at least one EV controller software release from model to production vehicle.
- Good-to-have qualifications
- • Set up or commissioned an EV controls lab or HIL bench from scratch.
- • ISO 26262 functional safety exposure (ASIL decomposition, safety-case evidence from testing).
- • ISO/SAE 21434 cybersecurity awareness or certification.
- • ASPICE SWE.4–SWE.6 process experience or audit participation.
- • CI/CD for model-based workflows (Jenkins, GitLab CI, Simulink Project, Git/SVN).
- • Static analysis with Polyspace and MISRA C compliance.
- • Battery algorithms (SOC/SOH estimation) or DC rapid-charging protocols (Bharat DC-001, CCS2, GB/T).
- • Commercial 3W or 4W EV background, where duty cycles and fleet uptime drive requirements.

📌 Lead - MBD Validation (EV Controls) (Delhi)
🏢 Euler Motors
📍 Delhi