This didn’t start as a headline project.

It started with uncertainty.
Limited data.
Limited compute.
A small team.
And a market that didn’t fully believe ADAS belonged in Indian commercial vehicles.

But that’s exactly what made it worth doing.

The Context: ADAS for Indian Commercial Vehicles

At Euler Motors, I led the ADAS R&D division with a clear but difficult goal:

Build production-ready ADAS for Indian roads—not demos, not lab experiments.

This meant designing systems that could survive:

• chaotic traffic patterns
• poor lane markings
• unpredictable pedestrians and vehicles
• harsh lighting, dust, and weather
• real cost and hardware constraints

No shortcuts. If it didn’t work on Indian roads, it didn’t ship.

🎥 Project video:
https://www.youtube.com/watch?v=rYAtfVqzBkM

Video Credits: https://www.youtube.com/watch?v=rYAtfVqzBkM

Phase 1: Ambition Meets Reality

Early prototypes exposed uncomfortable truths:

• algorithms that worked in simulations failed on real roads
• perception models broke under lighting extremes
• latency and reliability mattered more than accuracy alone
• edge cases weren’t edge cases—they were the norm

This phase forced a mindset shift.

Not “Can we build ADAS?”
But “What ADAS is actually deployable here?”

Phase 2: Engineering for the Real World

We focused on fundamentals:

• robust perception pipelines over flashy models
• tight hardware–software integration
• relentless field testing instead of overfitting datasets
• designing for failure modes, not best cases

From this came production-focused features, including:

• Night Vision Assist
• Front Collision Warning

These weren’t experiments.
They were engineered, validated, and market-ready.

Delivery: From R&D to Road

The real milestone wasn’t internal demos.

It was seeing these systems:

• attract strong market attention
• validate that ADAS can work in Indian commercial EVs
• shift conversations from “Is this possible?” to “What’s next?”

A small team.
High expectations.
Real impact.

What This Project Was Really About

This wasn’t about copying global OEMs.

It was about:

• building advanced systems under extreme constraints
• respecting Indian road realities instead of ignoring them
• translating research into deployable products
• proving that serious ADAS engineering can be done locally

What Leading This Taught Me

More than technology, this role taught me:

• ADAS fails fast if you disrespect context
• robustness beats novelty
• deployment is harder than research
• leadership means protecting engineering integrity
• small teams can outperform—if focused

Most importantly:

You don’t build ADAS by chasing features.
You build it by surviving reality.

Closing Thought

These systems weren’t built to impress slides.

They were built to work.

Grateful to CEO Saurav sir for trusting a small, determined team to take on something that was considered risky—and for backing engineering over optics.

This wasn’t just ADAS development.

It was applied engineering—done the hard way.