Systems Engineer Resume Tempe, AZ - Hire IT People

TECHNICAL SKILLS

PROFESSIONAL EXPERIENCE

Confidential

Systems Engineer

Responsibilities:

Created test case and participated in reviews of test cases. Reviewed and wrote test procedures for Safety of Flight testing.
Designed architecture for testing environment for teh automated test equipment (ATE) in TestStade, which included outputting reports for teh customer.
Created support VIs for teh supporting teh tests that were run on teh ATE using TestStand.
Updated System Development Plan and System Test Plan for release.
Created Requirements Verification Test Matrix (RVTM) view in DOORS by writing DXL scripts.

Confidential, Tempe, AZ

Test Engineer

Responsibilities:

Created Test Applications in Test Stand to test Medical Devices.
Created support drivers to communicate with devices in LabView
Lead test engineer for teh Hybrid Cardiac Assist System (HCAS)which is to upgrade teh current manufacturing software to teh Final Functional - Titan System Tester.
All projects are using TestStand for teh Final Functional Tester.
Analyzed data from runs on teh final functional tester to determine whether it was ready to release to manufacturing.

Confidential, Tempe, AZ

Lead Engineer

Responsibilities:

Software Verification testing for APU.
Created test cases from DOORS requirements assigned. From teh test cases, created test procedures that would be run through a Script Generation Tool (SGT created in Python) to create teh test script that would be used to run in teh test environment.
Led informal reviews of test procedures and test case to provide feedback to developers and to ensure all processes were being followed.
Created scripts in testing environment to automate testing results (vb.net)
Help with maintenance and upgrades to teh SGT (Python)
Created multiple Excel macros to help in reporting of status and help developers' complete work.
Worked on A429 communication verification on teh Simulation and Bench environments.

Confidential, Burnsville, MN

Staff Software Engineer

Responsibilities:

Lead Integration Engineer for teh Smart Display Unit (SDU) and Aircraft Interface Device (AID) for teh Cockpit Data Management (CDM) system
Presented for PDR and CDR reviews.
Created print server in python to communicate with AID to use teh 429 bus to print on a Miltope Printer using Confidential 744 communication.
Created a new binary protocol for Confidential 429 and Confidential 717 to replace teh STAP protocol currently used as an interface between client applications and aircraft data. Teh binary protocol improved teh network performance by eliminating teh STAP strings passed across teh TCP/IP network.
Streamlined software for teh real time embedded system on teh AID and SDU to increase performance.
Created an automated unit test environment for developers to use for continuous checkout of software while implementing change requests.
Responsible for lab equipment, setup, and remote availability for our testing group in India.
Created requirements in DOORS for teh SDU and AID
Final integration of software and timing analysis of system
Created testing scripts in Python to help verify teh IO process

Field Test Engineer

Confidential, Yuma, AZ

Provided on-site field support at teh Yuma Proving Grounds to assess various automotive performance and durability characteristics, such as reliability and maintainability and other test specific characteristics
Stryker Variants and their sub-components by applying mechanical and electronic engineering principals applicable to teh test and evaluation of these vehicles.
Served as a technical specialist to locate utilized components through DMIS, Team Center, blueprint, drawings, and technical manuals
Provided daily reports, engineering changes, data gathering, and submitting failed parts for analysis

Confidential, Yuma, AZ

Project Engineer

Responsibilities:

Mobility Site Lead in charge of planning, testing and instrumentation of teh Future Combat System Non-Line of Site Cannon prototype.
Implemented and planned software and hardware upgrades.
Lead of configuration control for writing and tracking issues for teh hardware or software on teh prototype
Lead for data analysis of data captured from teh system software and controls software

Confidential, Yuma, AZ

Senior Software Engineer

Responsibilities:

Software development lead for teh Future Combat Systems Non-Line of Sight Mortar.
Developed software in a fast paced environment to get a prototype out teh door within seven months
Managed team of software engineers with reporting EVMS (Earned Value Management System) weekly
Worked directly with controls engineer and verifying/creating software interfaces to teh hardware which was over 21 electric drives on teh mortar ammunition handling system
In charge of integration and configuration control of teh software that was delivered to teh Test and Integration group at teh remote site

Confidential, Yuma, AZ

Software Engineer

Responsibilities:

Member of teh ammunition control software group that worked with creating sequencing software for teh Future Combat Systems Non-Line of Sight Cannon (NLOS-C).
Moved to integration and completed final hardware integration of Software at Yuma Proving Ground, AZ.
Worked with teh systems group to define and write requirements for teh NLOS-C.
Lead teh change control process at teh remote test site and made decisions on what changes would be integrated into teh software build that was test firing at teh site.

Confidential, Minneapolis, MN

Associate Software Engineer

Responsibilities:

Responsible for software configuration for teh Common User Interface (CUI) group for teh Crusader program.
Developed in teh Translator sub system using ADA.