We provide IT Staff Augmentation Services!

Embedded Engineer Resume

5.00/5 (Submit Your Rating)

San Antonio, TX

PROFESSIONAL SUMMARY:

  • 6 + Years of Experience in the field of Automotive Embedded software development Experienced in writing test plans for the Automotive Applications.
  • Strong experience in Automotive domain products - Instrument Cluster, Infotainment etc.
  • Experience in C/C++/STL/Design Patterns
  • Experience in writing the CAPL scripting to automate the test case based on CAN massage and Manual inputs.
  • Good understanding of Vehicle Function Testing.
  • Bench Level testing using Vector Canoe, LIN, CAPL Scripting, and UDS Protocol.
  • Participation in Design Reviews, DFMEA, BOM Cost Reduction (VAVE) Proposals.
  • Design FMEA for complete Engine management ECU software.
  • Working experience in QNX - IPC, Multithread coding, Resource Management etc
  • ISO Confidential (ITEM Definition) & Safety Test with (DVP)
  • Modelling & Simulation using MATLAB & Simulink, Stateflow.
  • Good experience in QNX, freeRTOS, VxWorks
  • Good Understanding of CAN, SPI, I2C, MOST
  • Experience with Configuration tool like Clear Case, CM Synergy & DOORS.
  • Well Experienced in Model Based Design and Testing with Simulink & State flow.
  • Experience of working under an Agile/Scrum methodology in self-organized teams.

TECHNICAL SKILLS:

C/C++, QNX, Clear Case, DOORS, CAN, KWP2000

C/C++, QNX, MOST, Perforce

PROFESSIONAL EXPERIENCE:

Confidential, San Antonio, TX

Embedded Engineer

Responsibilities:

  • Analysis of requirement for CAN, Non CAN based instrument panel cluster requirements with functionalities like vehicle/engine speed, DTE (Distance to empty), Fuel coaching, Fuel Economy, Cruise control, Auto-Manual transmission, Gear shift indication, diagnostics.
  • Development of modules DTE (Distance to empty), Fuel coaching, Fuel Economy, Cruise control, Auto-Manual transmission, Gear shift indication, diagnostics.
  • Ensure compliance with Auto SPICE process throughout STLC
  • Review of test artifacts, bugs observed for software delivery to client
  • Mentor junior colleagues and knowledge transfer

Environment: C/C++, QNX, Clear Case, DOORS, CAN, KWP2000

Confidential, Portland, OR

Embedded Engineer

Responsibilities:

  • Module lead for Confidential application in Confidential Infotainment.
  • The tasks are preparation of test plan & test procedures
  • Designed and developed Confidential & USB Feature
  • Implemented IPC communication mechanism using MOST protocol
  • Developed Confidential IOT test cases and Matrix (Performance cases, Stress, SRS/SRD based cases and Scenario based cases).
  • Supported for IOT testing on different Confidential devices (around 18 devices).
  • Providing technical guidance for team in execution of test procedures
  • Preparation of error list and preparation of summary report.
  • Creating Sanity and Functional level test cases for the project
  • BT testing (Bluetooth).
Environment: C/C++, QNX, MOST, Perforce

Confidential

Senior Embedded Engineer

Responsibilities:

  • Involved in the analysis of business requirements, system specifications for ABS modules
  • Developed ABS modules
  • Handling branch issues and providing new branches for Development
  • Following EDR model in terms of maintaining branches
  • Performing builds based on Release Management requirement
  • Involved in unit testing, integration testing, system testing, acceptance testing, Ad-Hoc testing, Regression testing, Black box, White box testing.
  • Design and creation of new build process steps and documenting those processes for future reference
  • Performed Basic sanity for all the release build images Created complete build & release process from delivery point of view

Confidential

Embedded Engineer

Responsibilities:

  • Point of contact for any kind of MOST 25 and Most 150 related Network Queries
  • Automation Test Planning, Design, Development, Maintenance
  • Software Test Automation Framework Development ( Confidential ). This involves test result reporting, defining reusable procedures, hardware configuration, event handling, remotely controlling power supplies etc.
  • Test Scripting using 4CS tool from GADV, MOST/CAN/CAPL automation using Vector CANoe Integration Automation Testing on QNX/MOCCA platform
  • Test Plan development for upcoming projects
  • Work on Project Architecture and Use case Development for MOST domain
  • Manual Test Case and Automation Test Case Execution, Ticket Verification, Test reporting
  • Interaction with German peers on regular basis regarding project status, proceedings and future goals

Confidential

Embedded Engineer

Responsibilities:

  • Tracking and sending status report to client daily and weekly.
  • Executing tests, generating test reports, and following-up on issues found during testing.
  • Contributed to platform validation and Performance test execution on weekly build.
  • Analyzing logs to find the root cause of the problem.
  • Design and develop testing procedures to ensure that software products are within quality management standards; update and modify existing test procedures as necessary
  • Responsible for performing and Assigning User Acceptance Test plans for Rogers Operator Applications like urMusic, Rogers live and Rogers Account
  • Call Performance, FOTA, Smart Dock (HDMI/USB/Audio Out) and Roger’s testing.
  • IOT testing between flex device and other Bluetooth products

Confidential

Embedded Engineer

Responsibility:

  • The driver makes provision to cyclic measure a configurable number of analog-voltages and scale them to a resolution.
  • All AD-channels are successively converted automatically by a mechanism featured by the microcontroller (Auto Scan Single Conversion).
  • Buffers converted values by using DMA.
  • Supports for synchronous conversion in which case running scan of the channels has to be stopped, the requested A/D channel has to be measured, the interrupted scan of the channels has to be continued.
  • Raising bugs on issues found during testing and follow up with developers in resolving the issues by providing logs and pin-pointing use cases that help reproduce the issue.
  • Log analysis and debugging.
  • Identifying test conditions and writing test cases for the new features and targets.

We'd love your feedback!