We provide IT Staff Augmentation Services!

Advanced Software Engineer In Test Resume

2.00/5 (Submit Your Rating)

Chicago, IL

SUMMARY:

  • Skilled software engineer with over ten years of experience with software engineering, verification and validation, quality assurance, and test automation skills in waterfall and agile environments.
  • Excels and quickly learns new technologies and programming languages and skilled at finding the challenging defects.

TECHNICAL EXPERIENCE:

Software Languages: C/C++/C#, Java, Javascript, SQL, XPath/XML, Robot Framework

Operating Languages: Windows 98 - Win10, Linux, MS-DOS

Applications/Tools: MS Office Suite, TortoiseCVS, Selenium, Eclipse, Jira, Git, Burp/Fiddler

WORK EXPERIENCE:

Confidential

Advanced Software Engineer in Test, Chicago, IL

Responsibilities:

  • Wrote tests in Robot Framework and C#
  • Tracked and logged bugs using Jira and other in-house programs
  • Created and updated QA tests
  • Implemented changes and added new methods to existing framework
  • Helped create a new testing framework
  • Taught new employees how to use Robot Framework
  • Helped lead project to start converting Robot tests to C# integration tests
  • Wrote and updated Javascript and C# code to help developers
  • Two-time Hackathon participant
  • Relativity Certified Admin
  • Helped implement and test a new document viewer
  • Helped implement and test conversion to using Microsoft Service Bus
  • Helped organize test cases for different features
  • Helped lead Scrum activities when Scrum Master was not available
  • Gave demos of our work at the end of sprints
  • Gathered metrics for the Manager

Confidential

QA Automation Engineer, Deerfield, IL

Responsibilities:

  • Automated over 600 tests
  • Tracked and logged bugs using Jira
  • Created and updated QA tests
  • Updated Java code
  • Implemented changes to existing framework

Confidential

Software Engineer; Alpharetta, GA

Responsibilities:

  • Verified hardware circuits
  • Ran test scripts on the CoPilot 429 data analyzer
  • Edited current test procedures for changes to requirements.
  • Used Merant Version Manager to keep track of changes to test procedures.
  • Peer reviewed existing procedures
  • Updated procedures for issues found in other peer reviews. Placed updated changes into DOORS and placed them into version control by using Subversion.
  • Participated in a formal qualification testing on two different test configurations of the Display Processor (DP) and System Processor (SP) High and Low Level Requirements (HLRs and LLRs).
  • Updated the Software Verification Cases and Procedures ( Confidential ) document with the changes to the existing procedures.
  • Kept Review Accomplishment Reports (RARs) for the changes to different documents and procedures.
  • Developed applications in C++
  • Peer reviewed existing procedures
  • Updated procedures for issues found in other peer reviews. Placed updated changes into DOORS and placed them into version control by using Subversion.
  • Kept Review Accomplishment Reports (RARs) for the changes to different documents and procedures.
  • Finished the qualification effort in a reduced time table

Confidential

Software Engineer; Rockford, IL

Responsibilities:

  • Performed requirements testing activities at customer site. Specifically
  • Wrote procedures to verify the requirements listed in the SWRD for the Confidential and the Confidential . The code was written to RTCA DO-178B Level A standards.
  • Used a simulator in a Linux environment to run my tests
  • Placed the finished product into DOORS for code review.

Confidential

Associate Programmer, Rockford, IL and Endicott, NY

Responsibilities:

  • Performed software verification and validation activities at customer site. Specifically:
  • Wrote code in Confidential and C/C++ to verify the performance of each type of input on four different test stands.
  • With the data collected from the qualification testing, designed various Aerospace Engineering Reports (AER) and Version Description Documents (VDD). The code was written to RTCA DO-178B standards.
  • Created and maintained a Concurrent Versions System ( Confidential ) repository for all test code and applications that were used for the qualification effort.
  • Designed requirements per Software Requirements Document and Software Design Document in accordance to RTCA DO-178B Level B standards
  • Used CANalyzer to view CAN traffic
  • Performed flight code verification activities at the satellite office. Specifically:
  • Translated requirements into code without optimizing it and tested it alongside the flight code sent by the customer. The code was written to RTCA DO-178B Level A standards.
  • Used MKS Source Integrity system to submit files once testing had been complete

We'd love your feedback!