Job Description & Details
This role puts you right in the middle of next-gen Driver Assist Technologies, working hands-on with AUTOSAR architectures for ADAS ECUs. If you enjoy wrangling arxmls and tightening the feedback loop between software generation and actual vehicle validation, this is a solid spot to build heavy automotive domain expertise.
What You'll Actually Be Doing
Your days will revolve around generating, checking, and integrating SWCs and arxmls using tools like Vector DaVinci. You are going to be configuring the RTE, building AUTOSAR compositions, and heavily automating these pipelines to keep code quality high. You'll also partner up with SIL and HIL teams to push CAE procedures forward so they spend less time chasing issues in physical vehicles and more time catching them in simulation.
The Core Tech Stack
Classic AUTOSAR and Vector DaVinci are the undisputed heart of this stack. You need a deep understanding of arxml generation, RTE configuration, and component inter-connections because a single misconfiguration here breaks the entire ECU build. Scripting and automation skills are just as crucial since the mandate is to eliminate manual overhead in code generation and report reviews.
Interview Expectations
Expect the hiring team to hand you a scenario where an RTE generation fails due to a mismatched port interface in an arxml file, and they'll want to hear your exact debugging steps using Vector tools. They are secretly testing whether you understand the underlying AUTOSAR metamodel or if you just blindly click buttons in GUI tools. They will also drill down into your experience with SIL/HIL setups to see how you tie software changes back to real-world sensor performance and hardware limitations.
Application Advice
Skip the generic automotive buzzwords and put your exact toolchain front and center. Explicitly list Vector DaVinci, Classic AUTOSAR, arxml authoring, and any Python or scripting languages you used to automate software workflows. ATS parsers are going to look for those exact tool names alongside your embedded C background, so make sure they appear naturally in your experience bullets.