C++ Platform Integration Engineer

Based in Mountain View, CA, Cyngn is a publicly-traded autonomous technology company. We deploy self-driving industrial vehicles
- specifically autonomous tuggers - to factories, warehouses, and other facilities throughout North America. To build this emergent technology, we are looking for innovative, motivated, and experienced leaders to join us and move this field forward. If you like to build, tinker, and create with a team of trusted and passionate colleagues, then Cyngn is the place for you. Key reasons to join Cyngn:

We are small and big.

With under 100 employees, Cyngn operates with the energy of a startup. On the other hand, we’re publicly traded. This means our employees not only work in close-knit teams with mentorship from company leaders—they also get access to the liquidity of our publicly-traded equity.

We build today and deploy tomorrow.

Our autonomous vehicles aren’t just test concepts—they’re deployed to real clients right now. That means your work will have a tangible, visible impact.

We aren’t robots. We just develop them.

We’re a welcoming, diverse team of sharp thinkers and kind humans. Collaboration and trust drive our creative environment. At Cyngn, everyone’s perspective matters—and that’s what powers our innovation.

• This is a high-impact, technical leadership role for a C++ Engineer who thrives at the intersection of complex software architecture and physical reality. You will join our Platform and Vehicle Infrastructure (VI) teams to architect, build, and deploy the core systems that command our autonomous tuggers. As a subject matter expert, you will bridge multiple domains—Firmware, Autonomy, and Cloud to ensure cohesive system design and seamless integration.
  
  We value engineers who take full ownership of their systems, drive architectural decisions, and provide technical guidance across the organization. If you are passionate about high-performance software engineering and seeing your architectural vision power real-world robotics, this is the environment for you.
• The physical vehicle is our primary development environment. A significant portion of this role involves hands-on integration in the vehicle bay - debugging on bare metal and working directly with hardware and sensors. This role is for the engineer who views physical interaction with the machine as the most rewarding part of the software development lifecycle.

• Develop and scale production C++ code within ROS 2 nodes and diagnostic tooling, focusing on modularity and high performance.
• Write code that other people can maintain: clear interfaces, real tests, useful logging, and honest documentation.
• Debug in earnest - gdb, sanitizers, profilers, core dumps, and log/bag analysis - including the failures that only appear on the vehicle.
• Own the full lifecycle of a feature from architectural discussion to deployment on hardware, supported by structured mentorship.

• Bring up new features on real vehicles: deploy, configure, run, observe, and report what actually happened.
• Own the hands-on integration loop - connect to the vehicle, run the scenario, capture bags and logs, reproduce the problem, and narrow it to a root cause.
• Work directly with the hardware: sensors, compute, CAN traffic, firmware versions, cabling, and the physical vehicle itself.
• Build and improve the test tooling, scripts, and automation that make this loop faster and repeatable for everyone.
• Help validate release candidates on hardware alongside VI and QA, and help chase down regressions that only show up in the real world.

• Partner with the Firmware team when the problem is below your layer, the Autonomy team when it's above, and the Cloud team when it crosses the vehicle boundary - and help all three by producing clean, well-characterized reproductions instead of "it doesn't work".
• Support the Platform and VI teams on whatever the vehicle needs that week; this is a role where being useful matters more than owning a fiefdom.
• Communicate clearly and often with teammates in the office and remote colleagues in other time zones.

• Use…