Base Software Engineer - Communications

The Base Software Engineer will be responsible for the development of software for difference inhouse-developed control modules. Engineer will perform software requirements analysis, design, coding, test plan creation, and testing for Communication Stack software features and related CDD features. Perform reviews and/or inspections for requirements, design documents, Specifications, Autosar BSW Configurations, C/C++/assembly code, and test plans. Interact with other department/vendors on eliciting software requirements. Embrace and ensure virtualization methods and techniques are used in controls/software development life cycle. Basic Qualifications:

• Bachelor of Science degree in Electrical Engineering, Computer Engineering or a related Engineering degree from an ABET accredited University
• Minimum 5 years of Embedded software engineering experience
• Minimum of 3 years of experience or good understanding of embedded C/C++ software.
• Minimum of 3 Experience in Classic Autosar Communication stack configuration
• Deep understanding of Ethernet and CAN/LIN protocols
• Experience in programming / scripting language(s)
• Experience in software verification / validation
• Experience using data acquisition tools
• Strong communication skills, both verbal and written
• Ability to adapt to a changing environment with minimal effect on productivity

Preferred Qualifications:

• Experience with CAN stack, Ethernet Stack, SPI, LIN and Flash Bootloader integration, OSEK OS, or diagnostic management
• Hardware background (ability to read/understand ECU schematic, identify HW-SW integration issues)
• Automotive software development related experience either at work or university
• Embedded C/C++ software experience in Real Time Operating System environment
• Experience with Autosar Tools, ETAS ISOLAR, CANoe, CANAnlayzer, Lauterbach debugger
• Experience implementing Embedded Real-Time Controls and Software solutions.
• Strong understanding of internal combustion engines and/or vehicle subsystems
• Familiarity with microprocessor-based controls and development tools (emulators, debuggers, etc.)
• Experience in simulation/virtual methodologies and/or tools