While in this role I wrote and tested audio drivers to be used on a next-generation surgical device running QNX. Special care was paid to its time-critical requirements as the sounds played were part of the user interface- these sounds will give surgeons cues when operating on a patient so that they can focus on the surgery without looking away.I wrote code to support a variety of features- supporting state-based functionality, hardware-driven cues, hardware device recognition, disabling touch feedback on demand, and regularly resolving defects as needed. In order to test the device, I helped to champion a hardware simulator which mitigated supply-chain difficulties and pushed testing and defect resolution time frames forward. I was then given a devops role, specifically to aid software stability. While integrated software builds were being tested and code churn was at its' heaviest, I would load integrated, automated software builds on hardware from a central build repository. My responsibilities were to verify that the system as a whole would boot to a user-ready state, that all subsystems would load without failure, and that basic user interactions would work without having to interfere with or tweak the system. As issues arose I would document them and suggest/implement a solution if one was present.Finally, I was responsible for developing and updating the technical requirement diagrams for medical device certification. Using MagicDraw, I would create flowcharts detailing the code's functionality and link requirements from the JIRA database to show how compliance was being met. This included diagrams detailing the subsystem interfaces implemented in DDS, FPGA interface calls, and file I/O functions.In other contracts I have written software for processing data from GPS units, as well as developed software requirements for aviation-related projects.

I started as an engineer on the GAC 2500, spearheaded a retrofit of a web-based driver onto a WindowsCE device, as well as tested and fixed bugs as they were found on the GAC 2500. This product was then sunset and released.I then worked to spearhead a new platform to become the company standard - an embedded Linux SOM running a mono application. This helped to significantly speed up development and increase our flexibility. I then took charge of the software development for the Application side of the GAC 2700 and in time managed a contractor in order to drive work to completion. When other developers would fall behind I would pick up their work in order to keep the project moving forward.I was then asked to move to leading a team of developers for the company's new platform in a software architect style role. The desire is that I will be one of the driving factors to create or update several embedded hardware products per year. In 6 months I led a team to develop the next generation of Certifier FA+ product while all were remote. During this time I took on the responsibilities of Principal Software Engineer, Technical Lead, and Scrummaster. At the end of that period, the product was demonstrated to the Product Owner who was able to take a development unit on a sales call to show off what will be the effective final product.

I worked closely with the SME of the Software Engineering department, and in a short period of time I created four drivers and simulator pairs. As part of the development process, the drivers and simulators tested and verified a new distributed process communication architecture across three of the pairs. As a piece of independent work I researched the in-house testing system, built up a test suite for each of my drivers, experimented in how to combine them with legacy test suites. Finally, I looked into the feasibility of integrating these with our build systems. I took on the role of point engineer on the software/hardware integration project for the 9/12 research project- on this system I have tested physical sensors (GPS, INS, and others) with a stripped down read-only linux system and verified data integrity, debugged startup issues, and wrote a procedure to create a manufacturing-ready Debian stack.I have taken point on documenting the starting process for engineers, updating defunct information in our wiki, and have streamlined the documented process on how to create the test system for the software/hardware integration project.

During my time here I worked on a long running software program in a CMMI 5 environment. I quickly acclimated to the legacy project and became the SME on several subsystems. Working closely with team leads, systems team members, and SQA team members, I completed several deadlines ahead of schedule.Myself and two other new hires spent time inside and outside of the workplace analyzing the processes in use for software engineers. This culminated in the creation of a knowledge-sharing wiki for the software department; it which was put into production and used as an example of risk reduction and a major source of cost-savings in tribal knowledge transfer.

I was a developer of tests for an internal software product to ensure compatibility and reliability. I created and ran a routine of 240 unique tests to ensure the stability of the manufacturing software that configured Starkey's hearing aids. Additionally, I worked on installers and build management in Visual Studio, starting in XAML and moving to TFS 2015. Finally, I created a tool to bridge the gap between developers and testers, allowing the testers to upload and download virtual copies of hearing aids with an easy to user interface.

Worked with C in LabWindows to provide a user interface for the systems that Hysitron develops. I was lead developer on two product lines and been branching out into other areas as well. During my time here I investigated and evaluated new technologies including replacement optics for systems, evaluating other design schemes for controlling and interfacing with the instruments, and new IDEs for future use.

I worked with art and math teams in order to create video games for distribution to casinos the world over. I completed one game in a self-driven environment in C++ and using the Ogre graphics library.

Maintained a large network of servers, with an emphasis on self-education. Did customer support for a variety of server side email and connectivity issues.

Created mechanical and electrical diagrams for cables using GIMP, and followed up with overseas manufacturers.Did extensive bidding research involving over 50 different vendors in order to procure a casing for the product that was to be shipped within the year.

Kept surveillance over a 800+ piece art museum resulting in no incidents.Fully trained as a docent. Led multiple tours throughout the galleries.