• Us Citizen

• Green Card

• EAD (OPT/CPT/GC/H4)

• H1B Work Permit

• Corp-Corp

• Consulting/Contract

• UG :- - Not Required

• PG :- - Not Required

• No of position :- ( 1 )

• Post :- 6th Apr 2021

Job : Sr. Embedded Software Engineer / AUTOSAR
Location: Auburn Hills - MI
Duration: 12+ Months
Looking for 8+ Yrs(H1B,GC,USC)


Description/Comment:
Sr. Embedded Software Engineer / AUTOSAR

Requirements:

Embedded C/C++, Matlab, Simulink, Stateflow, Altia, Qt, Kanzi, Visual Studio, Android Automotive, AUTOSAR, IBM Rhapsody

Preferred Skills:

1. Work experience in Automotive domain

2. Understanding of Automotive CAN, Diagnostic, Ethernet protocols

3. Work experience in Agile product development

Job Description:

1. Model based software developer will be responsible for modeling word based requirements using Matlab/Simulink or Stateflow and IBM Rhapsody for components such as Instrument Cluster, Body Control Module or Battery Management Systems.

2. Configure models as per AUTOSAR architecture and generate the code using autocode generation tools.

3. Perform the MIL (Model In Loop) and SIL (Software In Loop) testing using the requirements and developed model and report code coverage, MCDC etc.

4. Support the vehicle and HIL validation teams issue analysis, debugging and resolution.

5. Working knowledge with dSpace HIL testing, Vector tools, rapid prototype controllers, unit-level test tools such as LDRA or RTRT.

6. Working knowledge of battery motoring hardware and software, high voltage system control and diagnostics, embedded BMS, Instrument Cluster or Body control software implementation

Product Design:

'1) Co Author the Design for a specific module / functionality.
2) Choose design methods that facilitates:

a) abstraction modularity and other features which control complexity.
b) the expression of:

1) functionality.
2) information flow between elements.
3) sequencing and time related information.
4) timing constraints.
5) concurrency and synchronized access to shared resources.
6) data structures and their properties.
7) design assumptions and their dependencies.
8) exception handling.
9) design assumptions (pre conditions post conditions invariants).
10) comments.
c) ability to represent several views of the design including structural and behavioural views.
d) comprehension by developers and others who need to understand the design.
e) verification and validation.
c Understand interdependencies of the various components in work packages that are being developed.
d) Work with architects to understand the architecture of the application high level approaches and ensure that the design is in line with overall direction.
conduct peer review as required.
e) Organize design review sessions with various stakeholders to validate design is as per requirements.