1

Embedded Autosar Developer Jobs in Michigan (NOW HIRING)

Showing results 21-40

Embedded Autosar Developer information

What is an Embedded Autosar developer?

Embedded AUTOSAR Developers are software engineers who specialize in developing, integrating, and maintaining automotive software systems based on the AUTOSAR (AUTomotive Open System ARchitecture) standard. They work primarily with embedded systems in vehicles, creating standardized software components that enable interoperability and scalability across different automotive platforms. Their responsibilities include configuring AUTOSAR stacks, writing application code, and ensuring compliance with automotive safety and quality standards. They often collaborate closely with hardware engineers and other software teams to deliver robust automotive solutions.

What are the key skills and qualifications needed to thrive as an Embedded Autosar developer?

To thrive as an Embedded Autosar Developer, you need a solid background in embedded systems, C/C++ programming, and familiarity with the AUTOSAR architecture, often supported by a degree in computer engineering or a related field. Experience with tools like Vector DaVinci, EB tresos, and knowledge of automotive communication protocols such as CAN, LIN, and FlexRay are highly valued, along with AUTOSAR certification. Strong problem-solving skills, attention to detail, and effective teamwork enable developers to handle complex automotive software requirements. These skills ensure reliable, scalable, and safety-compliant automotive software solutions in a rapidly evolving industry.

What are some common challenges faced by Embedded Autosar developers when integrating third-party software components?

Embedded Autosar Developers often encounter challenges when integrating third-party software due to compatibility issues with Autosar standards, version mismatches, and differing coding guidelines. Ensuring seamless communication between components and maintaining real-time performance can be complex, especially when dealing with proprietary APIs or hardware constraints. Close collaboration with suppliers, thorough documentation review, and rigorous testing are crucial to address these challenges and ensure system reliability.

What is the difference between Embedded Autosar Developer vs Embedded Software Engineer?

AspectEmbedded Autosar DeveloperEmbedded Software Engineer
Required CredentialsBachelor's in Computer/Electrical Engineering, Autosar certifications (optional)Bachelor's in Computer/Electrical Engineering, relevant certifications (e.g., embedded systems)
Work EnvironmentAutomotive industry, embedded systems developmentVarious industries including automotive, consumer electronics, industrial
Employer & Industry UsageAutomotive OEMs, Tier 1 suppliersWide range of sectors, including automotive, aerospace, IoT
Common Search & ComparisonYesYes

Embedded Autosar Developers specialize in automotive-specific embedded systems using Autosar architecture, focusing on automotive standards and protocols. Embedded Software Engineers have a broader scope, working on embedded systems across multiple industries. While both roles require embedded programming skills, Autosar Developers need specific knowledge of Autosar standards, making their expertise more specialized within automotive embedded development.

Embedded C Software Engineer

Dearborn, MI • On-site

Dechen Consulting Group
IT Services • 11 - 50 employees

$121K - $159K/yr

Other

Re-posted 16 days ago


Job description

W2 ONLY PLEASE, NO C2C

As an Embedded Controls Software Engineer, you will be a critical contributor to the design, development, and validation of advanced embedded control software for next-generation automotive systems. This specialized role focuses on the Body Control Module, directly impacting vehicle safety, user experience, and electrification readiness. You will leverage your expertise in controls theory, real-time systems, and embedded architecture to architect, develop, and optimize complex, safety-critical software throughout the entire product lifecycle. The Body Control Software team is a team dedicated to creating Body Control Application Software components, developing and enhancing existing software components that integrate with existing architectures, as well as our next-generation vehicle systems. 

PRIMARY SKILLS REQUIRED: 
Embedded Software 
– Candidate should demonstrate the full lifecycle of embedded software development 
— from requirements to implementation to on-target validation 
— for safety-critical automotive systems. 
Example: Taking a system-level requirement for a new BCM feature, translating it into a functional spec, implementing the control logic, and validating it through SIL/HIL testing using Vector CANoe before production release. 
5. Embedded Systems 
– Candidate should understand the broader hardware-software interaction, real-time constraints, and communication protocols (CAN/LIN) governing embedded automotive systems.
Example: Diagnosing a field issue where a BCM module intermittently fails to respond over CAN, performing root cause analysis using CANoe traces and the MULTI debugger, and implementing a fix that accounts for timing/interrupt behavior on the target ECU.

Skills Required:
Matlab, Coding, C++, Embedded Software, Embedded Systems 
1. MATLAB – Candidate should demonstrate hands-on experience using MATLAB/Simulink (including Stateflow) to model, design, and simulate embedded control algorithms for BCM features. 
Example: Building a Simulink state machine to model a vehicle lighting or door control feature, running Model-in-the-Loop (MIL) simulations to validate logic, and using Model Advisor checks to ensure modeling standards compliance before code generation. 
2. Coding – Candidate should be able to write clean, efficient, and standards-compliant code for embedded automotive applications, including scripting for automation. Example: Developing a Python automation script to parse test logs and auto-generate pass/fail reports, reducing manual validation time during regression testing cycles. 
3. C++ - Candidate should show proficiency writing and debugging C/C++ code for real-time, resource-constrained embedded targets, including implementing AUTOSAR software components. 
Example: Implementing a C++ AUTOSAR SWC (Software Component) for a BCM feature (e.g., power window control), integrating it via DaVinci Developer, and validating memory/timing constraints on target hardware.