• [email protected]
• www.linkedin.com/in/mike-castle-nexus
• San Francisco Bay Area
• 347-829-5432

A seasoned release engineer with over 20 years of experience in software engineering, systems administration, and release engineering, specializing in building tools, managing releases, and optimizing engineering productivity. Most recently served at Google, where efforts included overhauling an internal AI SDK release process for mobile devices and contributing to the improvement of development workflows to enhance efficiency.

Expertise spans problem solving, technical communication, and code review. Dedicated to creating efficient, consistent systems that reduce manual effort and improve user experience. My background includes developing bespoke continuous integration systems, administering version management tools, and supporting large-scale engineering teams with reliable solutions.

• Improved release processes
  • Owned and overhauled existing release process for an internal AI SDK for mobile devices.
  • Built, tested and deployed services on a bi-weekly, weekly, and daily.
  • Developed new processes for analyzing dependencies and specifying release branches.
  • Collaborated with engineers to develop and document best practices for releases, including QA cycles and deployment processes.
  • Migrated services to then new containers (Borg).
  • Scaled from 2 to 1,000+ projects.
• Built bespoke continuous integration [CI] system (Tobam)
  • Reduced mean time to discovery [MTTD] of a breaking change from two weeks to two hours.
  • Runs at various frequencies with multiple configurations.
  • Performs culprit finding and optionally provide rollbacks.
  • Works around bugs in other parts of the tech stack.
  • Handles flaky tests and transient failures.
• Owned CI/CD process and software for low level libraries (Components)
  • Stabilized the process from high-touch to hands-off.
  • Reduced MTTD of breaking changes from 12 hours to two hours.
• Co-owner of a Python based wrapper for the in-house SCM stack
  • Provides a well-lit path for working with the SCM stack.
  • Library using in house RPC mechanisms.
  • Used by most Python based build tools.
• Owned and turned down legacy release service (BYOBuild)
  • Assisted teams in migrating to replacement release service.
  • Created dashboards for tracking progress.
• Perforce administration team
  • Analyze performance for local and remote users and improve processes to reduce server load and improve the user experience.
  • Assessed bugs and performance issues in Perforce software and reported issues back to Perforce.
  • Owned command line tool (g4) and associate Python library (p4lib) that implemented business logic on top of Perforce (e.g. code reviews, testing, workspace management).
  • Trained new engineers.

Missouri University of Science and Technology
Bachelor of Science, Computer Science

• Userscripts, often called Greasemonkey scripts, are a form of augmented browsing.

• A small Python library for handling mundane things like subcommands, flags, and logging.

• This is a tool for working with Ingress data such as maintaining bookmarks and planning adventures.