Ajit Vilas Gajre

Ajit Vilas Gajre’s career sits at a hinge-point in the automotive industry: the shift from feature-by-feature electronics to software-defined vehicles, where capabilities like seating, steering, and safety systems are engineered as tightly governed software products rather than isolated ECU behaviors. Over more than a decade in automotive engineering, he has built a track record in a domain that rarely gets public attention but determines whether modern vehicles feel refined, safe, and dependable—requirements engineering, software design release, and validation of complex chassis and occupant systems, frequently under functional-safety constraints.

In his most recent work as Subsystem Lead Engineer for Occupant Positioning, Gajre’s scope centers on translating “what the vehicle must do” into subsystem-level requirements and traceable blueprints—then coordinating software, hardware, and validation teams to deliver. His application describes this effort as part of a broader migration away from distributed ECU-based designs toward centralized compute and zonal control, a direction widely recognized as foundational to software-defined vehicle programs because it reduces hardware duplication and enables faster, more consistent feature evolution via software.

Before that, he served as a Software Design Release Engineer for memory seat modules, delivering integrated software and calibration packages across multiple programs while driving validation traceability and “saleable” readiness. The thread connecting this work is less about a single feature and more about disciplined systems engineering: ensuring driver/passenger memory behavior is consistent across vehicle lines, requirements map cleanly to test artifacts, and supplier collaboration does not introduce late-breaking risk.

Earlier, as a Lead Subsystem Validation Engineer, he operated at the proving ground between design intent and real behavior—validating rear steering, front steering, driveline and related diagnostics on HIL benches and vehicles. These are not cosmetic capabilities: four-wheel steering modes (including GM’s well-known “CrabWalk” behavior on certain platforms) are a visible consumer differentiator, but they are only shippable when control logic, diagnostics, and edge-case handling stand up under exhaustive validation.

His foundation in active safety functional-safety validation (Traffic Jam Assist and Low Speed Collision Mitigation Braking) reflects the other half of the modern vehicle equation: the features that must work correctly not just in demos, but across long-tailed, safety-relevant scenarios—and do so in a way that satisfies industry functional safety expectations such as ISO 26262.  In practice, this often means requirements-driven test design, peer-reviewed procedures, and execution on established validation toolchains (for example, requirements management platforms like IBM DOORS and HIL environments from dSPACE are widely used in the industry for exactly this kind of verification discipline).

Across these roles, Gajre presents a profile of an engineer operating where software rigor meets physical-world constraints: ensuring that features involving human positioning, steering geometry, chassis actuation, and safety behavior are specified with precision, verified with traceability, and delivered with a level of repeatability that software-defined vehicle programs demand.