Model Based Development Engineer- Vehicle Control Software

< Back

Model Based Development Engineer- Vehicle Control Software

Bengaluru, Karnataka, India

Work Model

On - Site

Career Level

On-Site

Availability

Immediate

Job ID

260801

Apply Now

About The Role About the role We are building a performance electric two-wheeler from the ground up — our own VCU, BMS, and motor controller software. We are looking for a Model-Based Development (MBD) engineer who will own the controls design layer of that stack: turning functional requirements into executable Simulink/Stateflow models, proving them out in MIL, and handing them to the firmware team in a form they can implement and trust. You will be deciding how the control logic and estimation algorithms actually work and defending those decisions in review.

What You’ll Do

• Translate functional requirements into models.

Take functional requirements for VCU, BMS, and MCU features and build corresponding Simulink / Stateflow / MATLAB models and algorithms— supervisory state machines, mode managers, torque arbitration, thermal derating, charging control, fault handling.

• Do the mathematical modelling.

Develop the underlying algorithms and plant models: battery equivalent-circuit models, SOC/SOH estimators, vehicle longitudinal dynamics, motor and drivetrain models, sensor models. Choose and justify the estimator structure, tuning, and numerical behaviour.

• Own MIL verification end to end.

Build test harnesses, author test cases traceable to each requirement, run model coverage (statement / decision / MC-DC), close gaps, and produce the verification evidence. Set up regression suites so model changes don’t silently break behaviour.

• Be the bridge to firmware.

Walk the firmware team through model intent, data types, fixed-point vs floating-point decisions, execution rates, signal ranges, and interface definitions. Review their implementation against the model. Debug together when bench behaviour diverges from simulation.

• Enforce modelling discipline.

Apply and maintain modelling guidelines, reusable libraries, data dictionaries, and version control of models.

• Close the loop with the vehicle.

Correlate models against bench, dyno, and on-road data. Re-tune, re-validate, and keep the model the source of truth as the vehicle matures.

• Support the path to SIL/HIL as our test infrastructure builds out, and contribute to code-generation workflows where we adopt them.

Requirements

• B.E./B.Tech/M.Tech in Electrical, Electronics, Mechanical, Instrumentation, Control Systems, or equivalent.
• 3–5 years of automotive experience in model-based development. EV experience strongly preferred.
• Deep hands-on Simulink, Stateflow, and MATLAB. You have personally built and shipped models, not just maintained someone else’s.
• Strong mathematical foundation — state-space representation, control theory (PI/PID, feedforward, anti-windup, gain scheduling), estimation and filtering, linear algebra, discretisation and numerical stability. You should be able to derive an algorithm on a whiteboard, not just wire up a block diagram.
• One of the following is mandatory: Battery estimation algorithms — SOC/SOH estimation using Kalman-family filters (EKF/UKF), coulomb counting with OCV correction, equivalent-circuit or electrochemical models, parameter identification from cell test data, SOP/power-limit estimation; or

FOC motor control — PMSM/BLDC field-oriented control, Clarke/Park transforms, current and speed loop design, field weakening, MTPA, sensorless position estimation or resolver/encoder handling, PWM and inverter modelling.

• Requirements-driven mindset. Comfortable working from formal functional requirements and maintaining bidirectional traceability from requirement to model to test.
• Clear technical communication. You can explain a filter, a state machine, or a derating curve to a firmware engineer well enough that they can implement it correctly without you in the room.

Good to have

• Auto-code generation experience (Embedded Coder, TargetLink) and fixed-point design.
• Functional safety exposure — ISO 26262, safety requirements decomposition, ASIL-rated functions, safe-state design.
• Python or MATLAB scripting for test automation and data post-processing.
• HIL / SIL experience (dSPACE, Speedgoat, Typhoon, PLECS, or custom rigs).
• Simulink Test, Simulink Coverage, Simulink Design…