Embedded C++ Engineers

We are seeking 3 Embedded C++ Engineers (junior to mid-level, 1–4 years) to support development and integration of domain controller and datalink software platforms used across machine and vehicle applications.

This role focuses on building and supporting application-level software that interfaces with core datalink and communication layers , enabling higher-level features and system functionality.

Key Responsibilities

• Develop and support application-layer software in C++ built on top of domain controller and datalink frameworks.
• Integrate software components across ECUs, communication stacks, and vehicle systems to enable end-to-end functionality.
• Work with CAN, J1939, Ethernet, and other datalink protocols to support data flow between subsystems.
• Collaborate with systems, controls, and hardware teams to ensure proper interface definition and system integration .
• Troubleshoot and resolve system-level and communication issues across software and network layers.
• Support software validation and integration testing , including debugging data flows and signal behavior.
• Contribute to feature enhancements for domain controller platforms supporting multiple applications.

Required Skills

• 1–4 years of experience in embedded C++ development POST MASTERS. Don’t show me pp w just projects in masters
• Experience working in embedded systems or vehicle/machine platforms .
• Understanding of datalink protocols (CAN, J1939, Ethernet) and how data moves across systems.
• Experience with Linux or embedded operating systems .
• Strong debugging and problem-solving skills at system and integration level (not just component-level).
• Ability to work across cross-functional teams in a fast-paced environment.

Preferred Qualifications

• Experience working with domain controllers or centralized compute architectures .
• Exposure to AUTOSAR, middleware, or communication stacks .
• Familiarity with tools like CANalyzer, Wireshark, or similar diagnostic tools .
• Background in automotive, off-highway, or robotics platforms .

Nice to Have

• Understanding of applications layer vs firmware (focus is NOT low-level drivers) .
• Exposure to autonomy, telematics, or connected systems.