Run the Developer Platform Engineering team focusing on GCP Serverless technologies and the Anthos hybrid-cloud development platform. Also do customer engagements with regards to software development life cycles, engineering culture, and have a strong bent towards DevOps methodologies. Cross functional team builder. DEI advocate and speaker. Google representative for Technical Oversight Committee, Continuous Delivery Foundation.

Oversee both the Systems Engineering team responsible for the production environments of our virtual reality platforms, as well as the Build Engineering team responsible for the developer environment and deployment pipelines. Tasks include project and vendor management, employee growth and mentoring, cross-company and third-party collaborations and guidance on issues around performance, security, and strategic planning around production costs.

Oversaw creation of new lighweight dev process model from monolithic environment via Subversion and Bamboo to self-contained team environments using Git and Jenkins. Helped introduce Chef as a configuration management scheme and oversaw early adoption efforts for cloud deployments in AWS and OpenStack.Moderator of Lithium Brain Trust, fostering cross-functional discussions between all engineering technical leadership.Member of Patent and Open Source Committee.Moderator of Lithium's Women in Engineering Initiative.

Introduced continuous integration to Pixar Studio Tools department. Created scalable build farm and initial custom software deployment system for internal proprietary software using Perl and MySQL. Assumed role of Perforce administrator, developed initial source auto-integration scripts to handle automated migration of fixes from older versions to newer versions of software. Became Apache admin and MySQL DBA for Studio Tools infrastructure servers. For new internal R&D project, was part of 2 person team that designed and implemented new product config management system using C++, Python and sqlite3 to store related collections of proprietary and thirdparty software packages in modular ways as well as recording metadata about those packages, customizable by department. (sqlite3 was eventually replaced with Oracle).Also for new internal R&D project, wrote new and improved build deployment system in Python and MySQL.Wrote small custom data mining and visualization tools (Python and Confluence API) to represent internal code churns, emergency build requests, and other sundry data points to help build an ongoing picture of the health of the software development process at the studio. Have overseen the expansion of build engineering support and advocacy for development best practices into other areas of the studio, including feature production teams and franchise projects. Act as primary contact for Studio Tools R&D to the Systems department, helping coordinate advance testing of new hardware and driver upgrades.Over the course of time at Pixar, have managed between one and eight people.

Bugzilla Project Owner: 2000 - 2002 - helped develop initial public installation mechanism and installed first non-Netscape instance - took over ongoing maintenance as sole official contributor. - actively engaged in growing community of interested contributors and built up a team that included new developers, testers, and doc writers. As this initial team was from North America, Europe and Australia, used IRC as the primary mode of communication - with a team grown to around a dozen contributors, successfully handed off ownership to senior developerBonsai Project Owner: 1999 - 2006 - limited work, primarily focused on writing basic documentation and some installation guidelines for public installs. - provided some basic system administration for bonsai.mozilla.org, particularly for security issues with regards to Perl CGI interface. - given the creation of new, better-supported commercial web interfaces to CVS such as Fisheye, development largely ceased as far as external customers

Was first build engineer hired at while company still a very young startup. Was responsible for proposing and creating initial engineering infrastructure before active code development began.Was then responsible for hiring and managing the build/release team, though initially continued as the primary Windows build engineer. Primary tasks included: * Development support (both build systems like make and ant, and custom developer tools) * Continuous Integration system (Tinderbox) * SCM administration for CVS repository * installers for Windows, using InstallSHIELD * oversaw development of installers for AIX and Solaris operating systemsNotable projects: * With one other team member, designed CVS "code cascade" that allowed for automatic code propagation between branches. This allowed developers to fix a bug in a given version and have it automatically included in all later product revisions. * Working with Blue Martini professional services department (who were supporting many startup customers with limited developer resources), we invented a mechanism to image and deploy plug and play Linux servers pre-installed with a CVS repository, Bonsai and Bugzilla installations.Promoted to Director of the Engineering InfrastructureTook over management of group including Build, Performance, and Platform Porting teams. Oversaw adding support of Blue Martini product from being solely on Oracle/Weblogic to also include IBM's DB2/WebSphere platform. As part of the IBM port, worked extensively with performance team to conduct extensive load testing and performance benchmarking using LoadRunner and related custom tools.

Was the first build engineer hired for the Client Engineering team, and initially provided build support and installer development for the Windows platform for Netscape Navigator. Eventually took over management of team for all platforms (at our peak the team had 13 engineers and builds on over 40 software platforms). Primary accomplishments for the team include developing systems to make development infrastructure as cross-platform as possible to reduce overhead given the high number of supported operating systems, help establish best practices for developers to follow also with regards to cross-platform needs, and write the installers for all browser distributions.As part of our team's internal efforts to improve the development environment, we participated in the development and maintenance of infrastructure tools now released via Mozilla.org:* Tinderbox: Web-based continuous integration system* Bonsai: Web-based interface to CVS repository* Bugzilla: Web-based bugtracking system

Worked on Release Engineering team supporting the Borland Languages division, focusing on the C++ and Delphi development kits. Was responsible for Windows and OS/2 installers for C++ product, using Borland-proprietary BOOGIE install engine.Imaged a whole lot of floppy disks. Was extremely thankful for the introduction of software CDs.