🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Division R&D Department ARAS, CS & Validation Level EX Functional Area Control Strategy 1 Job Title Vehicle Control Software Development 2 Reporting Functional reporting to: General Manager, R&D 3 Background i) Educational Qualification Essential: B.Tech / M.Tech in Mechanical / Mechatronics / Automobile / Electrical (with strong control & system dynamics background) ii) Experience Minimum: 3 Maximum: 7 4 Job Role & Responsibilities Role: Vehicle Control Software development Technical/ Functional: Responsible for designing and developing control software and control strategies for vehicle systems across Powertrain, Braking, Chassis, Body, Hybrid & Electric vehicle domains. Developing Model Based Design (MBD) solutions using MATLAB, SIMULINK & STATEFLOW as per system and software requirement specifications. Generating production-quality C code using Auto Code Generation tools such as dSPACE TargetLink / MathWorks Embedded Coder. Performing Model-in-Loop (MiL), Software-in-Loop (SiL) validation and unit-level testing. Integration of generated C code with Base OS, task scheduling, and real-time execution validation. Development and integration of CAN Interface Layer, followed by full system integration testing. Vehicle-level Testing & Validation of control software on prototype and production-intent vehicles. Calibration and tuning of performance parameters using tools such as INCA, CANape, etc. Vehicle data acquisition and analysis using tools such as BUSMASTER, CANoe, etc. Preparation and maintenance of software documentation, control strategy documentation, and requirement traceability. 5 Competency Requirements Specific expertise required for functional area: Strong understanding of vehicle control systems, control theory, and dynamic systems. Sound knowledge of Powertrain systems (ICE/HEV/EV), Braking Systems (ABS/ESP), and Vehicle Dynamics. Multi-disciplinary understanding of vehicle electronics, sensors & actuators, ECUs, powertrain and chassis systems. Sound knowledge of CAN-BUS communication, diagnostic concepts, and vehicle network architecture. Strong hands-on experience with MATLAB, SIMULINK, STATEFLOW. Strong hands-on with auto-code generation tools such as TargetLink, Embedded Coder. Hands-on vehicle calibration and validation experience is mandatory. Good understanding of Model-in-Loop (MiL) and Software-in-Loop (SiL) testing practices. Awareness of software development best practices, source code management (SVN, Git), and CI/CD workflows. Python scripting knowledge for automation and data processing is an added advantage. Strong mechanical systems intuition: torque generation, driveline dynamics, etc. 6 Likely sources Continental, Eaton, Tata Technologies, Bosch, Daimler Truck Innovation Centre India, MBRDI, L&T, Ather, Ola Electric, KPIT, AVL.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.