Cloud control plane, focusing on our multi cloud resource placement and scaling

Cloud Control Plane team

TL of API Infrastructure Team- Building a code generator to automate common backend API development tasks for internal systems. We read a configuration file and generate the schema and all Java code necessary to read from a database and return data via their API.- Advise on best practices and guidelines for internal teams to follow when building APIs.Using 20% time to help enable social features for a new Area 120 project (Google's startup incubator, http://area120.google.com).Google CloudPreviously held a R&D role to enable new workloads to run on GKE (Google Cloud's Kubernetes Engine).

Java developer for the Fusion Workforce Reputation Management application. Work directly with management and architects to design and implement new product features. Some of the key areas responsible for include: - Gathering data from social networks (Facebook, Linkedin, Twitter, etc) using their public REST APIs and formatting the data for analysis.- Algorithm to match social media profiles of the same users across different social media sources.- Web services layer to prepare and transfer data between the management and employee applications.

Software engineer on the Time Based Flow Management (TBFM) contract. TBFM is a software system used by FAA air traffic controllers that builds schedules of arrival for all aircraft landing at all major airports in the continental US. It also aids controllers in scheduling departures and handling outbound traffic in air traffic control centers.Worked as a software engineer in the C and C++ programming languages. Primary area of work was the Communications Manager (CM) CSCI. Handled multiple enhancements and maintenance of code in this area, as well as the system wide common code libraries that were shared among all processes. Main functional areas for CM include managing a system-wide run-time database, assignment of major data elements to aircraft, message passing, failure recovery, filling in message data, etc.Spent roughly a year on a small team evaluating the use of the Agile programming methodology and new tools (Git, JIRA, etc) to help support this process. Worked on making major areas of the code more dynamic to allow for user flexibility (modifiable vs fixed aircraft stream class assignments; ability to turn system scheduling fixes on and off dynamically; taking over some M&C based functionality for the GUIs so they can become decoupled from the existing M&C controller). Also did research into using web technologies (gSOAP) to facilitate passing data between the existing C and C++ code and a new web based Java GUI.

Primarily worked on the Traffic Management Advisor (TMA) contract for the FAA. This contract was later put up for rebid and awarded to Lockheed Martin under the TBFM contract base, so I transitioned to Lockheed to work TBFM at that point.8/2008 - 10/2010:I worked on the CM CSCI for TMA, working on major enhancements and bug fixes. Major enhancements included coupled scheduling, which gave the system an extra level of deconfliction (I.E. a scheduling point where no aircraft could be tied) which allowed the system to be accurate at far greater distances than before. Also developed a prototype for retrieving a new weather type from a 3rd party server, and formatting the XML data for display.10/2007 - 8/2008:Software engineer on the Departure Spacing Program (DSP). DSP was built for the FAA and is responsible for creating departure schedules for aircraft from all major airports in the New York area to reduce delay once the planes are airborne. Main task was to port the source code from Unix to Linux. Also worked on bug fixes as needed, and a major update to alert the air traffic controllers when a plane had an unexpected change in it's state.6/2005 - 10/2007:Worked as an adaptation developer for the TMA project for the FAA. Duties included configuring a set of input files that contained airport specific data. Was the primary adapter for the Salt Lake City airport, where I took the system from gathering requirements to becoming operational within an 18-month period, meeting all FAA deadlines. This position required a lot of travel and working closely with the sites to help them understand how to use the system. This close working relationship allowed me to adapt the system to best meet their very specific needs. Also assisted in adaptation development for the Las Vegas, Los Angeles, and Oakland airports.