Automotive Software Engineer focused on robust embedded systems, safety-critical workflows, and data-driven vehicle platforms.
I work at the intersection of embedded firmware, functional safety culture, and scalable telemetry—turning requirements into maintainable code, traceable verification, and clear system-level outcomes.
A timeline snapshot of work focused on embedded reliability, safety, and vehicle data platforms.
I aim to build automotive software that is dependable by design—clear interfaces, predictable timing, strong diagnostics, and a safety culture that holds up in production.
Deliver vehicle software that behaves predictably in the real world: graceful degradation, actionable diagnostics, and maintainable architecture that teams can evolve confidently.
ADAS-adjacent systems, embedded C/C++, AUTOSAR concepts, vehicle communications, cloud telemetry pipelines, and a strong verification mindset aligned with safety expectations.
I communicate with crisp artifacts—design notes, interface contracts, test strategy—so cross-functional teams can align quickly, reduce ambiguity, and ship with confidence.
I’m Santosh Kumar, an Automotive Software Engineer who enjoys building embedded systems that are both resilient and understandable. I care about clean boundaries, practical verification, and the invisible details that make products feel trustworthy—startup behavior, timing margins, recovery paths, and diagnostics that help service teams move fast.
My work spans embedded firmware, vehicle communications, and telemetry—bridging on-target constraints with the needs of cloud analytics and product iteration. I’m comfortable moving between low-level debugging and system-level design discussions.
I’ve helped teams ship features with tighter integration loops and clearer ownership by improving interfaces, test strategy, and build-time checks. I like solving problems that reduce friction for everyone: better tooling, better error messages, and more reliable release processes.
I prioritize clarity: define the contract, write the smallest correct solution, and back it with tests and observability. If you’re interested in collaborating, take a look at my resume or reach out via email.
If you’re here to evaluate fit quickly, these are the fastest ways to get context—work, resume, community efforts, and contact.