Recently, the frequency of updates has decreased as we approach the project milestones, and I went on a long business trip for road testing and debugging. Based on this business trip experience, I would like to discuss the current situation of embedded software engineers in the automotive industry:

The Dilemma of Today’s Embedded Software Engineers

The General Environment

Firstly, in the context of a highly competitive environment, almost all car manufacturers have further reduced the development cycles for new models and iterations, under the guise of “cost reduction and efficiency improvement.” In this context, a chain reaction occurs:

• Some projects have weakened or eliminated the DV phase, directly entering the PV phase, which leads to different software and hardware versions being produced at different times. The software version of the first batch of vehicles may even lag behind several versions, necessitating continuous updates or ensuring that the factory produces the latest version.
• Engineers often work late nights, and all-nighters are common; if one lacks the ability to handle pressure, it can lead to burnout.

Job Characteristics

Once in the mass production stage, the cost of software updates is much lower than that of hardware updates. This is also why software engineers often travel more than hardware engineers. Additionally, since embedded systems combine both hardware and software, some hardware issues are also addressed by software engineers. Although embedded software engineers generally earn slightly more than their hardware counterparts, I feel the cost-effectiveness is not as high.

Due to the cost of software, most people’s first thought when solving problems is:

• Can it be solved through software? Algorithm optimization? Strategy optimization?
• Can it be avoided by software? Temporary measures?

Company Attitudes Towards Business Trips

In the past, getting approval for business trips was easy, and the allowances were considerable. Nowadays, with the “decline of the river and the sea,” the reduction of travel allowances and even limits on accommodation and meal expenses have been a blow to many who “enjoy” traveling for work.

When client issues arise that need resolution, a decision on whether to travel on-site is often not made until the last moment; the first choice is usually remote support, as business travel is costly.

Remote support is often inefficient, and analyzing and troubleshooting problems can be challenging. Engineers frequently find themselves rushing to the site with tools and equipment just before the deadline.

How to Break the Deadlock?

The author is confused; leave your thoughts…