120 day detail as CSO & SMA Lead for the Solar Electric Project, including the AEPS and PDP subprojects

Working on communications for Unmanned Aircraft Systems (UAS) in the National Air Space (NAS) project at the NASA Glenn Research Center

Working in the areas of flight simulation and training.Software IPT lead on F-35 Landing Gear Maintenance Trainer.- responsible for requirements, design, budget and schedule estimation- led team to a successful Preliminary Design Review (PDR)- led team in preparing detailed designArchitect and lead for an in-house software tool for tracking trainer parts fidelity- written in C#/.Net, using a MySQL backend database with support for local SQLite database as wellArchitect and lead for an in-house software tool for handling DISA compliant STIG scan results, - written in C#/.Net, using a MySQL backend database- allowed Information Assurance Engineers to record scan results and compare scans across multiple changes to the system to ensure compliance

Airborne IRCM, Systems/Software Integrated Product Team lead.High Altitude Airship, SW engineer on development of flight/ground software for demonstration airship. Flight engineer during demonstration flight.Graduate of the Advanced Technical Leadership Program (ATLP)Graduate of the Lead Software Engineer Development/Qualification Program (LSWE DQP)

Analysis of GPS/INS for an autonomous navigation system

Worked as a principal/lead software engineer on several microgravity science experiments, including fluid dynamics investigations, thermal energy management and acceleration measurement systems.Participated in 8 Space Shuttle, 1 Space Station, and 2 sounding rocket missions; 3 drop tower operations and 78 reduced gravity aircraft (KC-135/DC-9) sorties. As part of the aircraft work, obtained flight certification and amassed over 185 flight hours with over 3500 (mostly stomach calm) parabolas.Was involved in aspects of the experiments beyond the software role. These ranged from assisting in the requirements definition for the electrical and mechanical components to defining and performing the actual operation of the experiment.Worked closely with the customer, usually the principal investigator, to identify operational and procedural requirements.

I helped evaluate the requirements of customers looking to Logisync for power line communication solutions. I helped distill customer statements and use cases into actionable requirements and then advised about the software needs of the project.

I worked as the lead (often the only) software engineer on a series of microgravity science experiments. These experiments operated across NASA's family of microgravity platforms ranging from drop towers to parabolic aircraft thru the Space Shuttle and Space Station. I designed, implemented, tested and often operated the software that controlled the data acquisition and control of the experiment.

For my first four years I acted as the liaison between the Structures Division and the Computer Division. I helped communicate the computer needs of the Structures Division to the folks running the mainframe and supercomputers. As PC's and Unix Workstations became more commonplace I became part systems administrator, part developer, and part evangelist.I then changed positions and went to work in the Space Experiments Division, specifically working on flight and ground support software for a Thermal Energy Storage experiment. I wrote code and conducted tests leading up to the integration and flight of the experiment on the Space Shuttle.