Career Advice: Mastering C/AUTOSAR/Yocto vs. Expanding to Physical AI/ROS?

19 hours ago 3
ARTICLE AD BOX

Hello everyone,

I am an aspiring embedded software engineer currently enrolled in the '42' program, focusing heavily on C and C++ from the ground up.

Currently, I am working on a project using the S32K144EVB with AUTOSAR MCAL (RTD) via EB tresos. At the same time, I am studying the Yocto Project to build custom embedded Linux images.

My dilemma is that I have an opportunity to take a "Physical AI" course involving Python, ROS, and AI model deployment on Raspberry Pi. While it sounds exciting, I feel that my C/C++ foundation is not yet solid, and managing all these (42 tasks, S32K/AUTOSAR, Yocto, and AI) simultaneously feels overwhelming.

My questions to the community are:

In the current automotive industry (SDV, Zonal Architecture), is it better to double down on the "Deep Stack" (C/C++, AUTOSAR internals, Yocto/Kernel) or expand "Wide" with AI and Python early on?

How much does a junior's lack of deep C/C++ knowledge (e.g., memory mapping, hardware timing analysis) hurt their career even if they know AI/ROS?

Would focusing solely on the S32K144 + Yocto integration (HPC-to-Zone architecture) be a competitive enough portfolio compared to a general AI-robotics project?

I would love to hear from senior engineers who have seen how the industry is evolving.

Thank you for your time!

Read Entire Article