Developing Clearbot an automation robot designed to automate a 30 day tissue clearing protocol currently done by lab technicians Developed on the STM32 in C++ on a ARM Cortex M7 processor, chiefly with SPI and USART communication to TMC boards.

• Creating appropriate technical documentation. This ranges from the technical for the network engineers to the high level for the Policy office and Audit office workers to bring the network team to provide new engineers the resource to setup network configuration for Walmart’s network infrastructure. • Coordinate and lead meetings with Engineering teams, Policy office, and Audit office, to fulfill the plethora of requirements their respective office needs to agree upon similar protocol across all Walmart network infrastructure.

• Individual project as an undergraduate, which I designed and constructed a device that stimulated three evoked potentials somatosensory (shocking), visual, and auditory to construct an EEG map of the brain’s response which abnormalities to waveforms can be used to localize brain lesions or hemorrhages in 10 minutes.• Created proposals for grants to fund the project, and wrote an IRB for human testing. • Created a brain diagnosis device using C# on a microcontroller (Netduino), tested and functional by August 2013• Tested and analyzed EEG data from my device using R, Matlab used to detect brain abnormalities such as lesions and hemorrhages.

• Took Avamar customer data to create predictive analytics for automated customer quality care dubbed “BIG DATA” eg. Notifications on future data usage using the Monte Carlo method to determine when the customer needs to buy more space. (Used PostgreSQL)

• Made a system testing data analysis environment by using Perl to parse though system test data logs, SQL lite to provide a backend database for the parsed information, and an internal server using Apache to present failures at each level: machine, OS, program, and sub sections of programs to engineers who just did a system test on their update to isolate where the failure occurred. • Previously methods of resolving system test failures required email strings from the head of each department who manually scrolled though test data logs resolving problems in 5 days or never and the engineer eventually gave up on implementing new code into the system reducing functionality on new projects for the company. • Presented demos to the QA department for using the tool. When implemented, the time to resolve a failure reduced from 5 days to within a day. • Created a wiki on the webserver with all the documentation on use of the website, and architecture of the server and code, so others may improve or update the code after my internship.